Templates
Structures to fill in, not wording to copy
A policy assembled from somebody else's model wording describes somebody else's institution, and a supervisor reading it can tell. These templates are structures and prompts: they tell you which decisions a document has to record, and leave the decisions to you.
The library
What is planned, and what it will contain
Each template below is outlined and none is yet written. They are deliberately prompts rather than model text — a template that supplies the answers produces a document nobody in the institution can defend when asked why it says what it says.
Placeholder — none of these assets has been written; the outlines below are statements of intent and no download exists yet. Replace with sourced, approved content before this page is made public.
- Planned
AML/CFT policy outline
A section-by-section outline for a board-approved AML/CFT policy, with prompts for the decisions each section has to record rather than model wording to copy.
Written for: Compliance policy owners preparing a policy for board approval
What it will cover
- Governance, accountability and the reporting line for the compliance function
- Risk appetite statements expressed as decisions rather than sentiment
- Due diligence tiers and what differs between them
- Reporting, record keeping, training and independent testing sections
- A version and approval block, so the policy carries its own governance
- Planned
Enterprise-wide risk assessment template
A structure for assessing inherent risk across customers, products, channels and geographies, scoring control effectiveness, and arriving at a residual position that downstream controls can be derived from.
Written for: Compliance policy owners and risk functions
What it will cover
- Inherent risk dimensions with prompts for evidence rather than assertion
- Control effectiveness assessment, separated from control existence
- Residual risk presentation, and how it maps onto customer risk bands and monitoring coverage
- A review and refresh log
- Planned
Customer risk factor matrix
A worksheet for defining factors, values, sources, missing-value treatment and weights, with space for the rationale behind each weight and the approval that fixed it.
Written for: Model owners and compliance policy owners
What it will cover
- One row per factor: source system, vocabulary, missing-value treatment, weight, rationale
- Mandatory trigger register, kept separate from the weighted factors
- Band definitions with the operational treatment each band produces
- Model version, approver and effective date block
- Planned
Report narrative structure
The narrative skeleton for a report of suspicion — subject, trigger, expected profile, observed activity, gap, enquiries, explanation, assessment, disposition — with guidance on what belongs in each section.
Written for: Investigators and MLROs
What it will cover
- Section-by-section prompts, with the distinction between fact and inference made explicit
- A pre-submission checklist covering completeness, language and evidence references
- Guidance on recording checks that produced nothing
- Planned
Rule tuning proposal and approval record
The record a monitoring parameter change should leave behind: current behaviour, proposed change, evidence from both directions of testing, and the maker and checker who agreed it.
Written for: Monitoring leads, model owners and internal audit
What it will cover
- Baseline metrics for the rule over a defined period
- Proposed parameters, with the rationale and the risk accepted
- Above-the-line and below-the-line results, with sample sizes and reviewer identity
- Maker, checker, effective date and scheduled review date
- Planned
Alert disposition reason code set
A starter closed vocabulary for alert closure reasons, with definitions precise enough that two analysts choose the same code for the same situation.
Written for: Monitoring leads and investigation team leads
What it will cover
- A compact code set with a definition and a worked example for each
- Rules for when free text is required in addition to a code
- The per-rule reports the vocabulary makes possible once it is in use
- Planned
Independent testing scope checklist
A scoping checklist for an independent review of the AML/CFT programme, covering design, operating effectiveness and decision quality rather than policy existence alone.
Written for: Internal audit and compliance leadership commissioning a review
What it will cover
- Scope statements per programme element, with the evidence each one should be able to produce
- Sampling approach for decisions, not just for controls
- Reporting structure and follow-up tracking
- Planned
Retention and legal hold register
A register for recording retention decisions by record category and for tracking legal holds, including the reconciliation between a hold and any pending erasure request.
Written for: Compliance, legal and data protection officers
What it will cover
- Record categories, the retention basis for each, and the owner of that determination
- Hold register: scope, requester, start, review date and release
- Reconciliation prompts for holds that intersect a data subject request
Free to read now
Registering interest tells us which of these to write first, and we will send it when it exists. We will not send you a benchmark figure we have not measured or a template we have not had reviewed — which is the reason this shelf is shorter than it could be.
In the meantime
Governed forms beat a document you maintain by hand
Due diligence forms, risk factor models and approval records can live under version control and maker-checker governance instead of in a shared drive.