Custody exceptions
Each bin that does not match between the route sheet and the depot log is listed with its driver, route and time.
A general manager at a document shredding company can usually say how many trucks went out today, but not which bins are still unsigned at the depot. A manager app for document shredding companies shows custody exceptions, certificate backlog and route density on one screen, so the gap is visible before a client asks for proof.
A shredding company runs a chain of custody from the customer's room to a sealed truck, to a depot, to a witnessed destruction. Every link is a place where a bin can go missing on paper. A generic dashboard shows trucks and jobs but cannot show a bin that left a site and never reached the depot.
Margins are set by route density and shift output. A truck that runs half empty costs as much as a full one, and a depot that waits for a witness can hold up a whole batch. The general manager needs those numbers beside each route, not in a report that arrives after the month closes.
Start with three views: the custody exception queue, the certificate backlog view and the route density report for each day. The exception queue lists every bin where the depot log and route sheet disagree, with the driver and time attached. The backlog view shows batches destroyed but not yet certified, so a client's request never waits in silence.
Leave margin modelling by client type, truck cost allocation and driver incentive pay for a later phase. Those depend on cost data many shops do not yet hold in one place. The daily views give the general manager control first, and finance views can follow once the numbers are trusted.
The general manager opens the app at seven and sees two custody exceptions from yesterday, both on the same route. He opens the first, a bin scanned at the customer's site but not at the depot, and reads the driver's note that it was left in a locked corridor. He calls the client's facilities contact from the app and confirms the bin was collected the next morning.
Next he checks the certificate backlog. A batch destroyed on Monday still has no witness signature, so he assigns the depot supervisor to find the witness record and close the item. The route figures show the north route ran most of its stops in a single hour, and he asks dispatch to rebalance next week's stops.
Before lunch he reviews the afternoon shift. It processed fewer bins than the same weekday last month, and the app ties the drop to two witness absences. He moves the next witness slot earlier and sends the change to the depot lead with the reason logged.
Each bin that does not match between the route sheet and the depot log is listed with its driver, route and time.
Batches destroyed but not yet certified sit in a queue with their age, witness status and a named owner.
Stops per hour, bins per stop and miles per route are shown for each truck and each shift.
Bins processed per shift, set against witness availability, so a slow shift shows its cause.
Standing pickup contracts appear with their renewal dates, volumes and the account owner for each one.
The build needs route sheets and depot logs for the last year, so the app can compare the custody record with what really happened. It also needs the customer list with sites, contract terms and the price per bin or per pound, plus the list of trained witnesses and their shifts.
Certificate records matter too. Share a sample of past certificates, the batch format and the witness rules. Give the project team read access to a test copy of the route tool, so exception rules can be checked against real stops before go-live.
The first mistake is alerting on everything. A queue of forty exceptions a day trains the manager to ignore it, so the first release should raise only exceptions that affect a client's proof. The second is measuring trucks rather than bins, which hides the custody gap that matters most.
The third is keeping the witness schedule in a separate calendar. A destruction waiting for a witness is a certificate waiting for a signature, and the two should appear together. Keep one queue per problem, and give each item an owner on the day it appears.
Measure the share of bins with a matched custody record by the end of each day, the average days a batch waits for its certificate and bins processed per witness hour. Add route density by truck and the number of client complaints about proof. Each figure comes from the route, depot and certificate records.
Compare these with the same period before launch, and review them every month with the depot lead. If the general manager stops asking for the custody count each morning and starts asking about route density on the largest contract, the app is working. The better signal is a proof request answered the same day.
Usually a morning phone call with the depot lead, a route sheet read at the end of the day and a certificate tracker kept in a spreadsheet. The app puts those facts on one screen and updates them as each bin moves. The morning call can still happen, but it starts from the data.
It can read stops, route sheets and scan records where the route tool offers an export or an interface. Where a link is missing, we say so during the scoping call. Many shredders start with a daily file import and move to a live link later.
The owner and finance lead see pricing and margins. Depot leads see output and exceptions, and route supervisors see density for their own routes. Each change to a role is logged, and access can be reviewed at any time.
A mobile build starts at $4,500, and the scope sets the final number by view, role and data feed. Each one appears as a separate line in writing, so the first release can be sized to what the depot can use.
Book a free scoping call and get the scope and price for the manager view in writing.