Modules · Review EngineConstruction Operating System

Review it
in place.

Sequential document review with markup, comments and stamped decisions — on the record the document belongs to. Reviewers work in order, every revision is kept, and the decision becomes part of the document's history. No separate markup app, no lost redlines.

Follow the review

SUB 08-40 · Curtain Wall · Mock

Watch a review become a decision.

A standalone markup app returns a redlined PDF someone has to interpret. Here, one review moves from reviewers → comments → version → decision — and the answer writes back to the submittal on the record.

sub 08-40 · mock · review.log

Reviewers

3

Comments

7

Decision

Approved as noted

Last write

awaiting review

01writes

Review Workflows

Review started · 3 reviewers

Reviewers work sequentially, ball-in-court always clear, workflow on the record.

02writes

Markup & Comments

7 comments · marked up

Clouds, callouts and threaded comments anchored to the exact spot and revision.

03writes

Version Control

rev 2 · changes tracked

Each round is a versioned record. Nothing overwritten, nothing lost between rounds.

04writes

Approvals

Decision recorded · approved as noted

A stamped decision becomes part of the record and writes back to the submittal.

one review · one historyreview-engine.review / recorded
Tools ·01 · Review Workflows02 · Markup & Comments03 · Version Control04 · Approvals

The tools · Review Engine

Four tools. One review.

One thread runs down the page — reviewers routed in order, comments anchored to the revision, a version kept, a stamped decision written back to the submittal.

ILLUSTRATIVE MOCKUP — NOT CUSTOMER DATA

01
Tool

Review Workflows

  • · Sequential Reviewers
  • · Ball-in-Court
  • · Turn Notifications
  • · On the Record

Reviewers, in order.

Route a document to reviewers sequentially, each notified when it's their turn, ball-in-court always clear — the review workflow is ours and it lives on the record, not in a reviewer's inbox.

writes → review started · 3 reviewers
REVIEW · SUB 08-40● IN REVIEW
  1. ✓

    General Contractor

    Complete

    Done
  2. ◉

    Architect

    Reviewing

    In turn
  3. ○

    Owner

    Queued

    Queued
our workflownot a reviewer's inbox
02
Tool

Markup & Comments

  • · Clouds & Callouts
  • · Threaded Comments
  • · Anchored to Revision
  • · Resolvable

Redlines that stay attached.

Mark up the drawing or document in place — clouds, comments, callouts — and every note stays attached to the exact spot and the exact revision. The redlines don't live in a screenshot someone emailed.

writes → 7 comments · marked up
MARKUP · SUB 08-40 rev 2● 7 OPEN

  • Anchor spacing exceeds detail

    Open

    Architect

  • Mullion 14 sealant gap

    Resolved

    GC

  • Sample finish per spec?

    Open

    Owner

anchored to the revisionredlines stay put
03
Tool

Version Control

  • · Version History
  • · Round Tracking
  • · Change Log
  • · Compare

Every revision, kept.

Each round produces a versioned record — what changed, who asked for it, what the reviewer said — so the document's history is the review's history. Nothing is overwritten, nothing is lost between rounds.

writes → rev 2 · changes tracked
VERSIONS · SUB 08-40● TRACKED

  1. rev 2 · anchors revised

    Current

    Per Architect markup

  2. rev 1 · initial submission

    Superseded

    Curtain-wall package

nothing overwrittenhistory = the review
04
Tool

Approvals

  • · Stamped Decisions
  • · Status Writeback
  • · Distribution
  • · Audit Trail

A decision that sticks.

Reviewers close with a stamped decision — approved, approved as noted, revise and resubmit — and that decision becomes part of the record, visible to the field and carried into the submittal's status. The answer isn't in an email; it's on the document.

writes → decision recorded
DECISION · SUB 08-40 rev 2● RECORDED

Stamped decision

Approved as noted

ArchitectJul 28

"status writes back to the submittal · field notified."

stamped on the documentwrites back to the submittal
Four tools · One reviewsyntecton.review-engine / tools — 2026
Blueprints marked up in place — kept on the revision

Marked up in place — kept on the revision

Why an operating system

The redline didn't get emailed. It stayed on the document.

A standalone markup tool is one more place to export to and forget. Review Engine reviews on the same record everything else uses — so the comment anchors to the revision, the decision writes back to the submittal's status, and the field sees the answer without anyone forwarding it. One document, one review, one history.

PreconstructionFinancial ManagementProject ControlsField ExecutionProject RecordSafety & ComplianceSignature EngineReview Engine

Workflows

Review Workflows

sequential reviewersball-in-courtturn notificationson the recordclouds & calloutsthreaded commentsanchored to revisionresolvable commentsversion historyround trackingchange logcompare revisionsstamped decisionsstatus writebackdistributionaudit trailsubmittal reviewshop drawingsspec reviewdocument reviewfield visibility
Concrete frame — reviewed in place, decided on the record

Reviewed in place — decided on the record

See it on a real project · Review Engine

One document. One review.

Legacy tools route drawings through a markup app that lives outside the project — the comments end up in a PDF, and someone re-keys the decision into the submittal after the fact.

The Construction Operating System reviews on the record — reviewers in order, comments anchored to the revision, versions kept, a stamped decision written back to the submittal the field is watching.

Review Engine is where a review becomes the record — on the document it belongs to.

01Review Workflows
02Markup & Comments
03Version Control
04Approvals
syntecton.review-engine / outcomes — 2026