Skip to main content

Document Placeholders

One live document list for the life of your order

Build your list from customer codes and equipment specs, or import data straight from engineering. It becomes the master list powering cover pages, submittal tracking, and final books, updating automatically as the project evolves.

  • Generate the list from your customer’s codes and your equipment, or load the list you already have.
  • Tag numbers, serial numbers and line numbers inherit from the equipment, so nothing is typed twice.
  • Change the equipment mid-project and DocBoss shows you exactly which documents are affected.
Schedule a Demo
Browse Other Features

5 things your document list does that a spreadsheet never will

Establish complete document visibility before the project kicks off, adapt flexibly to any customer spec, and keep your data locked to reality as orders change.

01

Inheritance

Equipment data is entered once. Tag lists, serial numbers, line numbers and models flow onto the documents and onto every cover page, index and book built from them. That means populating forty tags on a cover sheet takes zero manual typing.

02

Scope

Link an order’s required documents directly to the equipment to generate your full placeholder list before any files exist. Catch and negotiate exceptions in week one instead of discovering them at closeout.

03

Change

Change orders are normal on capital projects. DocBoss finds every document affected by an equipment change and asks how you want each one handled, rather than breaking your list.

04

Shape

One document code can produce one document per order, per tag, per model, per line, per skid or per shipment, and anything that does not follow that pattern is added one at a time or loaded in bulk. This keeps the list aligned with how you receive the documents.

05

Continuity

The list is not a spreadsheet someone maintains alongside the work. It is the thing the work runs on, so it cannot drift from reality without someone noticing.

One document list that stays right for the life of the order

Catch scope gaps in week one instead of closeout. Book a live walk-through to 
see how DocBoss builds your master list from customer codes and equipment data without double typing.

Schedule a Demo Explore All Features

HOW IT WORKS

Total equipment document control, from kickoff to handover.

Whether you derive documents from tags or import engineering spreadsheets, establish a single master list that feeds every cover page, index, and submittal.

Two ways to build the list

Generate documents automatically from equipment codes or load engineering spreadsheets in bulk. Most projects use generated documents for equipment-driven rules and loaded lists for everything else.

Equipment data flows onto the documents

Linking documents to equipment feeds cover sheet tag lists, supplier document indexes, databook splits, and expediting queues automatically from a single data entry point.

Valve and instrument assemblies, the way they actually arrive

Import multi-column assembly lists directly into parent and sub-unit tiers. Group repeated model references on a single cover sheet without duplicate tag rows.

When the equipment list changes

Manage mid-project equipment revisions safely. DocBoss flags affected active documents and prompts you to update references, reset statuses, void files, or carry history forward.

Set the rule for how many

Assign document codes by order, unit, tag, or shipment grouping. Define custom equipment groupings to match whatever divisions your customer invents.

Documents your customer never sees

The list isn’t only what you owe your customer. Shop documents, internal quality records and sub-supplier documents you manage but don’t submit belong on the same list, because they’re part of the same job. Each document can be hidden from the customer so it’s never submitted, kept internal-only, packaged into a single document for submission, or held out of submittals and included only in the databook. One list runs the whole project, and your customer sees exactly the slice they should.

Skids, vessels, and other things that contain other things

Track two-tiered equipment structures like skids and vessels. Sub-unit documents inherit major tag metadata, enabling automated databook splits by skid or vessel later.

Splitting and merging as reality arrives

Split drawings across tags or merge multiple certificates into one file without losing underlying equipment links or inherited project data.

FAQs about Document Placeholders

Get answers to questions about DocBoss’s Document Placeholders

Still have questions?

Contact Us
We already have our document list from engineering. What does DocBoss add?

Everything downstream of the list. Once it is in DocBoss with each document tied to its equipment, cover pages and indexes populate themselves, submittals assemble, status is tracked, expediting runs, and the final books compile from it. The list stops being a spreadsheet someone maintains and becomes the thing the project runs on.

Our customer sent a numbered document list rather than a list of codes. Can we use it?

Yes. The usual approach is to read the groupings out of their list, build a code list from those patterns, generate the documents and then update titles and numbers in bulk. On a small or genuinely one-off project, every document can be loaded manually instead. Which fits depends on the shape of their list, and support will walk you through it.

We supply valve assemblies where the valve, actuator and positioner each have their own model and tag. Does that work?

Yes. The assembly imports as one line with its sub-units, and assembly documents can list every tag across the sub-lines on the cover page.

FAQs about Document Placeholders

Get answers to questions about DocBoss’s Document Placeholders

We already have our document list from engineering. What does DocBoss add?

Everything downstream of the list. Once it is in DocBoss with each document tied to its equipment, cover pages and indexes populate themselves, submittals assemble, status is tracked, expediting runs, and the final books compile from it. The list stops being a spreadsheet someone maintains and becomes the thing the project runs on.

Our customer sent a numbered document list rather than a list of codes. Can we use it?

Yes. The usual approach is to read the groupings out of their list, build a code list from those patterns, generate the documents and then update titles and numbers in bulk. On a small or genuinely one-off project, every document can be loaded manually instead. Which fits depends on the shape of their list, and support will walk you through it.

We supply valve assemblies where the valve, actuator and positioner each have their own model and tag. Does that work?

Yes. The assembly imports as one line with its sub-units, and assembly documents can list every tag across the sub-lines on the cover page.

Still have questions?

Contact Us

Document list guides

Guides to building a complete document list and keeping it accurate as the order changes.