Copyable thread-level communication log
MESSAGES 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 messages 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 messages opened | Appointment question sent | COM-2026-018.
18 Jun | Medical messages 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.
How Casewell can help
Casewell keeps dated notes and their files together, then exports the ones you choose as a PDF for a lawyer, a mediator or your own records.
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.
Sources
Legal steps and terms vary. These official sources were checked for the general points used in this guide.