Your client and the other parent communicate through a co-parenting platform such as OurFamilyWizard, TalkingParents or AppClose, and a hearing is coming. Co-parenting app records can be some of the cleanest evidence in a family matter, because the platform, not either parent, controls the timestamps and the message history. They are also easy to misuse: a 900-page export handed up without an index, a cherry-picked exchange that invites a completeness objection, or a “viewed” timestamp asked to prove more than it can.
This guide covers what these records contain, how to obtain the official version, how foundation and hearsay usually work, and how to build exhibits a judge can follow in a short hearing. Family matters are decided under state rules. The Federal Rules of Evidence are cited here because many state evidence codes track them, but numbering and wording vary, so verify your forum’s version and local practice. This is general information for legal teams, not legal advice on any particular matter.
What do co-parenting app records actually contain?
More than messages. Depending on the platform and subscription level, one account can hold several distinct record types, and each proves something different.
| Record type | What it can show | Watch for |
|---|---|---|
| Message threads | Statements, refusals, admissions, tone, response times | Context that lives outside the app |
| Sent and viewed timestamps | When a request or notice was delivered and opened | What “viewed” means on that platform |
| Shared calendar and trade requests | The agreed schedule, swap requests, approvals and denials | A calendar entry is not proof an exchange happened |
| Expense logs | Reimbursement requests, receipts, responses, payments | Payments made outside the app |
| Journals or private notes | The client’s contemporaneous observations | Client-authored, possibly discoverable, not neutral |
Before anyone builds an exhibit, inventory which features the parents actually used and for what date range. Features differ between platforms and some are optional add-ons, so do not assume the other parent’s account looks like your client’s.
How do you get the official record instead of screenshots?
Use the platform’s own export or records process. Screenshots of the app on a client’s phone crop timestamps, drop attachments and invite authenticity fights that a platform-generated report usually avoids.
- Scope it. Identify the platform, both account holders, the features used and the date range that matters to the pleadings. Go a few weeks earlier than the first key event so the context is in the record.
- Preserve it. Tell the client in writing not to close the account, change the subscription or alter settings while the matter is pending, and confirm whether access to older history depends on an active subscription.
- Pull the party report. Most platforms let a user generate a printable or downloadable report for a date range. Have the client generate it, or walk them through it on a screen share, rather than collecting their password.
- Escalate when needed. If authenticity will be contested, or you need records only the platform holds, consider a subpoena or records request to the platform with a custodian certification. Follow the forum’s subpoena rules and any notice obligations.
- Fingerprint and log. Save the report exactly as received, record a hash value, note who generated it and when, and work only from copies.
How do you authenticate co-parenting app messages?
The threshold is modest. Under Rule 901(a), the proponent needs evidence sufficient to support a finding that the item is what it is claimed to be, and co-parenting records usually get there through familiar routes.
- Witness with knowledge (901(b)(1)). The client testifies that they use the account, generated the report on a stated date, and that it accurately reflects the thread.
- Distinctive characteristics (901(b)(4)). The account is registered to the other parent, and the content references facts only that parent would know.
- Process or system (901(b)(9)). Evidence that the platform produces accurate results, which matters most when the timestamps themselves are disputed.
- Certification (902(11), 902(13)). A qualifying custodian certification can make platform records self-authenticating if the advance-notice requirements are met. See our guide to self-authenticating electronic records under Rules 902(13) and 902(14).
For the foundation questions shared by all message evidence, see authenticating text messages under Rule 901.
Which messages are hearsay, and which aren’t?
Run the analysis message by message. One thread contains statements from different declarants offered for different purposes.
- The other parent’s messages, offered against them, are generally opposing-party statements under Rule 801(d)(2)(A) and not hearsay.
- Your client’s own messages are not party-opponent statements when your side offers them. Offered for their truth, they are hearsay. They are often offered for another purpose instead: to show that a request was made, that notice was given, or to make the other parent’s reply intelligible.
- Third parties on the platform, such as a stepparent or a professional with an access account, need their own analysis.
- Platform-generated data, like timestamps and view records, is treated by many courts as not a “statement” by a person at all, though the reliability of the system can still be challenged.
Expect completeness arguments. Rule 106, as amended in 2023, lets an adverse party require introduction of another part of a statement that in fairness ought to be considered at the same time, and it now reaches unrecorded statements too. Building fair excerpts up front is faster than litigating them at the hearing. Our article on hearsay and text messages covers the exceptions in more depth.
How should co-parenting app exhibits be built?
Present excerpts organized by issue, keep the full report available, and make every page traceable to the source.
- Group excerpts by issue (schedule interference, expense disputes, notice of medical or school decisions), each with the surrounding messages that give context.
- Keep the full report as a separate exhibit or available for inspection, especially if you rely on a summary.
- Confirm the time zone the report uses. Reports may reflect an account setting, and parents in different time zones can produce timestamps that look inconsistent.
- Add page or Bates numbers so the court and opposing counsel can find the same message in seconds.
- Prepare an index of key messages by date, sender, page and issue for counsel’s use at the hearing.
- For large volumes, consider a summary chart under Rule 1006, with the underlying records made available to the other side as the rule requires.
Template: summary chart row for schedule-change requests
Columns: Request date and time | Change requested | Response date and time | Response | Exhibit and page
Row: [MM/DD, time] | Swap weekend of [date] for [date] | [MM/DD, time] | Declined, no alternative offered | Ex. [ ], p. [ ]
What about communication that happened outside the app?
Assume it exists. Even when an order requires the platform, parents text about a late pickup, call from the school parking lot or email teachers together, and those exchanges often explain what the app record leaves out.
Collect the client’s texts, messaging apps and email for the same period, then reconcile them against the platform report in a single chronology with each entry labeled by channel. A tool like Message Extractor can normalize iPhone message exports made with iMazing, Android SMS backups, WhatsApp chat exports and email files into one paginated log with sender, timestamp and channel on every entry, which is far faster than lining up screenshots by hand. If the order mandates the app, off-app contact may itself become an issue for either side, so flag it for the attorney rather than quietly leaving it out.
Gaps cut both ways. If the other parent says “I told you by text,” you want those texts before the hearing, not during cross. A case chronology that merges every channel is the most reliable way to find the gaps first.
What goes wrong with co-parenting app evidence?
Most problems are preventable at intake. These are the recurring ones.
- Reading only the other parent’s side. The record cuts both ways. Review your client’s messages first; anyone reading a long thread sees both parents’ tone.
- Overreading “viewed.” A view timestamp may show a message was opened. It does not necessarily show it was read in full, understood or agreed to.
- Wrong date range or missing attachments. Confirm the export includes attachments and expense receipts, not only message text.
- Producing journals by accident. Private journal entries are your client’s statements. Decide deliberately whether and how they are used, and assume they may be requested in discovery.
- Treating calendar entries as attendance records. A shared calendar shows the plan. Prove what actually happened with exchange records, messages and witnesses.
- Volume over clarity. A judge with a short hearing slot is unlikely to read hundreds of pages. A dozen well-chosen, indexed excerpts usually communicate more than the whole export.
