Technical Matter Guide
Procedure and 2026 court-bundle rules checked 24 September 2026Chronologies and timelines in Family Court: dates, evidence, procedural history, safeguarding patterns and bundle references
A chronology should make a complicated case easier to understand. It places material events in date order, identifies what happened procedurally and factually and directs the reader to the evidence. A working timeline can go further by helping a litigant analyse contact changes, safeguarding concerns, professional involvement, disputed accounts and the effect of delay before distilling that material into a concise court-facing chronology.
Court chronology and working timeline are not quite the same thing
A formal court chronology is a concise preliminary document designed to help the judge navigate the proceedings.
A working timeline can be much more detailed.
It may be used privately during case preparation to analyse evidence before deciding what belongs in the formal court chronology.
Court chronology
Short, neutral and date-ordered.
Usually records only material procedural and factual events and cross-references the relevant bundle pages.
Under PD27A it should ordinarily be agreed between the parties and is subject to the 10-page default limit.
Working timeline
An analytical tool used during preparation.
It can contain source, evidential status, competing accounts, contact due, professional response, child impact, relevance and other fields that would make a formal chronology too cumbersome.
It is not automatically a document to file with the court.
Think of it as compression
A large case might begin with:
5,000 pages of disclosure → 400 relevant documents → 150 timeline events → 45 materially important events → a concise court chronology.
The court does not need every fact you have collected merely because the fact exists.
Different chronologies answer different questions
A chronology is not a case summary
A case summary explains the background and procedural position in narrative form.
A chronology answers a more focused question: what happened, and when?
It should not become three pages of argument underneath every date.
Building an accurate chronology from the evidence
Start with documents capable of fixing dates reliably.
Depending on the case these may include:
- sealed court orders;
- applications;
- hearing notices;
- judgments;
- Cafcass reports;
- police records;
- school or medical records;
- social-care records;
- emails;
- messages;
- contact-centre records;
- and contemporaneous notes or correspondence.
Start with fixed points
Court order dated 3 February.
School email sent 8 February.
Contact due 10 February.
Police attendance 12 February.
Cafcass telephone interview 20 February.
These fixed events allow less certain or approximate dates to be placed around reliable anchors.
Date of event versus date of record
These can be different.
A professional record created on 20 June may describe something said to have happened on 17 June.
Do not automatically enter 20 June as the date of the underlying event.
| Date | Event | Source / bundle reference |
|---|---|---|
| 17 June 2026 | Child reportedly became distressed following handover; event later recorded by school. | School safeguarding record created 20 June 2026, C114. |
| 20 June 2026 | School created safeguarding record referring to the 17 June event and recorded action taken. | C114–C116. |
Use exact dates where the evidence supports them
If the evidence establishes an exact date, use it.
Where it does not, do not manufacture precision.
Appropriate chronology entries can use:
- “approximately March 2025”;
- “between September and December 2025”;
- “during the Easter school holiday”;
- or another honest chronological marker.
Keep formal entries short
PD27A says each formal chronology entry should be limited, if practicable, to one sentence.
The one-sentence discipline
Less useful:
“On 14 May there was yet another incident which demonstrates the respondent's complete disregard for the child's welfare and is part of the ongoing campaign which I have explained throughout my evidence...”
More useful:
“14 May 2026 — Weekend contact due under paragraph 7 of the order dated 2 February 2026 did not take place; the respondent's email at C214 gives the reason as illness.”
Cross-reference, do not reproduce
If a court order contains the relevant information, point to it.
If an email proves the date, give the bundle page.
The chronology should not paste the whole email beneath the entry.
Do not turn disputed allegations into chronology “facts”
Chronologies can become misleading when the language used silently upgrades a disputed allegation into an established event.
| Status | Chronology wording |
|---|---|
| Agreed fact | State the event neutrally. |
| Admission | State that the event is admitted where relevant. |
| Judicial finding | Identify the finding and the judgment or order containing it. |
| Disputed allegation | Attribute it: “Mother alleges…” / “Father says…” and identify the dispute where material. |
| Professional assessment | Identify whose assessment it is rather than presenting the professional opinion as a judicial finding. |
| Direct observation | Identify the observer or source where necessary. |
Compare the evidential effect
Unsafe wording:
“4 March — Father assaulted Mother.”
If the allegation remains disputed, that wording assumes the conclusion.
Neutral wording:
“4 March — Mother alleges Father struck her during handover; Father denies the
allegation; police incident record at D52–D58.”
If the court subsequently finds the allegation proved, the chronology can then be updated to record the finding accurately.
Agreement does not require pretending there is no dispute
PD27A provides the solution where parties cannot agree an entry.
The chronology should still, at final hearing, be a single document. Where the parties disagree, the disagreement and their differing contentions should be identified at the appropriate place.
Repetition is not automatically corroboration
Suppose one allegation appears in:
- a parent's email;
- a police log repeating that parent's report;
- a school note recording what the same parent told the school;
- and a Cafcass report summarising those earlier records.
That may still be one original account repeated through several documents.
A working timeline can help map:
Source chain
alleged event → first account → first contemporaneous record → later professional repetition → independent observation, if any.
This prevents one factual source from being accidentally counted as several independent events or pieces of corroboration.
Chronology can reveal inconsistency — but does not decide credibility
A timeline may show that:
- accounts changed;
- dates do not align;
- a document predates or postdates an alleged event;
- a professional acted before a later explanation was given;
- or an allegation was first recorded much later.
Those matters may be evidentially relevant.
But the chronology itself does not decide why the discrepancy exists or whether somebody is truthful. That remains a matter for evidence and, where necessary, judicial determination.
Safeguarding, domestic abuse and patterns over time
Chronology is particularly useful where the significance lies not in one event but in the relationship between events over time.
That can include allegations of:
- coercive or controlling behaviour;
- repeated threats;
- monitoring or surveillance;
- financial control;
- post-separation abuse;
- repeated interference with arrangements;
- litigation-related conduct;
- or repeated professional concerns.
Chronology + pattern analysis
A useful working timeline may therefore include:
| Date | Conduct / event | Source | Possible pattern relevance | Child / welfare impact |
|---|---|---|---|---|
| Date | Specific conduct described neutrally | Message / statement / record / finding | Monitoring / isolation / threats / arrangements / litigation | Observed or evidenced effect, if any |
That expanded analytical timeline may be useful in preparation.
The formal court chronology can then contain the material dates without becoming an argumentative spreadsheet.
Chronology helps show sequence; evidence proves the propositions
For example:
relationship separation → alleged threats → contact dispute → professional referral → court application → alleged post-separation conduct → safeguarding assessment → findings / no findings → later welfare recommendation.
Seeing the order of events may be highly important. But the sequence alone does not establish causation or prove every disputed allegation.
Re H-N and pattern-based analysis
Re H-N and Others (Children) (Domestic Abuse: Finding of Fact Hearings) [2021] EWCA Civ 448 remains an important authority on considering alleged coercive and controlling behaviour in context.
The chronology can assist that exercise where it reveals the duration, frequency, escalation or post-separation continuation of the alleged behaviour.
Child-centred chronology
A chronology should not become entirely adult-focused.
Relevant child events may include:
- changes in residence;
- when contact stopped or restarted;
- school changes;
- significant health events;
- professional referrals;
- important sibling changes;
- moves between areas;
- and long periods under interim arrangements.
Contact chronology
In cases where contact arrangements are disputed, a detailed working chronology can record:
- what contact was ordered or agreed;
- what was due to take place;
- whether it occurred;
- if not, what reason was given;
- when notice was given;
- whether replacement contact was offered;
- what indirect communication occurred;
- and whether any later order changed the position.
Working contact timeline
DATE → ORDERED ARRANGEMENT → WHAT OCCURRED → REASON GIVEN → SOURCE → REPLACEMENT OFFERED → COURT STATUS → CHILD IMPACT.
This can be far more useful than an undifferentiated list saying simply “contact was stopped repeatedly”.
Who prepares the chronology and when does it go into the bundle?
The latest court order always comes first.
Subject to any case-specific direction, PD27A provides the default framework for non-financial family proceedings.
Who takes the lead?
Usually the applicant takes the lead in preparing agreed preliminary documents, including the chronology.
But where the applicant is a litigant in person and another party is represented, PD27A provides that the represented party must take the lead in preparing those agreed documents.
Agreement timetable
Under the default PD27A timetable:
- the parties should seek to agree the contents of the bundle no later than seven working days before the hearing;
- the main bundle is ordinarily served and filed five working days before the hearing;
- and preliminary documents not already filed must ordinarily be served and filed by 11am on the working day before the hearing.
A case-specific court order may set different dates and must be followed.
The formal chronology at final hearing
PD27A requires:
- one up-to-date chronology;
- in an agreed form;
- with disagreement recorded where necessary;
- entries limited to one sentence where practicable;
- bundle cross-references;
- and a normal maximum length of 10 pages.
Agreement process
A practical way to prepare it is:
draft → send editable copy → identify agreed entries → mark genuinely disputed wording → rewrite neutrally where possible → retain both contentions where disagreement remains → finalise one document.
Do not delete inconvenient events merely to achieve “agreement”
Agreement should improve accuracy, not sanitise the procedural history.
Where an event is relevant but its interpretation is disputed, the chronology can record the event and the respective positions.
Remove outdated chronologies
PD27A requires superseded preliminary documents — expressly including outdated chronologies — to be removed when the bundle is updated for a later hearing.
Bundle references must remain stable
If a chronology says: “C214”, the judge should be able to go directly to that page.
This is one reason the chronology should ordinarily be finalised alongside the hearing bundle rather than months in advance with page references that no longer match.
The JSH Law chronology audit
Seven questions for every chronology
1. DATE
Is the date accurate, approximate or inferred — and have I made that clear?
2. EVENT
What actually happened, stated as concisely and neutrally as possible?
3. STATUS
Is this agreed, alleged, admitted, observed, professionally assessed or judicially found?
4. SOURCE
What document or witness supports the entry?
5. REFERENCE
Can the judge find that document immediately in the bundle?
6. RELEVANCE
Why does this date matter to a live procedural, factual, safeguarding or welfare issue?
7. PROPORTION
Does this event genuinely need to appear in the formal chronology?
A simple court chronology format
| Date | Event | Bundle reference |
|---|---|---|
| 12 January 2026 | Applicant filed C100 application seeking variation of existing child arrangements. | A1–A14 |
| 5 February 2026 | Court made interim child-arrangements and safeguarding directions. | A35–A42 |
| 18 March 2026 | Cafcass filed safeguarding material identifying the issues recorded at paragraphs 12–18. | C22–C29 |
| 7 April 2026 | FHDRA took place; court directed section 7 report and continued interim arrangements. | A65–A72 |
A more detailed working evidence timeline
| Date | Event | Source | Status | Issue / relevance |
|---|---|---|---|---|
| Date | Concise description | Document / witness / record | Agreed / alleged / finding / assessment | Contact / risk / child impact / procedure |
Common chronology mistakes
| Mistake | Better approach |
|---|---|
| Everything is included | Include material dates. Keep minor background in the working timeline if needed. |
| Every entry argues the case | State the event neutrally and reserve argument for the position statement or submissions. |
| Allegations appear as facts | Attribute disputed accounts and identify findings accurately. |
| No source | Cross-reference material entries to the bundle wherever practicable. |
| Record date is mistaken for event date | Separate the underlying event from the later report or professional record. |
| Multiple records are treated as multiple events | Trace the original source and distinguish repetition from independent evidence. |
| Outdated chronology left in bundle | Replace superseded versions with the current chronology in accordance with PD27A. |
| Twenty pages of detail | Apply the current 10-page limit unless the court has specifically directed otherwise. |
30-point chronology checklist
1. What is this chronology for?
2. Which hearing will use it?
3. Does the latest order direct one?
4. Is it a formal chronology or private working timeline?
5. What date does the chronology begin?
6. What date does it end?
7. Are the dates in strict chronological order?
8. Are exact dates supported by evidence?
9. Have approximate dates been labelled honestly?
10. Have I separated event date from record date?
11. Is each formal entry concise?
12. Could each entry be reduced to one sentence?
13. Is every event actually relevant?
14. Have I removed minor adult disputes?
15. Have I included important procedural orders?
16. Have I included material changes affecting the child?
17. Have I distinguished allegations from findings?
18. Have I distinguished professional opinion from judicial fact?
19. Are disputed events attributed?
20. Have I traced repeated records to their original source?
21. Are bundle page references accurate?
22. Does every material entry have a source where practicable?
23. Have I accidentally argued the case in the chronology?
24. If domestic abuse is relevant, can the sequence show the alleged pattern without reducing it to isolated incidents?
25. Does the chronology show important periods of delay?
26. Does it reflect the timetable for the child where relevant?
27. Has the other party had a proper opportunity to comment on the draft?
28. Are any disagreements shown accurately within the single document?
29. Is the chronology within the current 10-page limit unless otherwise directed?
30. Could a judge unfamiliar with the case understand the sequence quickly?
Primary sources and official guidance
- Practice Direction 27A — Family Proceedings: Court Bundles — current chronology requirements, agreement, bundle cross-referencing, responsibility, page limits and filing timetable.
- Judiciary — Preparing Court Bundles for Family Proceedings: Guide for Litigants in Person — official practical guidance accompanying the March 2026 PD27A regime.
- Practice Direction 12B — Child Arrangements Programme — timetable for the child, private-law case management and the importance of significant child-centred dates.
- Practice Direction 12J — Domestic Abuse & Harm — domestic abuse, factual issues, patterns of coercive and controlling behaviour, risk and child impact.
- Re H-N and Others (Children) [2021] EWCA Civ 448 — context, patterns of coercive and controlling behaviour and proper domestic-abuse analysis.
- Family Procedure Rules — Part 22 — evidence and witness statements, helping distinguish the chronology from the underlying evidential material.
- Family Procedure Rules — Part 4 — case-management powers and procedural directions.
Years of family-court history and no clear way to present it?
JSH Law can help turn large volumes of messages, orders, professional records and disclosure into a structured chronology and working evidence timeline.
Support can include procedural chronologies, contact timelines, safeguarding timelines, evidence-source mapping, bundle cross-referencing and identifying the material events that actually need to appear in the court-facing chronology.
We can also help distinguish: allegation from finding, event date from record date, repetition from independent corroboration and procedural delay from substantive welfare change.
The aim is not simply to put everything in date order. It is to make the history usable, evidentially accurate and easier for the court to understand.
Book a Free 15-Minute Consultation
© 2026 JSH Law Ltd. All rights reserved.
© 2026 JSH Law Ltd. All rights reserved.
© 2026 JSH Law Ltd. All rights reserved.
© 2026 JSH Law Ltd. All rights reserved.