UseFreeTools

Symptom and Trigger Timeline

Put entered symptoms and separate context events on a timestamped timeline for later discussion.

Files stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

One tab-separated row per symptom, exactly five columns. The date is YYYY-MM-DD, the time is 24-hour HH:MM and the offset is the UTC offset that was in force, such as +06:00 or Z. Up to 200 rows and 100,000 characters; the label is up to 80 and the note up to 200. The offset is required so the order of events does not depend on a guessed time zone.

Optional rows in the same five columns for anything that might be relevant later, such as meals, sleep, travel or medication. Listing an event near a symptom does not mean it caused it.

Drop your file here

or choose one from your device

Open a JSON project saved by this page. The file names the tool and schema it was written for; values in the file replace the matching fields above and are checked the same way as typed input.

    Processed in your browser. Your inputs stay on this device.

    Showing a generated example. Generate again for a new result.

    How to use Symptom and Trigger Timeline

    1. Enter your own symptom records with dates, clock times, UTC offsets, labels and notes as shown by the fields.
    2. Add separate context events if needed, then review their timestamp order and the printable packet.
    3. Download CSV for rows, JSON to continue editing later, or PDF for a printable copy. Review exports before sharing them.

    Example: Symptom and Trigger Timeline

    Order one context event before a supplied symptom entry.

    You add
    Symptoms: date, time, UTC offset, label, note (tabs): 2026-10-01 09:20 +06:00 Example symptom Sample row, replace with your own Possible context events: date, time, UTC offset, label, note (tabs): 2026-10-01 08:00 +06:00 Example context event Sample row, replace with your own
    You get
    Placed 1 symptom and 1 context event on one timeline. Sample rows: 1 | Context | 2026-10-01 08:00 | UTC+06:00 | Example context event | Sample row, replace with your own; 2 | Symptom | 2026-10-01 09:20 | UTC+06:00 | Example symptom | Sample row, replace with your own

    Options

    Explicit timestamps
    Offsets identify actual instants across different locations or clock changes. The page does not guess a time zone.
    Separate context
    A nearby context event remains a separate record. Its position does not establish a trigger or cause.

    Supported inputs and limits

    Up to 200 entries per dataset and 100,000 characters per dataset. Text is bounded by the fields. The page does not triage or diagnose symptoms. Processing runs in the browser without uploading entries or automatic saving. JSON projects are limited to 100,000 bytes/characters. Saved files contain your supplied details. Printable reports use standard Latin fonts; unsupported characters are refused rather than omitted.

    Where your input is processed

    This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

    Sequence is not evidence of a cause

    An event appearing before a symptom can help organise a conversation, but the timeline does not establish a trigger or explain a cause. Entries are not clinically checked, ranked for urgency or interpreted as a diagnosis. Keep the descriptions in your own words and review the packet before sharing it.

    Questions about Symptom and Trigger Timeline

    Does a nearby event mean it caused a symptom?

    No. The tool orders supplied timestamps without testing causation.

    Why do entries need UTC offsets?

    Offsets identify the actual instants, so records made in different places or across clock changes can be ordered consistently.

    Will the page decide how urgent a symptom is?

    No. It is a record organiser and does not perform clinical triage or recommend treatment.

    Project manager: Tony Hines · Content updated 4 October 2026 · Report a problem

    Related tools

    All tools in Health and Fitness

    Online Notepad

    Write a note that stays in this browser, then export or delete it.