HOW IT WORKS

From standard
to issued for bid.

A standard holds the requirements every project shares. A datasheet beside it holds the values that change from job to job. You adopt, set the values, mark what the drawings still owe you, and issue the result as access to a sealed revision.

Create accountBrowse the standards

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

STANDARD

Steel Deck

CURRENT REV

7

REVISION HISTORY

7

Coating raised G60 G90 for composite floor deck.

6

Added minimum design-thickness clause.

5

Adopted into project from the open wiki.

DATASHEET

Deck depth
3 in
Coating
G90 · rev 7
SYNC OPEN STANDARDVERIFY a3f82c19d04e
A revision log for an adopted SynC standard, showing tracked changes across revisions and the current datasheet values.

PART 1 — GENERAL

Why it's built this way

1.01

The document is boilerplate. The datasheet is the job.

A standard carries the requirements every project reuses. The values that change from job to job (coating, depth, gauge) live on a datasheet beside it. You set the datasheet instead of editing prose in six places, and each value stays a line item that reads the same to every bidder.

1.02

A copy leaves. Access stays.

Send a PDF and you have issued a copy you can't correct, update, or trace. Issue a share link instead and the recipient reads the sealed revision in place. You see who accepted and when, you choose whether later addenda reach them, and you can withdraw access if you must.

PART 2 — PRODUCTS

The pieces you work with

The open library

Construction standards organized by discipline and structured to the clause. Read any standard in full, free, with no account. One click starts a project with it attached.

Your company library

Your own standards, private to your company and adopted into projects the same way. Converting your office master is work we do with you.

Project specifications

Adopt a standard into a project and it becomes your spec. Edit a clause where this job differs. The rest stays tied to its source, so when the standard is revised you see what changed and can pull it in.

Datasheets

The configurable values for each adopted standard, kept beside the text as structured line items. A field you leave to the drawings goes on the coordination checklist until someone answers it.

Revisions

Every published revision is numbered, summarized, and sealed with a fingerprint. Compare any two, line by line. A quote or a contract can be checked against the exact revision it was written to, long after the documents left your hands.

Comments on the requirement

Anyone with access can comment on the clause or field they are working from, tagged Comply, Deviation, Exception, or N/A. Comments travel back up the share chain to whoever can act on them, and you can see which ones you still owe upstream.

PART 3 — EXECUTION

The workflow, step by step

  1. STEP 01

    Start from a standard

    Search the open library by discipline, or open your company library. Read the whole standard before you commit.

  2. STEP 02

    Adopt it into a project

    Pull the standard in. It becomes your project spec, with its history tracked from the first save.

  3. STEP 03

    Set the datasheet

    Fill in this job's values and edit clauses where it differs. Mark anything the drawings still owe you. It goes on the checklist.

  4. STEP 04

    Issue as access

    Publish a sealed revision and send share links. Export a PDF where paper is required. Forwarding goes only where you allowed it, to the depth you set.

Built for the whole project team

Owners & end users

Set requirements once, see what each firm issued against them, and keep the record of who received what.

Engineers & architects

Write requirements once and reuse them on every job. Exceptions come back on the clause, not in an email.

Contractors

Read the revision you were issued, free. See what each addendum changed, and answer line by line.

Manufacturer reps

Pull requirements as data into your quoting tools, and send line-item feedback back to the engineer.

Questions

What is the difference between the spec and the datasheet?
The specification holds the requirements every project shares. The datasheet holds the values that change from job to job. Keeping them apart means you change a value once, not in six places of prose, and every bidder reads the same line item.
Do I need an account to read standards?
No. The open library is free to read and export as PDF with no account. You create an account when you want to adopt a standard into a project.
How are revisions verified?
Each published revision is sealed with a content fingerprint. Anyone holding a document can look up the fingerprint and confirm it matches what was issued. Exports also carry a signed certificate that can be checked offline.
What happens when a standard I adopted is revised?
SynC shows which of your datasheets upgrade cleanly and which need a look. Your values are kept; only the standard's text changes. A set whose datasheets are behind the standard they use cannot be published until you reconcile it.
How is access controlled?
Access is granted per person and per project. A share link is issued against a published revision, at the role you choose, and you decide whether the recipient may forward it, how far, and whether they may export a copy. You can see who accepted and when, and withdraw access.
Can AI help?
Yes. Anyone on a project can ask it questions, and it answers from the published record with citations. It can propose an edit, and every proposed change waits for a person to approve it. The decision stays with the licensed professional.

Put a standard to work

Read the library free. Create an account when you’re ready to adopt a standard, set its datasheet, and issue it.

Create accountContact us

Or back to home