T129 Service exception action sheet
Service exception action sheet
Every late pickup, late delivery and missed appointment on Hollowell Paper Products loads in the week of September 21, 2026, tied to one owner and one next action, so each plant hears one update from Quartzline Freight and not two. Prepared by the Quartzline operator on shift for the Hollowell plant shipping leads and for Bettina Kowalczyk, Transportation manager at Hollowell. Priyanka Raghunathan, Operations manager, decides the routing action on each open exception. Marcus Ellery, Key account manager, is the only person who approves an update to the shipper. Issued Thursday, October 1, 2026, from records checked on Monday, September 28, 2026.
Sample template: the firm, people, clients and figures are fictional.
What happened in the week
Quartzline moved 312 Hollowell loads in the week of September 21, and 23 of them had a service exception. Carriers, drivers and plant staff reported them. Late pickups are the largest group by far, with 14 of the 23.
Live example from the Dashboards app, shown with Hollowell Paper Products' demo data. Block dates move forward each week, so they can differ from the sample dates on this page.
| Exception type | Count | Share of the 23 |
|---|---|---|
| Late pickup | 14 | 61 percent |
| Late delivery | 7 | 30 percent |
| Missed appointment | 2 | 9 percent |
| Total | 23 | 100 percent |
The shares are rounded to the nearest percent from the counts in the table.
Who owned each exception, and how fast
An exception is owned when one named Quartzline person has accepted it and written the next action. The target is an owner within one hour of the report. Nineteen of the 23 met it.
Live example from the Dashboards app, shown with Hollowell Paper Products' demo data.
Open exceptions and the next action
Four of the open exceptions are the four that produced conflicting updates. Priyanka Raghunathan owns each one. The last column shows what the plant received and what happens next.
| Exception | Load | Plant or lane | Status | Next action | Update to the plant |
|---|---|---|---|---|---|
| Late pickup at the north plant | QF-32204 | North plant | Review the exception owners and the update rule with the night shift on Oct 7 | Two updates from two people, from different information | |
| Late pickup at the other plant | QF-32219 | Other plant | Review the update rule with the night shift on Oct 7 | Routing action decided by Priyanka; Marcus approves the next update | |
| Late delivery to a customer site | QF-32240 | Other plant to customer lane 6 | Send one approved status through Marcus | The carrier ETA changed twice and each change went out as a separate message | |
| Missed appointment at the north plant | QF-32266 | North plant | Decide the routing action and send one approved status | Priyanka is deciding whether the load is rebooked or rerouted |
Four conflicting updates went to the plant
In the week of Sep 21, four exceptions produced conflicting updates to the shipper from two Quartzline people. The night operator and the account team both answered the plant, from different information, because the exception had no single status. The plant leads had to decide which message to trust. Until the rule is reviewed with the night shift on Oct 7, only Marcus Ellery approves an update to the plant.
The single-voice rule
The life of an exception
Each exception moves in one direction. It is not resolved until the plant has the approved status and the operational task is done.
stateDiagram-v2
[*] --> Logged
Logged --> Owned: Owner named within one hour
Owned --> Updated: Marcus approves one status
Updated --> Owned: New fact changes the plan
Updated --> Resolved: Task done and plant informed
Resolved --> [*]
An exception that returns from Updated to Owned gets a new approved status. It never gets a second status from a second person.
What Priyanka decided
Live example from the Dashboards app, shown with Hollowell Paper Products' demo data.
The plant should never have to ask which of us is right. One status, one name behind it, and the next step written next to it.
If the update does not arrive
The plant shipping lead can escalate when an exception has no approved status after the times below.
- Review the exception owners and the update rule with the night shift. Owner: Priyanka Raghunathan, Oct 7
- Send one approved status on QF-32240 for the two ETA changes. Owner: Marcus Ellery, before Oct 7
- Decide rebook or reroute on QF-32266. Owner: Priyanka Raghunathan, before Oct 7
- Make Marcus Ellery the only approver of shipper updates. Owner: Priyanka Raghunathan, done
How to use this template
Build one sheet for each reporting week, once the week's exceptions are logged. List every open exception with one owner, one next action and the update the shipper received, and mark any exception that produced more than one message.
| Variable | Meaning | Required |
|---|---|---|
{{account.name}} | Shipper the sheet is for | Required |
{{week.start_date}} | First day of the reporting week | Required |
{{exception.counts}} | Exceptions by type for the week | Required |
{{exception.open_rows}} | Open exceptions with load, owner, status and next action | Required |
{{update.approver}} | The one person who approves shipper updates | Required |
{{update.conflict_count}} | Exceptions that produced conflicting updates | Required |
{{exception.owner_time}} | Time from report to named owner for each exception | Optional |
If a required value is missing, show Needs review in its place and hold the sheet; never guess an owner or a status. If the exception log cannot be read, show Unavailable for the counts.
The live Dashboards blocks on this page show the Hollowell Paper Products demo profile. Point each block at your own client's profile, or remove it, before you share the page.