Struction

The agent reads and writes only inside Struction's own workspace. Chat can create, rename, combine or split scopes of work. It can create, resolve or rerank risks and RFIs, pull counts from a schedule into a quantity and find duplicates of a symbol. Documents come in by upload (drawings, specs, bid documents, schedules and BIM), and scopes go out by export to Excel for subcontractors and ITBs. A person carries the files in and out.

Struction names no construction platform, document management, ERP or estimating integration, and no connector types, credential scoping or custom tools.

Sourcestruction.com/docs/editing-with-chat, /docs/upload, /docs/scopes-of-work; readread 2026-09-15

A multi stage generation pipeline runs on upload, with deterministic steps, approval gates and version control. Struction reads the documents, labels each one, organizes them by discipline and writes a first draft scope of work for each trade. It then surfaces risks, RFIs and scope gaps. Items that fit no trade go to scope gaps instead of being forced into the wrong scope. Deterministic and agent steps mix.

Quantities can be manual, assisted or automated, counts land on a scope item with the sheet measured, and approval cards sit between chat actions and data changes. Scopes carry major.minor version history with restore. Background jobs run on the item while the user keeps working, and one job per item prevents collisions.

Struction names no workflow authoring surface, explicit retries, fallback paths or reuse across teams. Regeneration reruns on request.

Sourcestruction.com/docs, /docs/scope-creation, /docs/scope-editing, /docs/editing-with-chat; readread 2026-09-15

Struction builds a persistent, linked map of a project's own documents and answers from it with citations. Users upload drawings, specs, bid documents and schedules, and Struction reads them, labels each one, organizes them by discipline and handles replacement sets. Struction lists five ideas behind the product, and one is that every source is connected.

Scopes, drawings, specs and issues are linked by their relationships and navigated as trade and document maps that include the federated BIM model, with callouts, details and spec references linked into one chain. For project chat, Struction has read every drawing, spec, addendum and model element on the project.

Cited answers carry a clickable chip to the page, scope, issue or spec section, and every output has a source. Context attached to chat is shown before sending, and chat never works with context. New project knowledge enters without retraining, and Struction says it will not train on project data.

Struction names no source permissioning and no handling of conflicting documents beyond manual replacement.

Sourcestruction.com/docs, /docs/cited-answers, /docs/context-aware, /landing; readread 2026-09-15

An approval card appears before any chat action changes project data. The user accepts, edits or denies it before it happens, so chat never silently changes the project, and bulk actions are grouped into a single card. Scope Editing adds a verify step, where users mark items as verified as they confirm them, turning an AI first draft into a scope they stand behind. Regeneration warns before overwriting edits a user has made. Context attached to chat is shown before sending.

The gate is always on, and Struction names no setting by action or approver and no way to route approvals to other channels.

Sourcestruction.com/docs/editing-with-chat, /docs/scope-editing, /docs/context-aware; readread 2026-09-15

When a project is created, the creator and their team are the only ones who can edit it, and changes are stamped with who made them. Struction says it won't train on customer project data. The Enterprise GC tier is for larger builders with scale, security and unmetered chat, without naming a control. Struction names no roles, SSO, SAML, SCIM or MFA, and no attestation, certificate or trust center. It shows no compliance badge and publishes no security or privacy page.

Sourcestruction.com/docs/sharing, /pricing, /landing; readread 2026-09-15

Every AI change and every user edit is recorded and reversible, with version history a customer can inspect and restore. Every scope carries its full history. An AI change, such as a regeneration, bumps the major version number, and a user edit bumps the minor.

Version history lists previous versions with a summary of what changed, a count of items added and removed, timestamps and who made the change. Risks and RFIs are stamped with who changed them and when. Background jobs show progress on the item being worked on. The record of what the agent changed and when is kept separately from the chat.

The record covers changes to outputs, not each tool call. Struction names no step level inspection of prompts and model calls, no export to monitoring tools and no retention by plan.

Sourcestruction.com/docs/scope-versioning, /docs/version-control, /docs/editing-with-chat; readread 2026-09-15

An organization can upload exemplar scopes so Struction matches its format. Organizations and individuals can also write preferences, which are system prompts that steer generation and chat. These persist because a person wrote them down. The project map of documents, scopes and issues persists as project data. Struction names no conversation or long term memory that the agent keeps across sessions.

Sourcestruction.com/docs/scope-customization, /docs; readread 2026-09-15

Customers reach a hosted web workspace by signing in at struction.com, and projects are uploaded and processed in the hosted product. Struction names no dedicated, VPC, on premises or self hosted option, including on the Enterprise GC tier, which mentions security without naming a deployment mode. No hosting region or residency choice is published.

Sourcestruction.com/docs, /pricing, /faq; readread 2026-09-15

Scopes are created automatically when a project is created, one for each trade Struction identifies in the documents. Each first draft reflects that specific project, not a generic checklist. The only templates are the customer's own exemplar scopes, uploaded in Settings, and Struction names no prebuilt agents. A Specialty Contractors plan is offered as early access by request.

Sourcestruction.com/docs/scope-creation, /docs/scope-customization, /pricing; readread 2026-09-15

Project chat inside the product carries the agent's work, and work starts only when a person acts. Chat can do almost anything a user can do by clicking and is context aware to the current view. Processing starts when a user uploads documents. Struction names no event triggers, and a new drawing set arriving does not start processing on its own. Document version replacement is manual, and Struction says it will soon handle replacement itself. The Dispatch email is a newsletter, not a channel into the product.

Sourcestruction.com/docs/editing-with-chat, /docs/upload, /docs/version-control; readread 2026-09-15

Customers on the Enterprise GC tier choose a chat model across Google, Anthropic and OpenAI, and the choice is theirs to control. It applies to chat only, not to scope generation, takeoff or issue discovery. Struction names no model policy by workspace or action and no fallback visibility.

Sourcestruction.com/pricing Enterprise GC tier; readread 2026-09-15

The product is UI only. Struction names no API, SDK, webhook or MCP surface, and the only outbound path is export to Excel.

Sourcestruction.com/docs, /docs/scope-exporting (title in index), probes; readread 2026-09-15

The Verify step marks individual scope items as confirmed. Struction calls its accuracy high fidelity and says it only ships automated takeoff customers can rely on, which is its own internal release standard. Struction names no way to evaluate a change to the agent before or after release, no testing with fixtures or datasets and no scoring of output quality over time.

Sourcestruction.com/docs/scope-editing, /faq, /landing; readread 2026-09-15

Struction reads uploaded drawings, specs and BIM models with computer vision, detects symbols and acts inside its own workspace. It names no browser or computer control. A person can drive the BIM viewer with a game controller.

Sourcestruction.com/docs, /landing; readread 2026-09-15