Tracking submittal history across revisions without losing the thread

Six months into a project, the questions get specific. Which revision went out on submittal 47? What status came back, and when? Why is the customer’s copy at revision 2 while ours says C? If your tracking is a register in Excel, the answers exist, but only if the register was built to hold them. Here’s what that takes.

The register that can answer

One row per document, history in column groups. For each issue: date out, submittal number, issue purpose, revision sent, date back, status returned. Sends and returns belong in the same group, paired, because “we sent it on the 4th” and “it came back rejected on the 19th” are one event to a project manager and two unrelated cells to a badly built sheet.

Two revision columns, not one. Your revision and the customer’s move independently. You’re at C internally while their system says 2, and both have to be right on every output, which means the register carries both and nobody “tidies” them into one column.

All the numbers. The same drawing can be known by up to five numbers: yours, your customer’s, one for the end user behind them, your sub-supplier’s, and whatever internal reference you file it under. Most projects live on the first two. When the others exist, they need columns, because every party expects to see their own number on what you send them, and a translation table in someone’s head isn’t a system.

Real dates, even for the past. Adopting the register mid-project? Backfill the earlier submittals with their actual dates, in order. A history that starts at month six answers no questions about months one through five, and those are the months the meeting will be about.

Where it strains

The wide format grows a column group every issue and breaks the day a document exceeds the template. The pairing discipline depends on the person logging returns having time to find the matching send. And the export problem is permanent: the customer wants status in their layout, which means re-shaping the register by hand every time someone asks.

Where DocBoss comes in

DocBoss holds the history against each document: every submittal in and out with dates, submittal numbers, issue purposes, revisions and statuses, with sends and returns paired so the round-trip reads as one story. It carries up to five numbers per document and tracks revisions separately against your numbering and your customer’s, so revision C and revision 2 are both right on every sheet. Earlier submittals can be entered with their real dates so a mid-project start still reads continuously, and the current state exports as a status report or as an index in the customer’s own layout when someone wants it as a file.

Even if your register already does most of this, set up a free demo to see what else DocBoss offers.