Tying your document register to the equipment list

Document requirements on equipment orders multiply. One test report per tag. One general arrangement drawing per model. One packing list per shipment. One certificate for the order. So the register you owe your customer isn’t a list somebody writes, it’s a calculation: the required-document list crossed with the equipment list.

Most teams run that calculation by hand once, at project start, and then spend the rest of the project defending the result against change. Here’s how to do it in a spreadsheet properly, and where it gives out.

The spreadsheet version

Two sheets, one join. The equipment list, one row per tag with model, serial and line data. The register, one row per document, each row carrying the document code and a reference to the equipment it belongs to. Every piece of equipment data the register shows (tag lists on documents, serials, line numbers) comes through that reference by lookup, never by paste.

Expand the codes deliberately. For each document code, decide what it multiplies against: per tag, per model, per line, per shipment, per order. Build the rows from that rule. The rule matters more than the rows, because it’s what you’ll re-apply when the equipment changes.

Protect the join. The lookup key (tag or model) has to be typed identically in both sheets forever. One space character in a tag number and a document silently loses its equipment data.

Where it gives out

Change orders. Six tags added in month four. The rule says which documents that creates, but the sheet doesn’t apply rules, so someone re-derives the affected rows by hand, and has to decide what happens to documents already submitted whose tag references just changed. That decision, per document, is the real work, and a spreadsheet doesn’t even show you the list of documents affected.

Reality arrives mis-shaped. The drawing that was going to cover four tags shows up as four drawings, or four certificates arrive merged as one. Splitting and merging rows while keeping the equipment references intact is fiddly, manual and easy to get half-right.

Assemblies. Valve, actuator and positioner each carry tags and models on sub-lines. The flat two-sheet model needs a third tier it doesn’t have.

Where DocBoss comes in

DocBoss runs the calculation both ways: generate the register from your customer’s document codes against the equipment list, or load the register your engineering team already built, with each document tied to its equipment either way. That link is what does the ongoing work. Equipment data flows onto documents, cover pages, indexes and books without lookups to protect, and when the equipment changes mid-project, DocBoss identifies every affected document and asks what should happen to each: keep it, reset it for resubmission, void it, or supersede it with its history carried across. Split or merge documents as reality arrives and they stay linked to their equipment.

If your register is a spreadsheet with a VLOOKUP you’re afraid of, bring it to a demo.