Struxen documentation

Struxen is a construction project platform with an AI layer over your project documents. You bring in the drawing set, the specifications and the rest of the record; Struxen indexes it, and the registers, the automated checks and the assistant all read from that one source.

New here? Getting started takes you from your invitation to your first cited answer. Access is by invitation, so start there rather than looking for a sign-up button.

How the product is arranged

Two containers and four products.

The containers are your organization, which owns billing and the people, and its projects, which own everything else. Struxen works one project at a time: you pick a current project and every surface scopes to it. How Struxen is organized covers the model.

The four products all operate on that current project.

Product	Route	What it does
Struxen Core	/core	Run the project. Drawings, documents, specifications, submittals, RFIs, observations, schedule, daily logs, punch, meetings, inspections, safety, photos, transmittals and the team directory.
Struxen LEDGER	/ledger	Run the money. Prime contract, commitments, the change chain, direct costs and the budget. Paid — not in the CORE free tier.
STRUX	/strux	Ask the drawing set. Cited question and answer over your documents, plus five purpose-built instruments. Paid — not in the CORE free tier.
Struxen VANTAGE	/vantage	See what was drawn. Automated multi-document quality-control runs producing findings, and a 3D read of the set. Paid add-on at $250/month per project.

Two surfaces are shared across all four: Findings, which collects what the automated checks turned up, and Reports.

Documentation by section

Eight sections. Each covers one area of the product end to end.

Platform

The containers, the navigation, and the two surfaces every project starts on.

Page	Covers
How Struxen is organized	Organizations, projects, the current-project model, the four products, where each setting lives.
Projects	Creating a project with the wizard, the eleven project settings sections, deleting a project, the all-projects portfolio view.
Project home	The widget board at /overview: eleven widgets, three templates, edit mode, and how your arrangement is saved.
Struxen Core	The /core landing surface: the setup checklist, the overdue list, and the module grid.

Documents and drawings

Getting source material into the project and making it searchable. Start here if STRUX cannot find something.

Page	Covers
Documents	The document library and how it is filed.
Uploading	Accepted file types, size and batch limits, rejection codes.
Processing	What each processing status means and what to do about it.
Drawings	Drawing sets, sheet splitting, review and publishing to the sheet register.
Sheet viewer	Viewing, marking up and comparing published sheets.
Specifications	The specification register, section import and what it costs.

STRUX

The assistant and its instruments.

Page	Covers
STRUX	What STRUX is, how it is gated, and how to read an answer.
Field Q&A	Asking questions of the project, citations, and refusal behaviour.
Agents	The agent studio, templates, schedules and run budgets.
Workflows	Multi-step checks run on the VANTAGE engine.
Submittal Review	Automated pre-review of a submittal against the specification.
Revision	Comparing drawing revisions and reading the change set.
Commissioning	Equipment and systems checks.

VANTAGE

Automated quality-control runs, the findings they produce, and the model surface. Sold as a per-project add-on.

Page	Covers
VANTAGE	Run kinds, the built-in checklists, phases and statuses.
Findings	Reading, triaging and escalating a finding.
Digital twin	The 3D read of the drawing set, and its stated confidence limits.

Field operations

The registers that run the job day to day. Each page covers one module's lifecycle, its limits and its states.

Page	Covers
Field operations	Section index, and the rules common to every register.
RFIs	Raise, route and close requests for information.
Submittals	Packages, multi-step review and per-company status aliases.
Transmittals	The outbound record of what was formally issued, and to whom.
Observations	Logging and sending observations.
Punch list	The assignee, manager and final-approver workflow.
Inspections	Template-driven inspections and deficiency promotion.
Daily logs	Sub-log types, completion attestation and distribution.
Photos	Albums, dating, tagging and share links.
Safety	Incidents and toolbox talks.
Meetings	Agenda and minutes modes, business items, attendance.
Schedule	Activities, dependencies, and the two ownership modes.
Reports	The canned reports and how they are sent.

LEDGER

The cost and contract side of a job: the prime contract, commitments, the change chain, direct costs, the budget, pay applications and retainage. See LEDGER.

Account and billing

Everything that belongs to the organization rather than to one project.

Page	Covers
Account and billing	Section index.
Organizations	Members, invitations, roles and ownership.
Roles and permissions	Organization roles, project access levels and per-tool permissions.
Billing	CORE free tier, organization fee, VANTAGE, credits, top-ups and invoices.
Integrations	Connecting Autodesk, what imports, and what does not sync back.
Privacy	Data handling, retention and the controls available to you.

Reference

Look-up tables rather than reading material.

Page	Covers
Limits	Every enforced limit in one place.
Statuses	The exact status names each module uses.
File types	What can be uploaded, and on which path.
Troubleshooting	Symptom, cause, fix.

A note on what these docs claim

Struxen is built to distinguish "the answer is not in your documents" from "the data could not be reached", and to show an honest error instead of an empty table. The documentation is held to the same standard: if a page does not describe a capability, assume it is not there. Nothing here is written ahead of what has shipped.

Something missing or wrong? Email support@struxen.io.