For construction lawyers
The record, assembled.The judgment, yours.
Adjudication packages, immutable audit logs and original documents. Review the chronology and the missing evidence through client-granted access, with professional judgment firmly in your hands.
A personal walkthrough. Arranged by email.
Client-granted access. Business records stay read-only.
An adjudication package, with its history.
- The package
- The audit log
- The gaps
One package. A traceable record.
Assemble the available documents, audit extracts and file manifest for review. Missing attachments stay explicit.
Adjudication Evidence bundle
Start with the source record
Get to the facts
behind the dates.
A date on a summary is only the beginning. You need the underlying event, the supporting document and a clear view of what has not been supplied.
Review the invoice, recorded receipt and notice history through client-granted access. Keep sending and receipt distinct, and identify the gaps before relying on the chronology.
Explore a sample adjudication fileInvoice sent
Original invoice P-024
Receipt recorded
The source event used for the owner dates
- Date unconfirmed
Notice service evidence
Not supplied in this illustrative file
Recorded events and missing evidence remain distinct.
A record of what changed
History with
a visible trail.
Review immutable audit logs alongside the original documents. Recorded entries are append-only and linked by hashes; corrections add a new entry instead of overwriting the earlier history.
File fingerprints help establish whether a document matches its recorded version. They do not establish factual accuracy, legal entitlement or admissibility.
Know what an export contains.
Audit extracts include event summaries and stored hashes. They do not independently replay the full audit chain.
- 01
The original entry.
Retained in the recorded history.
- 02
The next event.
Added to the linked sequence.
- 03
A correction.
A new entry, preserving what came before.
Linked hashes support integrity checks. They do not establish the truth of the underlying facts.
Prepare the material for review
Assemble the package.
Keep the gaps visible.
Bring the available contract, invoices, notices, payment records and supporting documents into an indexed adjudication package.
Include audit extracts and a file manifest with fingerprints and missing attachments. Examine what is present, what is absent and what still needs to be obtained.
Preparation supports your judgment.
Review the applicable filing requirements. Legal advice, filing and any required signing or swearing remain with the appropriate professionals.
A file you can follow.
- 01Contract & original invoices
- 02Notices & payment records
- 03Supporting documents
- 04Audit extracts
- 05File manifest
Keep missing attachments visible in the review.
Examine an assumption without changing the source
Explore the date.
Preserve the record.
A different receipt date can change the dates that follow. Explore supported scenarios while keeping the original event intact.
The Legal seat keeps the client’s authorised business records read-only. Corrections remain with appropriately authorised members of the client’s team.
Bring a question to the walkthrough.
Review a sample package, its audit history and how the Legal seat fits your practice.
A different receipt.
A different date to examine.
| Event | Record | What if |
|---|---|---|
| Receipt | ||
| Notice by | ||
| Payment due |
The recorded receipt stays 05 Oct 2026.
Questions for your review.
Plans & pricingWhat is included in an adjudication package?
A cover sheet, recorded dispute details, available contract and invoice documents, notices, payment records, declarations and audit extracts. A file manifest lists the contents and fingerprints, with missing attachments identified. Review the package and the applicable filing requirements before submission.
How are the audit logs kept immutable?
Recorded entries cannot be edited or individually deleted. Corrections add new entries. Each event is linked to the preceding event by a cryptographic hash, supporting checks for alterations to the stored history. Workspace retention and deletion follow the privacy policy.
Read the privacy policyWhat does a file fingerprint establish?
Whether a file matches the recorded version. It does not establish factual accuracy, legal entitlement or admissibility. Exported audit extracts include event summaries and stored hashes; they do not independently replay the full audit chain.
Can I change the client's records?
The Legal seat reviews the operational record the client authorises. Corrections remain with appropriately authorised members of the client's team. Supported date scenarios do not overwrite original events.
Does Tiercord file the adjudication?
No. It prepares records and supported documents for review. Legal advice, filing, adjudicator appointment and the required signing or swearing of declarations remain with the appropriate professionals.
Where is the client's data stored?
Tiercord's core application servers are configured to run in Montréal, Canada. Core workspace records and files are stored in Canada Central. Connected AI, email and accounting services can involve processing outside Canada. See the privacy policy for the separate uses.
Read the privacy policyWhich rules apply to my project?
Supported provincial rules cover Ontario, Alberta, Saskatchewan and Manitoba. Federal eligibility depends on location and party tier. Timing depends on the contract and recorded facts.
British Columbia: prompt payment is pending. Those clocks stay out of statutory overdue counts and reminders; existing lien and holdback rules remain separate. View the statute.
Tiercord supports professional review. It does not provide legal advice, determine entitlement, file an adjudication or swear a declaration.
Explore the provincial guidesStart the conversation with the file.
Review a sample adjudication package, its audit history and the Legal seat with your practice in mind. A personal walkthrough, arranged by email.