Give your team a clear reason for what comes next.

Write the work item in a way someone can complete: clarify a new enquiry, confirm an approval route, resolve a delivery question or check a site announcement. An account can have several tasks with different owners and urgency. A single high-priority account label does not tell the service team and the sales team which work belongs to them.

Start with the queue’s purpose and the available capacity. Is this the account owner’s morning review, a research team’s weekly work or a cross-team escalation meeting? Record which types of work belong in it. Keep specialist queues where needed, but make dependencies visible so a sales task does not bypass an outstanding service commitment.

The ideal customer profile describes which companies and needs fit the offer. A priority queue adds the current task and context. High fit can justify research without establishing a live need, while an existing customer’s urgent service issue may deserve attention regardless of its expansion potential.

Assess fit against the requirements you can serve. Assess relevance by connecting the present event or question to that offer or relationship. Assess timing from a customer-agreed date, a real deadline or a documented dependency. Assess readiness by checking whether the owner has enough information and the right authority to take the proposed action.

Use an account research brief to resolve missing company or operating context before assigning a confident fit judgement. Keep an unknown state for each dimension. Missing information should create a research or clarification task when that work is worthwhile. It should not quietly become a low score that hides a promising account, or a high score that treats an assumption as a fact.

HubSpot’s scoring documentation separates property-based fit scores from event-based engagement scores and also allows combined scores. The useful lesson for a review queue is to retain the underlying reasons. A total can organise records, but cannot establish why a customer needs something or whether a contact is appropriate.

Identify work governed by an existing customer commitment, a real deadline or a service escalation rule. Then check exclusions and boundaries: a paused opportunity, an unsuitable requirement or a recorded stop-contact instruction should not be overridden by a high activity score.

For discretionary work, agree the criteria the team can explain. You might prefer a well-matched account with a specific unanswered requirement over a loosely matched account with repeated generic activity. The buying-signal guide helps establish the evidence behind that distinction.

Add capacity and dependencies. A technically complex enquiry may need an estimator who is unavailable today; record the acknowledgement owner and the expected internal handover. Capacity changes the scheduling decision, not the truth about the account. Do not mark an opportunity low quality because your team cannot work it immediately.

If you use a score, document the inputs, weights, missing-data treatment and exclusions. Test whether repeated activity from one source can dominate the result. Group duplicated announcements and related events so the queue does not reward copies of the same evidence.

Compare two records whose order feels wrong. Is a company-size preference overwhelming a direct, relevant request? Is old engagement outweighing a recent customer instruction to pause? Does a record with missing fields disappear from review entirely? Fix the rule or the data and retain the reason for the change.

Allow a named owner to override the order with a short explanation. Review recurring overrides: they may reveal an important factor the rule omits. Overrides that exist only in private messages make the queue look consistent while the actual work follows a different process.

Trial the rules on a small mixed set: direct enquiries, current customer tasks, researched accounts and items that should receive no action. Ask two colleagues to explain the next action for each. Disagreements reveal missing definitions, evidence or ownership that should be repaired before automating the order.

Review what happened after tasks left the queue, including completed work and decisions to pause or stop. Did the owner receive enough context? Did the task resolve a question? Were urgent commitments missed while lower-value activity filled the day? Use the monthly review for operating changes, the pipeline review for decisions inside active opportunities and the account plan for ongoing customer context.

A focused Plan assignment can review the evidence and recommend priority rules for your team. Within a Build campaign, agree how we select accounts, handle responses and adjust the next batch. ClarityRev can operate that work, share it with your team or hand over the research. A separate working view or automation has its own scope. Name the decisions people retain and the evidence they need to make them.