Add context, files, and instructions to a workflow
Every workflow combines three layers of knowledge:
- Instructions — written guidance for how to do the task.
- Context files — documents always available on every run (standards, specs, prior approvals).
- Requested files — slots the user fills in when they run the workflow (today's drawing, this submittal, this RFI).
Use the right layer for the right kind of content and your workflows stay accurate as projects change.
Instructions
Instructions describe the procedure: what to check, what tone to use, what to skip, what to flag.
- Write them like you'd write a short SOP for a teammate, not as a prompt to an AI.
- Spell out edge cases. "If the sheet has no scale bar, note it and continue."
- Include the output format you want — bullet list, table, marked-up PDF — and Nomic will follow it.
- Include a final verification step when the task needs every page, section, or item checked.
Context files
Use context files for things every run should consider: project standards, code references, design narrative, glossary of trades.
- Add them in the workflow builder under Context.
- Folders work too — Nomic will pull from everything inside.
- Update them as your standards evolve; runs always use the latest version.
Avoid putting one-off inputs in context — they bias every run.
Requested files
Use requested files for the inputs that change every run: today's drawing set, the specific submittal, this week's RFI log.
- Define a named slot in the builder (e.g. "Drawing set", "Submittal package").
- When a user runs the workflow, they upload or pick a file for each slot.
- The slot name is what the user sees when running the workflow, so make it descriptive.
Let one slot take several files
By default a slot takes one document. If one input needs several files, such as a few drawing sheets or several standards documents, turn on Accept multiple files for that slot instead of combining them into one PDF first. A multi-file slot also accepts a folder.
- Open the workflow in the builder and expand Context.
- Under Requested Files, click a slot to open Edit Requested File, or click Add Files to add one.
- Turn on Accept multiple files. Turn on Optional if people can run the workflow without filling the slot.
- Click Save Changes (or Add File), then save the workflow.
Saving only updates the draft. People running the workflow keep the previous version until you click Release changes — see Workflow management. Update the instructions to refer to "every attached drawing" rather than "the drawing" so the agent checks all of them.
Common mistakes
- Putting the input in context instead of a requested file — every run will analyze the wrong drawing.
- Vague instructions — "check this drawing" gives unpredictable results; "flag any duct shown crossing through a structural beam" is reliable.
- Too much context at once — pruning to the standards that actually apply for this task improves precision.
- Skipping a sample run — broad workflows are harder to debug after a full drawing set has already run.