The incident log is a private HR record on each team member's panel: what happened, how serious it was, and what you did about it. Only admins and owners can see it, and the person it's about never does.
For something involving a client, a visitor or the premises, use Record and follow up on venue incidents instead.
Before you start
- Who can do it: admins and owners.
- Stick to facts. Write it as you'd want it read in a dispute: what was said or done, when, and nothing you've assumed.
Log an incident
Open their incidents
Go to Team, select the person, and open Incidents.
Start
Select Log incident.
Choose the type
Choose the Category (Attendance, Conduct, Performance, Safety, Client complaint, Policy or Other) and the Severity (Minor, Serious or Gross).
Say when and what
Set When it happened; backdate it to the real day, but not into the future. Describe What happened. If it reads like an opinion, you're asked to describe the behaviour instead. Add the Action taken (optional).
Mark protected leave
Tick Protected / excused leave for absences that mustn't count against someone, such as documented medical leave or approved leave.
Save
Select Log incident. You see Incident logged, and it's listed with Logged by your name and the date.
Spot a pattern
Under Pattern rule (org-wide), set Flag after (incidents) and Within (days), and select Save. When someone reaches that many incidents of one category in the window, their log says so, for example "3 attendance incidents in the last 90 days". Protected leave never counts.
Export the log
Select Export CSV to download the person's full record.
Check it worked
The incident is at the top of their Incidents list with its category, severity and date.
If something goes wrong
"The incident date can't be in the future"
Change When it happened to today or earlier.
Can the employee see their log?
No. Whether and how you share it is part of your HR process.
Should every complaint be logged?
Log what you'd want a dated record of: a pattern of lateness, a client complaint, a safety issue. A one-off coaching chat usually doesn't need one. A well-kept log also supports any later decision to let someone go. See Suspend, archive, or offboard a team member.