Entries are saved in browser localStorage and persist across sessions. Export CSV for permanent record.
Workflow
1 Branch Setup
›
2 Pick Observationspending
›
3 Enter Detailspending
›
4 Attach Annexurespending
›
5 Preview & Reviewpending
›
6 Sign-off & Savepending
›
7 Send Draft to Auditee
›
8 Import Responsespending
›
9 Receive / Amend
›
10 Send to RO
›
11 Official Issuancepending
Step 5: 🔎 Preview & Review□ Pending — Click "Generate / Refresh Report" to preview the full report. Review the synopsis, KPI tiles, and observation cards for accuracy before finalizing.
📋 Audit Work StatusCategory-wise observation checklist & progress tracker
Branch Code—
Branch Name—
Region—
City—
Heat Map Overview
Overall Summary
Total Observations Cleared0 / 359 (0%)
Progress Report
📋 Summary Table
📈 Bar Chart
Category
Active Total
Checked & Clear
In Progress
Pending
N/A ※
Sampled Out ※
% Done
Checked & Clear
In Progress
Pending
N/A (excluded)
Sampled Out (excluded)
Category Details
📄 Draft Report — Observation SummaryAll observations currently added to the draft report
Branch—
Report No.—
Total Observations0
New0
Repeated0
Branch & Report Information🔒 Locked
🔒
Click to edit Branch & Report Information
📍 Branch Lookup — type in any field to auto-fill all others
Draft – Head of School Review
From
To
⚠ Audit Period To must not be later than Visit From date.
From
To
🔄 Repeat Detection
Filter Observations
Search Hint
Observations
🔍 Select a Type or Category filter, or type keywords in Search Hint, then click Search / Filter.
No observations match your filter/search.
📄 Report Introduction
▼
Click Fill from Databank to populate with standard S&A audit language — branch name and dates are substituted automatically. Leave blank to omit.
⚠ Highlighted items need your attention — update the bracketed text below.
⚠ Highlighted items need your attention — update the bracketed text below.
⚠ Highlighted items need your attention — update the bracketed text below.
⚠ Highlighted items need your attention — update the bracketed text below.
Annexures
No annexures added yet.
📋
Report Preview
Select a Branch, tick observations on the left, then click Generate / Refresh Report.
Manage
📊 Risk Assessment
🏆 Cross-Branch BRI Ranking
Branch Risk Index — normalised for branch size/complexity | HO View Only
📊 Risk-Based Audit Planner
Load previous audit report(s) for a branch to profile its risk exposure, identify high-risk areas, and generate a risk-prioritized audit plan for the upcoming visit.
📍 Branch Being Audited
Filter by Region
✕
✕
📄 Previous Audit Report(s) — Source Data
Supports Word (.docx), Excel (.xlsx), JSON session, or plain-text files. Add as many as needed.
Loaded Files:
① Branch Planning Score
The system will use:
• Sensitivity distribution from uploaded past report
• Outstanding observations table (Analysis of Audit Observations)
• Branch complexity score — enter below when branch is selected
Extracts sensitivity & outstanding data from uploaded past report · uses complexity score entered above
📋 Upcoming Audit Details
⚙ Scoring Mode
Analyses previous report data to build a risk-prioritized audit program for the upcoming visit
⚙ Branch Complexity Score
Enter the Branch Code or Name to look up the branch, then set or update its complexity score (0–100). Scores save automatically and are used in Stage 1 planning.
All saved scores are stored permanently and used automatically in Stage 1.
①
Stage 1 — Branch Planning Score
How to use:
1. Select the branch to plan
2. Load its previous audit report (.docx)
3. Select the Branch Complexity bands
4. Click Calculate Branch Planning Score
The system extracts sensitivity distribution and outstanding observations from the uploaded report and computes a risk-based priority tier.
⚙
Branch Complexity Matrix
Enter the complexity score for each branch in the table on the left.
Score Guide: 75–100 Very High · 55–74 High 35–54 Medium · 15–34 Low · 0–14 Very Low
Stage 1 will automatically use the stored score for any branch you select.
If no score is set for a branch, a default of 50 is applied.
📋
Risk-Based Audit Planner
How to use:
1. Select the branch you plan to audit
2. Load or paste its previous audit report(s)
3. Fill in upcoming audit details
4. Click Generate Risk-Based Audit Plan
The system will analyse historical observations, identify high-risk areas, and produce a risk-prioritized audit program with effort allocation and specific procedures for each area.
Overall Risk Score
--
Run analysis to calculate
LowMediumHighCritical
📋 Risk-Based Audit Plan
Category Risk Matrix
Observation Frequency by Category
🎲 Risk Heatmap — Likelihood vs Impact Matrix
📋 Enterprise Risk Register (ERM)
📝 Risk-Based Audit Program
📈 Trend Analysis (Older vs Newer Report)
⚠ Persistent / Repeated Issues
✅ Audit Planning Recommendations
📄 Databank Manager
Browse, edit, suppress and merge observations in the audit databank. All changes are stored locally and reversible.
📄 Databank Manager — User Guide
Basic Actions
Click any row
Opens the observation detail panel on the right in read-only view. Read the full observation text and recommendation before taking any action.
✏ Edit Details
Switches to edit mode. You can update the title, category, type, observation text and recommendation. Changes are saved to your local browser and do not affect other users.
🔴 Suppress
Hides the observation from all filters, searches and reports without permanently deleting it. It can be restored at any time using the Suppressed filter.
🟢 Restore
Brings a suppressed observation back to active status. Use the Suppressed only filter to find suppressed observations.
⇄ Merge
Suppresses one observation and keeps the other as the canonical version. Use when two observations have the same meaning but different wording.
↩ Undo Last
Reverses the most recent action (suppress, restore, edit or merge). Up to 50 actions can be undone within the current session.
🔍 Scan Duplicates
Automatically scans all active observations and finds pairs with 70%+ title similarity. Both observations are shown side by side in full so you can read and compare before deciding which to keep.
🔒 HO Update Workflow (step by step)
1Auditor makes changes in Databank Manager (suppress, edit or merge observations), then clicks "📤 Export Proposed Changes". This downloads a small dbm-proposed-changes.json file and sends it to HO.2Administrator opens the system, goes to Databank Manager, and clicks "🔒 Import & Review (HO)" (requires Administrator password). A review screen opens showing every proposed change with Approve / Reject checkboxes.3HO reviews each change, ticks or unticks as required, then clicks "Apply Approved Changes". The approved changes are now active in HO's browser session.4HO clicks "🔒 Update HTML File". This permanently bakes all approved changes into a new file called index-updated.html which is saved to the Downloads folder on HO's computer.5HO renames index-updated.html to index.html and uploads it to Netlify. All auditors who open the Netlify link will now have the updated databank automatically.
Important Notes
• All changes made in Databank Manager are saved in the browser only — they are not written into the HTML file automatically.
• The dbm-proposed-changes.json file exported by an auditor is not a system file and cannot be uploaded to Netlify directly.
• Only the index-updated.html produced by "Update HTML File" should be uploaded to Netlify.
• After uploading to Netlify, ask auditors to do a hard refresh (Ctrl+Shift+R) once to ensure they get the latest version.
#
Title
Category
Type
Source
Status
Actions
🔗 Risk Mapping Editor
Review and edit how each observation is linked to a Sub-Risk (SRR). Flag mismatches and reassign where needed.
Review how each observation is mapped to its Sub-Risk Register (SRR) entry and parent Risk Register (RR). Flag mismatches, reassign where needed, attach supporting evidence, and submit approved changes to HO. Use Import Risk Map Updates to load changes from a saved session or issued HTML report.
📎 Attached Files:
Total: 0Flagged: 0Reassigned: 0Showing: 0⚠ Fallback (no keyword match): 0
🔎 Risk–Control Activity Mapping Audit
Every observation showing its auto-matched SRR, keyword score, matched keywords, and Control Activity. ⚠ = fallback used (no keyword matched — likely mismatch).
💡 How to Correct Fallback & Weak Matches
Step 1 — Identify
Use the filter above to show ⚠ Fallback or
⬦ Weak rows.
These are observations where BRAINS either found no keyword match (fallback) or only one keyword matched (weak).
Step 2 — Fix (per session)
Click ✎ Fix on any row.
This switches to the Editor, opens that observation's detail panel, and lets you select the correct Risk (SRR) from a dropdown.
The correction is saved in your session file.
Step 3 — Fix permanently (Administrator)
Session-level fixes apply only to this report. For a permanent correction, an Administrator must add the missing keyword(s)
to the correct SRR's keyword list in the databank and export an updated app — so future reports auto-match correctly.
Use Submit Risk Map in the editor to flag changes to HO for databank update.
Obs ID
Observation Title
Category
Score
Matched SRR
Risk (RR)
Control Activity
Keywords Matched
Fix
ID
Observation Title
Category
Mapped SRR
Sub-Risk Name
RR
Action
OBSERVATION
RECOMMENDATION
CURRENT RISK MAPPING
Flag this observation if the risk mapping seems incorrect
CHANGE RISK MAPPING
Select the correct Sub-Risk
Note / Reason (optional)
📄 Paste Source Text (optional)
Paste Diligent risk text, policy clause, or reference material to help define the new risk.