Opportunity Stage Requirement Review Checklist
Use this checklist with your sales manager and Salesforce administrator before adding or changing a requirement on one opportunity stage. Start with one stage and one business need.
Purpose and coverage
- [ ] Define what the stage means and the evidence needed to enter it.
- [ ] Name the person who needs the information and the decision or task it supports.
- [ ] Identify the waiting time, repeated explanation or rework caused by its absence.
- [ ] Explain why the information is needed here rather than earlier or later.
- [ ] Decide which opportunities are covered, including relevant sales processes and record types.
- [ ] Decide whether the requirement applies only on entry, on saves while in the stage, or in later stages as well.
- [ ] Identify any existing records that would fail the new requirement during an ordinary edit.
Useful information and seller experience
- [ ] Write one useful entry in the team's own words, such as “Confirm the revised quote with the customer's finance lead on [date].”
- [ ] Write one vague entry that would pass a blank check, so managers can coach against it.
- [ ] Consider whether guidance alone would meet the need before blocking saves.
- [ ] Make the expectation visible before the seller encounters an error.
- [ ] Make the message say what to add, where to add it and why it helps.
- [ ] Check that the wording fits both a stage change and an edit to a deal already in the stage, if both are covered.
- [ ] Confirm that the people expected to complete the field can see and edit it.
Tests before a production rollout
Run these checks in a sandbox or another appropriate test environment. Record expected and actual results, including any intentional exceptions.
- [ ] Enter the covered stage with the information missing, then with a useful entry.
- [ ] Edit another field while in the covered stage with the required information missing.
- [ ] Clear the required information while in the covered stage.
- [ ] Save an earlier-stage deal without the information.
- [ ] Move backwards and skip directly to a later stage.
- [ ] Create a record directly in the covered stage.
- [ ] Close as lost from the covered stage without the information.
- [ ] Check Path, direct field editing and the other controls sellers actually use.
- [ ] Test representative seller permissions and relevant record types.
- [ ] Test the imports, integrations and automation that create or update these opportunities.
Ownership and follow-up
- [ ] Name an owner for the requirement, message and documentation.
- [ ] Agree how to handle legitimate exceptions.
- [ ] Set a review date and ask whether the information is being used.
- [ ] Compare the questions colleagues had to chase before and after the change, alongside the extra effort required from sellers.
- [ ] Check for vague entries, repeated handoff questions and blocked legitimate updates.
- [ ] Agree what would make you simplify or remove the requirement.
A completed field is not proof of a qualified deal or buyer commitment. Use the information to support a useful conversation.
Need help deciding what should be required? Contact Logic Conduit with your stage list and an example of a handoff that creates extra work.