PROJECT TOOLS · FOR ENGINEERS & ARCHITECTS
Stop carrying last project’s spec, and its buried conflicts, into the next one. Keep your standards in one library, set each job’s values on a datasheet, and issue a sealed revision as access. When the exceptions come back, they come back on the clause.
Keep your own standards · Exceptions land on the clause
STANDARD
Indoor 208V Panels
REV
3
STATUS
✓ VERIFIED
Panelboards shall be listed to UL 67 and service entrance rated where required.
DATASHEET
Room 108 is a wash-down area on the mechanical drawings. Recommend Type 4X for the two panels there.
PART 1 — GENERAL
Every project’s spec starts from the last one, edited a little at a time. With no standard underneath, every fix is a one-off, and the same conflicts ship again on the next job.
Requirements live in prose that no two readers, bidders, or subs read the same way. A transmitter’s range written in six places is six chances to disagree.
Vendor and field feedback arrives as PDF markup and email. Nothing records it against the requirement, so nothing gets resolved, and the same lesson is learned again next time.
The knowledge is there. The format loses it.
PART 2 — PRODUCTS
2.01
Keep your office master in a private company library and adopt from it on every job. Adopt from the open library where it fits. Customizations stay in the project, so the master stays clean. Converting your existing library is work we do with you.
Browse the wiki→2.02
The switchboard is per UL 891 on every job. Whether the bus is tin- or silver-plated changes per project. The narrative stays in the standard and the choices go on the datasheet, so reviewers read a clean numbered spec and selectors see only the fields to fill.
2.03
Mark a requirement as deferred to the drawings and it goes on the project’s coordination checklist, with every datasheet field you left open. Work the list down before the issue date instead of finding out by RFI.
2.04
Publish and the revision is sealed with a fingerprint. Compare any two revisions of a datasheet, a standard, or the whole project, line by line. When a standard you adopted is revised, SynC shows which datasheets upgrade cleanly and keeps your values. When one turns out to be wrong, the correction reaches every project that adopted it.
2.05
Anyone you issue to can respond on the exact requirement: Comply, Deviation, Exception, or N/A. Responses come back up the share chain grouped by element, so you resolve them in one queue instead of decoding a marked-up PDF.
2.06
Ask the AI what a clause means for this job or what changed between two revisions. It answers from the published record with citations, and it sees exactly what your account sees. It can propose an edit; you approve it or you don’t.
PART 3 — EXECUTION
STEP 01
Pull a company or open standard into a project draft instead of a blank page.
STEP 02
Fill this job’s values and edit clauses only where it differs. Mark what the drawings still owe.
STEP 03
Publish a sealed revision and issue it as access. Responses come back on the clause, in one queue.
OPEN LIBRARY
UL, ANSI, IEEE, and NEMA tell you the range of what is acceptable. They don’t tell you the configuration your project needs. SynC standards fill that gap, and they get better when engineers write down how the codes are applied in practice.
Adopted SynC standards are released under Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0). Your name, or a pseudonym if you prefer, stays on every adopted revision your contribution appears in.
PART 4 — ON THE ROADMAP
PLANNED
When a standard you customized is revised, a side-by-side redline with carry-over for the changes that don’t conflict, and a review for the rest.
PLANNED
Pricing and lead-time signals from vendor responses, shown while you make selections.
Sign up free, or book twenty-five minutes and we’ll walk through one section of your own master with you.