Projects and evidence
Organise projects and claim events
Separate the permanent project record from individual delay or claim events.
5 minute read Project and commercial teamsUpdated 15 August 2026
On this page
Quick answer
A project holds the contract and job context. An event records one factual occurrence, its notice history, effects, evidence and outputs. Use separate events when the causes or notice obligations are materially different.
What belongs in a project
- The project title, reference, location, parties and contract family.
- The contract edition and key dates that apply across the job.
- The company members authorised to work with that project record.
What belongs in an event
- A factual title and description of what happened.
- The occurrence date, knowledge chronology, notice recipient and service record.
- Affected work, programme activities, mitigation and available evidence.
- The status, risk, generated outputs and professional review trail for that event.
Record early, conclude carefully
Record the earliest reliable facts even when entitlement or a clause reference is not yet confirmed. Keep the factual issue and potential contractual route separate until the operative terms have been checked.
Still need help?
Continue with the assistant or support team
The in-app assistant can explain the page you are using. For an account-specific problem, send support the expected result, reproduction steps and any safe request or job ID.