One merged drawing set out, twenty separate statuses back

Some customers want the complete drawing set as a single file on every issue: one bookmarked, hyperlinked PDF a reviewer can move through. Easy enough to send. Then it comes back, and although you sent one file, they’ve statused every drawing inside it separately. Three rejected, two approved with comments, fifteen approved. One PDF, twenty different outcomes.

Now the manual work starts, and it’s the worse half of the job. Split the file back into its twenty documents by page range, without losing a page. Re-key each drawing’s status into the register. Route the three rejections to the sub-suppliers who produced them, and only those three, while the fifteen approved drawings close out. Then, next issue, rebuild the merged set from the current versions, remembering which drawings moved, because the reviewer on the other end wants to know what changed since last time and will not enjoy re-reading two hundred pages to find out.

Most teams end up with a side spreadsheet whose only job is remembering what’s inside the merged file and where each piece stands. That spreadsheet is the tell: the deliverable format and the tracking unit have come apart, and a person is holding them together by hand.

The two honest options

Push back on the format and ask to submit the drawings individually. Sometimes that works; the requirement is often habit rather than policy. Or accept the format and build the discipline: a page-range map maintained per issue, statuses keyed per drawing, a fixed routine for the re-split. It’s all doable. It’s also permanent overhead on every issue of every drawing set for that customer.

Where DocBoss comes in

DocBoss treats this as one capability with two halves. Going out, it combines the drawings into the single bookmarked file the customer asked for, a package, while every drawing inside stays its own tracked document; the package goes out in a submittal and appears on the transmittal as one line. Coming back, DocBoss breaks the package apart against the page ranges, with a page-count check so nothing is lost, and each drawing takes its own return status and its own route: the rejected ones back to their sub-suppliers, the approved ones to done. The next issue is a fresh package built from current versions, and it can carry a revision index showing the reviewer exactly which documents changed since last time. The side spreadsheet retires. Break-out applies to packages DocBoss built for the submittal.

If one of your customers insists on the single-file format, this is the feature to see end to end.