Evidence + Timeline (2026): A Calm Workflow for Facts, Sources, and Dates
A court-friendly guide to using Equalora’s Evidence + Timeline feature to organize events, attach reusable Facts, connect Sources with locators, and export a clean PDF for preparation.
Quick summary
Pin every event to a date, a fact, and proof—so your record speaks for itself.
Educational only — not legal advice.
What this is
Evidence + Timeline is a calm structure for parents under stress.
It helps you record what happened, when it happened, and where the supporting material lives.
This is organizational support — not legal advice.
Who this is for
• Parents representing themselves who want a simple system for dates, facts, and proof.
• Parents preparing for mediation, settlement talks, or trial prep who feel overloaded.
• Parents who want to stay neutral, consistent, and credible in written records.
What this helps with
• Turning scattered documents into reusable Facts you can attach to multiple events.
• Building a readable timeline that stays focused on dates and verifiable events.
• Attaching Sources (messages, PDFs, photos, reports) with locators so details are easy to verify later.
• Keeping your wording neutral so the record stays calm and court-friendly.
• Exporting a clean PDF with optional descriptions, sources, quotes, and locators — then previewing it inline before downloading.
How the feature works (plain language)
Equalora separates your case record into three building blocks: Facts, Sources, and Timeline Events.
Facts are structured records: a fact_key and a value (text, date, number, boolean, or json), plus optional notes.
Facts can have Sources attached. A Source includes a source_type, source_id, locator, and an optional short quote.
Timeline Events are dated entries with an event_date, title, optional description, and tags.
Events can link to Facts as Support. This keeps the timeline readable while still anchored to specific details and sources.
When you export, Equalora generates a court-friendly PDF with options (include descriptions, include sources, include quotes, include locators, and a sources-per-fact limit).
Preview shows the PDF inline. Download saves the PDF.
Workflow: build a clean record without spiraling
This workflow is designed to keep you moving without needing perfection.
1) Start with your timeline spine (dates only). Create 5–10 Timeline Events for the biggest milestones first.
2) Write neutral Event titles. Use observable language (who/what/when/where). Avoid labels, motives, or conclusions.
3) Add a short description only when it increases clarity. Keep it to one or two sentences.
4) Create Facts for details you may reuse. Use consistent fact_key naming (snake_case) so you can find them later.
5) Attach Sources to Facts. Always include a locator so the source can be found quickly.
6) Link Facts to Timeline Events as Support. This keeps events clean while still grounded in proof and detail.
7) Tag your events so you can filter patterns without editorializing (exchanges, school, medical, schedule, finances).
8) Preview the PDF. Adjust titles and descriptions for clarity and tone.
9) Export when it’s readable, not when it’s “complete.” Use sources-per-fact limits to keep the PDF calm and skimmable.
Examples (neutral, verifiable, and easy to check)
Example Timeline Event title:
• 2024-11-03 — School pickup exchange occurred at 3:10 PM
Example Fact (structured):
• fact_key: exchange_location
• value_type: text
• value: Main office entrance, Example Elementary School
• notes (optional): Location matches the school’s standard pickup location.
Example Source (with locator + short quote):
• source_type: message
• source_id: msg_2024-11-03_1612
• locator: Text thread “Pickup Schedule”, 11/03/2024, 3:12 PM
• quote: “I’m here at the main office now.”
Best practices
• Write Event titles like a calendar entry: what happened + where + when.
• Separate Events (dated entries) from Facts (reusable details).
• Keep quotes short. Let locators do the heavy lifting.
• Use specific locators: page/line, timestamp, or exhibit label.
• Prefer verifiable details over intensity. The goal is readability and trust.
• Add notes to clarify context, not to argue or diagnose intent.
• Build in small passes: dates → facts → sources → linking → export.
• If you’re flooded, write the most neutral version first. You can refine later.
Common mistakes to avoid
• Writing event titles as conclusions (labels, motives, or insults).
• Adding Sources without locators (hard to verify later).
• Overloading descriptions with emotion, speculation, or commentary.
• Duplicating the same detail in many places instead of using a reusable Fact.
• Exporting a giant PDF without limits (too long to read, too hard to follow).
Ready-to-use template
Use these as copy/paste starters. Replace placeholders with your details.
6 example Timeline Events (titles + date placeholders):
• [YYYY-MM-DD] — Parenting-time exchange occurred at [location]
• [YYYY-MM-DD] — Schedule change request sent
• [YYYY-MM-DD] — School notice received regarding [topic]
• [YYYY-MM-DD] — Medical appointment occurred for [child initials]
• [YYYY-MM-DD] — Payment made for [expense category]
• [YYYY-MM-DD] — Incident noted: [neutral description, one line]
10 example Fact keys (with suggested value types):
• exchange_location — text
• exchange_time — date
• message_sent_time — date
• missed_call_count — number
• payment_amount — number
• payment_date — date
• child_absence_days — number
• has_shared_calendar_access — boolean
• incident_summary — text
• document_reference — json
3 example Source locator formats:
• Page/line: PDF “School Report.pdf”, page 3, lines 12–18
• Timestamp: Video “ExchangeParkingLot.mp4”, 00:01:12–00:01:28
• Exhibit label: Exhibit B, Photo 2, filename IMG_1042 (metadata shows 2024-11-03 15:09)
Start here (calm, small, doable)
Start by creating 3 Timeline Events today.
Attach 1 supporting Fact to each event.
That’s enough to begin building a record you can trust when things get loud.
Educational only — not legal advice.