Procedures
A policy says what your organisation commits to; a procedure says how people actually carry it out — written, versioned, reviewed, acknowledged and mapped to controls like any other governance document.
A procedure is the operational layer beneath
a policy. Where a policy says "all production changes must be approved", the
procedure tells the change manager what to check, in what order, and what to
record. Procedures follow the same lifecycle as policies — Draft,
In Review, Approved, Retired — and live
under COMPLIANCE in the left menu, at /procedures.
Who uses it
Anyone signed in can read the register. A
Contributor can create a
procedure, edit a draft, run the AI actions, choose reviewers and readers, and
move it through the lifecycle — submit for review, return to draft, revise,
retire and reactivate. Approving, rejecting and deleting take a
Manager or
Admin. Where your organisation has
named approvers for the procedure or its category, the person approving must be
one of them — by person, role or group; where nobody is named, anyone holding
the approve permission can approve. A
Viewer sees everything read-only:
Create Procedure is only rendered from Contributor upwards, and
/procedures/new redirects a Viewer to /unauthorized.
What's on this screen
The register at /procedures is one page with one table. The header
reads Procedures, "Manage operational procedures and SOPs"; on the
right sit a List / Grouped view toggle and the navy
Create Procedure button. Below them is the filter row —
All Statuses, All Levels and
All AI analyses — and, underneath, a
Search procedures... box with a Search button. The
filters combine.
All Statuses also offers Active (not retired), the set
the dashboard's active-procedures tile counts, and, for anyone who can approve,
Pending My Approval — your own approval queue.
All Levels lists strategic, tactical and operational, plus
Unclassified for procedures without a level.
All AI analyses narrows the table to procedures whose AI Enhance
run is queued or running; it is hidden while Pending My Approval is
selected.
The table runs a selection checkbox, Title, Status (a
coloured chip — grey Draft, amber In Review, green
Approved, darker grey Retired), Level (a
pill), Owner, Version, Parent Policy (a
link to that policy), Effective Date, AI analysis,
Updated and Actions, which holds a pencil and an eye.
AI analysis shows the latest AI Enhance run as Queued,
Analysing, Ready or Failed, or a dash
when none has run; while any row is queued or analysing, the table refreshes
itself every ten seconds. The capture was taken as a Contributor in the Meridian
Financial Group demo organisation: approved, in-review and draft procedures,
mostly Operational, each linked to a parent policy, a dash for the
effective date of the draft, and no bin in Actions (that appears
from Manager upwards).
-
Use the
List/Groupedtoggle to switch between the flat table and a register grouped by governance level. The page changes in place. -
Select
Create Procedureto reach the full-page create form at/procedures/new. -
Choose a value in
All Levelsto narrow the table to one governance level; it refetches immediately.All Statusesdoes the same for lifecycle state. -
Choose
AI analysis: queued or runninginAll AI analysesto see only the procedures an AI Enhance run is still working on. -
Type a word into
Search procedures...and selectSearch. Only titles containing that word remain, within whatever the dropdowns filter. -
Select a
Titleto open that procedure on theDocument information & detailstab; clicking elsewhere in the row opens theContenttab instead.
The row actions do the same from the right-hand end: the eye opens the details
tab, the pencil the Content tab. The pencil only appears for users
who can edit procedures; a Manager or Admin also sees a bin, which asks for
confirmation first.
The bin icon and the bulk Delete procedure action take the
procedure out of the register and out of the AI assistant's search index.
Both ask for confirmation first, and neither can be reversed from the
interface. To keep the document on the record while showing it is no longer
in force, use Retire instead.
Creating a procedure
Create Procedure opens a dedicated page, not a popup, headed
Create New Procedure under a
Procedures / Create New Procedure breadcrumb:
Procedure Details and Timeline side by side, with a
Content card beneath. Only Title and
Content are required — each carries a red asterisk.
- Enter a
Title— the name that appears in the register. -
Optionally type a
Category; the placeholder suggestsIT Operations,HRorSecurity. -
Optionally choose a
Parent Policy. The dropdown opens onNone (standalone)and lists your policies; the helper text reads "Optionally link this procedure to the policy it implements." -
Set a
Level. It opens onUnclassified; the helper text explains the hierarchy — strategic sets direction, tactical translates it into standards, operational covers day-to-day work instructions. The level drives theGroupedview. -
In
Timeline, set anEffective Date— when the procedure becomes binding — and adjust theReview Cycle, pre-filled with365days. -
Write the body in
Content: theEdittab has a formatting toolbar (undo, bold, italic, block type, lists, checklists, links, tables, a divider and full screen) and thePreviewtab shows the result. Where your organisation has set a company document template, the editor arrives pre-filled from it — on the captured screen it opens with aPurposeheading — and a note says so until you start typing. SelectCreate Procedureat the foot of the page — the procedure is saved as aDraftand you land on its workspace.
The procedure workspace
The detail page at /procedures/{id} is a tabbed workspace under a
Procedures / [title] breadcrumb. The header carries the title with
its status chip, then a "Version 2.0 • Last updated …" line whose right-hand end
shows the AI status — Ready when idle, progress or an error while a
job runs.
Under that sits one row of labelled buttons: Edit, the lifecycle
action (Submit for Review on a draft, Retire in red on
an approved procedure as here, Reactivate on a retired one),
Export to Word and More, which holds the rest —
Improve Writing, AI Enhance,
Review & Draft, the second lifecycle action (Return to Draft
while in review, Revise once approved),
Upload Word/PDF on a draft, and Help, which explains
each button. On a narrow window the labels give way to icons; hover one, or
reach it by keyboard, to read its name.
The tab row is the workspace: Document information & details,
Content, Required Readers, Audit,
Translations, Version history,
Controls and Evidences. AI result tabs —
Document Review, Improve Writing,
AI Enhance — join the row after Content only once that
action has been run. Opening a procedure without naming a tab lands on
Content. Every tab can be linked to with ?tab=, for
example /procedures/{id}?tab=audit, and the address bar follows the
tab you open. Comments and review requests sit below the tabs, on every tab.
The details tab is an overview: a summary band (title, status, version, owner,
level), a
Next step banner naming what the procedure needs now, who acts and
by when, with shortcuts to the Required Readers and
Audit tabs, and three tiles — Reviewers (open review
requests), Approvers (a procedure has a single approval: "Not yet
submitted for approval", "Awaiting approval" or who approved it) and
Required readers (how many have read the current version, with a
progress bar). On the captured screen the approved procedure's banner reads
"Review the document by its next review date", the Approvers tile
names the approver, and the readers tile shows "7 of 10 read".
Below them sit Edit details and three collapsible cards:
Identity, Planning and Approval with the
Approval History. The next review date in Planning is
the effective date plus the review cycle — on the captured screen, an effective
date of 12 July 2026 gives a review due by 8 January 2027. Then come the
collapsed Changes since last approved version panel; for users who
may read the audit log, Recent activity; any roadmap work that
addresses the procedure; and the action items created from its AI actions. On a
phone everything stacks in one column and each card folds shut when you tap its
title.
-
Select
Editto open the body on theContenttab. It works on aDraftonly; on any other status the button stays in place but greyed out, and its tooltip says the procedure must be inDraft. Beside it sits the lifecycle action for the current status. -
Select
Export to Wordto download the body as a.docx. -
Open
Morefor the AI actions, the second lifecycle action,Upload Word/PDFandHelp.Improve WritingandAI Enhancestay in the menu outsideDraft, greyed out. -
Read the
Next stepbanner; its shortcuts open theRequired ReadersandAudittabs. -
Check the tiles — each links on:
Reviewersto the collaboration panel below the tabs,Approversto theApprovalcard,Required readerstoAudit. -
Select
Edit detailsto change the title, level, category, parent policy, effective date and review cycle in place, in any status. The procedure text itself is edited on theContenttab.
Choosing reviewers, approvers and readers
The Required Readers tab has two parts. At the top,
Reviewers and approvers sets who reviews the procedure before
approval and who approves it. Each card carries a label saying where its list
comes from: From this document, From the category or
Organisation default. The procedure's own list wins; when it is
empty, the category default applies. Changes apply from the next submission for
review. Further down, Required Readers holds the audience that must
read and acknowledge the procedure. The capture was taken as a Manager on an
approved procedure with no reviewers or approvers of its own, so both cards show
Organisation default.
-
Check the source label on each card. It reads
From this documentonce the procedure has its own list, andUnsaved changeswhile you are editing it;Use the category defaultat the foot of the card hands the list back to the category. -
Under
Reviewers, choose a group, role or person inChoose a group, role or person…and selectAdd. A group becomes one review request per member. Set theRule—Everyone must agreeorAt least a minimum number— and theDeadline (days), 14 on the captured screen. A bar appears withDiscardandSaveuntil you save the change. -
Select
Ask reviewers nowto start a review round with the current list. A confirmation counts the review requests sent. The button shows only where collaboration is part of your licence, and not while there are unsaved changes. -
Under
Approvers, add who approves, in order. Only people who hold the approve permission are offered. With nobody named, the card reads "No approvers are set: anyone who holds the approve permission can approve." -
Leave
Owner does not approve own documentticked: the owner then approves only when no other approver exists and the organisation allows it. -
Scroll to
Required Readers.Who must read thislists the audience as chips —Role: ManagerandRole: Contributoron the captured screen. Remove one with its cross.
The rest of the readers section sits below the captured area:
-
Type in
Add readersto search groups, departments, roles and people, and tick the ones to add. Matches come grouped — whole organisation, roles, people, Aegis groups, Entra groups and HR departments — each with its member count. Groups and departments stay dynamic: people who join or leave are picked up every night. An audience holds at most 100 sources. -
Read
Preview before saving: the total, how many read via login, via a read link, and how many cannot be reached. People without an e-mail address are listed withNo invitation; they never block saving or publishing. -
Select
Save Required Readers. A confirmation appears, theMust Readlist on theAudittab shows who still has to read the current version, and theRequired readerstile counts them.
Approvers cannot change while the procedure is in review; send it back to
Draft
first. A procedure takes a single approval, so an approver rule that would need
several approvals is refused when you save. Without permission to edit the
procedure, the readers section says "You can't change who must read this
procedure. The Audit tab shows who has read it." instead of showing the form.
Reader view — confirming a read without a login
A required reader with no Aegis account reads and confirms the procedure through
a single-use read link, exactly as they do for a policy. When the procedure
reaches Approved, Aegis e-mails invitation E1 with
a link that works once and, by default, for 24 hours and opens the last approved
version. Where the approved version carries an owner-accepted change note, E1
and the reader view show it under What changed in this version; the
reminder (E2) does not repeat it.
On the document view the reader selects Send code, enters the
six-digit Confirmation code that Aegis e-mails them, and selects
Confirm. Before they confirm, the panel states how the confirmation
is recorded: "When you confirm, your IP address is stored as evidence of your
acknowledgment and kept for 24 months on the basis of our legitimate interest
(proof of acknowledgment)." Twenty-four months is the fixed default term, not a
self-service setting in the app; after it lapses only the IP is cleared, while
the confirmation itself is kept as lasting proof. On success a "Reading
confirmed" page shows the version, time and reference, and a receipt is
e-mailed. A lapsed link opens the Link expired or invalid page with
a Request a new link form, and re-approving or requesting a new
link extends the reader's existing invitation rather than issuing a second one.
The full walkthrough, with the IP-retention detail, is in
Policies.
Review and approval
Lifecycle transitions live in the toolbar; the decision itself is taken on the details tab.
-
From a
Draft, selectSubmit for Review: the chip turns amber,Approval StatusbecomesAwaiting Approval, and aSubmitted for Reviewentry joins the history. If nobody but the owner could approve it, the submission is refused: a notice above the toolbar, headed "This document cannot be submitted for review yet", explains why and offersSet approvers. -
An eligible approver opens the details tab, where the
APPROVAL STATUScard names the designated approvers, and selectsReview & Approve. TheReview Proceduredialog offersApprove(optional comments) orReject, which needs a reason — the owner is notified with it and the procedure returns toDraft. -
On an
Approvedprocedure the toolbar showsRetire, in red, andMoreholdsRevise— a change summary, a snapshot into the version history, a version bump, back toDraft.Reactivatereturns a retired procedure toDraft. WhileIn Review, anyone who can edit may pull it back withReturn to Draft, also underMore.
| Status | What it means | Who can move it on |
|---|---|---|
Draft |
Being written; the only editable status. | Contributor+ submits for review. |
In Review |
Awaiting a decision. |
A designated approver (Manager+) approves or rejects;
Contributor+ can
return it to Draft.
|
Approved |
Published and binding. | Contributor+ revises or retires it. |
Retired |
Kept for the record, not in force. | Contributor+ can reactivate it. |
Acknowledgements, controls and evidence
For users who can edit the procedure, the Audit tab opens with the
required-readers audit: a version picker, tiles for required, read, open,
overdue, older-version and exempt readers, a progress bar, filters, a per-person
table and a reading timeline per person, with reminders and resent links;
exemptions and the evidence export are offered only to those allowed to manage
readers. It works as it does for policies — see
Policies. A Viewer does not see it.
The Read By section below it is always there. Anyone signed in who
has not yet confirmed sees a Mark as Read button; selecting it
replaces the button with "You have acknowledged this procedure" and adds them to
the list with the date and time. Once a required reader list is saved, the
section also shows a running count — "3 of 8 acknowledged" — above a must-read
list naming who is still outstanding. Someone who confirmed an older version is
asked to Re-confirm as Read once the procedure has been approved
again. Four tabs then connect the procedure outwards.
-
Controlsholds the control mappings. Link a framework control and the procedure counts towards it in Compliance frameworks; an unmapped procedure is documentation only. -
Evidenceslists linked evidence — name, type, owner and valid-until, with an expired marker where that date has passed. You link an existing item from the Evidence locker rather than uploading a file here. -
Translations: where your licence includes document translation, request an AI (DeepL) translation per language or all at once. Results appear as language tabs onContent, and one whose source has since changed is flagged as out of date. E-mail addresses, phone numbers and other personal data are replaced by placeholders before the text goes to DeepL and put back in the translation, so they never leave Aegis. Secrets (API keys, passwords, access tokens, connection strings, private keys) and classification banners such as "STRICTLY CONFIDENTIAL" stop the translation, and the panel names what it found. While DeepL is retrying, the panel says so with the attempt number and the last error; a failure reads "Translation failed:" followed by the reason. -
Version historylists every version with its timestamp — what the procedure said when a given incident or audit happened. You can compare two versions side by side, and restore an earlier one, which is written as a new version rather than overwriting the current text.
The AI assist
Three AI actions sit in the More menu, each parking its result on
its own tab instead of changing the procedure.
Improve Writing (draft only) rewrites the body section by section
for clarity. AI Enhance (draft only) suggests improvements,
including framework controls it thinks the procedure should map to.
Review & Draft works in any status: it reads the procedure
alongside its parent policy and mapped controls, checks scope, steps and review
freshness, and drafts tightened steps for the gaps it finds.
One job runs at a time: the header status text shows progress and the other AI
buttons grey out, though Export to Word stays available. Every AI
action is logged against your organisation's AI usage, and a person reviews each
suggestion and decides — the AI never edits, approves, publishes or retires a
procedure on its own.
Using a Review & Draft result
The Document Review tab keeps the last result, dated "Reviewed …",
with a note that it reasons over internal records only and is a proposal, not a
binding decision. Three buttons sit above it for users who can edit.
Apply drafted steps opens a confirmation that shows the exact text
it will write; confirming replaces the procedure body with the drafted steps and
keeps the current body as a version. It works on a Draft only, and
if the procedure changed while the review sat in the tab, Aegis asks you to
reload and run the review again. Run again starts a fresh review,
and Dismiss findings
clears the result so the tab disappears until the next run.
Reviewing an AI Enhance result
While an AI Enhance run waits for a free slot, the status line and
the AI Enhance tab read "AI Enhance is queued for this procedure
and starts when an earlier analysis finishes…"; while it runs, the tab carries a
pulsing dot. On the tab, Generate on an improvement opens a
Preview Generated Content panel, and
Add to Procedure appends the text to the body. A suggestion that
fixes a contradiction, a duplicate or the structure of one section replaces that
section instead: the preview names the section and shows a before-and-after
comparison, and Replace section overwrites that heading's section,
subsections included, and nothing else. If the heading is missing, duplicated or
too long to review, the preview explains why and offers no apply; if the
procedure or that section has changed since the preview, generate the suggestion
again.
Controls already linked to the procedure are not proposed again; when nothing
new remains, the panel reads "No new framework controls to propose — the
relevant controls are already linked." A citation that covers several controls
offers one Link per control, and one that is not in the Aegis
catalogue says so, so you link a control by hand from the
Controls tab. There, + Link Control searches a page at
a time: "Showing n of total matching controls" with Show more for
the next page.
Tips and limits
-
The parent policy link is optional and can be set later with
Edit details.Level, left atUnclassified, puts everything in oneGroupedheading. -
To change an approved procedure, use
ReviseunderMore: it keeps the approved text in the version history and sends the new text back around the review loop. -
The Word round-trip exports
.docxand accepts.docxor.pdfback, on a draft only. An upload first shows the changes against the current text before anything is replaced.Categoryis free text with no picklist behind it. -
Selecting rows in the register gives bulk
Change Status,Exportand (from Manager)Delete procedure; a bulk change toApprovedskips anything that is not in review or outside your approver rights, and reports how many it approved and how many it skipped, with the reason, for example "currently Draft; only In Review can be changed to this status". -
If you cannot see
Create Procedure, you hold the Viewer role — ask an administrator to raise it.
Where this connects
Procedures implement Policies and satisfy controls in Compliance frameworks. Proof that one is followed belongs in Evidence; for records attached to a live event, see Playbooks. Review requests and comments are covered in Collaboration. Approvals, acknowledgements and status changes appear in the Audit log; overdue reviews surface in Action items.