Keeping a secure incident chronology

An incident chronology should let a reader follow what happened and find the supporting material. It works best as a factual sequence, with uncertainty visible, rather than a running argument about the other person's character.

Use one entry for one event

Give the date or approximate period, place, people present and a short description. Record words used where you remember them, distinguishing an exact quotation from a summary. Link the entry to a message, photograph, medical record or police reference if one exists.

Separate what you witnessed from what someone told you. For repeated behaviour, identify examples and explain the wider pattern without inventing exact dates. This makes the chronology useful when preparing the supporting account for an FL401 application. ^[1]

Preserve the record's history

Date later additions and explain corrections. Do not overwrite an earlier entry to make the account appear more certain. Keep original evidence outside the narrative so an adviser can examine the source, not only your interpretation.

Store the record where it is safe to do so; a document title on a shared drive can expose it. Correspondence and device access addresses that risk. When a new event is urgent, report it through the immediate-risk route before spending time updating the chronology.

Choose a structure that keeps facts and sources separate A practical entry can identify the incident date, when the note was written, what happened, who was present and the supporting reference. Keep the description short enough to scan while retaining the facts needed to understand the event. Place longer messages or documents outside the narrative and link them by a stable label. This prevents a chronology from becoming an unsearchable collection of pasted conversations in which the sequence and source of information are difficult to identify.

Distinguish the date of an event from the date you learned about it. If you discovered a transaction in June that occurred in April, both dates may matter for different reasons. State whether a time is exact, approximate or inferred from another record. An approximate period with a clear explanation is more reliable than an invented precise date. The chronology can help prepare the supporting account required for a protection application, but its format and contents may need further legal work before filing. ^[1]

Describe a pattern through identifiable examples Repeated behaviour may not be remembered as a series of perfectly dated events. Explain the general period and use examples that you can describe accurately, indicating which are supported by messages or other records. A pattern of restrictions on money, repeated unwanted contact or threats around particular occasions should be connected to its actual effects. Avoid filling gaps with assumptions about how often something must have happened or labelling every disagreement in the same way without context.

Where a particular incident appears minor in isolation, explain why it mattered in the wider sequence. A message about an address may have a different significance after earlier attempts to locate you. Keep that contextual explanation distinct from the words actually sent. If another person offers an interpretation, identify it as their view. The reader should be able to separate observed behaviour, information received from others and your explanation of its effect without guessing which category a sentence belongs to.

Make corrections visible and preserve relevant earlier notes Memory and documents can reveal that an entry needs correction. Add the corrected information with the date and reason, rather than rewriting the record to appear as though it was always certain. For example, explain that a bank statement established a different transaction date or that a message showed who was present. Keep a relevant earlier version where safely possible. Transparency about a correction supports an accurate account and helps an adviser understand any inconsistency before the material is used.

Do not backdate an entry written from present recollection. If you are reconstructing an older event, say when the reconstruction was made and what helped refresh your memory. An existing note made at the time can be kept separately as a source. Likewise, a friend's later account should be identified by who supplied it and when. A chronology is most useful when its history can be followed, rather than when every entry has been polished into the same apparent level of certainty.

Use the record without making its storage another exposure Consider where the chronology's title, previews, backups and printed copies may appear. A shared drive or family account can reveal the existence of a record even if the full text is not immediately visible. Discuss a suitable storage and transfer method with the adviser or specialist support where monitoring is a concern. Do not respond to uncertainty by making unplanned device changes that could create a new risk or destroy material that may need to be preserved.

When supplying the chronology, identify the version and the date to which it is current. Keep a note of the material sent and any request for further detail. A newly urgent incident should be reported promptly through the appropriate route instead of waiting until the document is reorganised. After that immediate response, add the event with its sources and any relevant agency reference. The chronology should support communication and preparation, not become a task that delays help or requires repeated exposure to distressing material without a clear purpose.