How to Document What Your Child Reported

Your child said something on the drive home from the other parent’s house. It mattered. You want it in your custody log accurately, and you want to be sure you don’t do anything that weakens the entry later in court.

What family-law attorneys and custody evaluators look for in an entry like this is narrower than most parents expect. They want the child’s words, verbatim, with the surrounding context: who was present, when it happened, what prompted it, what you said back. They don’t want your interpretation. They especially don’t want to see a string of leading questions in the lead-up. That pattern is one of the first things a Guardian ad Litem (GAL) or evaluator is trained to flag.

This post covers the direct-quote logging format for child disclosures, the leading-question discipline that protects the entry, and the general hearsay tension that makes child statements one of the more legally sensitive categories of custody documentation.

Why direct quotes outweigh your interpretation

The child’s actual words are the data. Your interpretation isn’t.

Custody evaluators, GALs, and family-court judges read child-statement entries with a specific question in mind: what did the child actually say, in what context, and was the documenting parent restrained or pursuing? An entry that reports “M was clearly upset because her dad has been yelling at her” tells the reader almost nothing verifiable. An entry that reports “M (8), unprompted, on the drive home at 6:47pm Sunday: ‘Dad was yelling really loud at the TV again and then he yelled at me for being scared.’ I said: ‘I’m glad you told me. Are you okay?’” tells the reader exactly what the child said and exactly what the parent did.

Contemporaneous, specific, verbatim records carry more evidentiary weight in most jurisdictions than reconstructed narrative. (See, e.g., Federal Rules of Evidence Rule 803, which governs hearsay exceptions including recorded recollection; state evidence rules follow similar principles.) For child-statement entries specifically, the verbatim standard does extra work: it removes the question of whether the parent is filtering, dramatizing, or characterizing the child’s account.

The discipline is to record what the child said and let the words stand. The court, through whatever process applies in the case, decides what to do with them.

The hearsay tension, in general terms

Child statements are one of the most legally sensitive categories in your log. Understand the general frame; let your attorney handle the specifics.

In most U.S. jurisdictions, statements made by someone outside the courtroom (including a child to a parent) fall under the general definition of hearsay. (See Federal Rules of Evidence Rule 801 for the general definition.) That doesn’t mean they’re useless. It means the path by which the child’s account reaches the court is usually more complicated than the path for other kinds of evidence.

Family courts handle this in different ways. Many use custody evaluators or GALs who interview the child separately and report their findings to the court. Some use in-camera (in-chambers) interviews where the judge speaks with the child outside the courtroom. Some jurisdictions allow specific hearsay exceptions for statements made by children in particular contexts. The applicable approach depends on the jurisdiction, the judge, the age of the child, and the nature of the statement.

What this means for your log: your job is to make sure the record of what the child said is as clean as possible (verbatim, contextualized, non-leading). Your attorney’s job is to decide what to do with that record in your specific case. Don’t try to construct the entry for a specific legal theory you don’t yet have; build it for accuracy and the legal use will come later.

The post you’re reading isn’t legal advice for your case. It’s the documentation discipline that gives your case the best raw material to work with.

The five-field child-statement entry

Use a structured entry for every child disclosure, with the five fields below in the order shown.

The format applies the same five-element discipline as a general custody log entry, calibrated for the specific risks of child-statement documentation.

1. Date, time, and location of the disclosure. This is the date and time the child told you, which may be different from the date of the underlying event the child is reporting. Both can matter, and both can go in the entry, but the disclosure context is the anchor. Example: “Sunday, May 17, 2026, 6:47pm, in my car, on the drive home from the exchange at the school parking lot.”

2. Who else was present. Witnesses change the evidentiary picture. If a sibling, a grandparent, or any third party was in the car, in the room, or within earshot, name them. If no one else was present, write “no one else present.” Silence on this field is worse than the truthful answer either way.

3. What prompted the statement. The most consequential field for evaluator review. Three categories: unprompted (the child raised it on their own), open question from you (“anything you want to talk about?”), or specific question from you. If you asked a specific question and the child answered, log the question verbatim too. If the child volunteered the statement, write “unprompted.” Custody evaluators read this field first.

4. The child’s words, verbatim, in quotation marks. Quote the exact wording. If you can’t remember the precise phrasing, say so explicitly: “M said something close to: ‘He was really mad at me again.’” That hedged precision is more credible than fabricated precision. Avoid paraphrase, summary, or translating child-language into adult interpretation. “Dad got mad at me” is the data; “Dad emotionally abused our daughter” is interpretation.

5. Your response. What you said back, what you did. One or two sentences. “I said: ‘I’m glad you told me. Are you okay?’ I did not ask follow-up questions. M then changed the subject.” Your restraint is itself documentable, and an evaluator reading the entry months later will notice that you didn’t pursue.

What you didn’t ask, you didn’t lead

The leading-question trap is the most common way a well-intentioned parent contaminates a good disclosure.

A leading question suggests the answer. “Did your dad yell at you?” is leading. “Did he hit you?” is leading. “Were you scared?” is leading. Custody evaluators and GALs are trained to identify when a child’s account has been shaped by the questioning parent. Once a pattern of leading questions appears in a log, the disclosure that follows becomes harder for the court to credit.

The open-question alternatives that don’t lead:

“How was your weekend?”
“Anything you want to talk about?”
“How are you feeling today?”
Or simply silence; many of the most useful child disclosures happen when the parent is doing something else and the child volunteers something.

When the child says something, the discipline is the same as the documentation: record what they said and what you said back. Don’t pursue. Don’t ask twelve clarifying questions. Don’t extract a fuller account. The next disclosure, if there is one, comes when the child raises it again on their own timeline.

One specific rule with no exceptions: never promise the child that what they tell you will or won’t get told to a judge, an attorney, or the other parent. You can’t keep that promise, and a custody evaluator who learns it was made may treat the disclosure with caution.

The reason this discipline matters isn’t only legal. The child is reporting an experience from their own home life. The parent’s job in that moment is to receive the statement, not to investigate it. The investigation, if one is needed, belongs to professionals: GALs, evaluators, therapists, attorneys, sometimes child-protective services. Your role is the faithful recorder.

Weak vs. strong: the same disclosure, logged two ways

The same disclosure from the same fictional family, logged two ways.

Weak version (15 words):

May 17. M told me her dad was mean to her again. Clearly upset.

Strong version (152 words):

Sunday, May 17, 2026, 6:47pm. In my car on the drive home from the exchange at the school parking lot. No one else present.

M (8) raised this unprompted as we were turning onto our street. She said:

“Dad was yelling really loud at the TV again and then he yelled at me for being scared.”

I said: “I’m glad you told me. Are you okay?” M said: “Yeah, I just don’t like it when he’s loud.” I did not ask follow-up questions. M changed the subject to dinner.

Note: M used the phrase “yelling really loud at the TV” earlier this month (logged 2026-05-03). Both reports involve the same general behavior pattern but different incidents. No physical injury reported in either disclosure. I have not asked M further questions about either incident.

Same disclosure. The weak version is fifteen words and could describe almost anything. The strong version captures the child’s exact words, the context that lets an evaluator assess whether the disclosure was leading or unprompted, the parent’s restrained response, and a brief pattern note for the parent’s own records.

That’s the difference between a child-statement note and a child-statement entry that holds up.

How Verascribe Guardian structures child-statement entries

The structure isn’t decoration. It’s the discipline, made automatic.

In the Verascribe Guardian workbook, you pick a category first: Communication, Significant Event, Parenting Time, and so on. For a child disclosure, you’d typically choose Significant Event, and the relevant fields surface for that type of entry: who was present, what prompted the statement (with “unprompted” as the default if you leave the field blank), the verbatim quote field with a length nudge that gently prompts you to capture more than a few words, the child’s response, and your response. Each field is structured to match the five-element format above, so the discipline is built into the form.

Timestamps are automatic. The entry is part of a cryptographically-verified chain, meaning if any entry were added, removed, or edited after the fact, the chain would break and the workbook would flag it. For child-statement entries specifically, that tamper-evidence matters more than for most other categories. The integrity of the record is part of what makes a disclosure credible to an evaluator or judge months or years after it was recorded.

Here’s the part most custody apps don’t tell you: most other tools in this space store your logs on the company’s servers. That means a company you don’t control holds your most sensitive family records, including everything your child has ever told you about the other parent’s home. Verascribe works differently. Your log lives in your own Google account: your Google Drive, your data, your control. Verascribe never holds your records, never sees them, and can never hand them over to anyone. The co-parent has no access. Neither do we.

Start your custody log

What you have now

You have a five-field template for child-statement entries and a discipline that keeps each entry usable. Date and context, who was present, what prompted the statement, the child’s words verbatim, your response.

The next time your child reports something about the other home, you have the format. Just as important, you have the discipline that protects the entry: log what they said, log what you said back, don’t pursue, don’t lead, don’t interpret. The child’s words, recorded faithfully, are the only version that holds up under the kind of review a GAL or custody evaluator will eventually apply.

Your restraint is part of the record too. The parent who logs and doesn’t extract reads, to a trained evaluator, as the parent the child can keep talking to.

The case is built one entry at a time. The most sensitive entries, the ones about your child, are the ones where the discipline matters most.