Templates triggeredby workflow milestones
Letters, contracts, evidence packs, and statements, generated automatically as cases progress, with policy-aware merge fields and full version control.
Trigger map
Workflow milestones, documents, and delivery, all configured together
Every document is wired to the workflow event that produces it, with conditions, recipients, format, and delivery channel travelling with the template.
Application submitted
Stage 01 · Capture
always
Application acknowledgement
PDF · Email + customer portal
Pre-approval issued
Stage 03 · Decisioning
auto-decision = approve
Indicative offer letter
PDF + e-sign · Customer + broker
Conditional approval
Stage 05 · Approval
risk grade ≤ B
Approval-in-principle pack
PDF · 8pp · Email + broker portal
Policy override applied
Stage 05 · Approval
override.recorded
Override evidence memo
PDF · audit · Audit trail · regulator pack
Loan documents ready
Stage 05 · Settlement
final approval
Loan contract & schedule
PDF + DocuSign · All borrowers + guarantors
Settlement booked
Stage 05 · Settlement
PEXA confirmed
Settlement confirmation
PDF + SMS link · Customer + broker + solicitor
First repayment due
Stage 06 · Servicing
T-7 days
Repayment reminder & schedule
PDF + email · Customer
Template library
Branded, versioned, policy-aware
Edit templates visually with merge fields, conditional blocks, and brand assets. Every change versioned, every render traced.
Application acknowledgement
v4.2First-touch confirmation with case number and next steps.
Indicative offer
v7.1Pre-approval with rate, term, and conditions placeholder.
Loan contract
v12.0Full credit contract aligned to NCCP and ASIC RG209.
Approval-in-principle
v5.3AIP pack including credit decision and conditions.
Override evidence memo
v2.1Reason, approver, policy reference for any override.
Settlement confirmation
v3.4Settlement date, distribution, and account setup.
Repayment schedule
v6.0Amortisation table with redraw and offset detail.
Decline letter
v4.5Compliant decline notice with internal review path.
Document governance
Templates as policy artefacts, not Word files on a share drive
Document templates as files
Word docs, manual merge, mystery versions
- ×Word templates emailed between compliance, legal, and ops
- ×Merge done by hand or ad-hoc scripts
- ×No version control; auditors can't trace which template was used
- ×Brand inconsistency across letters, contracts, statements
- ×Every policy change is a hunt-and-replace exercise
Templates as governed, policy-aware artefacts
- Visual editor with merge fields and conditional logic
- Every render captured with template version + data snapshot
- Compliance approves changes inside the platform
- Consistent branding across every channel
- Policy-aware rules engine drives conditional clauses
See document generation wired to a real workflow
A live demo: trigger a milestone, watch the document render, e-sign, and audit-trail in real time.