Documents
Document governance built into the customer service journey.
Turn agreements, statements of work, service schedules, reports and evidence packs into visible workflows with reminders, acceptance and audit history.
Make customer document actions impossible to miss.
The dashboard gives providers immediate context before they move into the individual document, pack or reminder workflow.
Acceptance and reminders
Keep approvals, acknowledgements and provider follow-up in one customer action queue.
Expiry and renewal
Surface contract and evidence dates early enough for proactive renewal planning.
Packs and versions
Track required pack items, accepted versions, current state and historic records.
Commercial context
Keep contract dates, value, service owner and customer signatory with the document.
A page with clear working modes
Actions
Packs
Library
Relationships
Audit
Separate actions, packs, library, relationships and audit.
Keep the high-level document status visible while giving each workflow a focused workspace.
ActionsPacksLibraryRelationshipsAudit
Workflow starters and the customer action centre.
Create, edit and manage grouped customer deliverables.
Preview, download, edit and manage acceptance.
Link governing and child documents such as MSA → SoW → schedule.
Review accepted versions, reminders, current state and history.
Build complete customer packs through a guided sequence.
The pack builder turns a potentially inconsistent manual task into a repeatable, governed workflow.
- 1Select customer
Choose the tenant and customer context for the pack.
- 2Name the pack
Set the purpose, due date and customer-facing summary.
- 3Choose governing documents
Select the MSA and any linked statement of work.
- 4Add service evidence
Include schedules, reports, evidence packs and other required items.
- 5Publish and track
Create the pack, expose it to the customer and track completion.
Templates and variables
Generate consistent documents from reusable data.
A structured template model reduces repetitive editing while keeping customer and contract context inside the portal.
- Customer and document variables: name, title, version and generated date.
- Commercial and ownership variables: contract dates, value, service owner and signatory.
- Relationship context: link generated content to the governing MSA or service schedule.
- Human review: keep generated content under provider control before publication.
Document template
Managed Service Schedule
Reusable content with customer and contract merge variables.
Customer{{customer_name}}
Contract period{{contract_start}} → {{contract_end}}
Renewal date{{renewal_date}}
Service owner{{service_owner}}
Customer signatory{{customer_signatory}}
Acceptance and audit
Keep the customer action and the evidence together.
Document governance should answer what was sent, which version was accepted, who acted, when reminders were issued and what is current now.
- Acceptance audit records the customer action against the relevant document and version.
- Reminder history captures provider follow-up without relying on an external email trail.
- Relationship history preserves the connection between governing and child documents.
- Renewal context links operational review to commercial dates and ownership.
- Mobile access lets customer stakeholders review reports and documents requiring attention from the AssurSight app.
Documents as assurance evidence
Make governance records part of the current assurance picture.
Accepted service schedules, evidence packs, policy records, exercise results and approval history can support mapped outcomes without being copied into a separate assessment tool.
- Version and acceptance state remain visible.
- Observation and review dates support evidence freshness.
- Parent-child relationships preserve the governing context.
Make document governance visible to the customer.
Review how packs, reminders, acceptance, relationships and audit history could fit into your service-delivery model.