How to read this in the UK

Three things need to stay separate in a record. What the arrangement says, what actually happened, and the file that shows it. Blur them together and a reader has to take your word for it. Keep them apart and the record speaks for itself.

The UK is not one family-law system. England and Wales, Scotland and Northern Ireland each have their own rules, forms and vocabulary. Use the words that appear in your own order or agreement rather than a term borrowed from somewhere else.

Keep the complete source file, not a crop of it. Write events in the order they happened, and say plainly where something is missing or unclear. A family solicitor can work with a record like that. They cannot work with a reconstruction.

Which part of the UK your case is in

England and Wales, Scotland and Northern Ireland each have their own family courts and rules. Say which one your case is in, and use the same words your order or plan uses. Only mention addresses or schools when they help explain what happened. Before you treat a private timeline as a court document, check the rules with a solicitor.

Copyable thread-level communication log

COMMUNICATION ID: COM-[YEAR]-[NUMBER]
CHILD / TOPIC:
CHANNEL / THREAD REFERENCE:
OPENED DATE/TIME:
REQUEST OR INFORMATION SENT:
RESPONSE NEEDED BY: [date + practical reason]
RESPONSE RECEIVED: [date/time or none as of dated review]
FACTUAL RESPONSE SUMMARY:
EXACT QUOTE: [only if material and exact]
OUTCOME: [agreed / declined / unresolved / information only]
PRACTICAL EFFECT:
ORIGINAL MESSAGE REFERENCES:
FOLLOW-UP:
STATUS / LAST REVIEWED:
TIMELINE LINE:

A deadline belongs in the record only when it came from an order, agreement, institution or genuine practical need. Don't manufacture urgency after the fact.

Annotated example: six messages become one record

COM-2026-029. Topic: school trip consent. Channel: email thread MAIL-077. Opened 2 Sep, 08:16. Request: Parent A forwarded the school's consent form and asked whether Parent B agreed before the school's 5 Sep deadline. Responses: 2 Sep, 19:42, Need to check; 4 Sep, 21:10, Yes, agreed. Outcome: agreed.

Practical effect: form submitted 5 Sep, 08:05. Receipt SCH-031. Status: closed. Annotation: the two incoming messages remain in the original thread. But the timeline needs one line: 2–5 Sep | School messages | Consent requested, received and submitted by deadline | COM-2026-029. MAIL-077. SCH-031. This shows the outcome rather than selecting only the delayed middle response.

Rewrite tone claims as checkable facts

Emotional: She ignored me for days and then sent another rude brush-off. Factual: `Question sent by email 12 Jun, 09:04, asking whether the 18 Jun medical appointment could proceed. Reply received 15 Jun, 18:22: “Do whatever you want.” No answer to the appointment question was included. Follow-up sent 16 Jun, 08:10.

Status: unresolved as of 17 Jun, 12:00. ` The rewrite doesn't praise or excuse the response. It lets dates, the exact quote and the unresolved question carry the meaning.

What belongs in the log

Log schedule, school, health, travel, expenses and agreements when the exchange creates an action, decision, unresolved question or relevant pattern. Routine arrived or thanks messages usually don't need their own entry unless they complete an existing thread or timing itself matters. Keep enough context to prevent quote-mining.

If you screenshot, capture participants, timestamps and nearby messages. Keep a full export separately and use stable references in the log. The communication logs guide explains collection habits. This page is the working form.

Place communication in the chronology

Use the date the issue opened for the main timeline line and include the date range when it spans several days. If the eventual reply materially changes the outcome, update the thread status and add a second dated line rather than moving the first date. Example: 12 Jun | Medical communication opened | Appointment question sent | COM-2026-018.

18 Jun | Medical communication resolved | Agreement received after follow-up | COM-2026-018. This preserves sequence and stops ten screenshots from occupying ten timeline rows when they concern one decision.

Before you share your record

Everything above is about keeping your own record. Before you show any of it to someone else, a few extra steps help.

Work from a copy and leave the original untouched. Take out any private details the reader does not need.

Check that every important sentence links back to a date or a source. If one does not, rewrite the sentence rather than filling the gap with a guess.

Family law is different in England and Wales, Scotland and Northern Ireland. Make clear which one your case is in, and ask a family solicitor what the court rules let you share.

What a coherent UK record looks like

Casewell keeps the dated entry, its source file and any later addition together in one private timeline. When a review is needed, select only the records that answer the question in front of you and share those with a family solicitor.

Try for free
Should I log every message?

Usually not. Log substantive threads and keep the original conversation. A selectively defined but consistent log is easier to review than a duplicate of the entire inbox.

How do I record no response?

Write no response as of with the date and time of your review. Update the same thread if a reply arrives, while keeping the original status history.

Can I summarize a phone call?

Record the participants, time, duration, neutral summary and any follow-up confirmation you sent. Don't place reconstructed wording inside quotation marks.

Does this cover Scotland and Northern Ireland too?

No. England and Wales, Scotland and Northern Ireland have separate family-law systems, forms and terms. Use this page to keep your own record in order, and get advice from someone who works in your part of the UK.

Sources

England and Wales, Scotland and Northern Ireland have separate family-law systems, forms and terms. The official source gives orientation only. This page is a documentation guide, not legal advice.