Workflows
Turn your own QA/QC checklist or lessons learned into a reusable check that STRUX runs across the whole project document set
A workflow is a checklist you can run. You write the steps once, in your own words, and STRUX runs them across the project's documents and reports what it found as findings.
The instrument is the library plus the editor: browse what exists, draft a new one from a description or from a document you already have, and run it.
Workflows need the VANTAGE add-on
Workflow runs execute on the VANTAGE engine, so they carry the same entitlement as VANTAGE itself. Without it, starting a run fails with a message saying VANTAGE is not enabled on this project and that an account admin can add it in Project Settings for $250/mo. Browsing and drafting still work. See VANTAGE.
The library
Open STRUX in the left rail, then Workflows. The table lists every workflow available on this project.
| Column | What it tells you |
|---|---|
| Name | The workflow, with its one-line description underneath |
| Category | What kind of check it is |
| Built from | Where it came from: Struxen library, Team checklist, or Your checklist |
| Steps | How many steps it runs |
| Last run | When it last ran on this project |
| Runs | How many times it has run here |
Clicking a row opens it in the editor. Run in the last column starts it immediately without opening it.
The Struxen library ships built-in checks you can run as they are. See VANTAGE for what each built-in checklist covers.
Create a workflow
The bar at the top of the instrument is where a new workflow starts. Three things can seed it.
Describe the check. Type what you want checked, for example "cross-check that every mechanical unit has a matching electrical feed", and STRUX drafts editable steps.
Attach a document you already have. Use the paperclip to drop in a QA/QC checklist or a lessons-learned document. STRUX reads it and drafts the steps from it, so the workflow encodes your standard rather than a generic one.
Start from a seed chip. The chips under the bar are worked examples: From a QA/QC checklist, From lessons learned, Coordination check. Clicking one fills the bar so you can edit it.
Drafting calls a model, so it spends credits. So does refining a draft.
The editor
The editor is where a draft becomes a workflow.
- Name it and set its category.
- Edit the steps directly. Add, remove, reorder, or rewrite any of them.
- Ask for a change in plain language in the chat field, for example "add a step for roof curb coordination", and STRUX redrafts.
- Set Runs across to scope the run: The whole document set, HVAC (Div 23) only, Electrical (Div 26) only, or Architectural only.
- Press Save to keep it for later, or Save & run to save and start a run immediately.
Steps are prose, not a formal language. Write them the way you would write them for a person doing the check.
Running one
Starting a run opens the run theater, which shows the run's progress live. The run continues on the server, so you can leave the page.
When it finishes, what it produced is a set of findings. Those land in the project's findings queue, where they are triaged, escalated to an RFI or an observation, or dismissed. See Findings for the lifecycle, severities, and what to do with one.
Two runs per user per project can be in flight at once.
Limits
| Concurrent runs per user per project | 2 |
| Items in one checklist | 50 |
| Documents read per discipline | 100 |
| Documents read project wide | 200 |
| Run retention | 90 days |
Troubleshooting
"No workflows yet." Nothing has been created and no library workflow has been resolved for this project yet. Describe a check in the bar, or drop in a checklist document.
Run is refused with a payment error. The project does not have the VANTAGE add-on. An account admin adds it in Project Settings.
Run and Save & run are disabled. You are on the shared demo project, which is read only.
The run finished with no findings. That can mean the check passed. It can also mean the documents the check needed are not indexed on this project. Confirm the relevant drawings and specs show Indexed on the Documents page before concluding the project is clean. See Document processing.
The drafter returns an error. Drafting is a metered AI call and stops at a zero credit balance. See Billing.