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).

  1. Use the List / Grouped toggle to switch between the flat table and a register grouped by governance level. The page changes in place.
  2. Select Create Procedure to reach the full-page create form at /procedures/new.
  3. Choose a value in All Levels to narrow the table to one governance level; it refetches immediately. All Statuses does the same for lifecycle state.
  4. Choose AI analysis: queued or running in All AI analyses to see only the procedures an AI Enhance run is still working on.
  5. Type a word into Search procedures... and select Search. Only titles containing that word remain, within whatever the dropdowns filter.
  6. Select a Title to open that procedure on the Document information & details tab; clicking elsewhere in the row opens the Content tab instead.
The Procedures register with its view toggle, filters and table — /procedures.
The Procedures register with its view toggle, filters and table — /procedures.

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.

Deletion cannot be undone from the app

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.

  1. Enter a Title — the name that appears in the register.
  2. Optionally type a Category; the placeholder suggests IT Operations, HR or Security.
  3. Optionally choose a Parent Policy. The dropdown opens on None (standalone) and lists your policies; the helper text reads "Optionally link this procedure to the policy it implements."
  4. Set a Level. It opens on Unclassified; the helper text explains the hierarchy — strategic sets direction, tactical translates it into standards, operational covers day-to-day work instructions. The level drives the Grouped view.
  5. In Timeline, set an Effective Date — when the procedure becomes binding — and adjust the Review Cycle, pre-filled with 365 days.
  6. Write the body in Content: the Edit tab has a formatting toolbar (undo, bold, italic, block type, lists, checklists, links, tables, a divider and full screen) and the Preview tab 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 a Purpose heading — and a note says so until you start typing. Select Create Procedure at the foot of the page — the procedure is saved as a Draft and you land on its workspace.
The full-page procedure create form — /procedures/new.
The full-page procedure create form — /procedures/new.

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.

  1. Select Edit to open the body on the Content tab. It works on a Draft only; on any other status the button stays in place but greyed out, and its tooltip says the procedure must be in Draft. Beside it sits the lifecycle action for the current status.
  2. Select Export to Word to download the body as a .docx.
  3. Open More for the AI actions, the second lifecycle action, Upload Word/PDF and Help. Improve Writing and AI Enhance stay in the menu outside Draft, greyed out.
  4. Read the Next step banner; its shortcuts open the Required Readers and Audit tabs.
  5. Check the tiles — each links on: Reviewers to the collaboration panel below the tabs, Approvers to the Approval card, Required readers to Audit.
  6. Select Edit details to change the title, level, category, parent policy, effective date and review cycle in place, in any status. The procedure text itself is edited on the Content tab.
An approved procedure on its Document information & details tab — /procedures/[id].
An approved procedure on its Document information & details tab — /procedures/[id].

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.

  1. Check the source label on each card. It reads From this document once the procedure has its own list, and Unsaved changes while you are editing it; Use the category default at the foot of the card hands the list back to the category.
  2. Under Reviewers, choose a group, role or person in Choose a group, role or person… and select Add. A group becomes one review request per member. Set the Rule — Everyone must agree or At least a minimum number — and the Deadline (days), 14 on the captured screen. A bar appears with Discard and Save until you save the change.
  3. Select Ask reviewers now to 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.
  4. 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."
  5. Leave Owner does not approve own document ticked: the owner then approves only when no other approver exists and the organisation allows it.
  6. Scroll to Required Readers. Who must read this lists the audience as chips — Role: Manager and Role: Contributor on the captured screen. Remove one with its cross.
Reviewers, approvers and required readers of a procedure — /procedures/[id]?tab=required-readers.
Reviewers, approvers and required readers of a procedure — /procedures/[id]?tab=required-readers.

The rest of the readers section sits below the captured area:

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.

  1. From a Draft, select Submit for Review: the chip turns amber, Approval Status becomes Awaiting Approval, and a Submitted for Review entry 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 offers Set approvers.
  2. An eligible approver opens the details tab, where the APPROVAL STATUS card names the designated approvers, and selects Review & Approve. The Review Procedure dialog offers Approve (optional comments) or Reject, which needs a reason — the owner is notified with it and the procedure returns to Draft.
  3. On an Approved procedure the toolbar shows Retire, in red, and More holds Revise — a change summary, a snapshot into the version history, a version bump, back to Draft. Reactivate returns a retired procedure to Draft. While In Review, anyone who can edit may pull it back with Return to Draft, also under More.
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.

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

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.