Standards and SOPs

Two libraries make the difference between an agent that sounds plausible and one that is actually right about compliance:

• Standards — the external documents you must conform to, such as purchased ISO or IEC standards.
• SOPs — your own standard operating procedures, the way your company says work should be done.

Load both, and the Quality, Regulatory and Compliance agents cite real requirements from real sources instead of remembering them approximately.

The standards library

Go to Settings → Standards.

Upload standards

1. Drag files onto the drop area, or use Choose files or Choose folder. Whole folders including subfolders are supported.
2. Accepted formats are PDF, Word, text and Markdown.
3. Colleag extracts the text as Markdown for search and citation. The wording is not rewritten.

Your purchased original is kept in your own quality-system repository, so any answer that cites a standard can be checked against the source document.

Each entry in the library shows its edition and the original filename, and the extracted text is read-only.

Watch for the extraction warnings

Two markers appear on entries that need care:

• Scanned source read by OCR — the text came from a scan, so verify values against the original before you rely on them.
• Extract hit the size cap and is incomplete — a large standard was only partly read. Check the original for anything missing.

Using standards while you work

The canvas shows a Standards tree next to your documents. From there you can open the purchased original, or remove an entry from the library. Ask the Regulatory or Quality agent which clauses apply to what you are writing, and it will work from these files.

Licensing is your responsibility

Standards are usually licensed per company or per seat. Only upload documents your organisation has bought and is entitled to use internally.

Standard operating procedures

Go to Settings → SOPs, headed Standard Operating Procedures.

Start from the templates

An empty organisation offers a single button: Initialize SOPs from templates. That creates 25 built-in SOPs covering governance, quality, product development, operations, commercial and corporate processes. Start there and adapt, rather than writing from a blank page.

The SOP register

Each SOP is listed with:

Column	Meaning
SOP ID	The stable identifier, for example SOP-024
Title	What the procedure covers
Tier	Governance, Quality, Product Dev, Operations, Commercial or Corporate
Status	draft, in-review, approved, released or obsolete
Version	The current version
Review Due	When it next needs reviewing, driven by its review cycle

Click a row to expand it, then Edit to change it. You can set the tier, category, review cycle in months and the Agent Instructions — the part the agents read — plus the Governing Disciplines that own it.

Every status change is recorded with who did it, when and any comment, so the register doubles as your audit trail.

How agents use all this

An SOP is not a document that sits in a folder. It is part of an agent's brief: open ⋯ → Agent settings in the chat and you see the agent's Mission Stack, which is the set of SOPs and instructions it follows. Change an SOP's agent instructions and the agents that are governed by it change how they work.

Troubleshooting

Problem	What to do
An agent cites a standard vaguely or not at all	The standard is not in the library, or its extract is incomplete. Check Settings → Standards for the OCR and size-cap warnings.
A big PDF imported but looks truncated	It hit the extraction size cap. Split it, or work from the original for the missing part.
Review dates are all wrong	The review cycle is per SOP. Open each one and set Review Cycle (months).
The SOP list is empty	Nobody has initialised it. Click Initialize SOPs from templates.

Next: Integrations and your ERP →