What your sub-vendors owe you, and when: expediting the other direction

Fabricators know the first chase well: the customer has your drawings, the return date has passed, and someone sends the follow-up email. That direction gets attention because the customer’s silence blocks your shop.

The other direction gets less attention and hurts just as much. A coded job carries more sub-vendors than most supplier work: heads from one shop, relief valves from another, instrumentation through a distributor, NDE from a testing house. Every one of those scopes owes documents, drawings for your engineering to review, certificates for the book, test reports, and every one of those documents has a date on which your own schedule starts to care about it. The vessel does not ship because a sub-vendor’s certificate is sitting in someone’s outbox.

The reason this chase gets neglected is structural. Customer returns are one list against one party. Sub-vendor documents are many small lists against many parties, none individually urgent, and the tracking scatters to wherever each purchase order lives. Nobody owns the aggregate view, so the aggregate view does not exist, and the first sign of trouble is a book with holes in it.

Two dates make the tracking work, and they are not the same date: when a document is due to go out, and when a document sent out is expected back. A drawing sent to a sub-vendor for correction has an expected return; a document owed by a sub-vendor’s scope has a due date. Track both per document, per party, and “who owes us what, and how late is it” becomes a report instead of a meeting.

The chase itself should be cheap. If assembling the reminder is a project, it happens rarely; if it is cheap, it happens whenever it is useful. The useful form is one message per party listing everything outstanding with them, not one email per document.

This is how expediting works in DocBoss, in both directions. Every document carries its dates, out and expected back, per party. An expedite report is generated on demand across the projects and parties you select, each party’s outstanding items gathered into their report, previewed with its email before anything sends. Standing reports run on their own from your profile: overdue documents, status changes, submittals the customer has not downloaded, so the reminder goes out while it still matters. Sub-vendors get a portal to upload into and collect from, with the history of submittals passed each way, which means their responses land in the project rather than an inbox. And where a sub-vendor’s fabrication is gated on its own document approvals, that release is a stage with a record of when it went.

Your customer chases you; that part of the market is well built. The fabricators who stay off the critical path are the ones who run the same discipline downstream.