Worked example: statute of limitations in United Kingdom

DocketMath’s statute of limitations calculator for the United Kingdom is designed to help you structure and document your date calculations, not to tell you what the law is or how it applies to your case.

This worked example walks through:

• The key inputs you’d enter into DocketMath
• How those inputs affect the output date
• How to run quick “what if?” checks to see how sensitive the result is to small changes

Example inputs

To keep things concrete, we’ll use a simple civil claim scenario grounded in common UK limitation rules (particularly the Limitation Act 1980 for England and Wales). The point is not to restate the law, but to show how you would structure the calculation in DocketMath.

Imagine you’re tracking limitation for a straightforward contract claim in England:

• A company supplies services under a written contract.
• The client fails to pay the final invoice.
• You want to record and monitor the last date to issue a claim in court.

1. Choosing the jurisdiction and regime

In DocketMath’s statute of limitations calculator, your first step is to pick the relevant jurisdictional settings. For this example:

• Jurisdiction: United Kingdom
• Sub‑jurisdiction / legal system: England and Wales
• Claim type: Civil – Contract (simple contract, not a deed)

Behind the scenes, DocketMath will map this to a typical six‑year limitation period for simple contract claims in England and Wales.

2. Key factual dates

Next, you’ll enter the dates that drive the calculation. For a contract debt claim, a common starting point is when the cause of action accrued—often the date payment became due and was not made.

Assume:

• Invoice date: 10 March 2020
• Payment terms: 30 days from invoice
• Due date for payment: 9 April 2020
• Non‑payment: Client does not pay by the due date

For this worked example, we’ll treat:

• Accrual date (cause of action arises): 9 April 2020

In the calculator, you might see an input such as:

• “When did the cause of action accrue?” → 9 April 2020

3. Limitation period selection

Depending on how your tool is configured, you may either:

• Let DocketMath infer the limitation period from the claim type (e.g., “Contract – 6 years”), or
• Manually specify the period (for more custom or cross‑border work).

For this example, we’ll assume:

• Limitation period: 6 years from accrual

In DocketMath, this might be represented as:

• Length: 6
• Unit: years
• Direction: forward from accrual date

4. Optional adjustment inputs

Many real‑world calculations need extra switches or flags. Typical examples:

• Acknowledgement / part‑payment that might restart time
• Disability / minority (e.g., claimant under 18)
• Fraud / deliberate concealment
• Latent damage (for certain tort claims)
• Contract as a deed (potentially 12 years instead of 6)

For this basic run, we’ll assume:

• No acknowledgement or part‑payment
• No special disability or concealment
• No alternative statutory regime

So in the calculator you’d leave those toggles off.

Example run

Putting the inputs together, here’s what a typical DocketMath run might look like conceptually.

Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

1. Core calculation

Input summary

• Jurisdiction: United Kingdom – England and Wales
• Claim type: Civil – Simple contract
• Cause of action accrues: 9 April 2020
• Limitation period: 6 years from accrual
• Adjustments: None

Step 1 – Add the limitation period

• Start: 9 April 2020
• Add 6 years → 9 April 2026

Step 2 – Interpret the end date

A common approach for limitation is that the claim must be issued on or before the anniversary date.

So the tool might present the result as:

• Last day to issue proceedings (subject to legal confirmation): 9 April 2026

In a DocketMath‑style output table:

2. Visualising the timeline

It’s often helpful to record the key milestones that matter operationally:

• 9 April 2020 – Cause of action accrues
• 9 April 2025 – One year before limitation (internal “heads‑up” date)
• 9 January 2026 – Three months before limitation (escalation date)
• 9 April 2026 – Calculated limitation expiry

In DocketMath, you could add internal buffer reminders on top of the legal deadline:

• Add 12‑month pre‑expiry reminder
• Add 3‑month pre‑expiry reminder

That way, the tool isn’t just giving a single date; it’s generating a workflow timeline you can track.

3. Documenting the assumption set

For auditability, you’d usually record the assumptions that went into the calculation, for example:

• Assumed six‑year limitation under Limitation Act 1980 for simple contract
• Assumed cause of action accrued on due date for payment (9 April 2020)
• Assumed no acknowledgement, part‑payment, or standstill agreement
• Assumed no special statutory regime displacing the default six‑year period

DocketMath is designed to make these assumptions explicit in the calculation record, so a future reviewer can see why a particular date was produced.

For more on documenting calculations, see our jurisdiction‑aware workflow guide: A practical workflow for jurisdiction-aware legal calculations (and how to document them).

Sensitivity check

Once you’ve run the main scenario, the next step is to stress‑test the result. Small factual changes can move the limitation date significantly. Here are some typical sensitivity checks you might run in DocketMath.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1. What if the contract is a deed?

Suppose the contract was executed as a deed, and you want to see the impact of a longer period.

Change in input

• Claim type: Civil – Contract (deed)
• Limitation period: 12 years from accrual
• Accrual date remains: 9 April 2020

New output

• Start: 9 April 2020
• Add 12 years → 9 April 2032

Compared side‑by‑side:

Operationally, this kind of check is useful when you’re unsure whether a document qualifies as a deed and want to see the range of possible deadlines.

2. What if there was an acknowledgement?

Imagine the debtor wrote a clear written acknowledgement of the debt on 1 February 2024. For some claims, a valid acknowledgement can restart the limitation clock.

Change in input

• Acknowledgement date: 1 February 2024
• Rule applied: “Restart period from latest valid acknowledgement”
• Limitation period: 6 years from acknowledgement

New output

• Start: 1 February 2024
• Add 6 years → 1 February 2030

Compare with the base case:

3. What if the accrual date is disputed?

Another common sensitivity check is to vary the accrual date itself. Maybe there’s a debate about when the breach occurred, or when an invoice was actually due.

Consider three possibilities:

1. Payment due on 9 April 2020 (our base case)
2. Payment arguably due earlier: 25 March 2020
3. Payment arguably due later: 23 April 2020

Assuming a six‑year period, the outputs would be:

Related reading

• Worked example: deadlines in New York

• Worked example: interest in Maine

• Choosing the right statute of limitations tool for Vermont

• Why we started the DocketMath blog