Claims workflow
A visible next step from first event to issued document.
The workflow separates source facts, assisted analysis, professional review and approval so users can see what is known, what is missing and who remains responsible.
1. Set up the signed contract record
Create the project, select the contract family and version, record amendments, key dates, parties, notice recipients and service details. Contract wording and deadlines remain subject to verification against the executed terms.
Result: Project and contract particulars ready for review
2. Capture the event while facts are fresh
Record what happened, when it happened and became known, the affected work, mitigation, preliminary time or cost effect and the people involved.
Result: A structured event rather than a loose email trail
3. Add and select the source evidence
Upload correspondence, instructions, meeting minutes, programmes, progress records, photographs, diaries, labour, plant and cost material. Choose the sources relevant to the task.
Result: A source register with processing status and traceable references
4. Review facts, gaps and risk
Confirm extracted facts, resolve contradictions, check notice requirements and keep assumptions or missing records visible. The system must not silently fill gaps.
Result: A chronology and evidence-gap list for professional review
5. Create and refine the output
Choose a notice, EOT claim, loss and expense record, report or submission pack. Edit the draft, request targeted improvements and keep the selected evidence attached.
Result: An editable, source-linked document rather than raw generated text
6. Approve, export and preserve issue evidence
Complete the review checklist, approve the version, export Word or PDF, record the recipient and service method, and retain proof of issue and receipt.
Result: A controlled issued record with versions and next actions
Inspect the workflow in context