When several business scorecard gaps tie, choose the one that blocks another necessary task, has a material consequence and can be tested with available time. Cory Williams, active Managing Broker and founder of Elite Agent Accelerator, provides a framework for turning a tied diagnostic into one practical next step instead of several competing projects.
Key takeaways
- Treat a tied score as a prompt for investigation rather than a final priority.
- Identify which gap prevents another necessary task from being done.
- Separate urgent client obligations from discretionary improvement work.
- Choose a small test with an owner and a date to review the evidence.
A low score helps locate a problem, but a tie does not tell you which project belongs on the calendar first. Start with the free Elite Agent Operating System, then use the worksheet below to connect each gap to an actual piece of work and a decision you can make within seven days.

In this guide
- What does a tie on a business scorecard actually tell you?
- Which gap is blocking another necessary task?
- What should go in a priority comparison worksheet?
- How do you keep urgent work from swallowing the improvement plan?
- What should a coach help you decide?
- What are common questions about tied priorities?
- What can you decide within seven days?
What does a tie on a business scorecard actually tell you?
A tie tells you that the diagnostic did not distinguish the next project by score alone. It does not establish that the projects have equal consequences or need equal time. Investigate what each score means in actual work before dividing the week among several improvements.
Cory Williams’s Elite Agent Operating System uses seven business pillars to help agents find gaps and plan implementation. His active Managing Broker experience includes 500+ career transactions and $275M+ in career sales. That practitioner background informs the framework. A score is a planning aid rather than a validated prediction of future production or member results.
Use the Operating System framework to keep the pillar definitions visible. Then name one task behind each tied score. For example, a low Lead Generation score might represent an inconsistent prospecting window, while a low AI & Systems score might represent missing next actions in the CRM. The task definitions are more useful for sequencing than the labels alone.
Which gap is blocking another necessary task?
Look for a dependency: something that must work before another activity can produce a useful result. If agents cannot identify who owns an inquiry, adding more inquiries may amplify confusion. If the intake process is clear but the database has no appropriate prospects to contact, the next need may be different.
Map the chain with plain sentences. Write that a prospecting session depends on an approved contact list, that follow through depends on an assigned next action and that a weekly review depends on current records. Keep the map small enough to inspect. You are looking for the first broken link in a specific workflow, not every weakness in the business.
A dependency is a claim you should test. Observe one work session or inspect an approved fictional record. If the supposed blocker does not actually prevent the task, revise the sequence. Avoid building a large systems project around an assumption that a simple clarification could resolve.
What should go in a priority comparison worksheet?
Compare consequence, dependency and testability in separate fields. Do not combine guesses into a score that appears precise. Use the worksheet to explain why one task goes first and what would make you reconsider that choice.
- Gap: describe the observable task that is not working reliably.
- Consequence: identify what happens when it fails and who is affected.
- Dependency: name another task that cannot work well until this one does.
- Evidence: record what you observed and what is still an assumption.
- Test: define the smallest improvement you can inspect within the available time.
- Owner: assign responsibility, a review date and a condition for continuing or stopping.
For a hypothetical agent, Brand & Authority and AI & Systems tie at a low score. A profile refresh is desirable, but the agent also finds that incoming inquiries have no assigned owner. If that process is currently losing track of client requests, it deserves prompt attention through the approved workflow. The choice is based on an observed consequence and dependency, not a universal rule that systems always come first.
How do you keep urgent work from swallowing the improvement plan?
Separate obligations that need immediate action from projects intended to improve future work. Attend to actual client deadlines through the brokerage’s approved process. Then preserve a realistic window for one improvement that can reduce repeated failures. A scorecard should not become a reason to delay current responsibilities.
Cory Williams’s business planning framework connects a longer priority to near term actions. Use the Operating System scorecard after the comparison to name one project and explicitly defer the others. Write what evidence would cause an item to move back to the top instead of reopening every choice each morning.
For example, a hypothetical two hour improvement window might be enough to define one intake ownership rule and test it on fictional cases. It is unlikely to be enough to redesign the entire CRM, rebuild the website and rewrite the consultation process. These time figures are illustrative planning assumptions, not completion benchmarks.
What should a coach help you decide?
Ask the coach to challenge the dependency and the size of the test. A useful discussion should leave you able to explain why this task comes first, what success looks like and which fact could change the order. A confident recommendation without that reasoning leaves the same tie waiting for you next week.
Use this illustrative coaching question: These two scores tie, but one seems to block the next action on incoming inquiries. Which observation would help us confirm that, and what is the smallest repair worth testing? Bring fictional or appropriately redacted evidence rather than exposing a client database to make the point.
Before starting, identify what you will stop doing during the test window. The comparison may reveal a sensible first project without creating any room to complete it. Make the tradeoff explicit: defer one optional task, reserve the time and confirm who handles ongoing obligations. A priority is credible when its time and owner exist.
What are common questions about tied priorities?
Should I choose the lowest score even if another task is more urgent?
Use the score as a diagnostic signal, then consider actual obligations and consequences. Current client responsibilities may need attention before discretionary improvement work.
Can I work on two tied pillars at once?
Sometimes one small project improves both. Define one owner, output and review so that a connection between pillars does not become permission to start several unrelated projects.
What if the first priority was wrong?
Record what the test showed and adjust the order. A small test makes a revised decision less expensive than committing to a broad project before checking the dependency.
What can you decide within seven days?
Choose two tied gaps, inspect one example behind each and complete the worksheet. Select one test and write why the other task will wait. Review the evidence on a specific day rather than relying on how busy the week felt.
Use Cory Williams’s free Elite Agent Operating System to connect the decision to the seven pillar framework. Explore Elite Agent Accelerator’s free community or optional Education Membership if you want structured help turning the chosen priority into a working process.
