How to Document a Missed Exchange

A missed exchange, by itself, is a story your co-parent can spin. A missed exchange logged within the hour, in five fields, with the texts and the photo metadata attached, is something a judge can read. The difference between those two artifacts is what your retainer will eventually pay for, or save you from paying for.

What courts and attorneys actually want from a missed-exchange entry is the five fields a custody evaluator already knows how to scan, in the verbatim language the parenting plan uses, with corroboration that survives a challenge to authenticity. Long paragraphs about how upsetting the incident was do not survive that scan. Most parents log the wrong fields, in their own paraphrase, with screenshots that cannot be authenticated.

This guide covers the five fields every missed-exchange entry must contain, the verbatim-language standard that protects the entry from impeachment, and the corroborating evidence (texts, photos, location records) that turns one missed exchange into pattern data over time.

Why one missed exchange isn’t a case

A single missed exchange rarely moves a court. A documented pattern of missed exchanges, in a consistent format, often does. That distinction is structural, and it shapes everything about how to log the first one.

A first missed exchange is almost always explainable. Traffic. A sick child. A work emergency. The co-parent’s car. Your attorney knows the explanations because opposing counsel will offer them. One incident, however well documented, can usually be absorbed by the other side’s story.

What cannot be absorbed is the same incident logged twenty times across six months, each entry in the same five-field format, every one timestamped within an hour of the event and matched against a saved text thread. That record describes a pattern of conduct rather than a bad day. In many jurisdictions, family courts and custody evaluators weight a consistent pattern of unilateral non-compliance more heavily than any single incident. The shift from incident-thinking to pattern-thinking is the operator’s move.

That’s why the first entry matters. It doesn’t have to prove anything on its own. It has to be the first row of a record that gets read as a whole. Whether your specific situation eventually rises to a contempt filing, a modification, or a useful exhibit for your attorney is a question for that attorney, working from the documented deviation pattern the record establishes. The record is the operator’s job. The legal use of the record is the lawyer’s.

The five fields every missed-exchange entry needs

These five fields are the missed-exchange application of the five things every custody log entry needs, focused on one specific incident type.

Every missed-exchange entry holds the same five fields: the scheduled event, what actually happened, the communications around it, the child’s exposure and response, and the corroborating evidence on file. The format is the discipline. Without the format, the record reads as a diary.

The five fields, in working form:

Scheduled event per the order. Quote the parenting plan exactly: the date, the time, the location, and the paragraph reference. “Friday, May 8, 2026, 6:00pm exchange at the primary exchange location (parent’s residence, per Parenting Plan dated June 1, 2025, paragraph 3.4).”
What actually happened. Timestamped, factual, in the language of behavior rather than interpretation. “I arrived at 5:55pm with M (9). At 6:00pm, no co-parent present. At 6:30pm, no co-parent present. At 7:14pm, after no contact, I left the location with M.”
Communications around the event. Verbatim quotes from any text, voicemail, or email, with timestamps. Note the absence of communication when that’s what happened. “At 6:18pm I texted J: ‘I’m at the exchange location with M. Are you on the way?’ No response received by the time I left at 7:14pm.”
The child’s exposure and response. What the child saw, heard, said, and did, in the child’s words where you heard them. Recorded contemporaneously. “At 6:35pm, M asked, ‘Is Daddy coming?’ I told M I wasn’t sure and we’d wait a little longer. M stayed in the car the rest of the time and didn’t ask again.”
Corroborating evidence on file. What you saved, what file names, what witnesses. “Text thread exported to 2026-05-08_J-texts.pdf at 7:32pm. Photo of empty driveway taken at 6:15pm (filename IMG_4421.HEIC, original metadata retained). My partner, P, was present in the passenger seat throughout.”

Five fields, every time. A custody evaluator scanning thirty of your entries should see the same shape on every one. The format is the case the format is building.

The verbatim-language standard

Paraphrase is the most common reason a strong incident weakens by the time it reaches court. Quote the parenting plan in its exact words. Use the co-parent’s actual text in quotation marks. The child’s question goes into the entry the way the child asked it. Where you can’t recall the exact wording, mark it as approximate explicitly.

The parenting plan is its own document, with its own language. The order may use the term “primary exchange location” or “shall return the child by” or “right of first refusal.” Use those exact phrases in your entry. When the entry quotes the order in the order’s own words, the entry lines up with the document a judge will be reading next. When the entry paraphrases, the alignment breaks: now the judge is comparing your paraphrase to the order’s actual language, and the entry’s specificity is the first thing to lose weight.

Apply the same treatment to the co-parent’s words. “J said he’d be there in twenty minutes” is your reading of what J said. “At 6:32pm, J texted: ‘Running late. There in 20’” is the message. Quote the message. Save the message. If the words came in a voicemail, transcribe them in quotation marks and note “transcribed from voicemail received at [time]; original audio file saved.”

A child’s words matter the most, and they’re the words parents most often paraphrase. “M was upset” is interpretation, not evidence. “M said, ‘Why is Daddy always late?’” is evidence. Verbatim child quotes survive cross-examination in a way that adult interpretation of a child’s emotional state does not. Where you didn’t catch the exact words, write what you can recall and label it. “M said something close to: ‘I don’t think he’s coming.’” Explicit hedging is stronger than fabricated precision.

The principle behind all three (plan, co-parent, child) is the same. The court treats the record as the closest approximation available of what actually happened. Specifics that can be tested hold up. Adjectives that can’t be tested don’t.

Corroborating evidence: texts, photos, and what a screenshot can’t do

A screenshot of a text message is not the text message. In many courtrooms, raw screenshots face authentication challenges that the native export of the conversation does not. The discipline is to keep both, and to know which one carries the weight.

Screenshots are easy. They’re also easy to alter, easy to crop, and easy to challenge. A native message export (from iPhone, Android, or whichever messaging platform) typically includes timestamps, sender identifiers, and metadata that a screenshot strips out. Whenever a text exchange becomes part of an incident entry, export the full thread, save it with a date-stamped filename, and store it in the same location as the entry. The screenshot is a quick visual reference. The export is the evidence.

Photos at an exchange location follow the same logic, with one added trap. A photo of an empty driveway at 6:15pm is only evidence if the file’s timestamp and (where available) location data can be relied on. Take the photo on the device that natively records that metadata. Don’t crop it. Don’t screenshot the photo and discard the original, and don’t export it through a chat app that strips the data. Save the original file, with the original metadata intact, alongside your entry. Where the metadata is unavoidably stripped (a forwarded image, a screenshot of a photo), note in the entry the time you took the original and the witness who saw you take it. Honest hedging beats invisible loss.

Location records can corroborate where you were. A Google Maps Timeline entry showing your phone at the exchange address from 5:55pm to 7:14pm matches your text timestamps. A transit receipt, a parking app charge, a dashcam clip: anything that independently shows you at the place you said you were, at the time you said you were there, strengthens the entry. Save the relevant export at the time of the incident, not six months later when the cloud history may have rolled off.

Witnesses are corroboration too. Name them in the entry: the school staff member who watched you wait in the lobby, the grandparent in the car, the friend you called from the location at 6:30pm. Note what each witness observed, and keep their contact information separately so the entry stays clean. Witness names in the log don’t compel a deposition. They preserve the option.

One more habit worth building. The moment the missed exchange is logged, screenshot the entry itself (the entry, not the conversation it documents) and back the file up to the location your full archive lives in. That second copy, taken at the time of writing, is itself contemporaneous proof of when the entry was created. It’s a small step. It closes the gap a hostile attorney might otherwise pry open.

Worked example: a missed Friday exchange

Same incident. Logged two ways.

The weak version (16 words):

May 8 — J never showed for the Friday exchange. Waited an hour. Disrespectful as always.

The strong version (full five-field entry, ~210 words):

Scheduled event. Friday, May 8, 2026, 6:00pm exchange at the primary exchange location (parent’s residence, per Parenting Plan dated June 1, 2025, paragraph 3.4).

What happened. I arrived at 5:55pm with M (9). At 6:00pm, J was not present. At 6:30pm, J was not present. At 7:14pm, with no contact received, I left the location with M and drove home.

Communications. At 6:18pm I texted J: “I’m at the exchange location with M. Are you on the way?” No response received. At 6:45pm I texted J: “Heading home at 7:00pm if I haven’t heard from you.” No response received. As of entry time (7:42pm), no message from J. No voicemail. No prior notice of any change.

Child’s exposure and response. At 6:35pm, M asked, “Is Daddy coming?” I said I wasn’t sure and we’d wait a little longer. At 6:50pm, M asked, “Can we just go home?” M did not ask about J again on the drive home.

Corroborating evidence. Text thread exported to 2026-05-08_J-texts.pdf at 7:32pm. Photo of the empty driveway taken at 6:15pm (file IMG_4421.HEIC, original metadata retained, saved to evidence folder at 7:35pm). Witness: my partner P was in the passenger seat from 5:55pm to 7:14pm and on the drive home.

Same underlying event. The first version is a complaint. The second is an entry your attorney can read in ninety seconds, attach to a motion if the pattern eventually warrants one, and hand to a custody evaluator without rewriting. The difference between the two is roughly twenty minutes of disciplined writing at the moment the event was still fresh. That’s the trade.

How patterns get built (and how to keep the log credible)

Pattern evidence is built by logging consistently, in the same format, across both the bad days and the routine ones. A selective record reads as selective. A habitual record reads as habitual.

Contemporaneous logging is the rule. Within an hour of the event where possible. Where the entry is reconstructed (the event happened on a Tuesday and you didn’t get to write it up until Wednesday morning), say so in the entry itself: “Entry reconstructed Wednesday May 13 from text timestamps; original waiting time logged at the location via text.” Acknowledged reconstruction is honest. Unacknowledged reconstruction is what opposing counsel hunts for.

Log the voluntary swaps too, when the co-parent shows up on time, when an agreed schedule change goes smoothly. A log that only contains complaints reads as a complaint file. A log that contains complaints alongside the routine entries reads as a record. The routine entries don’t dilute the bad ones; they validate the bad ones by establishing that you’re not only writing when you’re upset.

The running tally is its own document, separate from the entries. A short summary, sorted by month, that counts the late or missed exchanges and references the entry IDs. Updated at the end of each month. When the time comes to walk into your attorney’s office, the running tally is the page they read first; the underlying entries are what they pull when they want to verify any single row.

Gaps in the log are noticed. If you stop logging for six weeks (vacation, a death in the family, a bout of depression), note the reason briefly in the next entry: “Entry break May 21 to July 3, family bereavement; no incidents logged but co-parent communications archived per usual.” Explained absence reads better than unexplained absence.

The discipline that holds the log together is small and daily. Same five fields. The same verbatim-quote habit, the same file-naming convention, the same folder. The pattern emerges over months without ever being the goal of any single entry.

How Verascribe Guardian structures this

The category surfaces the right fields automatically. You pick Parenting Time or Schedule from the log’s category list, and Verascribe presents the five fields this article describes (scheduled event, what happened, communications, child exposure, evidence on file) as the entry shape. The format you’ve been writing by hand is the format the app builds for you, every time.

Evidence attachments live in the Evidence Locker. You drop the text-export PDF or the photo of the empty driveway into the entry’s attachment slot. Each file gets a unique fingerprint when it’s stored, taken from the file’s contents at upload time. If the file is altered later, the fingerprint no longer matches the one on record. That property, a record that can be shown to be unchanged, is what survives a challenge to authenticity in a way a folder of loose screenshots cannot.

Here’s what most custody apps don’t tell you. Most other tools in this space store your logs and your evidence files on the company’s servers. That means a company you don’t control holds your most sensitive family records. The other parent’s attorney can subpoena those records from the company, on terms you didn’t write. Verascribe works differently. Your logs and your uploads live in your own Google account, in your own Google Drive. We never hold them. We never see them. The co-parent can’t reach them through us, because there’s nothing on our end to reach. A subpoena to Verascribe returns nothing, because we don’t have your records to return.

Start your custody log

What you have now

You have a five-field template that turns a missed exchange into an entry your attorney can read in ninety seconds. Scheduled event, actual event, communications, child exposure, corroborating evidence. The verbatim-language standard. The corroboration discipline.

Before the next exchange happens, tonight or before bed, write the template down somewhere you can reach it on your phone. The next missed or late exchange will arrive without warning, and the difference between a strong entry and a weak one is whether the template was already in your hands when the event began.

The case is built one entry at a time.