PROJECT TOOLS · FOR CONTRACTORS
Bid against the actual, live spec — not a stack of PDFs. Respond with structured comments the owner can act on, bring your subs into the same revision, and see exactly what every addendum changed.
Locked to a published revision · Element-by-element changelog
COMPARE
Building 400
CHANGES
3
ISSUED FOR BID → ADDENDUM 1
35 kA 65 kA
Type 2 SPD shall be integral to the panelboard.
Feed-through lugs shall be provided where indicated.
PART 1 — GENERAL
The spec arrives as a stack of forwarded PDFs that may already be two revisions out of date before you open them.
When an addendum drops, finding the three changes that matter means re-reading a thousand pages.
When you flag a problem with a requirement, it goes back as a marked-up PDF or an email — easy for the design team to miss, and with no record you can point to when it matters later.
You shouldn’t have to guess which version you’re bidding.
PART 2 — PRODUCTS
2.01
Owners and engineers send a share link with the role they want you to have. Click, accept, and you’re reading the live spec — even if you don’t have a SynC account yet; we set one up when you accept.
2.02
Forward the project on to your subs and vendors at whatever role fits each. Everyone bids and questions against the same revision, on a clean audit trail you can refer back to — no reconstructing email threads.
2.03
Tag every element Comply, Deviation, Exception, or Comment. The owner sees your responses grouped by requirement — exactly where your bid agrees and where it pushes back — instead of decoding a marked-up PDF.
2.04
Every share link points at a specific published revision — it can’t drift. When the owner issues a change you’re notified, and the old revision stays available so your bid history and change-order basis are preserved.
2.05
Every requirement is filed under its section with a stable address — jump straight to the clause that affects your scope instead of scrolling a two-thousand-page PDF with no bookmarks, hoping you didn’t miss the gotcha.
2.06
A new revision shows up as an element-by-element changelog with added, modified, and removed lines highlighted — so you update your bid in minutes, not days.
2.07
Don’t make estimators read 200 pages for one answer. Ask the project directly — the AI reads the spec, checks the comment history, and points you to the exact citation. It sees only what you see.
2.08
Every requirement carries a stable address tied to its published revision. Quote it in an email, an RFI, or a sub instruction, and everyone lands on the same paragraph — even after the spec is revised later.
PART 3 — EXECUTION
STEP 01
Open the invitation, see the role and purpose, and you’re reading the live, published revision.
STEP 02
Attach a Comply, Deviation, or Exception to each element, and forward to subs at the right role.
STEP 03
Get the changelog when a revision drops, and keep every earlier version for change orders and claims.
OPEN LIBRARY
You know where the spec lines up with how the work actually gets installed — and where it doesn’t. That gap rarely makes it back to whoever writes the next specification, and the same mistakes keep showing up. Contribute to the SynC standards wiki to close that loop. 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 attribution stays on every adopted revision your contribution shaped — a specific, verifiable claim of expertise you can point future customers to.
PART 4 — ON THE ROADMAP
PLANNED
A generated overview filtered to your trade — only the requirements that actually affect your scope, with the rest collapsed away.
PLANNED
Turn a published revision into a bid request for a single trade: pick the sections that apply, and those requirements come along automatically — nothing retyped, nothing left out.
Sign up free, or get in touch for a walkthrough of how SynC fits the way your team already bids.