Inputs you need for statute of limitations in United Kingdom

Inputs you will need

Run this scenario in DocketMath using the Statute Of Limitations calculator.

To run a statute of limitations check in the United Kingdom with DocketMath (calculator: statute-of-limitations), you’ll need a focused set of inputs. These act like the “data fields” that determine which limitation rule applies and when the clock starts.

Use this checklist to gather the minimum inputs before you open /tools/statute-of-limitations.

• Example categories you may need to distinguish: contract (breach of contract), tort (personal injury or other civil wrongs), breach of trust, and certain statutory causes.
• If you don’t have an exact accrual date, you’ll typically use the date of breach, the date of damage, or the date a claimant knew (where the rule depends on knowledge).
• Separate limitation rules can apply depending on whether the claim is England & Wales, Scotland, or Northern Ireland.
• DocketMath uses this to test whether the claim is time-barred based on the applicable limitation period.
• Many limitation regimes in the UK include knowledge-based concepts (for example, where a claimant became aware of facts giving rise to the claim).
• Examples include whether the claimant is a child, lacks capacity, or falls under a special protected category that can affect the limitation outcome.
• Certain limitation rules can hinge on whether the matter involves trustees/breach of trust, corporate matters, or other specific relationships.
• In practice, you may need to capture the injury date, when it was discovered, and any related timeline facts that determine accrual/knowledge.

How these inputs change the outcome

Here’s what each major input typically controls, and how it can change the result:

Where to find each input

Gathering inputs is mostly a documents-and-facts exercise. Below are practical places to look, plus what you’re extracting.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Claim type / cause of action category

Look for the legal basis you’re asserting, such as:

• Pre-action correspondence (letters before claim, letters of claim/response)
• Draft pleadings / particulars of claim
• Legal summary in your case file

What to extract:

• The category that best matches the claim (for example, breach of contract vs negligence/tort).

2) Accrual date (or best proxy)

Start from the timeline of events:

• Incident report / event record
• Breach documentation (contract termination notice, missed payment date, performance failure date)
• Damage evidence (first manifested harm, first loss)

If the rule depends on knowledge, also collect:

• When relevant facts were known or could reasonably have been known
• When the claimant took steps to investigate

3) Jurisdiction within the UK

Limitation territory can depend on where things happened and where the claim is expected to be brought. Check for:

• Where the relevant contract was made or where performance occurred
• Where the conduct occurred
• Where parties reside or where the claim is expected to be brought
• Court/tribunal choice already contemplated in your workflow

4) Date the claim was filed

Use actual dates wherever possible:

• Issue/filing confirmation
• Court response / acknowledgment
• Calendar entries tied to the filing

If you’re doing a “what if” analysis:

• Use your intended filing date and rerun scenarios.

5) Protected claimant status (if applicable)

You only need these inputs when the situation fits. Common evidence sources include:

• Medical records (for capacity/impairment facts relevant to timelines)
• Guardianship/care documentation
• Age evidence (for child status)

6) Personal injury timeline specifics (if applicable)

If the claim is personal injury-related, capture:

• Injury date from medical records
• Discovery/diagnosis timeline (when symptoms were identified, diagnosis dates)
• Treatment milestones (sometimes relevant to “knowable facts” narratives)

Run it

Once your checklist items are ready, run DocketMath.

1. Open the calculator: /tools/statute-of-limitations
2. Select jurisdiction code: UK, then specify the territory within the UK (England & Wales, Scotland, or Northern Ireland) if DocketMath prompts for it.
3. Enter:

   • Claim type
   • Accrual or knowledge dates (as applicable)
   • Filing date
   • Any protected status flags (only if relevant)
   • (If prompted) any defendant/type relationship details relevant to the limitation category
4. Review the result and the underlying “deadline logic” summary that DocketMath provides.
5. If the output is close (e.g., within weeks or months), rerun using alternate dates you can justify:

   • Example scenario: if “knowledge date” is uncertain between 1 April 2023 and 15 May 2023, run both to see whether the claim flips from “in time” to “time-barred.”

Interpreting outcomes: what to change first

If you need to reduce uncertainty, change inputs in this order:

Quick scenario table (example workflow)

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator