How to Keep an Antisocial Behaviour Incident Log Before Any Warning Letter

A neighbour emails about bass at midnight and you forward it to WhatsApp. Weeks later the council asks what you have done — and your only file is chat threads. Open one ASB incident log the day the first complaint lands: concrete rows, permission before you reuse their complaint, contact attempts beside any first warning. This guide builds that file — not a possession pack.

Tuesday 22:40 at Arden’s Milton Keynes terrace: a neighbour emails bass until 01:10, kids woken. Arden forwards it to a group chat and texts “keep it down.” Saturday another neighbour WhatsApps shouting at 00:55. By next month the council ASB team asks what the landlord has done — the only “file” is chat threads and one angry text.

Typical mistake: treating the stern text as the start of the case. GOV.UK’s landlord guide on antisocial behaviour (checked 25 September 2026) says keep evidence: a diary of events (times, dates, impact) plus records of speaking or writing to the person. Log first, warn second.

Disclaimer: IziRento is operations software, not legal advice. Local tenancy rules vary; check a qualified adviser for binding decisions.

When to open the ASB incident log?

Open one property tab the day the first neighbour, council, police, or co-tenant report lands. Do not wait for a “pattern.” Header: address, tenancy or property ref, date opened, and who made the first report.

For example, Tuesday’s bass email opens the log even if Saturday’s shouting never arrives. GOV.UK’s how-to-report page notes that some one-off incidents may not be classed as ASB — still log what was reported. Do keep damp or mould emails on the damp and mould correspondence file; repair tickets stay on the tenant repair-request process. This tab is only neighbour nuisance, noise, abuse, or similar reports about the let.

Local environmental health practice varies; your council may publish diary-sheet guidance. Call 999 if there is immediate danger. Domestic abuse or child safeguarding can be mistaken for ASB — use the separate reporting routes GOV.UK points to, not this ops log.

What to put on each incident row?

One row per event, written the same day when you can. Process fields, not a government form: incident time; reported time (they often differ); who was involved; concrete what and where; impact in the complainant’s words; witnesses; police or council refs; how it reached you; links to email, photo, or recording.

Ban lazy labels. Sandwell’s private-landlord toolkit (checked 25 September 2026) pushes the five Ws: avoid vague “Noise Nuisance” or “Verbal Abuse” — prefer “loud bass in the bedroom” and quoted words for foul language. Reading’s diary-sheet guidance: one form per incident; a second event the same night is a new form.

In practice: Tuesday row — 22:40–01:10, “loud bass from front bedroom,” impact “kids woken,” email attached, permission pending. Saturday — new form, shouting description, voice note linked. Do not merge two nights into one foggy “noise” note. Ask affected people to keep their own diary with time, duration, and nature of the behaviour.

Do you need permission before you use a neighbour’s complaint?

Yes, before you reuse their complaint as evidence. GOV.UK says ask for permission, think whether they will be easily identified, and whether that is appropriate. Track status on the row: asked, granted, refused, or anonymous. Anonymous tips can still open a landlord row for what was alleged and when — do not name the tipster.

Do not identify a complainant in a tenant-facing letter if it is unsafe or they refused. Keep copies even after you report to police or the council — treat the file as personal data.

How do you log contact attempts and a first warning?

Add a parallel column for every landlord call, email, visit, or mediation invite about the behaviour — date, channel, and a short gist. Log attempts before and with any first written warning.

The Renters’ Rights Act 2025 section 4 (checked 25 September 2026) amends Housing Act 1988 so courts weighing ASB possession must consider whether the person co-operated with any landlord attempt to encourage the conduct to cease. You are not drafting that claim here — you are dating the attempts.

If you send a first written warning, file the sent copy beside the log and date the contact column. Do not invent a mandatory three-letter chain as England-wide law. When you talk to the tenant, give specific examples from the rows — not a vague “you’ve been antisocial” line.

When to stop — before you reach Ground 14?

This article ends at the incident file. If the pattern continues and you need advice on Section 8, Ground 14, Ground 12, Ground 7A, or an injunction, hand the log plus warning copies to a qualified adviser. Do not draft Form 3A from this checklist.

GOV.UK names those grounds as escalation options after you cannot resolve — colour only. From 1 May 2026, Section 21 is not available for new assured periodic tenancies in the older AST way; ASB routes, if used at all, sit on Section 8 grounds. That dating context is why a clean log matters; it is not permission to serve notices from a blog post.

Success bar: open the log on day one; fill concrete fields; ask permission before attaching a neighbour complaint; file contact attempts and any first warning copy; treat a one-off as one row and a pattern as multiple dated rows; treat a noise-app clip as support, not the whole file. An IziRento workspace can hold the rows and attachments — it does not serve notices or obtain possession.

Workflow: First complaint → Open ASB tab → Same-day concrete row → Ask permission → Log contact attempts → Optional first-warning copy → Stop (hand log to adviser if escalation needed).