Escalation & DipNot
A safe path for problems that go unsaid.
A recorded channel for silent problems.
The problem
The most serious problems stay in the corridor.
Mobbing, overload, a broken process — people don't know whom to tell or how, and when they do, nothing is recorded.
AI in this module
Adds context automatically.
- Reports are linked to the relevant project, task and person
- On mobbing reports, a note is added if the same person sent the reporter's tasks back 3+ times in 30 days
- Open escalations flow into the Bottleneck Radar
What you can do
Five categories
Task issue, mobbing, workload, process, other; with a priority level.
Recipients by hierarchy
From a member or PM: team lead, department manager and CTO; from a team lead: department manager and CTO.
Sensitive records
Mobbing records are only visible to people allowed to view all escalations.
Status tracking
Open → In review → Resolved → Closed.
DipNot
A personal note up or down the hierarchy, linked to projects and tasks.
Reply tracking
Pending, answered and closed DipNots; whether a reply has been seen.
Who uses it and how
Member
Raises an issue on the record, to the right person.
Team Lead
Responds to reports and DipNots from the team.
Department Manager
Sees sensitive records and closes DipNots.
Frequently asked
Are reports anonymous?
No. The reporter is recorded; sensitive categories are only visible to authorised people.
How is DipNot different from escalation?
An escalation takes a problem up the management chain; a DipNot is a note or request to a specific person in the hierarchy.
See it with your own data.
Open a free workspace, or let's schedule a demo with your team.