Skip to content
Lintel

2026-09-15

Why notice windows decide claims, and how to stop missing them

Notice periods are short, start on an event and are easy to lose track of. Here is why they matter and what a reliable process looks like.

General information, not legal advice.

A claim for more time or more money usually has two parts. The first is the substance: what happened, and why the contract gives an entitlement. The second is procedure: whether the right notice was given, to the right person, within the right period. Teams naturally spend their energy on the first part. Many disputes are decided on the second.

Why the window matters#

Many construction and infrastructure contracts require a party to notify the other side of an event within a stated period, often measured from when the party became aware of it or ought to have become aware. Some contracts state plainly that a claim not notified in time is barred. Others soften the consequence but still make late notice a point of argument. Whatever the wording, the same practical truth applies: the earlier and more clearly notice is given, the fewer arguments remain.

The exact effect of a late notice depends on the contract and on the law that governs it. That is a question for counsel, and nothing here is legal advice. What software can do is make sure people see the window while it is still open.

Why windows get missed#

Windows are rarely missed through carelessness. They are missed because of how information moves on a project.

  • The trigger is not a date on a calendar. The window starts when something happens: an instruction is received, land is not handed over, a design is changed. If the event is recorded late, the clock has already been running.
  • The rule lives somewhere else. The period is in one clause, modified by a particular condition and again by an amendment. The person on site who sees the event may not know which clause applies.
  • Ownership is unclear. Everyone assumes the commercial team has it, and the commercial team has not been told.
  • Volume. On a live project there are many small events. A private spreadsheet works until the week it does not get updated.

What a reliable process looks like#

A dependable process has four properties, whatever tools it uses.

1. Each notice obligation is written down once, with its source. State the trigger, the period, how days are counted, who gives notice, to whom, and which clause says so. Keep the page reference so anyone can check it.

2. The trigger is recorded when the event happens. Give the site team a simple way to log an event with a date and a photo or message. The record does not have to be perfect. It has to exist.

3. The due date is computed, not remembered. From the trigger date and the counting rule, compute the last day. If the trigger date is corrected later, the due date should move with it, and the change should be logged.

4. Someone is reminded before the window closes. A reminder on the last day is too late to draft a good notice. Reminders should arrive with enough time to gather facts and get a review.

Counting rules deserve attention#

Two windows of “14 days” can end on different dates depending on whether the day of the event counts, whether weekends and public holidays are excluded, and what happens when the last day falls on a non-working day. These rules are contract-specific. A tool should therefore make the counting rule explicit for every obligation rather than assume one. It should also keep the reasoning visible so that a person can check it.

Where software helps and where it does not#

Software can read a contract and propose the notice obligations, with the clause and page each came from. It can hold trigger events, compute due dates, and remind the right person. It can keep the evidence for each event next to the deadline.

Software cannot decide what a clause means in a particular dispute, whether an event amounts to a delay event, or whether a notice was adequate. Those are judgments for the people responsible and their advisers. A well-designed system is explicit about this boundary: it proposes, cites and reminds, and people confirm.

A short test#

Pick one live project and ask three questions. Can you list every open notice window today, with its due date? For each, can you point to the clause that creates it? And for each, do you know who is responsible for acting? If any answer is “not quickly”, the process has a gap that will eventually be found by an event rather than by a review.

Lintel is being built around exactly this chain, from clause to obligation to trigger event to deadline. It is in early access, and the sample console on this site shows the idea with fictional data.

General information, not legal advice. Back to resources

Start with one contract.

Join early access, or book a walkthrough and we will show you how a single agreement becomes a live register.