Each revision checked before it is issued. Your document controller approves it.
The agent checks that a new revision has its signatures and the right distribution list, then drafts the register entry. The document controller approves the issue. A superseded revision is marked, not deleted.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for document control takes the checks that come before every issue. Did the named reviewer sign? Does the revision letter follow the last one in the register? Does the distribution list match the rule for that document type? Today a controller works through these by hand for each procedure, drawing and work instruction. The agent prepares the answer, and the controller decides.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
What changes for your document controller
- Each submission arrives with its checks done and any gap named.
- The register entry is drafted, with the reason for the revision.
- Readers get the new revision, and the old one is marked superseded in the same job.
Where a revision starts as an engineering change, the engineering change workflow comes first. The full library is on the workflows page.
One work instruction, from submission to the register.
The document and its revisions are examples. The approval comes before the issue, and the refusal protects the revision it replaces.
- 01Ticketing
Take the submission from the document control queue and receive a credential for this issue only.
- Who approves
- No approval on this step
- On the record
- credential issued · one issue
- 02Documents
Read the submitted work instruction at revision D and its cover sheet.
- Who approves
- No approval on this step
- On the record
- read-submission · allowed
- 03Documents
Check that the named reviewer and approver have signed, and that revision D follows revision C in the register.
- Who approves
- No approval on this step
- On the record
- check-signatures · allowed
- 04Office suite
Compare the distribution list with the rule for work instructions in the register. One work area is missing, and the agent flags it.
- Who approves
- No approval on this step
- On the record
- check-distribution · allowed · one area missing
- 05Documents
Issue revision D to the register. The step waits until the document controller approves it.
- Who approves
- Document controller
- On the record
- issue-revision-d · approved by document controller
- 06Documents
Try to delete revision C from the register. Deleting a controlled document is outside the permission for this job, so the step is refused. Revision C is marked superseded instead.
- Who approves
- No approval on this step
- On the record
- delete-revision-c · refused · outside permission
- 07Email
Send the notice of the new revision to each reader on the distribution list.
- Who approves
- No approval on this step
- On the record
- notify-readers · allowed
- 08Ticketing
Close the submission with a link to the register entry.
- Who approves
- No approval on this step
- On the record
- close-submission · allowed
The systems, by type
We name systems by type. Yours are named in the assessment.
Ticketing
Holds the submission queue. The agent takes one submission and closes it when the issue is done.
Documents
Holds the controlled documents and their cover sheets. The agent reads them and marks a superseded revision.
Office suite
Holds the register and the distribution rules, if you keep them in a spreadsheet.
Carries the notice of each new revision to the readers on the list.
The approval, the refusal, the record
- A person approves: Issue revision D to the register. The step waits until the document controller approves it.Issuing a revision makes it the version people work to, so the controller who answers for the register approves each issue.
- Refused: Try to delete revision C from the register. Deleting a controlled document is outside the permission for this job, so the step is refused. Revision C is marked superseded instead.A superseded revision is the proof of what people worked to before, so the job may mark it superseded but never remove it.
- On the recordEach check and its result, the gap flagged, the issue with the controller’s name, the refused deletion with its reason, and each notice sent.
What goes on the record
- credential issued · one issue
- read-submission · allowed
- check-signatures · allowed
- check-distribution · allowed · one area missing
- issue-revision-d · approved by document controller
- notify-readers · allowed
- close-submission · allowed
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not write or review the content of a document. Your authors and reviewers do.
- It does not set the distribution rules. It checks each submission against the rules you set.
- It does not delete a controlled document.
- It does not replace your document system. It works with it and with your register.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.