PROJECT TOOLS · OPEN STANDARDS

Issue the record.
Not a copy.

For spec writers and the firms that assemble a project’s specification book.

Drawings live in a model. RFIs and submittals live in a platform. The specification still leaves the office as an email attachment, a copy no one can correct, update, or trace. SynC issues your spec as access to a revision-tracked record instead.

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

STANDARD

Steel Deck

REV

7

STATUS

✓ VERIFIED

STRUCTURAL / STEEL & METAL FABRICATIONS

6.1

Base steel shall conform to ASTM A653/A653M, structural quality.

6.2

Galvanized coating shall be G60 G90 for composite floor deck.

MODIFIED · REV 7

6.3

Design thickness shall be not less than 22 gauge unless noted on the drawings.

DATASHEET

Deck depth
3 in
Design thickness
22 ga
Coating
G90 · rev 7
SYNC OPEN STANDARDVERIFY a3f82c19d04e
Excerpt of the SynC Steel Deck open standard showing numbered clauses, a tracked revision, and datasheet values.

PART 1 — GENERAL

The problem is the paperwork

1.01

The moment a spec goes out as a PDF, the record splits. Copies can't be corrected or updated, and no one can say who holds which one. The drawings got a model. The spec got an attachment.

1.02

Where the spec says "as indicated on the drawings," the drawings often never say. No one keeps the list of what was deferred, so the gap surfaces in construction: an RFI, then a change order, then rework no one gets paid for.

1.03

Exceptions and substitutions come back as marked-up PDFs, re-typed at every hop from manufacturer to sub to contractor to engineer. Then last project's spec, conflicts and all, becomes the starting point for the next one.

The people aren’t the problem. The format is.

PART 2 — PRODUCTS

What SynC gives you

RESOLVES 1.01

One record, issued as access

Publish a revision and it is sealed. Recipients open it through a share link, free, never through an attachment. You keep a register of who has access and when they accepted, and you choose whether later addenda reach them. When the contractor says they never got the addendum, you have the record.

How distribution works

RESOLVES 1.02

The coordination review, automated

Mark a requirement as deferred to the drawings and it goes on the project's checklist, along with every job value you haven't filled in yet. You work the list down before the issue date instead of reading the whole spec with a highlighter. And SynC will not publish a set whose parts have fallen behind the standard they came from.

How it works

RESOLVES 1.03

Exceptions come back on the clause

A sub's substitution request arrives attached to the requirement it concerns, tagged Comply, Deviation, Exception, or N/A, and travels back up the chain the same way. No re-typing at each hop, and no one has to remember whose comment was meant for whom.

How firms use feedback

PART 3 — EXECUTION

From standard to issued-for-bid

  1. STEP 01

    Start from a standard

    Adopt one from the open library, free to read with no account, or bring your own. Converting your office master is work we do with you, not a file you upload and hope for.

  2. STEP 02

    Set the values

    Pull the standard into your project. The values that change from job to job (coating, depth, gauge) go on a datasheet beside the text, and you edit a clause only where this job differs. Every change is tracked from the first save.

  3. STEP 03

    Issue and track

    Publish a sealed revision and issue it as share links. Export a PDF where paper is required. Anyone holding the export can look up the fingerprint of exactly what was issued.

Ask the project a question

Anyone on the project can ask: was the bus copper or aluminum, which addendum changed the fault rating, what is still unresolved. The AI reads the published record and answers with a citation to the requirement it relied on. Open the citation and you are looking at the clause, at its address, in the published revision.

It sees exactly what your account sees, nothing more.

ASK THE PROJECT

Building 400

SCOPE

YOUR ACCESS

ANSWERS CITE THE RECORDSEES ONLY WHAT YOU SEE
A looping demonstration of asking the project a question. Question: Was the bus in the Building 400 panelboards supposed to be copper or aluminum? Answer: Copper. The “Building 400 Panels” datasheet specifies copper bus for every panelboard in Building 400. The answer carries a citation labeled BUILDING 400 PANELS · 2.4.1; opening it shows the cited requirement at address 2.4.1 of the Building 400 Panels datasheet, revision 3: “Busbar material shall be copper.”

See it on your own spec

Free to start, no card required. Or bring one section of your office master and we’ll walk through it with you. Twenty-five minutes, on your own specification.

Or send us a message

Prefer to read first? Browse the open library →