Audit Engagements
An engagement is an auditor reviewing evidence your organisation already holds. The auditor may be external, or one of your own people acting as the auditor. The review is always seen from a mapped framework, such as Cyber Essentials 3.3 or ISO 27001.
An engagement covers one or more frameworks. It pulls in the SCF controls that map to them, and the evidence objects that support those controls. The auditor tests each evidence object on a review board, raises queries, and accepts or sends back the evidence. A dashboard shows how far the audit has got.
Find it in the app under Engagements, in the Admin section of the sidebar. An external auditor who is not a member of your organisation lands on My engagements after signing in, which lists only the engagements they have been granted.
Creating an engagement
Section titled “Creating an engagement”Click + New Engagement and fill in the drawer:
- Name — how you’ll recognise this audit, e.g. ISO 27001:2022 Certification — FY26.
- Frameworks — search and tick one or more. Each row shows the framework’s full name, its key, and how many SCF controls map to it. The frameworks you pick decide which controls come into the engagement.
- Audit period — the start and end of the window evidence is matched against:
- SOC 2 Type 2 — use the full observation period.
- ISO 27001 — use the surveillance year.
- You can leave the dates blank and set them later by editing the engagement.
On save, the engagement fixes its scope: a snapshot of every control mapped to the chosen frameworks, tagged with how your organisation scoped each one. The snapshot is the audit assertion. Evidence and control status stay live, but which controls are in, and why any were excluded, are captured at that moment.
At the same time the engagement creates one review card for every evidence object that maps to an in-scope control. If a control is brought into scope later, its evidence objects get cards the next time the board or dashboard is loaded. Cards are never deleted. A card whose controls all leave scope, or are retired in the catalog, drops off the board.
Each engagement in the list has these actions: Review board, Dashboard, View scope, Present, Auditors and Queries.
View scope
Section titled “View scope”The full set of framework-mapped controls, grouped by scope status:
| Group | Meaning |
|---|---|
| In scope | A control your organisation selected |
| Excluded | A control your organisation put out of scope on purpose. The exclusion justification is shown inline — this is what an auditor reviews to understand why a mapped control was excluded |
| Not tracked | Mapped to the framework but not yet in your control set |
Present
Section titled “Present”The controls re-ordered under the chosen framework’s own clause or Annex A identifiers. Switch frameworks with the pills at the top. Each control shows its live implementation status, owner and evidence. Evidence chips are green when the artifact was uploaded inside the audit window and muted when it was not. Nothing is hidden; the auditor decides. Control queries show against their control here.
Auditors
Section titled “Auditors”Manage who can review this engagement. An org admin grants access and chooses the kind:
- External auditor — someone outside your organisation, picked from your external auditor list. They see this engagement only: its controls, evidence, cards, queries and the shared discussion. Nothing else in your organisation. A member of your organisation cannot be granted as external; grant them as internal.
- Internal auditor — a member of your organisation acting as the auditor. The person must already be a member, or the grant is refused. See Internal auditors.
Revoking a grant ends access at once. Granting the same person again reactivates their old grant. A grant to an external auditor who has not signed in yet shows as Invited and turns Active at their first sign-in. External grants are revoked automatically the day after the engagement’s end date.
Inviting an external auditor
Section titled “Inviting an external auditor”Member invitations are locked to your organisation’s email domain, and that rule is unchanged for viewers, editors and admins. An external auditor is the one exception: invite them from Users → Invite User → Role: External auditor, or from the engagement’s Auditors drawer (Invite a new auditor…).
- Any company email domain is accepted. Public mail (Gmail, Outlook, iCloud and similar) is refused.
- They join your organisation’s external auditor list (under Users), not the organisation. They take no seat and see nothing until assigned to an engagement.
- On the bundled sign-in an account is created and a temporary password is shown once.
- Someone who is already a member is refused; grant them as an internal auditor.
- The audit log records the invitation and that the domain rule was exempted for it.
Review board
Section titled “Review board”The board is where the audit happens. Open it with Review board on the engagement. There is one tab per framework in the engagement; the clause chips and the clause filter follow the tab.
What a card is
Section titled “What a card is”A card is an evidence object: an entry from the SCF Evidence Request List, such as E-IAC-07. The auditor tests evidence objects, so they are the unit of review. Each card shows:
- the evidence id and title;
- the SCF controls it supports, and the clauses of the current framework that those controls map to;
- the number of files held, and how many of them fall inside the audit window;
- the number of open queries on it;
- the AI verdict — the worst existing AI assessment among its in-window files (no new AI call is made);
- the reviewer (an auditor) and the evidence owner.
How collection is going (files, in-window counts) sits on the card. It is never a column. A card only appears on a framework’s tab when at least one of its controls maps to a clause in that framework.
The five stages
Section titled “The five stages”| Stage | Meaning |
|---|---|
| Open | Not yet tested by the auditor |
| In progress | The auditor is testing the evidence |
| Action required | The auditor needs more from the organisation |
| Submitted | The organisation has responded and is waiting for the auditor |
| Accepted | The auditor accepts the evidence |
Who moves a card where
Section titled “Who moves a card where”These are the only moves the system allows. Any other move is refused.
| From | To | Who | Note |
|---|---|---|---|
| Open | In progress | Auditor | Not needed |
| In progress | Action required | Auditor | Required — tell the organisation what to do |
| In progress | Accepted | Auditor | Not needed |
| Action required | Submitted | Org editor or admin | Required — a response note, plus at least one linked file or a reason why there is none |
| Submitted | In progress | Auditor | Not needed |
| Submitted | Action required | Auditor | Required |
| Submitted | Accepted | Auditor | Not needed |
| Accepted | In progress | Auditor | Required — the reason for reopening |
“Auditor” means anyone holding an active grant on this engagement, external or internal. An org viewer cannot move cards. A card never goes back to Open.
When the organisation submits, the system also posts the response note and the names of the linked files as a shared comment on the card, so the auditor sees it in the discussion. Files can be linked from those already held for the evidence object, or uploaded from the response form.
Every move is recorded in the card’s History, with who made it, whether they acted as auditor or organisation, and the note. It is also written to the organisation’s audit log.
Moving a card
Section titled “Moving a card”There are three ways, and all three offer only the moves you are allowed:
- Buttons in the card panel: Start testing, Action required, Accept evidence, and the Respond to the auditor form for the organisation.
- Drag and drop between columns. A column that will not take the card does not light up.
- Move to… on each card, for keyboard use. Arrow keys move through the menu, Enter chooses, Escape closes it.
A move that needs a note opens the card panel with the form ready; finish it there. The board updates at once and goes back if the server refuses. If someone else moved the card after you loaded the board, the move is refused and the message tells you where the card is now. Reload and try again.
Filters and “My cards”
Section titled “Filters and “My cards””Filter by search (evidence id, title, control or clause), clause, SCF control, AI verdict, reviewer (including Unassigned) and Has open queries.
My cards shows the cards where you are the reviewer and, for org members, the cards you own as evidence owner.
Queries
Section titled “Queries”A query is a formal question with a status. Use it when an answer is needed and someone has to say when it is settled. It is the audit’s question log.
Two kinds
Section titled “Two kinds”- On an evidence object — raised from the card panel’s Queries section. Use it to ask about that evidence, for example for a newer copy of a document.
- On a control — raised from the No evidence — resolve by query strip above the board, for a control that has no evidence object. The engagement’s Queries action also raises control queries by SCF id.
A query is about exactly one of these, never both. A control query is refused unless the control is in scope for this engagement and not retired.
Lifecycle
Section titled “Lifecycle”A query is Open, Answered or Closed.
| From | To | What causes it | Who can do it |
|---|---|---|---|
| (new) | Open | Raise a query | Anyone with access to the engagement |
| Open | Answered | Post an answer | Anyone with access to the engagement |
| Answered | Answered | Post another answer (no change) | Anyone with access to the engagement |
| Open or Answered | Closed | Close query | An auditor with an active grant ¹ |
| Answered | Open | Set back to Open (API only; the panel has no button for it) | Anyone with access to the engagement |
| Closed | Open | Reopen query | An auditor with an active grant |
¹ An internal auditor cannot close a control query when they wrote its latest answer. Another auditor must close it.
The organisation answers; the auditor decides. Only someone with an active auditor grant on the engagement can close a query or reopen a closed one. This matters because closing a control query can mark a control with no evidence object Accepted.
A response to a closed query does not reopen it. The query stays Closed. The panel hides the answer box on a closed query; reopen it first if there is more to say.
Raising a query does not move the card
Section titled “Raising a query does not move the card”A query never changes a card’s stage. If the organisation needs to do something, the auditor must also set the card to Action required with a note. After an auditor raises a query on an evidence object, the panel reminds them of this.
Query, Action required or comment?
Section titled “Query, Action required or comment?”| Use | When |
|---|---|
| Action required | The organisation must act before the evidence can pass, for example supply a newer file. The card moves, the owner is notified, and the organisation must respond with a note and files to move it on |
| Query | You need an answer that is tracked to closure, and the card’s stage should not change. Also the only way to resolve a control with no evidence object |
| Discussion comment | Conversation: context, a quick clarification, a mention of a colleague. No status and nothing to close |
Controls with no evidence object
Section titled “Controls with no evidence object”Some in-scope controls have no evidence object mapped to them in the catalog. They have no card. They are listed in the strip above the board and on the dashboard.
Such a control is Open until it is resolved by a control-level query. It counts as Accepted once it has at least one Closed control-level query and none that are Open or Answered. Raising a new query, or reopening a closed one, puts it back to Open. That status then rolls up to the control’s clauses like any other control.
A control that does have evidence objects ignores its control-level queries for its status; its status comes from its cards only.
Worked example 1: a newer firewall review
Section titled “Worked example 1: a newer firewall review”The auditor is testing E-NET-04 (Network Security Controls). The only firewall rule review held is from before the audit window.
- The auditor opens the card and clicks Start testing. The card moves to In progress.
- The auditor raises a query on the card: “Is there a firewall rule review from inside the audit period?” The evidence owner is notified. The card stays In progress.
- The owner answers: “Yes, March’s review. Uploading it now.” The query is Answered.
- The auditor wants the file before testing further, so moves the card to Action required with the note “Upload the March firewall review.” The owner is notified.
- The owner opens the card, uploads the March file in Respond to the auditor, writes a note and submits. The card is Submitted and the reviewer is notified.
- The auditor checks the file, closes the query and clicks Accept evidence.
If step 4 had been skipped, the card would have stayed In progress with an Answered query, and nothing would have asked the owner to upload anything.
Worked example 2: a control with no evidence object
Section titled “Worked example 2: a control with no evidence object”Say control GOV-02 maps to a Cyber Essentials clause but no evidence object maps to it.
- On the board the auditor opens
GOV-02in the No evidence strip and raises a query: “How is this policy published to staff?” Org admins are notified. The control is Open. - An org admin answers with a link to the intranet page. The query is Answered. The control is still Open.
- The auditor is satisfied and closes the query. The control now counts as Accepted on the dashboard, and so do its clauses if their other controls are Accepted.
- If the auditor later reopens the query, the control is Open again.
Discussion
Section titled “Discussion”Each card has a discussion thread with replies, @mentions, edits and soft delete.
- Shared comments are seen by everyone with access to the engagement, auditors included. This is the default.
- Internal notes are for the organisation only, and are marked Organisation only — not visible to the auditor.
A reply takes its parent’s visibility. You can mention only people with access to the engagement; in an internal note, only org members who hold no auditor grant. A mention notifies that person.
You can edit and delete your own comments. Edits keep the earlier version in the comment’s history. An org admin, acting as the organisation, can delete anyone’s comment.
Owners, reviewers and notifications
Section titled “Owners, reviewers and notifications”Evidence owner. Each card shows who owns the evidence for the organisation. It comes from the organisation’s evidence tracking for that evidence id: the assigned person, then the accountable team (its primary and delegate), then the org admins. If your organisation does not track that evidence id, the card shows Unowned → org admins. Evidence is owned by a team, not assigned to a person, so an org admin sets the card’s Accountable team from the panel (the same team assignment as on the evidence screens). If a person was assigned to the evidence before team ownership, the admin can clear them and hand the evidence back to its team; a new person cannot be assigned. Auditors cannot change the owner.
Reviewer. The auditor reviewing a card. An auditor or an org admin can assign or clear it. The reviewer must hold an active auditor grant on the engagement.
Notifications. Each of these appears in the bell and is emailed, subject to the person’s notification preferences. Messages show people’s names, never their email addresses.
| Event | Who is notified |
|---|---|
| Card moved to Action required | The evidence owner (owner chain above), and the accountable team’s primary and delegate as well, even when a person is assigned. Not the auditor who moved it |
| Card moved to Submitted | The assigned reviewer, if they still hold an active grant; otherwise every active auditor on the engagement |
| Reviewer assigned | The new reviewer |
| Query raised on an evidence object | The evidence owner. Not the person who raised it |
| Query raised on a control | Org admins. Not the person who raised it |
| Query answered | The person who raised it, unless they wrote the answer, and only while they still have access to the engagement |
| Query closed or reopened | Nobody — check the query list |
| Mention in a comment | The people mentioned, except the author |
External auditors receive these notifications too, limited to their engagement. Clicking one opens the card.
Internal auditors
Section titled “Internal auditors”An internal auditor is an org member given an auditor grant of kind internal. They can make every auditor move on the board.
They are also an org member, so as an editor or admin they can respond for the organisation. Segregation of duties stops them accepting evidence where they are not independent. An internal auditor cannot accept an evidence object when:
- they own it (they are the assigned person or the owner on its tracking record);
- they are on a team accountable for it; or
- they made the latest organisation response on it (they moved it to Submitted).
The board does not offer Accept in those cases, and the server refuses it with a message giving the reason. Another auditor must accept it. External auditors are never blocked by this rule.
Dashboard
Section titled “Dashboard”Open it with Dashboard on the engagement. It shows one framework at a time. Every number comes from the server.
| Item | Meaning |
|---|---|
| Evidence accepted | Cards in Accepted, out of all cards on this framework’s tab |
| Clauses accepted | Clauses whose rolled-up status is Accepted, as a share of the framework’s clauses |
| Controls accepted | In-scope controls with a clause in this framework whose rolled-up status is Accepted |
| Action required | Cards in Action required |
| Open queries | Queries in Open status, on evidence objects on this tab plus on this tab’s controls. Answered queries are not counted |
| Stacked bars | Evidence, controls and clauses by stage |
| Clause grid | Each clause’s rolled-up status, grouped by the first part of its id |
| Evidence needing the organisation | Cards in Action required, with the controls and clauses each one holds back. Click one to open it on the board |
| Controls with no evidence object | Resolved by control-level query; see above |
| Timeline | Audit window opens and closes (from the engagement dates); testing started (first card move); all evidence tested (no card left in Open or In progress); all clauses accepted |
The roll-up rule
Section titled “The roll-up rule”The same rule turns a control’s cards into a control status, and a clause’s controls into a clause status:
- Any item in Action required → Action required.
- Otherwise, all items Accepted → Accepted.
- Otherwise, all items Submitted or Accepted → Submitted.
- Otherwise, any item past Open → In progress.
- Otherwise → Open.
So one evidence object in Action required holds its control in Action required, and that control holds its clauses there too.
Roles at a glance
Section titled “Roles at a glance”| Action | Org viewer | Org editor | Org admin | External auditor | Internal auditor |
|---|---|---|---|---|---|
| Create or edit an engagement | ✓ | ✓ | |||
| Delete a draft engagement | ✓ | ||||
| View scope, Present, board, dashboard | ✓ | ✓ | ✓ | ✓ | ✓ |
| List auditors | ✓ | ✓ | ✓ | ✓ ¹ | |
| Grant or revoke auditors | ✓ | ✓ ¹ | |||
| Auditor moves on the board | ✓ | ✓ ² | |||
| Submit the organisation’s response | ✓ | ✓ | ✓ ¹ | ||
| Assign a reviewer | ✓ | ✓ | ✓ | ||
| Set the accountable team | ✓ | ||||
| Raise or answer queries | ✓ | ✓ | ✓ | ✓ | ✓ |
| Close or reopen queries | ✓ | ✓ ³ | |||
| Shared comments | ✓ | ✓ | ✓ | ✓ | ✓ |
| See and write internal notes | ✓ | ✓ | ✓ | ||
| Delete anyone’s comment | ✓ |
¹ Through their org role: an internal auditor is also an org member and keeps the rights of that role. ² Except Accept where segregation of duties applies. ³ Except closing a control query whose latest answer they wrote.
Only a draft engagement can be deleted.
API reference
Section titled “API reference”Every route is under /api and needs a bearer token. Below, {base} stands for /api/organizations/{org_id}/engagements/{engagement_id}.
“Engagement access” means an org member (viewer or higher) or the holder of an active auditor grant on this engagement. Without it every engagement route returns 404, never 403, so a stranger cannot tell whether the engagement exists.
Errors: 404 not found or no access; 403 signed in with access but not allowed this action; 409 the move is not allowed from the current state, or the record changed; 422 a required field or note is missing or invalid; 400 an unknown value.
Engagements and auditors
Section titled “Engagements and auditors”| Method | Path | Who | What it does |
|---|---|---|---|
| GET | /api/organizations/{org_id}/engagements | Org viewer+ | List engagements (?status=) |
| POST | /api/organizations/{org_id}/engagements | Org editor+ | Create; fixes scope and creates cards |
| GET | {base} | Engagement access | One engagement |
| PATCH | {base} | Org editor+ | Update name, frameworks, status, dates |
| DELETE | {base} | Org admin | Delete a draft engagement (409 if not draft) |
| GET | {base}/scope | Engagement access | Fixed scope with badges |
| GET | {base}/presentation?framework= | Engagement access | Controls under the framework’s clauses |
| GET | {base}/auditors | Org viewer+ | List auditor grants |
| POST | {base}/auditors | Org admin | Grant {user_id, kind}; kind is external (default) or internal (422 if not a member) |
| DELETE | {base}/auditors/{auditor_id} | Org admin | Revoke a grant |
| GET | /api/my-engagements | Signed-in user | Engagements where you hold an active grant |
Review board
Section titled “Review board”| Method | Path | Who | What it does |
|---|---|---|---|
| GET | {base}/evidence-reviews | Engagement access | The board for one framework: cards, no-evidence controls, counts, filter options and what you may do. Query: framework, status, clause, scf_id, ai_verdict, has_open_queries, reviewer (user id or none), search, mine |
| GET | {base}/evidence-reviews/{evidence_id} | Engagement access | One card with its files, last decision and catalog text |
| POST | {base}/evidence-reviews/{evidence_id}/status | Per the move table | Move a card. Body: to_status, optional from_status, note, artifact_file_ids, no_artifact_reason |
| PUT | {base}/evidence-reviews/{evidence_id}/reviewer | Auditor or org admin | Assign {user_id} or clear (null) the reviewer |
| GET | {base}/evidence-reviews/{evidence_id}/events | Engagement access | The card’s history, oldest first |
| GET | {base}/evidence-reviews/{evidence_id}/files/{file_id} | Engagement access | A signed download link for one file |
| GET | {base}/review-people | Engagement access | Active auditors and org members, names only |
| GET | {base}/review-dashboard?framework= | Engagement access | The dashboard roll-up |
Send from_status with the stage you saw. If the card has moved since, the request fails with 409 and nothing changes. Leave it out to skip the check.
Queries
Section titled “Queries”| Method | Path | Who | What it does |
|---|---|---|---|
| GET | {base}/queries | Engagement access | List queries. Query: scf_id, evidence_id, status |
| POST | {base}/queries | Engagement access | Raise. Body: title, body, and exactly one of scf_id or evidence_id. Does not move the card |
| GET | {base}/queries/{query_id} | Engagement access | One query with its responses |
| POST | {base}/queries/{query_id}/responses | Engagement access | Answer {content}. Open → Answered; a closed query stays Closed |
| PATCH | {base}/queries/{query_id} | Close or reopen: active auditor grant | Set {status}: close, reopen, or answered → open |
Discussion
Section titled “Discussion”Paths are under {base}/evidence-reviews/{evidence_id}/comments.
| Method | Path | Who | What it does |
|---|---|---|---|
| GET | ?visibility=shared or ?visibility=internal | Engagement access; internal only for org members without a grant | The thread, oldest first |
| GET | /counts | Engagement access | shared, plus internal only for those who may see it |
| POST | (none) | Engagement access | Post {content, visibility, parent_comment_id, mentions} |
| PATCH | /{comment_id} | Author | Edit; keeps the old version |
| DELETE | /{comment_id} | Author, or org admin without a grant | Soft delete |
| GET | /{comment_id}/history | Engagement access | Earlier versions, newest first |
An internal note is a 404 to an auditor on every route above, exactly as if it did not exist.
MCP server
Section titled “MCP server”The SCF MCP server has tools for engagements, scope, presentation, auditors and control queries. It does not yet cover queries on an evidence object, the kind of an auditor grant (every grant it makes is external), the review board, card moves, reviewers, card history, the dashboard or the discussion. For those, use the web app or the API.
Notes & current limitations
Section titled “Notes & current limitations”- Evidence window uses the file’s upload date as a stand-in for when the evidence is from. This suits ISO’s last-period framing; a separate effective date per file, for SOC 2 Type 2, is planned.
- Clause groups on the dashboard are labelled by the first part of the clause id (for example
A,CC3, or3for Cyber Essentials3-BP4). The catalog holds clause ids only, with no section names. - Framework outline comes from the controls that map to the framework, so a clause no control maps to does not appear.
- Retired controls drop out of an engagement’s board and dashboard, even if they were in scope when it was created.
- Queries: closing and reopening send no notification.
- Download links for evidence files are valid for 15 minutes once issued, including after the auditor’s grant is revoked.
- Framework and control pickers take identifiers directly; friendlier pickers are planned.
Related Guides
Section titled “Related Guides”- Framework Management — activating and mapping frameworks
- Evidence Management — collecting the evidence auditors review
- Email Notifications — who is emailed for each engagement event
- Consultant Portal — managing multiple client organisations
