Skip to main content

Pest control

The pest control log is where SafetyBrik keeps every pest sighting, pest contractor visit and proofing job at your sites, with the contractor's report and any photos. It is the record an Environmental Health Officer looks for when they ask "have you had any pest problems, and what did you do about them?".

You will find it as the Pest control events tab on the Records page at /safety/records?tab=pest-events. Each event has its own detail page at /safety/pest-events/{id}. You can also log one from the Daily diary, with + Add under the day's pest events.

Logging a pest event​

Click Log pest event and fill in:

  • Event type - Pest sighting, Contractor visit or Proofing action (work you did to keep pests out, such as sealing a gap or fitting a door brush).
  • Event date - the day it happened. It can't be after today: "A pest event can't be dated after today."
  • Location - which site, if you run more than one.
  • Area (optional) - where on site, for example "Dry store" or "bin yard".
  • Pest species (optional) - Rodents, Flies, Cockroaches, Wasps / bees, Ants, Birds, Stored product insects or Other (with Specify species, which must be filled in). Not asked for a proofing action, which involves no live pest. If a species was already chosen before you switched the event to a proofing action, it stays on show, because it is still saved with the event: clear it if it doesn't apply. Changing the species away from Other, or clearing it, drops what was typed in Specify species.
  • Summary - what happened: where, how many, what time of day.
  • Action taken - what you did about it. Needed for a sighting or a proofing action, optional for a contractor visit.
  • Contractor - for a contractor visit, pick one of your saved pest control contractors from Emergency contacts, or type the name. One of the two is needed. A contractor removed from your contacts in the meantime is refused with "That contractor wasn't found. It may have been deleted. Pick another one, or type a name." If your saved contractors can't be loaded just now, the form says so with Try again: you can type a name instead, and an edit keeps the contractor it already has.
  • Needs a follow-up - on a new event, turn it on if something still needs doing. It adds a follow-up to the Follow-ups list as the event is logged (see Follow-ups below):
    • What needs doing - for example "Re-check bait stations, confirm the contractor's return visit". Up to 500 characters.
    • Who (optional) - "Optional. Leave it blank and it is yours."
    • By when - a date at the event's site, a week on to start. It can't be in the past.
  • Photos (optional) - up to ten. See Photos below.

When you press Log pest event (or Save changes) with something missing, nothing is saved. Each problem shows in red under its field, and you are taken to the first one:

  • "Enter the date of the event."
  • "Choose the location." (if you run more than one site)
  • "Say which species it was." (species Other with nothing in Specify species)
  • "Enter a summary of what happened."
  • "Say what action you took." (a sighting or a proofing action)
  • "Choose the contractor, or toggle off to type a name." or "Enter the contractor's name." (a contractor visit)
  • "Say what needs doing." (when Needs a follow-up is on)

Each message goes as soon as the field is filled in. The save button is only greyed out while photos are uploading or the event is saving.

The list can be filtered by event type, species, site and dates. Turn off Show closed follow-ups to see only the events that still need a follow-up. Voided events are hidden: turn on Show voided to see them (see Voiding a pest event).

Everything about the event is changed with Edit on its page. The edit form has no follow-up controls: an event's follow-ups are on its page (see Follow-ups).

If a save fails, the form stays open with the reason at the top, or "We couldn't save the pest event. Check the details and try again." It can't be closed while it is saving. If someone else voids the event while you have it open, a change you then make is refused, and the page turns read only and shows their void.

A pest event at a site that has been switched off or removed names its site as "Station Road (closed)" and is read only. Its page shows "Station Road is closed. Its records can be read and printed but not changed.", with no Edit or Void, and its follow-ups have no buttons. A report attached to it can still be opened, but not replaced or removed. The site filter lists your open sites, so choose All sites to find a closed site's records in the list.

A new event can only be logged at an open site, and an event can't be moved to a closed one. A change sent from a page left open is refused with "This site is closed, so its records can be read and printed but not changed." Before you switch a site off, the site closure dialog in Settings > Locations counts its events still needing a follow-up, so you can close them first.

Follow-ups​

A pest event's follow-up is on the shared Follow-ups list, with what needs doing, who it is for and the day it is due. It shows there, on Today and on the event's page. Pest follow-ups show on the web only for now, not on the Team App.

While an event has an open follow-up, it needs a follow-up: the list shows Open in its Follow-up column, and it counts towards Open pest follow-ups on the Overview. Closing or voiding the follow-up clears that.

On the event's page​

The Follow-up section of the event's page shows:

  • The open follow-up, with Close follow-up and Change, and Void for owners and admins.
  • Earlier follow-ups, closed or voided, listed under it, so the event keeps their history.
  • Add follow-up, when none is open. It is due a week on to start. Leave Who blank and it goes to whoever logged the event: "Optional. Leave it blank and it goes to whoever logged the event."

An event has one open follow-up at a time. There is no Add follow-up at a site that has been switched off or removed, on a voided event, or for viewers.

  • Close follow-up asks What happened, which is required, for example "Contractor came back and resealed the gap". SafetyBrik records who closed it and when, and the event no longer needs a follow-up.
  • Change can reword what needs doing, give it to someone else (Who) or move it to another day (By when, today or later at the site).
  • Void is for a follow-up added by mistake. It asks why, and voids the follow-up alone: the event stays as it is, no longer needs a follow-up, and can have another added.

See Closing a follow-up, Changing a follow-up and Voiding.

When the event changes​

  • Voiding the event voids its open follow-up too, with the same reason, who and when (see Voiding a pest event).
  • Moving the event to another site moves its open follow-up with it. It stays due on the same day, now at the new site, and the move is in the audit log as Follow-up changed.

Older events​

An event logged before pest follow-ups joined the Follow-ups list keeps what was typed about its follow-up, shown read only on its page as Original note. If it still needed a follow-up, it now has one on the list, worded from that note, for whoever logged the event.

Contractor reports​

Each pest event can have one report attached, usually the contractor's visit report. It goes in the Contractor report PDF section of the event's page.

  • Upload PDF attaches a report. Reports must be PDFs, up to 10 MB. Anything else is refused with "The report must be a PDF." or "The report must be 10 MB or smaller."
  • View report opens the report in a new tab. Reports are private: each time you click, Brikly makes a link that works for 15 minutes, so just click again whenever you need it.
  • Replace uploads a new report in place of the old one. When an owner or admin replaces a report, the old file is deleted; when a team member does, Brikly keeps the old file privately until the account is deleted.
  • Remove asks "Remove the contractor report?" first: "The report is removed from this pest event. You can upload it again at any time." When an owner or admin removes it, the file is deleted; when a team member does, Brikly keeps the file privately until the account is deleted.

If a report can't be saved or opened just now, the page says so ("We couldn't save that report just now. Please try again in a moment.") and nothing is lost.

Photos​

Photos can be JPEG, PNG or WebP, up to 5 MB each. A photo in the iPhone's HEIC format is refused with "This photo is in HEIC format. Save it as a JPEG and try again."

While photos are still uploading, the save button reads Uploading photos... and waits; Cancel still works. If a photo fails, the others are kept and the form says "That photo couldn't be uploaded. Try again." (or, for several, "2 photos couldn't be uploaded. Try them again."), with the reason instead when Brikly has one, such as the HEIC sentence above.

Photos are private to your business. Brikly opens each one through a link that works for an hour, and reloading the page gets fresh links, so a page left open for longer shows broken pictures until you reload it. While a link works, anyone who has it can open the photo, so don't copy photo links into emails or messages.

When an owner or admin removes a photo while editing an event, the file is deleted too, unless another record uses the same photo; when a team member removes one, Brikly keeps the file privately until the account is deleted.

Voiding a pest event​

A pest event is never deleted. One logged by mistake (a test or a duplicate, say) is voided instead: it stays on file, with why, who and when, and still prints in the EHO pack.

Owners and admins can void an event, with Void on its page or in its row's menu in the list. Void asks "Void this pest event?": "Void a pest event only when it was logged by mistake. It is never deleted: it stays on file and in the EHO pack as voided, with your reason." Why are you voiding it? is required. If the void can't be saved, the dialog stays open with what you typed. If someone else voided it first, yours is treated as done and the page shows their void.

A voided pest event:

  • Shows when, who and why. Its page has a Voided badge and a notice with when and who, for example "Voided Mon 9 Nov, 14:32 by Sam Taylor", then the reason and "This pest event was logged by mistake. It stays on file and in the EHO pack as voided, and can't be changed."
  • Is read only. It has no Edit or Void, and its follow-ups can't be added to or changed. Its photos and its report are kept: the report can still be opened with View report, but not replaced or removed.
  • Is hidden from the list. Turn on Show voided to see voided events, greyed out and marked Voided in place of the follow-up.
  • No longer needs a follow-up. Its open follow-up is voided too, with the same reason, who and when, and it isn't counted as an open follow-up anywhere.
  • Is left out of every count. It isn't in the list's counts, the Open pest follow-ups card on the Overview, the Daily diary, the 4-weekly review's pest questions or the site closure dialog.
  • Prints in the EHO pack as voided, with who voided it, when and why (see In the EHO Report Pack).

A void can't be undone. If an event was voided by mistake, log it again. An event at a closed site can't be voided.

Permissions​

RoleView and open reportsLog and edit, upload or remove a reportVoid
OwnerYesYesYes
AdminYesYesYes
MemberYesYesNo
ViewerYesNoNo

In the EHO Report Pack​

The EHO Report Pack has a Pest Control Events section for the events dated in the pack's period, and any event voided within the pack's dates, whatever its date, grouped into Sightings, Contractor Visits and Proofing Actions. With none, it says "No pest control events were logged in this period." Photos show as small pictures under each event. A report is mentioned, never linked: "Contractor report on file in Brikly" for a contractor visit, "Report on file in Brikly" for a sighting or proofing action, so you can open it on screen if an inspector asks. Under Follow-up, each event lists its follow-ups, newest first: how each stands on the day the pack is made ("Open" in red while it is open, or how it was closed or voided), what needs doing, and who it is for with its due day, for example "Sam Taylor, due 17 Nov". An older event's note follows as "Original note: ...". An event with neither reads "-". A voided event reads "Voided" under Follow-up, with a line under its summary saying when, by whom and why, for example "Voided 8 Oct 2026 by Sam Taylor: Logged twice". Each follow-up is also in the pack's Follow-ups section, and one opened before the pack's dates and still open is in Still open from before this period. See Photos in the pack.

Where else it shows​

  • 4-weekly review - two questions: one counts the period's sightings, contractor visits and proofing actions ("Has all pest activity, every contractor visit and all proofing been logged?", with N/A for None this period), the other asks whether their follow-ups are closed ("Are all pest follow-ups closed?", with N/A for None open). A review started before the questions were reworded asks both in one question.
  • Daily diary - each day lists its pest events, leaving voided ones out.
  • Audit log - logging, editing and voiding an event (Pest event voided), and attaching or removing a report (Pest report attached, Pest report removed), with who did it.