Features

A standard is the master. Each requirement in it is a clause with its own number, so it can be cited the way a construction specification is cited.

Adding a standard to a project creates a specification: the project's copy of the clauses, which you tailor to the job with its own requirements, comments and values. The specification keeps its link to the standard it came from.

A datasheet holds the equipment and material values for one scope of work. Its fields come from the standard, so an open-ended choice becomes a guided set of fields.

One standard can have several datasheets in a project (indoor panelboards and outdoor panelboards, say), each with its own values and its own history.

Your project follows the revision of each standard it adopted. When a newer revision is published, nothing in the project changes until you update to it. You can return to an earlier revision the same way.

When you update, the datasheets are reconciled to the new revision. Values that still fit carry forward. Anything that conflicts (a removed option, a changed field, a value that no longer fits) needs your decision before it applies.

Standards live in three places: the open SynC Standards wiki, your company's library, and your personal library.

A project can take a standard from any of them. Keep your own standards in the company library, draft in your personal library, and use the wiki where a community standard already covers what you need.

Not every value belongs in the specification. Some are shown on the drawings or left to the project engineer. Mark those requirements as deferred instead of guessing a value or leaving a blank.

Every deferred item on the project collects in one coordination checklist. An item is checked off by hand, or resolves on its own once a value is specified.

A project holds the specifications and datasheets for one job. You build it as a draft and publish it as a revision when it is ready to issue.

Each published revision is sealed. It is the record you send to the rest of the team, and you correct it by publishing the next one.

A revision of a project, standard or datasheet is a sealed snapshot of the full content, with a content fingerprint that changes if a single character does. Once made, it does not change; a correction is the next revision. Older revisions stay readable on their own.

Two revisions of a standard can be compared side by side. A datasheet's history shows each field as added, revised or removed.

A published revision exports as a PDF package, Word, Markdown or JSON, where your role allows export.

People who reached the project through a share link can export PDF and JSON, when the sender allows it. Word and Markdown stay with your own team.

The assistant answers questions about your specifications, datasheets and the standards behind them. Where you can edit, it can also propose changes, which you approve or decline one by one.

It reads only what you can already open. Conversations are saved to your account and private to you, and one you stop using is deleted 180 days after its last message. See AI usage.

Comment on a specification or a datasheet where the question arises. Replies stay in the thread, and a comment is marked resolved once it is settled. Reading and commenting require no seat.

Send a published revision to the rest of the team with a share link. You choose what each link allows and how long it lasts. Recipients sign in, or create a free account, to accept it, and reading stays free.

Allow forwarding to let recipients pass the link on. The access record shows who accepted it and when.

Connect your own tools, agents and scripts to SynC with API keys. Keys are issued under a company. Each key holds a subset of your own permissions, and you can revoke it at once.

The API integrations guide covers setup and authentication.

At a company, a person is a Company admin, a Library manager or a Member. A seat is given separately: with one, a person creates projects and edits standards and datasheets. Without one, they still read and comment.

On a project, access comes from a role on the project, a company role that covers it, or a share link.

Your account can be associated with more than one employer at a time, which suits consultants and anyone who works across companies. You choose which one is your primary for new work.

When you contribute to the wiki, every active employer is disclosed beside the contribution, so readers can judge a conflict of interest for themselves.

The SynC Standards wiki is an open library of construction standards. Anyone can read it. Contributors write, moderators review, and a reviewer adopts the revision that projects then use.

Contributions are attributed by name and governed by a Contributor License Agreement that keeps the library open. See Contributing to SynC Standards for how editing, attribution and adoption work.