PROJECT TOOLS · FOR ENGINEERS & ARCHITECTS
Stop carrying last project’s spec — and its buried conflicts — into the next one. Start from a shared library, author narrative text and structured datasheets in one editor, and finish with feedback your team can actually resolve — line by line, tracked across every project.
One editor for text & datasheets · Comments on every requirement
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, modified a little at a time. With no clear line between narrative and project-specific configuration, conflicts accumulate — and no single engineer ever reads every line again.
Requirements live in narrative documents that no two readers, bidders, or subs interpret the same way.
Vendor and field feedback arrives as PDF markup and email — impossible to resolve line by line, and gone by the next project.
The knowledge is there. The format loses it.
PART 2 — PRODUCTS
2.01
Anyone on a project can comment on the exact requirement they’re working from, tagged Comply, Deviation, Exception, or Comment. Every response is grouped by element in one review queue — and aggregated across your firm’s projects, so a recurring fix lands in your library instead of repeating on the next job.
2.02
Browse the SynC wiki for community-vetted standards, or import your firm’s own standards into a private company library — and pull either into a project draft in one click. Customizations stay scoped to the project, so your master standards stay pristine.
Browse the wiki→2.03
A markdown editor with live preview and keyboard shortcuts. The same syntax carries narrative spec text and fill-in-the-blank datasheet fields — the Word doc and the Excel sheet can stay in the recycle bin.
2.04
Narrative and configuration are different things: the switchboard is per UL 891 on every job, but whether the bus is tin- or silver-plated changes project to project. SynC keeps the narrative in the standard and the choices on the datasheet — reviewers see a clean numbered spec, selectors see only the fields to fill.
2.05
Publish a project revision and every stakeholder is reading the same document. Each revision carries a content fingerprint, so anyone can confirm the version in front of them matches what was published.
2.06
Every revision — of a datasheet, a standard, or the whole project — diffs against any other: what changed, and why, line by line. No manual change logs, and no comparing two PDFs by eye to reconstruct what happened.
2.07
When a parent standard publishes a new revision, SynC tells you which project datasheets upgrade cleanly and which need attention. Your filled-in values are preserved; only the spec text changes.
2.08
Ask the AI to research a requirement, explain what a clause means for your project, or summarize what changed between two revisions — every answer cites the exact element it came from. It operates with the exact access your account has, never more.
2.09
A spec that says “as indicated on the drawings” is a promise — and the classic coordination failure is that the drawings never deliver. Every deferred requirement and datasheet field rolls up to one project coordination checklist, so each one gets resolved before the issue date instead of becoming a construction-phase RFI.
PART 3 — EXECUTION
STEP 01
Pull a community or company standard into a project draft instead of starting from a blank page.
STEP 02
Set datasheet values and edit clauses where this job differs. Changes are tracked from the first keystroke.
STEP 03
Issue a fingerprinted revision, then resolve line-by-line responses that roll up across your firm’s projects.
OPEN LIBRARY
UL, ANSI, IEEE, and NEMA tell you the range of what’s acceptable. They don’t tell you the specific configuration your particular project requires. SynC standards fill that gap — and the way they get good is engineers like you writing down how the codes actually get applied in practice. No committee to join, no gatekeeper to satisfy.
Adopted SynC standards are released under Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0). Your name — or pseudonym, your choice — stays on every adopted revision your contribution appears in: a specific, verifiable, resume-worthy line the moment you make it.
PART 4 — ON THE ROADMAP
IN PROGRESS
Aggregated pricing, lead-time, and buildability signals from vendors and manufacturers, surfaced inline as you make selections. The vendor-comment plumbing ships today; the aggregation layer is next.
PLANNED
When a parent standard you’ve customized is revised, see a side-by-side redline with automatic carryover for non-conflicting changes and a step-by-step review for the rest.
PLANNED
Direct importers for the standards libraries and guideform specifications your firm already works from, so moving onto SynC never means starting from a blank page.
PLANNED
Ask the AI questions across the entire library you have access to — not just the standard you’re looking at — with citations back to the source element.
Sign up free, or get in touch if you’d like a walkthrough for your firm.