PROJECT TOOLS · FOR CONTRACTORS
The spec you were sent, organized so you can find what touches your scope. Every addendum shows exactly what changed since the last one. Ask a question while you estimate, or out on the site once building starts, and get an answer with the clause behind it. When something doesn’t fit, say so on the requirement and it reaches the engineer.
Organized by requirement · Every addendum diffed · Free to read
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 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 to miss, and nothing you can point to later.
You shouldn’t have to guess which revision you’re bidding.
PART 2 — PRODUCTS
2.01
The spec is filed by section, and every requirement has an address in its revision. Jump to the clauses that touch your scope instead of scrolling a two-thousand-page PDF. Cite the address in an RFI or a sub instruction and everyone lands on the same paragraph.
2.02
A new revision shows up as a changelog by element: added, modified, and removed, with the old text struck through. You know exactly what moved between bid one and bid two. The earlier revision stays available, so your bid basis and your change-order basis are on record.
2.03
Don’t make an estimator read 200 pages for one answer. Ask, and the AI answers from the spec and the comment history with a citation you can open. It works on the site once building starts, and it sees only what you see. Your own tools can connect the same way, with a key scoped to what you see.
2.04
Tag each requirement Comply, Deviation, Exception, or N/A. The engineer sees your responses grouped by requirement, exactly where your bid agrees and where it pushes back. Your subs’ responses come to you first, and you decide what goes up. When the bid goes out, your exceptions roll up into one list instead of a hand-typed exceptions letter.
2.05
The owner or engineer sends a share link at the role they want you to have. Accept it and you are reading the published revision they issued. Reading is free and stays free. If you don’t have an account yet, you create one when you accept.
2.06
Forward the project to your subs and vendors, at whatever role fits each, wherever the sender allowed it. Everyone bids and questions against the same revision, and the record shows who has it.
PART 3 — EXECUTION
STEP 01
Open the invitation, see the role and purpose, and you’re reading the published revision.
STEP 02
Attach Comply, Deviation, Exception, or N/A to each requirement. Forward to subs where allowed.
STEP 03
When a revision is issued, read the changelog and keep every earlier revision for change orders and claims.
OPEN LIBRARY
You know where the spec matches how the work gets installed, and where it doesn’t. That rarely reaches whoever writes the next spec, so the same mistakes keep arriving. Put it in the open library.
Adopted SynC standards are released under Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0). Your name stays on every adopted revision your contribution shaped.
PART 4 — ON THE ROADMAP
PLANNED
An overview filtered to your trade: only the requirements that affect your scope, with the rest collapsed away.
PLANNED
Turn a published revision into a bid request for one trade. Pick the sections that apply and those requirements come along, nothing retyped and nothing left out.
Sign up free, or get in touch and we’ll show you how it fits the way your team already bids.