PPaT Wiki
DocumentationPathwayKnowledge baseForumBlogContact
Week streakFOUNDATION0 badges
Language: English
  • English
  • Nederlands
  • Karen (S'gaw)
  • Français
  • Deutsch
  • Lea faka-Tonga
  • Te reo Māori
Ask the community

Your PaT Pathway

0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User

Advanced

  • ○Form Test Mode (not passed yet)
  • ○Pure Forms (not passed yet)
  • ○Conditional Formatting (not passed yet)
  • ○How to upload form elements to an SD (not passed yet)
  • ○Forms - Extract Data (the AI form builder) (not passed yet)
  • ○How to make form templates live for everyone to use (not passed yet)
  • ○Form builder: field types (not passed yet)
  • ○SD Forms (not passed yet)
  • ○Build a reporting system (not passed yet)
  • ○Endpoint Manager: finding endpoints and building your own UDF (not passed yet)
  • ○Configuring a UDF: columns and calculated columns (not passed yet)
  • ○Configuring a UDF: filters, grouping and endpoint details (not passed yet)
  • ○SD Dashboard: building a dashboard (not passed yet)
  • ○PaT SD Map Presentation (not passed yet)
  • ○PaT SD Map Overview (not passed yet)
  • ○Strategy System (not passed yet)
  • ○PaT SD Templates Overview (not passed yet)
  • ○How to use the PAR SD (not passed yet)
  • ○SD Security Settings (not passed yet)
  • ○SD Template Helper Functions (not passed yet)
  • ○Mastering the Business Strategy Template (not passed yet)
  • ○Using SDs as the LMS Document (not passed yet)
  • ○How to embed an SD into the LMS (not passed yet)
  • ○How to build modules in the Module publisher (not passed yet)
  • ○Module Publisher Content Options (not passed yet)
  • ○How to create module quizzes (not passed yet)
  • ○How to create module comprehension audits (not passed yet)
  • ○Module Completion Notification Setup (not passed yet)
  • ○Customer-specific training: setting it up (not passed yet)
  • ○How to create module evidential audits (not passed yet)
  • ○Module Admin: finding and managing modules (not passed yet)
  • ●Auto Escalation (this page)
  • ○How managers can turn on OOF for their staff (not passed yet)
  • ○Using Chat to SD to go from being a good manager to a great one (not passed yet)
  • ○Throttling (not passed yet)
  • ○Live H&S Reporting (not passed yet)
  • ○Chat Management - Pro Tips (not passed yet)
  • Company Structure: adding a new user
  • Company Structure: customer companies
  • Company Structure: departments, job titles and roles
  • Company Structure: modules for a site or a country
  • Company Structure: process categories
  • Connections: linking PaT to Microsoft 365
  • Forms - API Integration
  • How to create a campaign for the PaT Lite training portal
  • How to edit an existing Bulletin Board Post
  • How to set up your SD Map
  • LMS Feedback: learner ratings and comments
  • LMS Metrics - If you can't measure it, you can't manage it
  • Manage users
  • Pacing recertifications and escalations
  • PaT Business Unit Template Overview
  • SD Workflows - Multi Submit
  • SD Workflows - Workflow Settings
  • System Activity: escalations, logins, emails and more
  • System Config: company settings
  • The org chart
  • Add any Image as a Section Header Icon
  • Assigning an SD to a new parent
  • C2E Attachments
  • Chat reminder
  • Chat to email to chat
  • Chat to SD
  • Chat to task to project
  • Comprehension Audits
  • Customer-specific training: how it works
  • Different Form Uses
  • Docked Chats
  • Docking SDs and Updating Images
  • Email to BFF
  • Email to chat to email – non PaT users
  • Embedding live data in an SD (graphs and spreadsheets)
  • Embedding SDs in SDs
  • Evidential audits: completing one
  • Filing and retrieving SDs
  • Form Wall
  • Health and safety templates
  • How PaT Manages Inactive Users
  • How SD chats work with SD Members and External Users
  • How to unlock a module for a staff member
  • Info Icons
  • Inline chats
  • Invite Attendees
  • LMS Architecture
  • Moving Section Headers
  • Multi-Tasks
  • PaT AI
  • Pop-Out Chat Feature
  • Recurring tasks: create and edit
  • Running Meetings with SDs
  • Safe Walks
  • SD Element Categorisation
  • SD Form Responses: finding and exporting form responses
  • SD Owner Functions
  • SD Task wall view
  • Share and record your screen
  • Task Integrity: what it is and why it drops
  • Track Engagement
  • Using SDs as a report or meeting minutes app
  • Video rooms: guests joining and asking to record
  • Activity Notifications
  • Add members and set permissions
  • AI Summary: a quick summary of an SD
  • Capture and Manage Accidents
  • Capture and Manage Hazards
  • Chat to task
  • Chat Wall
  • Contextual Communication
  • Convert a Note to a Task
  • Create a new SD
  • Create a Task
  • Critical Chrome Extensions
  • Document Store: shared links, your folders and favourites
  • Fast Notes
  • Getting help: the PaT Helpdesk
  • Global Search
  • Group Chats
  • How to embed Outlook onto your PaT
  • How to resize your browser to best view PaT
  • How to use the PaT Lite training portal
  • Insert links
  • Module Learning - Desktop
  • Module Learning - Mobile
  • My Profile
  • Newbie PaT Intro – Chats and SDs
  • Notes
  • Out Of Office: turning it on, and the calendar on your Task Wall
  • Outlook 2FA Issue
  • PaT Chat Overview
  • PaT Mobile App – Overview
  • Preview, download and share files
  • Publish a Bulletin Board Post
  • Reading an SD in another language
  • SD Elements
  • SD Main page useful features
  • SD Overview
  • Section Headers
  • Security measures for multiple users on a device
  • Share Feedback
  • Signing in to PaT and resetting your password
  • Task Management
  • Task Management System
  • Task Wall
  • Traffic light progress
  • Upload file attachments
  • Video calls on the mobile app
  • Auto Escalation
  • Build a reporting system
  • Chat Management - Pro Tips
  • Conditional Formatting
  • Configuring a UDF: columns and calculated columns
  • Configuring a UDF: filters, grouping and endpoint details
  • Customer-specific training: setting it up
  • Endpoint Manager: finding endpoints and building your own UDF
  • Form builder: field types
  • Form Test Mode
  • Forms - Extract Data (the AI form builder)
  • How managers can turn on OOF for their staff
  • How to build modules in the Module publisher
  • How to create module comprehension audits
  • How to create module evidential audits
  • How to create module quizzes
  • How to embed an SD into the LMS
  • How to make form templates live for everyone to use
  • How to upload form elements to an SD
  • How to use the PAR SD
  • Live H&S Reporting
  • Mastering the Business Strategy Template
  • Module Admin: finding and managing modules
  • Module Completion Notification Setup
  • Module Publisher Content Options
  • PaT SD Map Overview
  • PaT SD Map Presentation
  • PaT SD Templates Overview
  • Pure Forms
  • SD Dashboard: building a dashboard
  • SD Forms
  • SD Security Settings
  • SD Template Helper Functions
  • Strategy System
  • Throttling
  • Using Chat to SD to go from being a good manager to a great one
  • Using SDs as the LMS Document
  • PaT Lite: Key aspects of PaT you need to understand
  • What is PaT and why it matters
  • PaT Lite: Chat to Task
  • PaT Lite: Introducing Strategy Documents
  • PaT Lite: Core Philosophy - Standards and Tactical Execution
  • PaT Lite: Intelligent tools that think with you
  • PaT Lite: The Future of business is Culture
  • Welcome to the PaT wiki
  • Setting up your workspace
  • Your first week
  • Strategy Documents
  • Tasks and assignments
  • Permissions model
  • Chat and discussion
  • Forms and submissions
  • Dashboards and reporting
  • Managing users
  • Workspace settings
  • Connecting an accounting system
  • Single sign-on
  • API overview
  • Access tokens
  • Webhooks
0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
Advanced quizzes: 0 of 37 passed
  • ○Form Test Mode (not passed yet)
  • ○Pure Forms (not passed yet)
  • ○Conditional Formatting (not passed yet)
  • ○How to upload form elements to an SD (not passed yet)
  • ○Forms - Extract Data (the AI form builder) (not passed yet)
  • ○How to make form templates live for everyone to use (not passed yet)
  • ○Form builder: field types (not passed yet)
  • ○SD Forms (not passed yet)
  • ○Build a reporting system (not passed yet)
  • ○Endpoint Manager: finding endpoints and building your own UDF (not passed yet)
  • ○Configuring a UDF: columns and calculated columns (not passed yet)
  • ○Configuring a UDF: filters, grouping and endpoint details (not passed yet)
  • ○SD Dashboard: building a dashboard (not passed yet)
  • ○PaT SD Map Presentation (not passed yet)
  • ○PaT SD Map Overview (not passed yet)
  • ○Strategy System (not passed yet)
  • ○PaT SD Templates Overview (not passed yet)
  • ○How to use the PAR SD (not passed yet)
  • ○SD Security Settings (not passed yet)
  • ○SD Template Helper Functions (not passed yet)
  • ○Mastering the Business Strategy Template (not passed yet)
  • ○Using SDs as the LMS Document (not passed yet)
  • ○How to embed an SD into the LMS (not passed yet)
  • ○How to build modules in the Module publisher (not passed yet)
  • ○Module Publisher Content Options (not passed yet)
  • ○How to create module quizzes (not passed yet)
  • ○How to create module comprehension audits (not passed yet)
  • ○Module Completion Notification Setup (not passed yet)
  • ○Customer-specific training: setting it up (not passed yet)
  • ○How to create module evidential audits (not passed yet)
  • ○Module Admin: finding and managing modules (not passed yet)
  • ●Auto Escalation (this page)
  • ○How managers can turn on OOF for their staff (not passed yet)
  • ○Using Chat to SD to go from being a good manager to a great one (not passed yet)
  • ○Throttling (not passed yet)
  • ○Live H&S Reporting (not passed yet)
  • ○Chat Management - Pro Tips (not passed yet)
  1. Documentation
  2. Advanced
  3. Auto Escalation

Auto Escalation

Summary PaT's Auto Escalation system automatically monitors task deadlines and escalates overdue tasks up the management chain when employees don't renegotiate them in advance. When an employee…

On this page
  • Steps
  • How an escalation works
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Step 9
  • Using escalations to lift performance
  • Clearing an escalation
  • Step 10
  • Step 11
  • Step 12

Summary PaT's Auto Escalation system automatically monitors task deadlines and escalates overdue tasks up the management chain when employees don't renegotiate them in advance. When an employee misses a deadline without a word, their Task Integrity score drops and an escalation task is created for their manager, and the escalation continues up through the supervisors until it is resolved. The system shows planning issues in real time, creates accountability through employment agreement standards, and helps managers give targeted support instead of reacting to performance problems after the damage is done.

Steps

Introduction. The fastest way to fix performance issues in any team is to fix missed deadlines. PaT's Task Auto-Escalation process makes that effortless.

What is Auto Escalation? Auto Escalation is PaT's methodology to help align organisational capability to the professional standards required of high-performing service delivery companies. It makes sure non-compliance, such as a missed deadline, is addressed proactively, by automatically escalating overdue tasks up through the management chain. Because PaT manages this, nobody has to monitor deadlines and then act on them. That saves managers a lot of time, and because the process is automated, the critical insights managers need to drive standards of excellence don't get overlooked, forgotten or ignored because managers are too busy. Auto escalation is a total game changer.

Why it helps. Task escalations highlight gaps in planning, communication or capability, showing where support or training is needed. Some people may feel uneasy about being monitored or held accountable, but they often benefit the most: once the gaps are identified, targeted training can be provided, helping them unlock greater productivity, confidence and job satisfaction.

How an escalation works

Step 1

An employee receives a task from their manager. It appears in their upcoming tasks, along with its deadline.

Step 2

The employee gets caught up with other tasks and misses the deadline without renegotiating it. That breaks the only task management rule in PaT: "It's OK if you can't meet the deadline. The ONLY thing you have to do is renegotiate it BEFORE it passes." Missing a deadline isn't important in itself; that's life. But regularly missing deadlines AND not bothering to negotiate new ones is a big deal: it's unprofessional, and it often adds up to serious consequences for other people in the business. Staff who often neglect to renegotiate deadlines before they lapse are signalling that they lack the professional maturity to manage their commitments. PaT's reporting puts a blowtorch on this issue, with empirical data that supports wrapping planning strategies around staff who otherwise won't ask for help. That support can take many forms, such as upgrading inadequate time management and planning systems, realigning professional standards, or basic time management training in skills like time blocking, building contingency into estimates and saying no. PaT highlights the issue in two ways, in Steps 3 and 4.

Step 3

First, the employee's Task Integrity rating is downgraded. PaT recalculates it every hour with the formula (Total Tasks - Missed Deadlines) / Total Tasks. Missed deadlines drop off after 3 months. If the employee renegotiates deadlines before they fall due, their Task Integrity stays at 100%: the holy grail. The goal is to behave like a true professional, who tells the task's assignor in advance when a deadline is at risk. That gives the assignor time to adjust and reduce the risk, and lets them manage their credibility before things go wrong, unlike people who only find out after the fact and are forced into stressful last-minute damage control.

Step 4

Second, PaT automatically creates an escalation task for the employee's boss, their manager, giving the manager 5 days to fix the issue. This adds a healthy awareness to the process. The manager should see it as a potential issue to investigate: does their team member need planning support?

Step 5

PaT works out who the employee's boss is, and names that manager as the assignee of the new escalation task.

Step 6

PaT also identifies the manager's own boss as the assignor of the escalation task, and assigns it to the manager on that boss's behalf, asking the manager to find out why the employee is missing deadlines. The manager's boss isn't notified straight away: they are only pulled in if the manager fails to resolve the issue within five days, or needs to renegotiate their own deadline. If the manager works with the employee to complete the task, or to negotiate a new deadline that fits the employee's workload, PaT quietly closes the escalation and removes it from both the manager's and their boss's view. That is exactly the point. Only if the original task stays overdue and the manager fails to manage their escalation task properly is the manager's boss notified.

Step 7

In short, the manager's boss only gets involved if the manager fails to act and misses their own deadline, which escalates the issue further up to them.

Step 8

If the manager ignores their employee's escalating task, the manager's own integrity score decreases, and their boss is notified.

Step 9

The manager's boss now gets an escalation task from their own boss, and is under tension to fix three things: why the employee isn't managing their tasks, why the manager isn't managing the employee, and why planning is breaking down. Escalation continues up the chain until the issue is resolved.

Using escalations to lift performance

Note. Escalations aren't a problem, unless they're frequent. When they are, PaT gives leaders real-time, empirical data to have meaningful, timely conversations with staff. This is the difference that makes the difference. In most businesses, by the time leadership realises something's gone wrong, the damage is already done. They're forced to backtrack, investigate, listen to excuses, reconstruct who said and committed to what, and scramble to create new processes to stop it happening again, usually days or even weeks too late. With PaT's auto-escalation process, issues surface in real time, so leaders can act fast, fix root causes and intervene before problems escalate. You recover time, reduce stress, and move from reacting at the bottom of the cliff to preventing issues at the top.

Insights from escalations. Escalations are never random: they're always a symptom of something deeper. But one truth remains: when staff fail to plan, they're planning to fail. Escalations usually fall into one of these categories: - Underdeveloped planning skills: the most common reason. These staff need better planning systems, mentoring, or manager training to build capability. - Unskilled, not lazy: missing deadlines is often a silent cry for help. If they knew how to plan, they would. They've never been taught what good looks like, and never taken the initiative to find out. - Disengaged or hiding: without systems like PaT, it's easy to bury failure under excuses, complexity or silence. - Under-resourced: in some cases the workload truly exceeds capacity. These staff aren't commercially mature enough to raise it as a business case, so they burn out or drop the ball.

Linking Task Integrity to the employment agreement. Most employees are fantastic: professional, proactive and committed to doing what they say they'll do. For them, checking their task list daily and flagging potential delays before they occur is second nature: it aligns with their ethical compass. In a service delivery business, though, consistent planning and follow-through aren't optional: they're fundamental. Unfortunately, some staff agree to this social contract but don't uphold it. That's why PaT recommends formally linking a minimum Task Integrity rating (for example, above 90%) to the employment agreement. In PaT's experience, 10% is more than enough to absorb genuine roadbumps when life gets in the way. Maintaining 100% Task Integrity couldn't be simpler: check your tasks daily, and if a deadline might slip, propose a new one. People who can't do this will harm your culture. When the standard is managed in PaT and met across the board, organisational performance and culture soar, because delays are managed before expectations are missed, eliminating one of the biggest sources of stress in most companies. This small clause unlocks a pathway to exceptional performance. And in the rare cases where someone consistently fails to meet the standard, you have a clear, fair framework to act on quickly, instead of wasting weeks chasing evidence after the fact.

Contractual wording example. In most companies, the starting point for performance management, day 0, is already too late. By the time issues are obvious, you have to spend days piecing together what went wrong, then weeks setting up a formal tracking process. PaT flips the script: management begins at day zero. With real-time visibility and a clear digital trail already in place, you skip the scramble, avoid weeks of stress, and take fast, fair action from the moment it's needed. An employment clause might be worded like this: "As a service-based organisation, effective planning and time management are considered essential functions of employment. Employees are expected to maintain a Task Integrity rating of 90% or above, as measured within the PaT platform. This is easy to do even during times of high workload: simply negotiate deadlines. Consistent failure to meet this standard, without reasonable justification, may constitute a performance issue and may be managed in accordance with the company's performance improvement or disciplinary process."

End the endless performance management cycle. With Auto Escalation, you can stop the cycle of starting over every time something goes wrong. Instead of chasing symptoms and rewriting performance plans, PaT gives supervisors a single, universal signal to focus on: task escalations, the clearest indicator of poor planning. It doesn't matter what the task is: the root issue is always the same, missed deadlines and silence. This data-driven approach, anchored to one clear KPI, removes the emotion and blame that often cloud performance discussions. It cuts through any ambiguity about a task's complexity or scope and replaces it with one question: was the deadline renegotiated, or not? It's faster, fairer and far less stressful for everyone. When tasks drive performance and deadline non-compliance is resolved, everything improves.

Using escalation data. With clear escalation data, a business can: - shift conversations away from looking back, with blame and excuses about why deliverables didn't meet expectations, towards better planning solutions and communication strategies that meet or exceed expectations in future; - rapidly correct poor performance through targeted support and training; - ensure accountability by reinforcing role expectations in the context of the employment agreement, and move forward appropriately.

Result. By enforcing a single, non-negotiable expectation (keep tasks from escalating), PaT drives consistent behaviour change. The result is a culture of accountability, higher performance and fewer stressful, last-minute firefights: in other words, an incredible company culture.

Clearing an escalation

Step 10

The manager addresses the escalation with the employee. Together they go through the employee's task list and assess their workload and planning systems, while the manager reinforces the importance of task management and proactive deadline negotiation, to improve the employee's reputation and keep stress low.

Step 11

There are two ways the employee can instantly remove all the related escalation tasks from their chain of command: - Complete the source task. Once the original task is completed, all associated escalations are automatically removed from everyone's task wall, with no further follow-up needed. - Negotiate a new deadline. When a new deadline is proposed, even after the due date, PaT considers the task back under control. All supervisor escalations are cancelled, and the task continues with renewed clarity.

Step 12

A manager who receives an escalation task can extend the deadline on that escalation task if needed, so that their own supervisor isn't assigned an escalation task. To view the escalation history, they can click the orange info icon on their escalation task. Managers should also work proactively with their employees to prevent future escalations. Auto Escalation means smarter management and stronger teams: because planning challenges are now transparent, employees end up with the training and systems they need to excel.

Check yourself

Checking your PaT sign-in…

PreviousVideo calls on the mobile appNext Build a reporting system

On this page

  • Steps
  • How an escalation works
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Step 9
  • Using escalations to lift performance
  • Clearing an escalation
  • Step 10
  • Step 11
  • Step 12
PPaT Wiki

Documentation, knowledge base and community support for People and Tasks.

Documentation

  • Getting started
  • Core concepts
  • Integrations
  • API reference

Support

  • Knowledge base
  • Community forum
  • Contact us
  • Service status

Company

  • PaT
  • Blog
  • Terms
  • Privacy

© People and Tasks. All rights reserved.