Start with the planned contact
Record the source of the plan first. The order, written agreement, calendar entry or confirmed message. Add the date, scheduled start and end, exchange place and who was expected to attend. This prevents the log from becoming a memory of disappointment rather than a comparison between plan and outcome.
Record what actually happened
Use separate fields for actual start, actual end, whether contact went ahead, and whether the contact was changed by agreement. If the reason was given in a message, summarize it and attach the full thread. If the reason is unknown, write that it was not known at the time.
Include ordinary contact too
A contact log that only records problems can look selective. Include completed contact, agreed changes and make-up time. Everyday entries give the reviewer a baseline and make repeated missed or late contact easier to count.
Connect every entry to evidence
Attach or reference the message, call log, calendar record, travel receipt, school note or witness observation that supports the entry. Do not force weak evidence into the log. A blank evidence field is better than implying proof exists when it does not.
Prepare the log for professional review
Before sharing the log, filter it by date range and issue. Add a short cover note naming the question for review, such as missed weekend contact or repeated late returns. Keep originals separately and ask a qualified expert what should be included.
Use one reference for each source
Give every order, message thread, call log and file a stable ID, then use that ID in the contact row. This lets a reviewer verify an entry quickly and makes later corrections less confusing.
Contact log checklist
Use this checklist for each contact period.
Copyable contact log row
Paste this into a spreadsheet or use it as the structure for a Casewell entry.
DATE:
SCHEDULE SOURCE:
PLANNED CONTACT:
ACTUAL CONTACT:
EXCHANGE LOCATION:
WHO WAS PRESENT:
MESSAGES SUMMARY:
EVIDENCE REFERENCES:
CHILD-RELATED EFFECT:
FOLLOW-UP OR MAKE-UP TIME:
KNOWN GAPS:- Useful wording
Scheduled contact was 10:00-16:00 under ORD-03. Contact began at 11:12. Message at 09:48 said traffic. Screenshot MSG-044 attached.
- Weak wording
Late again and clearly does not care about the order.
Example: reviewable contact entry
The strongest entry gives the reviewer facts and limits.
- Planned
Saturday 10:00 to 16:00, exchange at library car park, source ORD-03.
- Actual
Exchange completed at 11:12. Contact ended at 16:02.
- Communication
Message at 09:48 stated traffic. No earlier notice in the thread.
- Evidence
MSG-044 screenshot and complete thread export kept.
- Limit
Reason for delay not on its own verified.
Turn the log into a review-ready chronology
Casewell lets you keep each contact entry private, attach the supporting screenshots or files, and export a filtered PDF for attorney review, mediation or family court planning when the record needs to be easy to follow.
Should a contact log include successful contact?
Yes. Successful and everyday contact creates the baseline that lets an expert understand whether later missed or delayed contact is part of a pattern.
Is a contact log legal evidence?
A contact log can support planning, but a court or expert decides relevance, court process and weight. Keep the source material behind each entry.
How detailed should each entry be?
Use enough detail to reconstruct the plan, actual outcome, evidence and follow-up. A short complete entry is usually better than a long emotional narrative.
Sources
Legal steps and terms vary. These official sources were checked for the general points used in this guide.