An incident on its own says what happened. The logs around it say what the day was like before and after — and that is usually the part that matters when someone reads the file back.

Linking is worth the thirty seconds. Nobody reconstructs a shift from memory six months later.

Link a log

Open the incident and find the Linked Events card.
Select Link Event. A panel opens on the right, titled Link Event.
Find the log. Type into "Search logs by description or type…". The search runs over the log's text and its type as you type.
Select Link on the entry you want. It moves straight into the incident's list.

You can link as many as you need, one at a time.

What you'll be offered

Only logs that can sensibly belong to this incident:

The same young person. If the incident names a young person, only their logs are listed.
Not already linked. Anything attached is filtered out, so you can't double-link by accident.
The 50 most recent matches, newest first. Narrow the search rather than scrolling.

What linking records

Every link is written to the incident's audit trail as "Event Linked", with the log's type and the time it happened. Unlinking is recorded the same way.

So the history shows not just which logs are attached now, but which were attached, by whom, and when — including any that were later taken off.

Reading them back

View Evidence opens the linked logs as a timeline, in time order, with who wrote each one. That is the view to use when you're writing an update or preparing for a review, rather than reading the cards one at a time.

Linked logs also travel with the incident's PDF.