HOW IT WORKS

From open standard
to issued for bid.

SynC keeps the shared requirements in an open, revision-tracked library and the project-specific values in a datasheet beside them. Adopt a standard, set the values, and issue documents that stay verifiable after they leave your hands.

Create a free 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 shared requirements every project reuses. The values that change job to job — coating, depth, gauge — live in a separate datasheet. You set the datasheet instead of re-editing the specification, so the requirement stays a structured line item that reads the same to every bidder.

1.02

The library is open, and it improves with use.

Standards come from one shared, industry-reviewed library — 300+ of them, free to read and export with no account. Anyone with field expertise can contribute under the same open license as Wikipedia, so a correction lands once, for everyone, instead of living in a thousand private spec folders.

PART 2 — PRODUCTS

The pieces you work with

The open wiki

The shared library of construction standards, organized by discipline. Read any standard in full before you commit to it — free, and no account needed to read or export.

Project specifications

Adopt a standard into your project and it becomes your spec. Edit clauses where your job differs; everything else stays tied to the source so upstream fixes are easy to pull in.

Datasheets

The configurable values for each adopted standard, kept beside the text as structured, machine-readable line items — ready for bidders and quoting tools to read directly.

Revision records

Every change is numbered, summarized, and fingerprinted. A quote or contract can be checked against the exact version it was written for, long after the documents leave your hands.

Requirement-level comments

Anyone on a project can comment on the exact requirement they're working from. Comments are tracked and aggregated across a firm's projects, so the fix reaches the library, not the next job.

Scoped integrations

Connect AI assistants, BIM software, and procurement tools with exactly the access each one needs. Every connection is auditable and scoped — nothing sees more than it should.

PART 3 — EXECUTION

The workflow, step by step

  1. STEP 01

    Find your standard

    Search the open library by discipline — structural, electrical, mechanical, and more. Read the full standard before you commit to anything.

  2. STEP 02

    Adopt it into your project

    Pull the standard in and it becomes your project spec, with its history tracked from the first change.

  3. STEP 03

    Set the datasheet

    Fill in the project-specific values and edit clauses where your job differs. The requirements stay structured and readable, not buried in prose.

  4. STEP 04

    Issue and track

    Export clean PDFs, distribute through share links with your approval, and publish revisions everyone can trace and verify.

Built for the whole project team

Owners & end users

Standardize requirements across projects, surface issues through datasheet values, and compare bids on the same basis every time.

Engineers & architects

Write requirements once and reuse them on every job, with AI-assisted markup and aggregated field feedback closing the loop.

Contractors

Read specs the same way every time, with readable summaries and company-wide comments that keep bids and execution consistent.

Manufacturer reps

Pull machine-readable requirements straight into your configuration and quoting tools, and push line-item feedback back to the engineer.

Questions

What makes datasheets different from the spec?
The specification holds the requirements every project shares; the datasheet holds the values that change from job to job. Separating them keeps requirements clear and reusable — and as standards become familiar industry-wide, teams spend far less time re-reading specs on every project.
Do I need an account to read standards?
No. The open wiki is free to read and export as PDF with no account. You create an account only when you want to adopt a standard into a project and use the project tools.
How are revisions verified?
Each revision is numbered, summarized, and carries a content fingerprint. A quote or contract can be looked up against the exact version it references, so both sides know they are working from the same record.
Can AI help with specifications?
Yes. SynC includes AI-assisted markup for drafting and refining specifications collaboratively. The decision always stays with the licensed professional — the tools speed the work, they do not make the call.
What are machine-readable requirements?
Each standard can be exported as structured data — requirements as key-value pairs — ready for automated product configuration, pricing, or any tool connected to SynC.
How is access controlled?
Granular permissions at the company and individual level, share links that require the originator’s approval, and a full audit trail on every integration keep project data under your control.

Put a standard to work

Read the library free, forever. Create an account when you’re ready to adopt a standard, set its datasheet, and issue documents that stay verifiable.

Create a free accountContact us

Or back to home