How to Keep an Incident Log (Audio + Written)

Whatever you're dealing with — harassment, a dispute, a pattern of behaviour you may need to report — a clear, dated incident log is the single most reliable record you can keep. It's low-risk, it's credible, and it gives context to any other evidence. Here's how to keep one well.

Important: This is general information, not legal advice. BlackBox is a personal recording tool, not a safety or legal-evidence service, and you should never rely on it as your only record or protection. Recording people without the consent your area requires can be illegal — keep that in mind before adding audio. If you're in danger, contact emergency services, and consult a qualified professional for your situation.

Why a written log is so valuable

• Low legal risk. Writing down what happened to you doesn't require anyone's consent, unlike recording them.
• Credible. A contemporaneous, consistent, factual record carries real weight.
• Context. It explains the who/what/when/where that a lone audio clip can't.
• Reliable. It won't be excluded for how it was captured.

What to capture in each entry

Keep it factual and specific. For every incident, note:

Write entries as soon as you safely can, while details are fresh — contemporaneous notes are far more credible than ones written months later.

Combine written notes with other evidence

A log is strongest when it ties everything together:

• Messages and emails — reference them in the log and keep copies.
• Screenshots with visible dates.
• Audio, where lawful — note in the log that a recording exists, with its date. See can audio recordings be used as evidence? before relying on any recording.

If you do keep audio, keep the original unedited and let your written log supply the context — this avoids the mistakes that ruin audio evidence.

Keep it factual, not emotional

It's natural to feel angry or upset — but a log reads as more credible when it sticks to facts: what was said and done, observably. Record your emotional impact in the "impact" field rather than editorialising the events themselves.

Store it securely and back it up

A record is only useful if it survives and stays private:

• Keep it on a device and account the other person can't access — ideally not a shared or work device.
• For any audio, keep it on-device and locked — BlackBox stores recordings locally with no upload and a Face ID lock; see the privacy policy.
• Back up to storage you control, so a lost or confiscated device doesn't erase everything.

Don't rely on the log (or the app) alone

A log supports a process — it isn't the process. Combine it with official reports and professional help:

• Report through proper channels (HR, the police, a platform, a regulator).
• Get advice from a lawyer or relevant authority.
• Use specialised support services for harassment or abuse.

BlackBox is not an emergency or legal service; it can help you keep a private, on-device record, but it can't protect you or resolve anything. Treat it as one tool among several.

Incident log template

Use the same format every time:

Consistency is the value. A log with ten consistent entries is easier to understand than ten scattered notes in different apps.

When to record audio

Audio can help if the incident includes spoken words, threats, instructions, agreements or noise. It is less useful for visual damage, location, physical evidence or documents. Pair audio with photos, screenshots or written notes when needed.

Before recording, consider consent law and safety. If recording could escalate the situation, prioritize leaving, getting help, or writing notes afterward.

How to organize files

Create a folder structure:

• incident log document;
• original audio;
• transcripts;
• photos/screenshots;
• reports submitted;
• responses received.

Use filenames with dates, such as "2026-06-19-hallway-noise-audio". Do not rely on memory or generic filenames like "recording-14".

Preserve originals

If a file may become evidence, keep the original unchanged. Make duplicates for trimming, sharing or transcription. Keep a short note explaining when and how the recording was made.

Do not post incident recordings publicly unless advised by a qualified professional. Public posting can create privacy, defamation or retaliation risks.

Review routine

Once a week:

1. Add missing context.
2. Back up important files.
3. Delete unrelated audio.
4. Mark unresolved incidents.
5. Prepare a concise summary if you need to report.

The log should help you act, not become another pile of stress.

What makes a log credible

A credible incident log is boring in the best way: consistent dates, specific facts, original files, and clear context. Avoid exaggeration, name-calling or guessing motives. Write what happened, what was said, who saw it, and what evidence supports it. If you later need to share the log, that factual tone helps people understand it quickly.

Audio retention for incident logs

Keep audio that supports an unresolved incident. Delete routine or unrelated recordings after review. If an incident may become formal evidence, preserve the original file and make copies for transcription or sharing. This keeps the log useful without turning it into a pile of private background audio.

The bottom line

A dated, factual incident log is the most reliable, lowest-risk record you can keep — and it gives meaning to any messages or (lawful) audio you add. Keep it contemporaneous, factual, secure and backed up, and pair it with proper reporting and professional help. BlackBox can hold the audio side privately and on-device, as one part of a careful approach — never the whole of it.