Records
Contemporaneous records
Every mechanism on this site consumes records as its raw material. This section is the operating system that produces them, written for the people who actually have to keep them.
- Build the claim while building the projectThe cornerstone guide: the six categories, the cadence, the good diary entry and the seven ways records fail.
- Daily site records that prove factsWhat a daily entry has to fix, and the difference between a record and a complaint.
- Programme updates and narrativesWhat to preserve every month so the programme can explain why it changed.
- Records health checkTen links, scored zero to two. Below twelve, fix it now rather than later.
Where the record comes in
Every mechanism on this page turns on evidence: what happened, what was known and when. A record built as the job happens is worth more than any argument assembled afterwards. Construction Metric keeps that record automatically, from the messages, photographs and voice notes a site team already sends.
Built by AI Metric
The analysis on this site is only as fast as the evidence behind it. AI Metric builds bespoke systems for consultancies, contractors and claims teams: document and correspondence triage, event registers assembled from the project record, programme and cost reconciliation, and drafting support that always cites the document it came from. Built for review by your own experts, never to replace their judgement.
General explanation of how contract mechanisms, analysis methods and legal principles generally work. It is not legal or contractual advice, not an opinion on any project, and no standard-form contract wording is reproduced anywhere on this site. Standard forms are routinely amended, so every default described here, including every time period, can be different on your project. Your executed contract, as amended, and the governing law and forum always control. Deadlines may already be running: if an event has occurred, preserve your position and take qualified advice.