For the complete documentation index, see llms.txt. Every documentation page is also served as markdown: append .md to its URL or request it with Accept: text/markdown. A single-file snapshot of all docs is at llms-full.txt.

Alloovium

Routines

Claim evidence

Build a claim evidence pack from the records the project already holds — by asking, with every answer cited to source — then draft the formal claim from it.

Claim evidence

A claim evidence pack is the set of project records that proves what happened, what it cost, and what the contract entitles you to: instructions, correspondence, site records and photos, delay records, cost records, and the governing clauses.

You do not need to generate a document to see your evidence. Ask the assistant first — every answer is cited to the exact source record, so the answer itself is an evidence list with pointers to proof. Draft the formal claim only once the evidence is in front of you.

Gather the evidence by asking

Ask across the project's records one evidence category at a time. Each answer carries click-to-source citations, and each citation points straight back to the record that proves the item:

  • Instructions"Show every site instruction and direction about the level 3 pour, with dates."
  • Correspondence"Find the emails and letters about the June weather delays."
  • Site records and photos"What do the site diaries record for 12–26 June — weather, crew, and progress?"
  • Delay records"What changed in the programme around the level 3 pour, and when was it first flagged?"
  • Cost records"List the cost records touching the level 3 pour — dayworks, plant standing time, supplier invoices."
  • Contract clauses"Which clauses govern delay notice and extension of time, and what do they require?"

Check the notice position

Contractual commitments captured from the project land as action items with a notice clock — the governing clause attached and a countdown to the deadline. Check them before drafting: a strong evidence pack served after the notice window closed is a weak claim.

Draft the claim from the evidence

With the evidence in front of you, draft the formal document with Document Generation: describe the claim — the event, the date range, the affected works — and ask for the evidence organised by category. Pick the project so the draft grounds in the same records, and the result is an editable draft with citations.

Evidence is built as the job runs

The strongest packs are captured daily, not reconstructed later — site diaries, meeting notes, and a read inbox mean the record already exists when the claim comes.

A human sends it, not the AI

The draft is a starting point. Review every cited item, price it yourself, and check it against the notice clause before anything leaves the building.