Log the issue, not every bubble
Twenty messages about one school trip are one communication event. Give it a topic—“Year 6 trip consent and payment”—then record the initial request, material replies, decision and unresolved action. Attach the export or screenshots as the source. This keeps volume from disguising substance.
A useful log answers: What needed to happen? When was the information sent? Was an answer required? What answer came? What was the effect? A screenshot folder alone cannot answer those questions quickly.
Use a decision tree before saving
- Does the communication affect the child, schedule, care, cost, decision or safety? If no, don't log it.
- Does it contain a new request, answer, agreement or material refusal? If yes, update the issue entry.
- Is it abusive or threatening but unrelated to logistics? Preserve it safely if relevant to professional advice; don't repeatedly summarise every line.
- Is no reply itself material? Record the request, reasonable response point, follow-up and practical consequence. Don't describe silence as refusal unless the facts support that label.
- Has the issue concluded? Record the outcome and close the thread.
Copyable communication-log template
TOPIC / CHILD:
CHANNEL + THREAD REFERENCE:
OPENED DATE/TIME:
REQUEST OR INFORMATION SENT:
RESPONSE NEEDED BY + REASON:
RESPONSE RECEIVED DATE/TIME:
FACTUAL SUMMARY OF MATERIAL RESPONSE:
OUTCOME / WHAT WAS AGREED:
PRACTICAL EFFECT IF UNRESOLVED:
ORIGINAL MESSAGE REFERENCES:
FOLLOW-UP DATE:
STATUS: open / agreed / declined / no response / supersededA realistic completed entry
Topic: Orthodontist appointment, N
Opened: 7 June, 09:14 by email
Request: Confirm availability for either 18 June 16:00 or 20 June 09:00; clinic holds slots until 10 June.
Response needed: 10 June, because the clinic hold expires.
Response: 10 June, 18:42: “20th works.”
Outcome: 20 June slot booked at 18:55; confirmation forwarded at 19:02.
Evidence: COM12-A original email thread; COM12-B clinic confirmation.
Status: Agreed.
The summary makes cooperation visible. A good record isn't limited to disputes.
Record no response precisely
“Ignored me” combines fact and judgment. A better entry states the channel, sent time, delivery information if available, follow-up and deadline consequence.
“Message requesting consent for the school trip sent 2 September at 08:10. The form was due 6 September. Follow-up sent 5 September at 17:30. No response received by 6 September at 12:00. I told the school consent was still pending.”
If a later response arrives, add it to the same issue entry with its actual time. Don't alter the earlier status.
Preserve context and privacy
Keep enough preceding and following messages to show meaning, including your own contribution. Cropped screenshots can remove qualifiers, dates or the message being answered. Prefer a native export when available, and retain the original file.
Before sharing, check phone numbers, account details, health information and third-party messages. A private log may contain material that should not be filed or circulated. A local lawyer or court direction determines what must be disclosed and in what form.
Do I need screenshots if I have summaries?
Keep the originals. A summary helps navigation; it should not replace the material it summarises.
How should I log phone calls?
Record date, participants, topic, material points and agreed actions soon afterward. A short written confirmation can reduce later misunderstanding. Recording laws vary by location.
Should response time be calculated automatically?
It can help for genuine time-sensitive requests, but raw averages may mislead. Note whether a response was actually required and why the deadline mattered.
Sources