What a lock date protects
A forecast lock date is the moment in each cycle when submitted numbers stop being editable. Before the lock, the forecast is a working draft. After it, the forecast is evidence. Teams that skip the lock still produce a number every week, but they cannot grade it, because the call made on Monday quietly becomes the call they wish they had made by Friday.The lock is a governance control rather than a software setting. Any system that stores submissions can enforce one. What matters is that the organization treats the locked number as a commitment on the record, owned by the person who submitted it.
Where the lock sits in the cycle
Put the rep deadline first, manager reconciliation second, and the lock third, ahead of the meeting where leadership reviews the number. That order gives managers a real window to challenge deals and reclassify them before anything is fixed. It also means the review tests a number that already exists rather than producing one in the room.
Quarter-end usually deserves a tighter version of the same sequence. Some teams add a mid-week lock in the final two weeks. The sequence stays identical, only the frequency changes.
What locks and what stays open
Lock the submitted forecast: the category call at each level, the amount committed by each manager, and the total that rolls up. Leave the opportunity layer open. Reps have to keep close dates, amounts, and stages accurate as deals move, and a frozen CRM would corrupt the pipeline data the next cycle runs on.
The distinction is worth stating explicitly in your process document, because reps often assume a lock means they should stop updating deals. ORM treats a change in stage, close date, or amount as meaningful activity on an opportunity, and suppressing those updates removes the strongest signals available to a model.
Failure modes to watch
- A lock date that moves. If the deadline slides whenever the number looks weak, there is no lock. Publish the date and hold it. - Silent retroactive edits. Locking without preserving the submitted version accomplishes nothing. Store the submission before it is overwritten. - Locking only at quarter-end. A single locked number per quarter gives you four data points a year and no way to see when the call went wrong. - No stated exception path. Real corrections happen. Allow reopening with a named approver and a written reason, and count it.
A held lock date is what turns a weekly ritual into a measurable process. It is the precondition for tracking forecast accuracy and bias by rep and by manager, for catching deal slippage in the week it appears rather than the week after the quarter closes, and for the rest of the discipline covered in sales forecasting best practices.
Frequently Asked Questions
What is a forecast lock date?
It is the deadline after which submitted forecast numbers become read-only for the cycle. Reps and managers can still update opportunity records, but the number they called is preserved as submitted. Without a lock, the forecast is a live document that drifts toward the actual result, and accuracy cannot be measured against it.
When should the forecast lock?
Before the meeting where the number gets discussed, not after. A common weekly rhythm is a rep deadline early Monday, manager reconciliation the same day, and a lock on Tuesday morning ahead of the leadership call. Locking after the review lets the conversation quietly rewrite the record it was supposed to test.
Does locking the forecast freeze the CRM?
No. Lock the submitted forecast, meaning the category calls and the committed amounts at each level. Leave opportunity records open so reps can keep close dates, stages, and amounts current. The forecast is a claim about the period. The opportunity record is the live state of a deal, and freezing it would break the next cycle.
What happens when teams skip the lock?
They lose the ability to improve. Every accuracy and bias measurement compares what was called against what happened, so an editable forecast leaves nothing to compare. Teams without a lock date usually report better accuracy than they have, because the number kept moving toward the answer.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like forecast lock date into prescriptive action for your team.
Schedule a Demo