Keep dated, factual entries that distinguish what you observed from what someone told you. Connect each entry to the relevant original messages, photographs or documents, and preserve those separately. This is an organizational guide with a Texas example, not a determination of what your court will accept.

What one entry should contain

  • The event date, time and location; include the time zone when travel makes it relevant.
  • The date you wrote the entry, especially if you are recording it later from memory.
  • Who was present, what you personally observed, and what you learned from someone else.
  • Exact words only when you can quote them accurately. Label a remembered summary as a summary.
  • The practical effect on the child and your response, without guessing anyone’s motives.
  • The identifiers of related files and where the originals are kept. A screenshot is a capture of a source, not the source conversation itself.

Keep it factual and consistent

Use the same fields for each entry. Record events promptly when it is safe to do so. If you discover an error, append a dated correction that explains it instead of silently replacing the earlier account.

Include relevant context, including agreed schedule changes and your own actions. Separate observation, reported information and interpretation. These habits make the record easier to review; they do not establish admissibility or guarantee a court outcome.

Match each entry to an original

Texas Law Help’s visitation-journal guidance recommends recording the date, time, place and witnesses promptly and retaining supporting material such as a nearby purchase receipt. Its enforcement instructions concern Texas orders; use local legal advice for your own order. A receipt may support presence in an area, but does not by itself establish everything that happened during an exchange.

Connect the timeline to source material
Timeline itemKeep alongside itLimit to remember
Exchange or schedule changeRelevant messages and the applicable schedule or orderPreserve the surrounding conversation, not only an isolated line.
School or appointment eventComplete email, letter or attendance record available to youA screenshot may omit attachments and sender information.
Condition you observedUnedited original photo or video, with a separate factual entryA photograph does not by itself establish cause.
Witness accountName and contact details, where appropriateDistinguish your account from the witness’s own account; ask your lawyer what format is needed.

Where the log lives on iPhone

Choose storage according to who can open the device and its accounts. A note or document is an organizational container, not a privacy guarantee. Review sharing, connected devices and recovery access before placing sensitive records there.

Keep original files unaltered. Put crops, highlights and annotations in clearly labeled working copies. Keep a separate recoverable copy under appropriate access controls and test retrieval with a harmless file first; a second folder in the same synchronized account is not an independent recovery plan.

If abuse or monitoring is involved, consider a safer device and support from an advocate before changing the setup. NNEDV’s Safety Net project warns that discovery of documentation can lead to escalation. Some services notify other people of screenshots. Safety takes priority over completing a log.

A reusable entry format

The example below is fictional. Missing information stays marked as unknown. File references help a reviewer locate material; they do not prove the entry is accurate.

Example entry: an exchange that began later than scheduled
FieldExample
Event / entry written11 April, 6:00–6:52 p.m. local time / written 11 April, 8:15 p.m.
Location and observationLibrary entrance. I observed the other parent arrive at 6:52 p.m.
Schedule and communicationScheduled exchange: 6:00 p.m. I sent an ETA question at 6:20 p.m.
Child-related effectThe 6:30 p.m. lesson was missed. Attendance confirmation kept separately.
Related materialSchedule version A; message thread April 11; coach email April 12. Preserve complete sources.
Uncertainty / later correctionReason for delay unknown. Add later clarification as a new dated note.

Where Photo Vault fits, and the limits

Photo Vault imports photos and videos, not a text log or PDF case file. New Photo Vault Lossy imports store compressed picture samples and needed media tracks without embedding whole source files. Existing archives with retained originals keep their original-resource export path. New still-image exports are reconstructed JPEG or PNG files, with captured metadata stored separately in the encrypted index. Encryption uses a device-only installation key. This does not preserve a complete evidence timeline or establish recovery reliability. PhotoVault: Encrypt & Compress 1.0 runs on iPhone and iPad (iOS/iPadOS 26+) with AES-256-GCM local archive encryption and Secure Share (.pvsecure) export; always verify exported backups independently. Keep originals and complete correspondence independently.

An optional viewing copy can sit behind the app’s password, pattern or device-authentication gate. Device authentication permits a device-passcode fallback. After a Photos import, Photo Vault can request permission to delete eligible originals. Decline the iOS confirmation to keep them. Remaining Photos copies retain their existing exposure. The app has no encrypted backup service of its own.

Ask your lawyer or local court self-help service how to preserve, deliver and submit electronic material. This page does not determine filing requirements or authorize recording conversations.

PhotoVault: Encrypt & Compress 1.0 is available on the App Store for iPhone and iPad (id6824412013). Archive tests covered image reconstruction, metadata, video and Live Photo handling, append and deletion compaction. This is not a verified public release or a complete test of the workflow in this guide. Physical-device launch, final ZIP and sharing behavior, and portable recovery remain unverified. Encryption requires a new archive or successful migration; the device-only key is not a portable backup service.

Sources & further reading

Keep exploring