What is field-level locking in a CRM, and how does it enforce data quality at each pipeline stage?

A deal closes at $80,000. Two months later, a finance reconciliation turns up a closed-won opportunity showing $65,000 — a rep edited the amount after the fact to match a partial invoice, without anyone noticing the original number was ever different. Nothing was malicious, but the CRM’s record of what actually happened is now wrong, and there’s no trail showing it changed.

What does field-level locking do?

Field-level locking marks a specific field as read-only once a record hits a defined condition, most commonly a pipeline stage. A deal amount, close date, or discount percentage might be freely editable through negotiation, then automatically lock the moment the stage moves to closed-won — matching the same stage-gate logic behind MEDDIC qualification fields, applied to protecting a value instead of requiring one. Changing a locked field afterward requires an explicit unlock, usually restricted to a manager or admin role, which creates a deliberate speed bump instead of a silent edit.

How is this different from an approval workflow?

A CRM approval workflow reviews a proposed change before it happens — a rep requests a discount over threshold, and an approver signs off before the deal moves forward. Field-level locking works the opposite direction: it prevents changes to a value after it’s already been settled, without requiring a review for the original entry. The two are complementary — an approval workflow governs how a number gets set, and field-level locking governs what happens to it once it’s final.

Which fields are usually worth locking?

Not every field benefits from locking — locking a field a rep legitimately needs to keep updating (a next-step note, for instance) just creates friction without protecting anything meaningful. The fields worth locking are the ones used downstream for reporting, commissions, or forecasting once a deal closes: amount, close date, product or plan selected, and the loss reason on a closed-lost deal. Those are exactly the fields where a quiet after-the-fact edit does the most damage to trust in the numbers.

What should you do next?

If your team has ever found a closed deal’s numbers didn’t match the invoice or contract on file, that’s the specific failure field-level locking prevents. Start by locking amount and close date on closed-won opportunities — it’s the smallest change with the clearest payoff for anyone relying on those numbers for forecasting or commissions.