Inscription Proof Version Control for Monument Dealers
Version control errors - cutting from the wrong proof version - are one of the most avoidable and yet surprisingly common inscription error prevention in monument production. A family approved proof version 3. The production team cut from proof version 2. The stone comes back wrong, but the proof that was approved was correct.
This specific error produces a situation where both the dealer and the family are confused: the family approved the right thing, the dealer is sure the proof was correct, and yet the stone is wrong. It takes a version audit to understand what happened.
Prevention is straightforward. Implementation requires systematic discipline.
TL;DR
- Systematic process controls -- not individual effort -- are what reliably prevent inscription errors in monument work.
- Every order should pass through defined checkpoints: intake verification, proof creation, AI verification, and documented family approval.
- AI verification in TributeIQ runs three independent checks: date logic, name spelling, and proof-vs-order comparison.
- Human visual review fails at a predictable rate, particularly for familiar names and dates; AI comparison does not fatigue.
- Documented digital approval with e-signature is legal protection; verbal or text-message approvals are not.
- Re-cuts caused by preventable errors cost $3,000-$6,000 per incident on average; process discipline is far cheaper.
Why Version Control Errors Happen
Email Chains With Multiple Attachments
When proofs are delivered by email, each round of revisions produces a new email with a new attachment. After three rounds of revisions, the email thread has three proof PDFs attached, all with similar filenames (possibly "Smith proof.pdf," "Smith proof v2.pdf," "Smith revised proof.pdf" - or worse, all named "Smith proof.pdf").
The production team picks the wrong attachment. This is not an unusual failure mode - it happens in a normal email chain with no clear version labeling system.
File Naming Inconsistency
Without a standardized file naming convention that includes version numbers, proof files from different rounds look interchangeable. The production team that downloads "Smith_proof.pdf" from an email doesn't know if this is the first proof or the third.
Production File Generated From the Wrong Base
When a designer generates a production file for the engraver, they may generate it from the design file as-of a certain version. If the design file was modified after a proof was sent but the designer didn't update the saved version after the family approved, the production file may reflect an in-progress state rather than the approved state.
Shared Network Drive Without Version History
When proof files are stored on a shared network drive without version history, team members may overwrite previous versions with the same filename. A production person retrieving the file later gets whatever the last-saved version was, not necessarily the approved version.
The Version Control System That Prevents This Error
Principle 1: Every Proof Has a Version Number in Its Name
Every proof file generated should include a version number in the filename:
ORDER_12345_Smith_proof_v1.pdf
ORDER_12345_Smith_proof_v2.pdf
ORDER_12345_Smith_proof_v3.pdf
This is visible at a glance. When the production team sees v3, they know which version they're looking at.
Principle 2: Approval Is Documented Against a Specific Version Number
The approval record in your order system should capture the version number: "Family approved proof v3 on March 15, 2024 at 2:42 PM."
When production retrieves the order, they see: approval is on v3. They retrieve v3. Not v2. Not whatever's on the network drive.
Principle 3: Production File Matches the Approved Version
The production file (the file sent to the engraver) is generated from the approved proof version, with a clear label: ORDER_12345_Smith_PRODUCTION_v3.pdf
The "PRODUCTION" designation and the version number tell the engraver - and any subsequent reviewer - exactly which version of the design this file represents.
Principle 4: Old Versions Are Archived, Not Deleted
Previous proof versions should be archived (kept but clearly labeled as superseded) rather than deleted. They serve as the correction baseline if a question arises: "What was different between v1 and v3?" You want to be able to answer this.
Principle 5: A Version Lock Before Production
Before any order is released to production, verify:
- The approved version number in the order record
- The version number on the production file
- These two numbers match
TributeIQ's production release workflow enforces this check automatically. The system won't allow a production release against a proof version that isn't the currently approved version.
How TributeIQ Implements Version Control
MB ProBuild has no version control for proof files. Proof management on MB ProBuild is handled through whatever external file system and email process each dealer uses - which typically provides no version tracking.
TributeIQ's proof version control is built into the platform:
- Each proof generated is automatically numbered sequentially
- Family portal delivers proof with version number visible
- Approval is recorded against the specific version
- Production release is locked to the approved version - can't cut from v1 if v3 is approved
- All versions are archived in the order record
- Version history is visible to all authorized users
At $149/month, version control is part of the platform - not an add-on, not a process you have to manually enforce.
Related Articles
FAQ
What causes proof version control errors in monument production?
The most common causes are email delivery of proofs with multiple attachments in a thread (no clear current version signal), inconsistent file naming that doesn't include version numbers, production teams generating files from design software without verifying the version matches the approved proof, and shared drives where files get overwritten without version history.
How can dealers prevent cutting from the wrong proof version?
Use a version number in every proof filename. Record the approved version number in your order system at approval time. Verify that the production file version matches the approved version before release. Use software like TributeIQ that enforces version-locked production release, preventing cutting from superseded proof versions.
What should dealers do if a version control error is discovered after cutting?
Contact the family immediately. The version control error means the stone was cut from an earlier proof version that the family had already asked to be changed. This is a production process failure - absorb all correction costs. Review your version control process to identify how the wrong version reached the engraver and close that gap.
What records should be retained after a monument order is completed?
Retain the original order intake record, all proof versions with version dates, the family's digital approval with timestamp and e-signature, any cemetery correspondence, and the installation completion record. TributeIQ stores all of these within the order record automatically, making the retention requirement a byproduct of normal workflow rather than a separate filing task.
Try These Free Tools
Put these insights into practice with our free calculators and planners:
Sources
- International Cemetery, Cremation and Funeral Association (ICCFA)
- National Funeral Directors Association (NFDA)
- American Cemetery Association
- Monument Builders of North America (MBNA)
Get Started with TributeIQ
TributeIQ gives dealers a systematic proof workflow with AI verification built in at every step, from intake through family approval. The platform's three-layer verification catches the errors that manual review misses, and the digital approval system provides documented protection on every order. See how the workflow fits your shop.