SYNERGY IN CONSTRUCTION · PROJECT SPECIFICATIONS

Issue the record. Not a copy.

Your requirements as one live record with sealed revisions that your consultants, your clients and your contractors connect to. Everyone you share with reads and comments free.

Create accountBook 25 minutes
SYNC STANDARDS

Every revision sealed · Every recipient on record · Free to start

What it does

Live collaboration

Your collaborators work in the same draft at the same time. Every change tracked.

A consultant writes their sections inside your project from their own library. A clause two people changed is refused, never overwritten.

A looping demonstration of two people editing the same project draft, Building 400, draft of Rev 4, in the HVAC Ductwork standard. T. Nakamura of Meridian MEP is the mechanical consultant writing in Harbor Engineering's project. On the left, R. Alvarez of Harbor Engineering changes clause 12.2.8 to read "Joints with gaps exceeding 1/2 in. shall be re-fabricated or re-fitted, not merely bridged with mesh and mastic." and saves. The save lands. On the right, T. Nakamura adds "Remove any found on site before the leakage test." to clause 12.3.3, "Cloth-backed duct tape is not UL 181A or 181A-P listed and is not acceptable for ductwork sealing in any application.", and saves. That save lands too, and a notice says R. Alvarez's change to 12.2.8 is now in their copy. Both then edit clause 7.2.7, "Seal Class B is required for pressure class 3 in. w.g." R. Alvarez saves "Seal Class B is required for pressure class 3 in. w.g. and for all ducts in unconditioned spaces." first. T. Nakamura saves "Seal Class B is required for pressure class 2 in. w.g. and above." second. The second save is refused: a dialog titled "You and R. Alvarez both changed 7.2.7" asks T. Nakamura to choose which version to keep, and says nothing is saved until they choose. Nothing was overwritten: R. Alvarez's text for 7.2.7 stands.

Fill out the datasheet

Each standard asks its questions once. Fill in this job's values on a datasheet beside the text. The prose is never rewritten.

The choices are the ones the standard offers. A value outside them is refused before the revision is published, and every value is data your tools can read.

A looping demonstration of setting a datasheet in project Building 400. The create screen opens as New datasheet, Create New Datasheet, based on template Domestic Water Booster Pump Systems. The prefilled datasheet name is replaced with BP-1 Domestic water booster. The datasheet has 22 fields; four are shown. Field 6.2, Minimum Available Suction Pressure in psi, starts as indicated on the drawings, and the locator note Flow test on sheet C-101 is typed in, so its status reads As indicated on the drawings, Flow test on sheet C-101. Field 6.4, System Design Peak Flow in gpm, also starts as indicated on the drawings; Specify a value instead is pressed and its slider, from 20 to 1000, is set to 200 gpm. Field 6.4, Required Discharge (Boosted) Pressure Setpoint, keeps its default of 70 psi, on a scale from 40 to 125. Field 8.1, Pump Wetted Material, keeps its default, Type 304 stainless steel bowls and impellers (standard potable booster). Create datasheet opens the First revision summary dialog; the summary Initial values from the 60% plumbing set. is typed, the dialog notes the datasheet will be recorded as revision 1.0.0, and Create datasheet is pressed. The project draft returns with the notice Datasheet created successfully. Under Plumbing, the standard Domestic Water Booster Pump Systems now lists the datasheet BP-1 Domestic water booster, marked 1 deferred and Current, with content fingerprint 7f3a9c2e51b4 and an Edit button.

Revision tracking

Every issued revision is sealed. Compare any two project, spec or datasheet revisions and see the exact delta.

Each addendum reads clause by clause against any earlier revision.

A looping demonstration of comparing two revisions of the Air Handling Units standard in project Building 400. The base version is set to 1.1.0, Aug 14, 2026, and the comparison to 1.3.0, Oct 20, 2026, the current revision. The comparison opens as a revision register: 549 clauses changed between 1.1.0 and 1.3.0, and 107 datasheet fields. By kind: 305 clauses and 56 fields added, 49 clauses and 8 fields modified, 183 clauses and 43 fields removed, 12 clauses moved. Listing changes only, clause 3.2.1 is unchanged but its datasheet field changed: Required Closeout Submittals is renamed Closeout Submittals Required. Of its options, "Operation and maintenance manuals" now reads "Operation and maintenance manuals indexed by unit tag"; "Factory test reports for each unit" now reads "Certified factory test report for each unit"; "Commissioning records from startup and functional testing" is removed; "Signed startup report for each unit" is added. Clause 6.1.1 is modified: "Each fan shall deliver the scheduled airflow at the design external static pressure and at the site elevation." now reads "Each fan shall deliver the airflow indicated in the datasheet at the design external static pressure, at the site elevation, and at the design entering air conditions."

Project sharing

Control who has access and exactly what they can do. Every acceptance is on record.

Share links at the role you choose. Withdraw access when you must.

A looping demonstration of sharing a project. On the Distribution page for project Building 400, the Share dialog opens on revision 3.0.0. The recipient’s email, d.whitfield@northgate-builders.example, is typed in and the access level Viewer (read and comment) is chosen: the recipient reads the revision and comments on it, and cannot edit. Send confirms “Shared with d.whitfield@northgate-builders.example”, and the share link appears in the share links list as Pending. When it is accepted the status changes to Accepted, and the Access Records tab shows a new record: D. Whitfield of Northgate Builders, role Viewer, received Rev 3.0.0 on Oct 21, 2026, with a Remove access control beside it.

Comments on the clause

Anyone can comment on any clause. Each carries a citation and a reason, and lands in each recipient's queue.

Notes and suggestions for your own team stay internal. A recipient's response, Comply, Deviation, Exception or N/A, is forwarded one hop up the chain and resolved there or passed on.

A looping demonstration of commenting on a clause. In project Millbrook WTP Electrical Upgrade, a contractor, D. Whitfield of Northgate Builders, reads the SynC standard Low-Voltage Switchgear, revision 2.1.0, and presses the comment button beside clause 3.2.4: "Each main and feeder breaker shall be set to the coordination study and tested by primary current injection before the switchgear is energized." The comment dialog opens with that clause cited. The comment is a Compliance comment to Harbor Engineering, routed to bubble up the chain. The disposition is changed from Deviation to Exception and the reason is typed: "No primary injection test set for the 4000 A mains is available before the outage. We propose secondary injection at the mains." It is submitted and appears on the clause, dated Oct 21, 2026. The view moves to Harbor Engineering's comment register, where the comment is listed as received and awaiting response, with its citation Low-Voltage Switchgear 3.2.4, and in the as-bid rollup as open. Harbor Engineering resolves it with the outcome Rejected and the note: "Primary injection stands: secondary injection does not test the current sensors. Schedule the outage when a test set is available." The loop ends on Northgate Builders' view of the clause, where the comment now shows Rejected with that note.

One look, every author

Automated Word and PDF with a table of contents, bookmarks and consistent house styling, no matter who wrote it.

Section dividers, continuous page numbers and a bookmark outline in every export.

A looping demonstration of exporting a project. On project Building 400, Revision 3, the quick actions menu opens and Export is chosen. The export dialog opens on the PDF package format, with datasheet fields and the options not chosen included and all eight specifications selected: Storm Drainage, Steel Deck, Structural Steel Framing, Door Hardware, HVAC Ductwork, Chillers, Domestic Water Piping and Panelboards. HVAC Ductwork and Chillers were written by the consultant Meridian MEP and the rest by Harbor Engineering. Export PDF prepares each specification in turn, requests the certificate and builds the PDF. The dialog closes and the file, building-400-specifications-r3.pdf, opens on its cover page: project title, revision Rev 3, issue and export dates, and a contents list of every specification under its section with its revision code, all in one house style whoever wrote it. The footer reads Page 1 of 104, numbered continuously through the package. Beside it the bookmark outline lists the sections, one bookmark per section divider page, and Air Distribution opens to show HVAC Ductwork.

HOW TO START

Three steps to the first revision you issue

  1. STEP 01

    Create your account and company

    Name the company and you are its first author.

  2. STEP 02

    Bring one standard

    Adopt one from SynC Standards, or convert one of your own with the guide.

  3. STEP 03

    Start a project and issue it

    Fill out the datasheet, publish a sealed revision, and send it as share links. Export a PDF where paper is required.

WHAT IT COSTS

Everyone who receives your specifications reads, comments and responds free, forever. Your first author is free too. Every author after that requires a seat, at one price, with no tiers.

SEE PRICING

SYNC STANDARDS

Free to read, free to adopt

SynC writes and maintains a library of construction standards, structured to the clause and tracked by revision. Every revision is published under Creative Commons Attribution 4.0. Read them without an account and use them on any project, with credit. Your own standards stay yours, in a private company library.

Most-read standards

FULL INDEX OF STANDARDS

SENT A SPECIFICATION?

You are reading the record.

Open the link, accept it, and the revision that was issued to you opens. Comment on the clause and respond to the sender from the same page.

You cannot change the revision you were issued, or share it on unless the sender allowed it.

No seat · No card · No countdown

A looping demonstration of accepting a share link. The Project invitation page checks the link, then shows it as valid: an invitation to project Building 400, intended for d***@northgate-builders.example, revision 3.1.0, shared by R. Alvarez for bidding, expiring November 23, 2026, with forwarding allowed, and a message from R. Alvarez: “Addendum 1 for your bid. Site lighting is new; steel framing moved to Rev 3.0.0.” Signed in as d.whitfield@northgate-builders.example, the recipient chooses General contractor as their company’s role on the project and presses Accept access. The page turns to Access granted: Invitation accepted, project Building 400, revision 3.1.0, access Viewer, with Open project and Forward this revision buttons.

Start with one standard

Create an account and adopt one from SynC Standards. Or bring a section of your office master and we'll walk through it with you. Twenty-five minutes.

Create accountBook 25 minutes

Or send us a message