How to Catch Deadline Slippage Before a Task Is Late
Deadline slippage rarely announces itself: a task stays in progress, the due date passes, and the manager finds out when the work is already late. Deviation management turns that around — the assignee records a new forecast date the moment they know they will not finish on time, and the manager gets one email a week listing only the tasks that have drifted off plan. This three-and-a-half-minute video builds the whole setup on top of ordinary online task management: three custom fields, two scripts and one scheduled report.
What you’ll learn: how to catch deadline slippage in Planfix
- How the method works end to end: a forecast date from the assignee, a weekly report for the manager (0:15).
- Create the three custom fields the setup needs: forecast date, task state and deviation (0:46).
- Write two scripts that mark a short delay yellow and a long one red (1:49).
- Build the report, group it, and have Planfix email it on a schedule (2:31).
- Keep the manager-only fields hidden from assignees while the forecast date stays editable.
How to catch deadline slippage in Planfix, step by step
Step 1. Add a forecast date field
Open the object card for the tasks whose deadlines you want to track and add a custom field of the Date type for the forecast completion date. Add a reminder that asks for this field two days before the deadline, so the assignee is prompted for a realistic date while there is still time to react. This is the only one of the three fields assignees work with, so leave it visible and editable for them.
Step 2. Add the task state and deviation fields
The second field shows the state of the task. Make it a list-type field with two values: a yellow marker for a short delay and a red one for a serious one. The video copies colored circle emojis in as plain text, which is what makes the finished report readable at a glance. This field is for the manager, so hide it from employees.
The third field calculates the deviation itself. Set its result type to Number and give it a formula built on the DATEDIF function, which returns the difference in days between the forecast date and the task completion date. Hide this field from employees as well: the number behind the marker should not be editable by the person whose delay it describes.
Step 3. Write two scripts for the markers
Now automate the marking. Create a script triggered by a change in the deviation field, set its condition to a deviation of one to three days, and set its action to write the yellow marker into the task state field. Save it, then copy it: change the name, set the condition to four days or more, and swap the yellow marker for the red one. Those two automated scripts are the whole engine — every later change to a forecast date is classified without anyone touching it.
Step 4. Build the report and have it emailed
Create a new report, give it a name and select the object you want to work with. In the report view, add a column for the task state field, then columns for the task name, the task status, the due date, the deviation and the assignee. In the selection parameters, limit the report to active tasks, and set the grouping and sorting so the worst cases sit at the top. Save and run it once to see what the manager will get.
Then set up scheduled report delivery: choose the repetition period, the report generation period and the recipient, and finish with the permissions that decide who can use the report. Generating a report is resource-intensive, so Planfix runs it in one of three windows — night, before noon or after noon — and emails the recipient a link to the finished report.
A Monday email with only the tasks that slipped
The example in the video is a weekly summary for a manager. Every Monday, Planfix emails a report of the tasks that have missed their deadlines, with a yellow marker on the short delays and a red one on anything longer. Nobody writes a status update, and the manager reads a short list instead of opening project after project. The same mechanism, written out with screenshots of every setting, is in our post on deviation management with a RAG traffic light.
Who it’s for
- Managers and team leads: one weekly email that names the delays, instead of a chat thread asking for status.
- Project managers: a forecast date that arrives before the deadline does, while the plan can still be adjusted.
- Operations and support teams: an agreed line between a delay of a day or two and one that needs attention today.
- Client-facing teams: the same scheduled report can go to a contact, so a client sees the state of their work by email.
FAQ
How can a manager track missed deadlines without asking the team?
Ask assignees to keep a forecast date in the task, let scripts mark the deviation, and schedule the report so Planfix emails it every week. The manager then reads only the tasks that deviate from the plan.
What kind of field calculates the delay in days?
A custom field with the result type Number and a formula built on the DATEDIF function, which compares the forecast date with the task completion date. A calculated field is recalculated when the fields it depends on change.
Can a scheduled report be sent to a client?
Yes. Scheduled reports can be emailed to employees and to external users, that is contacts. They see the same tasks the report author sees, but they cannot open a task they have no access to.
Start with the project that slips most
Pick the project where deadlines slip most often and give it the three fields, the two scripts and one report; the setup takes an afternoon and then keeps running by itself. From there, the same columns and markers work in any of your Planfix reports, from overdue work by department to deals grouped by amount. New to Planfix? Sign up to try it.
