Inscription Revision Log Best Practices for Monument Dealers

By TributeIQ Editorial Team|Updated Mar 2026

A revision log isn't exciting. It's not something families know about or care about. It doesn't make your monuments better-looking or your workflow faster. But a well-maintained revision log is one of the most important tools in preventing the category of errors that follow this pattern: "We made the change, we just don't have a record of it."

Or: "We thought we made the change, but apparently it didn't get applied."

Or: "A different version of the proof was cut than the one the family approved."

These scenarios - which happen at shops of every size - are preventable with a systematic revision log.

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.

What a Revision Log Is and Isn't

A revision log is a chronological record of every change requested on an order, including: who requested it, when, through what channel, exactly what the request was, and what action was taken.

It is not:

A collection of emails (email chains are not a revision log)
Verbal notes ("she called and wanted the date changed" written nowhere)
A general order notes field that includes revision requests alongside other notes
A completed-actions log without the requests (you need both request and resolution documented)

What to Log for Each Revision Request

Every revision request should be logged with these fields:

Date and time: When the request was received

Requester name and relationship: Who requested the change (not just "the family")

Channel: Phone, email, portal message, in-person, funeral home intermediary

Exact requested change: The specific change, in enough detail that someone who wasn't present could implement it correctly

Order number: Always. No revision without an order number.

Staff member: Who received the request

Status: Pending, Applied, In Next Proof, Approved in Proof, or Cancelled

Logging Requests From Different Channels

Phone Calls

Phone revisions are the highest-risk channel because there's no inherent documentation. When a family calls to request a change:

Repeat the change back to them: "So you'd like to change the birth year from 1942 to 1943, is that right?"
Enter the request in the revision log before ending the call
Tell the family: "I've logged this change. You'll see it reflected in the next proof we send you, and we'll ask you to approve the updated version before we proceed."
Send a brief follow-up email or portal message: "Confirming the change you requested today: [change description]. This will appear in your next proof for review."

The follow-up email or message creates a second documentation point and gives the family a chance to correct any misunderstanding before the change is applied to the design.

Email Requests

Email revisions have natural documentation (the email itself), but they need to be entered into the order record, not just left in an email thread. When a revision request comes in by email:

Log it in the revision log immediately
Reply to the email with: "We've logged this change: [change description]. You'll see it in your next proof for approval."
Mark the email as linked to the order record if your system supports it

Portal Messages

If you're using TributeIQ's family portal, revision requests come in through the portal messaging system and are automatically logged against the order. This is the most reliable channel for revision documentation because the documentation is built in.

In-Person Requests

When families visit your location and request changes in person:

Log it in the revision log while they're present
Read back what you've entered: "Let me confirm what I've logged - you want to change [X] to [Y]. Does that look right?"
This confirmation step prevents misunderstandings and is also a moment of care - you're showing the family that you take their request seriously and are being precise.

Managing Multiple Revisions to a Single Order

When an order has multiple revision cycles, the revision log becomes the authoritative record of what the final proof should reflect. Before generating any proof:

Review the revision log for all pending changes
Confirm each pending change is applied to the current design
Note in the log which proof version reflects each change
After proof generation, send the proof with a note: "This proof reflects all changes requested as of [date]. Changes included: [list]."

This approach surfaces consolidation errors - situations where a requested change was logged but never applied - before the proof goes to the family.

Protecting Your Business With the Revision Log

When a family disputes what was requested or approved, your revision log is your documentation. A revision log showing "Client requested on [date] via phone that birth year be changed to 1942. Staff confirmed and logged. Proof v3 shows 1942. Family approved Proof v3 on [date]" is a complete, defensible record.

An email chain, a verbal note, or a general notes field does not provide the same clarity or protection.

How TributeIQ Handles Revision Logging

MB ProBuild has no structured revision logging. Changes on MB ProBuild orders are documented in whatever way individual staff members choose - which varies significantly between employees and over time.

TributeIQ's revision log is a structured, mandatory step in the order workflow:

Every proof version is numbered and linked to the revisions it reflects
Revision requests from the portal are automatically logged
Staff-entered revisions (from phone, email, in-person) are entered through a structured form
The revision log is viewable in the order record by all staff
Consolidation check runs automatically before proof generation, flagging any logged revision not reflected in the current design

At $149/month, the revision logging infrastructure is built in alongside the AI inscription verification that prevents most errors from reaching the revision stage at all.

FAQ

What causes inscription revision log failures?

The most common causes are phone revision requests that are verbally acknowledged but never documented, revision requests stored in email threads rather than the order record, and revisions applied to the design without being logged. Orders with multiple revision cycles are especially vulnerable when each revision isn't systematically linked to a proof version and approval event.

How can dealers set up an effective revision log?

Create a structured log in your order management system with fields for date, requester, channel, exact change, and status. Log every revision request before implementing it. Send a follow-up confirmation to the family after logging phone and in-person requests. Generate new proof versions after each set of revisions and require family approval of the new version before production.

What should dealers do if a revision is missing from the final cut?

Check the revision log to determine when the request was received and what status it shows. If the request was logged but the status shows "Applied" when it wasn't, there's a production gap. If the request was never logged, there's an intake gap. Contact the family, acknowledge the error, absorb correction costs, and fix the specific process gap that allowed the revision to fall through.

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.