The approved drawing that never made it back to your sub-supplier

It goes like this. The actuator drawing has been sitting with your customer for two weeks. It finally comes back approved. Whoever logs the return feels the loop is closed, tells the project manager the good news, and moves on to the next fire.

Except the loop isn’t closed. Your sub-supplier is holding manufacturing until that approval reaches them. Nobody sends it. Three weeks later someone asks why the actuator hasn’t shipped, and the answer is that it was never released, and the approval that would have released it has been sitting in your system the whole time.

On instrument and valve work this is one of the more expensive small failures there is, because the delay lands at the end of the schedule where there’s nothing left to absorb it. And the customer’s approval date is on record, so the three lost weeks are visibly yours.

Why this one gets missed

The step has no natural owner. Your register tracks what you owe the customer, because that’s what the SDI is for. The approval coming back reads as an ending, not as the start of a new obligation pointing the other way. And the person logging the return is usually the busiest person on the project, working through a stack of returns at once.

It also doesn’t get missed every time, which makes it worse. There’s no alarm and no pattern, just the occasional one that sat, discovered late.

The manual fix

If you run your projects on a spreadsheet, the fix is discipline plus a column. Add “released to supplier” with a date next to your return status. Make one rule: whoever logs a customer return either forwards it down the same day or flags it. Then sweep weekly for anything approved with an empty release date.

That works, on the projects where it’s followed. It’s a habit held up by the same overloaded person, and it fails exactly when everything else is failing, which is when it matters.

Where DocBoss comes in

In DocBoss you make the release a stage in the document’s own cycle. It’s your routing decision, not something a customer has to specify: when the approval lands, the document queues to the sub-supplier as the next step instead of depending on someone remembering. The stage can’t be skipped, and the record shows when it went. You can also see whether the sub-supplier has downloaded it, which is the difference between “we sent it” and “they have it,” and the prompt to call when they haven’t.

If this failure sounds familiar, it’s a five-minute part of a demo.