Skip down to the research record

Deal change records: 3 tools and their limits

Quota Forecast Editorial Team · Published · 10 min read

Keep deal change records with file versions for documents, attributed call notes, and a CRM log for field changes and reasons. Revenue leaders need a record that answers three questions: what changed on the deal, when it changed, and who changed it.

Key takeaways

  • Separate document revisions from CRM field changes.
  • Check your account's version settings before relying on older files.
  • Record the reason alongside each meaningful change.
  • Include restores and deletions in your logging routine.

That matters. Each one keeps something useful, but each has limits you should know before you rely on it. I'll describe what each tool's version history does, point out the limits stated on the official help pages, and suggest how to fill the gaps.

What a deal record has to show

Before comparing tools, agree on what the record is for. In most small firms it serves three readers. The first is the sales leader reviewing a forecast change who wants to know whether a close date slipped once or five times. The second is the sales ops owner who has to explain a stage change to finance at quarter end. The third is anyone who questions a commitment months later, after people have moved on.

For each change, the record should capture the item that changed, the old value and the new value, the date and time, and the person who made the change. Record the reason and the related customer conversation alongside those details.

It also helps to separate two kinds of change. Some changes live in files: a quote, a mutual action plan, a redline of an order form, or the notes from a discovery call. Others live in fields: stage, amount, close date, and owner. A file-version tool helps with the first kind. For the second kind you need your CRM's field history or a manual log. This post focuses on file versions, because that is where the three tools in scope operate and where the official pages say something specific. For field changes, see the guide to deal field edit history.

Tool 1: Box version history

Box keeps versions of files, and how many it keeps depends on your license. Its help article says that "Businesses and enterprises with a Governance license can save unlimited number of versions and preview the recent 1000 versions." (Box Support, Accessing Version History)

For a small firm, the practical takeaway is to check saved-version limits separately from retention duration. Ask your Box administrator which license your company holds. If you are on a different license, read the version rules on the Box page before you assume that every older revision is kept.

Box's main strength for this job is that the file and its history live in one place. The weakness is discipline. Preserve and update the same tracked file when saving revisions.

Tool 2: Dropbox version history

Dropbox's rules depend heavily on your plan, and the length of the history window is the first thing to check. The help page says that "Dropbox Professional, Essentials, Business, and Standard customers have 180 days." It also says that "Dropbox Business Plus, Advanced, and Enterprise customers have 365 days." (Dropbox Help, Dropbox version history overview)

Those two numbers matter for a deal record because a deal can stay open for longer than a window. If a deal starts in one quarter and closes in a later one, the early revisions may fall outside the window before anyone looks at them. Find out which plan your company is on and write the window down next to your process, so the team knows how far back the file history can reach.

The same page also covers upgrades, and the point is easy to miss. Dropbox's example moves a team from Basic, which has a 30-day version history window, to Professional, which has a 180-day window. The page explains that the full 180-day look-back is only available 150 days after the upgrade, because the longer window builds up over time. An upgrade extends preservation of retained and future versions; it does not recover versions already outside the old window.

Two more limits from the same page change how you should use Dropbox. The first is that "You can't view or restore previous versions of files and folders that have been permanently deleted." In practice, a deleted deal folder that was also purged is gone from the history. Limit who can permanently delete, and treat deletion of a deal folder as a change that needs a note.

The second limit matters more for sales teams. The page states that "Version history doesn't apply to web-based files, like Google Docs/Sheets/Slides, Paper docs, or Microsoft Office Online files." Many small firms keep quotes and pricing sheets in Google Sheets or Google Docs. If yours do, check their existing document history before choosing another archive. Dropbox still works well for files that people download, edit, and upload, such as signed PDFs, exported quotes, and scanned order forms.

Tool 3: Box Notes

Box Notes can keep the notes from deal calls and the decisions made in them. Box's help article describes the save behavior this way: "While you're working in Box Notes, we automatically save your changes as a new version roughly every 5 minutes or at the first update after at least 5 minutes of inactivity." (Box Support, Tracking Version History in Box Notes)

That save pattern has a direct effect on what you can prove. Versions are snapshots, not a record of each keystroke. For call notes, that is usually enough, because you care about what was agreed, not how each sentence was typed. But do not present Box Notes history as a complete log of every edit. If two people change the same paragraph within a few minutes, the saved version may show only the result of their edits.

Box Notes explicitly documents attribution. The same article says that "For each version, you will be able to see the date and time the version was saved and the editor associated with that version."

The article also explains how to review and roll back. "You can select any past version to view it, and you can click Restore for any of the past versions listed to make that version current." Viewing an old version is harmless. Restoring one changes the current document, so it is itself a change. Agree that anyone who restores a version adds a line to the note explaining why, with the date.

Do not assume how long they last. Check with your Box administrator, or with Box support, before you rely on Box Notes as your only archive of call notes.

Matching the tool to the record

Box and Dropbox are file stores with version history. They overlap, but they answer slightly different questions. For a signed contract, a file store is the right home. For the notes that explain why the close date moved, a notes tool with attribution is closer to what you need.

Gaps none of them fill

No version history will give you the full story of a deal. Three gaps show up again and again.

The first is the reason for a change. Version history alone does not explain the reason unless someone records it in the document or note. Someone has to write that down, and the best place is at the moment of the change, in the same record. Use a close date change log to connect the move with its explanation.

The second is changes that never touch a file. A verbal commitment on a call, a promise to add a discount, or a shift in the champion's role may change the deal's risk without changing any document. If your forecast depends on these events, log them as short dated entries in the CRM or in your deal note.

The third is access outside the account. A prospect may edit a shared document, or a reseller may hold the working copy. Ask for shared documents to be sent back to your system before they are used in a forecast.

Each of these gaps is a process problem, and a better tool will not fix a process problem. That is the main lesson of this comparison.

How to choose

Choose by where your documents already live, because the history only covers files that are stored in the tool. Before you pick a tool, list the document types your team uses on deals: quotes, order forms, mutual action plans, call notes, pricing sheets. Then check each one against the three tools.

If most of your deal files are downloaded, edited, and uploaded again, Box or Dropbox can carry the file history. Dropbox's history depends on the plan you hold and on the window that applies to it, so confirm the number before you decide.

For most small firms, the best answer is a combination. Keep the working call notes in a notes tool with attribution. Keep a short change log for stage, amount, and close date changes in the CRM, with the date, the person, and the reason. That combination answers the three questions without requiring any one tool to do everything.

A simple routine that holds up

A record only helps if people keep it. Here is a routine that small teams can run without much overhead.

First, name things consistently. Use the account name, the deal name, and the document type in every file and note title. A search should find the whole deal in one step. Inconsistent names are a common reason a version trail becomes hard to use.

Second, set one place for each kind of document. Quotes and signed files go in the file store. Call notes go in the notes tool. Stage, amount, and close date changes go in the CRM. Write the place down in a one-page guide so new team members follow it from their first week.

Third, log every meaningful change at the time it happens. A change log entry should take only a moment: the date, the field or document, the old value, the new value, the person, and one sentence on why. Make this a habit in the weekly pipeline review.

Fourth, treat restores and deletions as changes. If someone restores an old version or deletes a deal folder, they add a note explaining it. This is a small step that helps explain changes to the current document or its availability.

Fifth, check the settings once a quarter. Confirm your plan, your license, your retention window, and who holds permission to delete. Plans change, and a window that worked last year may not cover a long deal today. A short check each quarter is cheaper than discovering a gap during an audit or a dispute.

Illustrative example: recording an amount change

An illustrative deal amount changes from 80 to 70 after a call. Record the old and new amounts, the date, the editor, and the reason in the CRM change log. Save the revised quote as an update to the tracked file and keep the call explanation in the deal note. The file revision preserves the document; the log connects it to the amount change.

What to do next

Start with an inventory today. List every document and every field change on a deal, and mark where each one is recorded. You will probably find two or three places where the trail stops. Those are the places to fix first.

Then pick the tool that fits your largest gap, not the one with the longest feature list. A small firm with a Box account and a Governance license may need only a logging habit.

Finally, write down the rules. A short page that says where documents live, how long each place keeps history, who may delete, and how changes get logged will do more for your forecast than any single tool. When a leader asks what moved on a deal and when, the answer should take minutes to find, not a long search through email.

Related guides: Check deal stage duration across 4 CRM tools · Deal forecast months: date rules across 4 tools.

Questions about deal change records

Can file versions replace a CRM change log?

File versions cover document revisions; use CRM field history or a manual log for stage, amount, close date, and owner changes.

What should a change record include?

Include the changed item, old value, new value, date and time, editor, and reason, with a link to the related document or call note.

Sources