For each in-scope process from Step 3: generate or import the narrative and flowchart, accept them, then map the risks, controls and systems behind the process.
1
Process Setup and Generate
The process, its context, and the narrative + flowchart themselves
Picked from the Step 3 process list — free typing is off. If the process isn't listed, add it in Step 3 first.
Descriptive only — where this process mainly happens.
Select a process to see its Step 3 entity scope.
No file selected
Documents are extracted in your browser and appended to the process description above — nothing is overwritten. Excel files: save the sheet as CSV first (or paste the rows).
Import a narrative or flowchart
From this process's Engagement File entries (PN-/FC-), or from a file — a narrative document (.docx / .pdf) or a flowchart file (.drawio / .svg). You see a full preview first; nothing is saved from the preview. Imported output goes through the same consistency check and AI-warnings gate, and is marked “Imported”.
Building your flowchart...
Analysing process and generating diagram
📊 Visual Diagram
📄 Process Narrative
⚠️ Risks & Controls
🔀
Your diagram will appear here
Fill in the process details above and click “Generate” to build a visual swimlane diagram.
✎ Edit Diagram
Rename steps, change symbol type, lane/actor and control ID, add labelled decisions, drag steps between lanes, remove or reorder steps. Applying re-renders through the premium swimlane layout, and every export uses the edited version.
📄
Process narrative will appear here
The narrative provides an audit-ready walkthrough memo covering each process step, roles, controls, and risks.
Edits are yours — they are marked “AI-Edited” in the registers, never presented as raw AI output.
⚠️
Risk & control matrix will appear here
AI identifies risks at each process step and maps them to existing and recommended controls. The working registers are Sections 2 and 3 below — this tab is the raw AI view.
Improve with AI
Ask the AI to improve the narrative or the flowchart. You see the proposal side by side with the current version first — nothing changes until you accept it, and an AI edit can never confirm a step, risk or control for you.
Accept this output?
Accepting marks this output as the working version for the Risk Register. You can still edit afterwards — regenerating asks first.
2
Risk Register
What could go wrong in this process
Tip: accepting the generated output in Section 1 first keeps this register in sync with the narrative / flowchart. You can work here in any order.
AI-proposed risks arrive unconfirmed — review each one, fix the wording, category and severity, and add anything the AI missed. Confirm the register when it is ready; the Control Map in Section 3 is available in any order.
3
Control Map
The controls that answer each risk
Tip: confirming the Risk Register in Section 2 first keeps the Control Map aligned with it. You can work here in any order.
Controls sit under the risk they answer; a control with no linked risk stands alone. Confirm the map when it is ready; Push to RCM Hub in Section 5 is available in any order and sends the confirmed controls.
4
Systems Identified
The systems this process touches
Tip: confirming the Control Map in Section 3 first keeps Systems aligned with it. You can work here in any order.
Systems named in the narrative and flowchart arrive here on their own. Push forwards them to Step 5 (IT Systems Scoping) — re-pushing updates the same Step 5 rows, it never duplicates them.
5
Exit
Save the work, file it, and push it onward
Tip: Push to RCM Hub sends the confirmed controls — confirming the Control Map in Section 3 first is recommended, but the push is available in any order. Saving a draft is always available.
Save
Save Draft keeps this process in the database without filing it. Save to Engagement File files the narrative and flowchart as PN-/FC- entries in the Engagement File's Planning section — that needs the output accepted and every AI warning acknowledged.
Push to RCM Hub (Step 6)
Writes the confirmed risk–control pairs for this process to the engagement RCM and submits the control definitions to the Control Library. Only entities where Step 3 shows this process in scope and signed off are included.
Push to IT Scoping (Step 5)
Forwards this process's systems to Step 5's inventory, linked to this process. The same button lives in Section 4.
Export
Exports use the edited diagram and the current narrative. When you file to the Engagement File, the PDF, SVG, PNG, spreadsheet and draw.io exports are attached to the same PN-/FC- entries.