How to Document Property Damage During a Custody Exchange

Your child’s backpack comes back from the exchange with a broken zipper and a tear down one side. Your first instinct is to send a message saying so. The message feels like doing something. It rarely holds.

What holds is a record. A photograph of the damage, the date and time the item came back, and a few lines that describe what you can see, with not a single word about whose fault it is. That record is the thing an attorney can actually use. The angry message is the thing opposing counsel reads back to you on cross-examination.

The reason most parents get this wrong is that they document the feeling instead of the fact. A torn jacket is upsetting and it feels like disrespect. But the entry that survives a challenge records the tear, the measurement, and the date. It leaves the disrespect for someone downstream to argue about.

This guide covers the one mechanic that makes damage provable at all (the condition baseline), the exact fields a damage entry needs, and the neutral-language discipline that keeps the entry from undermining itself. For the broader walkthrough that covers any incident at a handoff, see the general method for documenting an exchange incident. This post stays on one scenario: belongings damaged at the exchange.

What actually belongs in a damage record (and what’s just two-household wear)

The test is not how the damage makes you feel. It’s whether the damage is specific, visible, and describable without guessing how it happened. A scuffed shoe and a snapped strap are different categories, and only one of them is an incident.

Belongings that move between two homes take wear. A faded shirt, a missing sock, a sneaker with a grass stain, a paperback with a bent corner: that’s the ordinary churn of a child living in two places. Logging it reads as vigilance turned up too high, and a record full of trivia weakens the entries that matter.

Documentable damage is observable, specific, and recent. A broken zipper, a three-inch tear along a seam, a cracked phone screen, a snapped backpack strap. These you can photograph, measure, and describe in a sentence a stranger would understand.

Here’s the honest part. One damaged item, on its own, almost never changes a custody arrangement. The value lives in the documented pattern over a year, in a consistent format, that your attorney can read as a whole. Most returned items won’t meet the bar for documentation, and that’s normal. Skipping the sock is the discipline working, not a lapse in attention.

Step 1: Record the condition before it leaves (the baseline that makes damage provable)

A damage record is a before-and-after. Without the “before,” the “after” is just your word against theirs. This is the step none of the standard advice gives you, and it’s the one that makes the rest possible.

You can only show that an item came back damaged if you can show what it looked like when it left. Damage at return proves nothing on its own. The co-parent says the tear was already there, the screen was already cracked, the strap was already loose. With no baseline, you have an assertion, and so do they.

So capture the send-off condition on the days it’s worth it. A quick photo of the new jacket before it goes in the bag. A one-line note: “Sent grey North Face jacket, size youth M, no visible damage, 2026-06-04, 9:10am.” The school laptop, the prescription glasses, the expensive coat. The items that cost real money, can’t be easily replaced, or are already a point of contention.

Be realistic about scope. You are not photographing every sock. The baseline is for items where the loss would matter or where the co-parent has a history with that category of item. A contemporaneous note works as a baseline too, not only a photo; the date and the description carry most of the weight.

The send-off baseline is the hardest part of this method to sustain, because the trouble at return is the part you remember and the calm moment at send-off is the part you forget. That’s the problem the rest of this method, and the right tool, is built to solve.

Step 2: Photograph and record the moment damage is observed at the handoff

Photograph the damage within minutes of the handoff, while the item, the timestamp, and your memory all still line up. The window is short, and it closes fast once the bag is unpacked and the day moves on.

When the item comes back damaged, photograph it before anything else. Three shots: the damaged area in close-up, the whole item for context, and a frame that establishes scale and date if you can manage one (the item next to a ruler, or in the same shot as a timestamped phone screen). The general capture-and-corroborate routine is the same one covered in the sibling posts, so this section stays on the damage specifics.

Then record, in the same few minutes, the things that fade: the date and exact time of return, who was present, the condition you observed, and the link back to your send-off baseline if you captured one. This is the contemporaneous-capture move, and the principle behind why it carries weight is that records made while a matter is fresh are treated as more reliable than after-the-fact reconstruction. The plain-language version: a record offered later has to be authenticated as what it claims to be, and a photo taken minutes after the handoff authenticates more cleanly than a description written from memory a week later.

If your child also had something to say at the handoff or there was a verbal exchange about the damage, that’s a separate record. Route it to verbal incidents at the handoff rather than folding it into the damage entry.

Step 3: The exact fields a damage entry needs

The entry records condition and chronology. Not cause, not blame, not what it says about the co-parent. Give your future reader a clean, scannable record, and give yourself a template you can fill in fast while the bag is still by the door.

A property-damage log entry holds these fields:

Date and exact time of return. “2026-06-06, 6:14pm.”
Item, specifically named. “Child’s grey North Face jacket, size youth M.” Not “a coat.”
Observed condition at return. The damage, described physically. “Left sleeve seam torn; tear approximately 3 inches; zipper pull missing.”
Condition at send-off (baseline reference). “Baseline photo and note from 2026-06-04 send-off; no visible damage recorded; photo file 2026-06-04_jacket.heic.”
Who was present. “Exchange at primary location. My partner, P, present in passenger seat.”
Child’s observable response, if any. What the child did or said, recorded as observed only. “M said, ‘It ripped at Dad’s,’ then went to put the bag away.” No interpretation of what M felt.
Photo reference(s). “Three photos taken 6:16pm: close-up of tear, full jacket, jacket next to ruler. Files 2026-06-06_jacket_01 through _03.”

These fields are the property-damage application of what every custody log entry needs, extended to cover the baseline and the photo discipline this scenario specifically demands. The format is what makes thirty entries readable as one record.

Step 4: Write it in neutral language — describe the damage, not the motive

The entry that records what you can see survives cross-examination. The entry that records what you assume hands the other side something to attack. This is the discipline the whole post is built around, so the model entries below have to embody it.

This rule is narrow and strict. Record the observable damage. Never assert cause or intent. “He ripped it,” “she’s careless,” “out of spite,” “to upset her”: every one of those is a guess about something you didn’t see, and every one of them gives opposing counsel a place to put pressure. Describe the tear. Leave the motive out.

Here are two damage entries written each way, with what changed.

A minor item, weak version:

“Sent M’s jacket clean and now it’s torn. He clearly doesn’t care about anything I buy for her. This is so disrespectful.”

Same item, clean version:

“2026-06-06, 6:14pm return. Child’s grey North Face jacket, size youth M. Left sleeve seam torn, approximately 3 inches; zipper pull missing. Baseline: send-off photo 2026-06-04, no visible damage recorded. Three photos taken 6:16pm.”

What changed: the clean version drops “he clearly doesn’t care” and “disrespectful.” Those are your reading of the co-parent, and a reader can’t verify them. The measurements, the date, and the baseline reference are facts a stranger can check against the photos. The first entry is an opinion the other side can dismantle; the second is a record they have to work around.

A significant item, weak version:

“The laptop came back with a smashed screen because he lets her throw it around over there. He’s destroying her school stuff on purpose.”

Same item, clean version:

“2026-06-06, 6:20pm return. Child’s school-issued laptop. Screen cracked across lower-right quadrant; display shows visible fracture lines; device powers on. Baseline: send-off note 2026-06-04, screen intact, no cracks recorded. Two photos taken 6:22pm. M said the screen ‘broke at Dad’s’; recorded as stated, not verified.”

What changed: “because he lets her throw it around” and “on purpose” are gone. You didn’t watch it break, so you can’t record how it broke. The clean version records the crack, the baseline, and the child’s statement framed as a statement (“recorded as stated, not verified”) rather than as proof. That last move matters. A child’s report is something you log, not something you vouch for.

The clean version is the one an attorney can use. Whether a documented pattern of damage supports anything legally (a conversation about the cost of replacements, a note for an evaluator, or something more) depends on your order, your jurisdiction, and facts only your attorney can weigh. Your attorney can advise on how this record can be used in your specific situation. Your job is to make the record clean enough that the question is theirs to answer. For more on the gap between an entry that holds and one that doesn’t, see the difference between a weak entry and a strong one.

How Verascribe records the send-off condition contemporaneously

The send-off baseline is the part that makes everything else provable, and it’s the part that slips first when you’re doing it by hand. Remembering to capture the “before,” on a calm day, before anything has gone wrong, is exactly the discipline that fades under the weight of everything else.

Verascribe Guardian logs the send-off condition at the moment you capture it. You photograph the jacket, the note and the photo are tied to the same timestamp, and the entry is there waiting when the item comes back damaged. The before-and-after is already linked, so you’re not reconstructing the baseline from memory under pressure at return.

What sits behind it is the part that matters in high-conflict custody. The major custody apps store your logs on their servers, which means a company you don’t control holds your most sensitive family records. Verascribe works differently. Your records live in your own Google account. We never store your data on our servers. The co-parent can’t reach it, and neither can the company.

Every entry is also part of a verified chain. Each entry is tied to the one before it, so a later edit would show. That’s the difference between “these are my notes” and “these are notes that can be shown not to have been altered after the fact.”

Start logging with Verascribe Guardian and the next send-off condition is captured before the trouble starts.

The pattern is built one entry at a time

One torn jacket is a data point; a year of clean, dated, neutral entries with baselines is a documented pattern your attorney can work with. Treating the single item like a case is how the record gets cluttered with grievances instead of facts.

The record is the deed to what the item looked like, not a verdict on who damaged it. You author the first half of that record at send-off and the second half at return, and you keep the motive out of both.

So capture the next send-off condition on the items that matter. Record the next return cleanly, in the fields above, in language a stranger could check. The case for the pattern is built the same way every time, one entry at a time.