How to use Symptom and Trigger Timeline
- Replace the sample Recorded symptoms with the date, 24-hour local time, UTC offset, event name and optional note for each observation.
- Add Possible context events separately when useful, such as meals or travel. Use the offset that applied to each event; a similar local clock time can represent a different actual instant.
- Select Build symptom timeline. The output merges both lists in timestamp order and keeps each row labelled Symptom or Context. Check the event descriptions before sharing.
- Download symptom-trigger-timeline.pdf for the visible six-column timeline, or its CSV for local-date fields plus a normalized UTC instant. Save the JSON project to restore both original editable lists later.
Example: Symptom and Trigger Timeline
The sample context event at 08:00 +06:00 appears before the symptom at 09:20 +06:00. The timeline records that sequence without assigning a cause.
Options
- Editable fields
- Recorded symptoms: Date, Local time, UTC offset, Event, Note (optional). Possible context events: Date, Local time, UTC offset, Event, Note (optional). Add or remove these records with the labeled controls; each new row starts blank.
- Advanced raw input
- Each list uses five tab-separated cells: date, local time, UTC offset, event and note. Keep the final cell even when the note is empty. Dates use YYYY-MM-DD; offsets use Z or ±HH:MM.
- 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
- Each list accepts up to 200 rows and 100,000 characters.
- Event names allow 80 characters and notes 200.
- The form requires symptom records; context is optional.
- Dates, times and explicit offsets must be valid.
- Ordering uses actual instants, while the table retains local time and offset.
More details
Equal-time context rows precede symptoms; that tie order implies no causal sequence.
The report does not identify triggers, rank severity, diagnose or provide triage.
Processing is local without automatic saving.
JSON projects from this page are limited to 100,000 bytes and characters; saved files include the details you entered.
PDF text uses the supported standard-font character set.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved 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.