One workflow. A named owner.
Define the inputs, target metric, permitted actions and manual fallback before using live records.
free working templates · 1.0.0
Keep the office in control.
Scope one workflow, name the approval boundary and make evidence easier to check. Editable templates you can use before a build or alongside an ASI skill.
Unzip the download. Open the CSV templates in Excel or Google Sheets; open the guide in any text editor. Free, no login or email required.
Make approval explicit.
An editable authority matrix to confirm who may approve what, and when review is required.
Track gaps and decisions.
A source checklist and exception log for conflicting figures, missing updates and their resolution.
ASI Governance Starter Kit · 1.0.0
Editable working templates for scoping one office workflow. Complete them with the people who already hold authority. This is a practical starting point, not a certification or legal compliance assessment.
1. Workflow scope
- Workflow and intended decision:
- Named owner and reviewer:
- Source records, entities and currencies in scope:
- Baseline today (measure it before the trial):
- Target metric and measurement period:
- Actions AI may prepare:
- Actions a person must approve:
- Actions excluded from scope:
- Approved AI environment and permitted data:
- Stop condition and manual fallback:
2. Authority matrix
Use authority-matrix.csv. Confirm actual approval rights; a title alone does not grant authority. Suggested starting point: AI drafts and flags; the authorised person approves consequential action. Do not use real names in a publicly shared copy.
3. Evidence checklist
- Every material number has a source, date, entity, currency and basis.
- Conflicting figures remain visible until reconciled.
- Missing evidence is marked; absence is not treated as proof of non-existence.
- Calculations are reproducible; released time is distinguished from cash savings.
- Recipient access and permitted data handling are agreed before using live records.
- Reviewer confirms accuracy, scope and authority before action or distribution.
- The final decision and its evidence are recorded in the office’s approved system.
4. Exception and decision log
Use exception-log.csv. Record the source discrepancy, impact, owner, resolution and approving person. Do not overwrite the original evidence when correcting a record.
5. Three starting workflow blueprints
| Workflow | Inputs | AI prepares | Human gate | Baseline metric |
|---|---|---|---|---|
| Weekly reporting pack | Dated entity extracts and prior pack | Draft pack; comparable movements; missing feeds | Authorised reviewer checks scope and approves distribution | Total preparation/review hours; exceptions caught |
| Diligence question preparation | Supplied memo and supporting records | Claims, conflicts, questions and evidence requests | Reviewer approves questions; decision authority stays with office | Review hours; material gaps resolved before reliance |
| Principal briefing | Weekly notes, prior brief and reporting period | Decisions, changes, exceptions and action register | Reviewer confirms facts, owners and recipients | Preparation time; unresolved decisions and stale updates |
Choose one workflow. A successful brief or prototype does not establish production readiness. If source access, data quality or authority is unclear, resolve that foundation before allowing actions.