Decision inputs
Facts that change the policy answer
The working material is prospect profiles, engagement data and qualification criteria; the intended result is a lead score or priority order. Recording that pair prevents a vague approval from spreading to other uses.
- 1Task and owner
- Revenue operations analyst wants to score sales leads. The request needs an accountable owner for a lead score or priority order, even when the tool prepares most of the first draft.
- 2Information involved
- Prospect profiles, engagement data and qualification criteria. Account for every route by which the tool receives the material, including plug-ins and linked storage.
- 3Tool and account
- An approved company account. The request should identify the exact account because product-level approval leaves important controls unknown.
- 4Intended result
- The expected result is a lead score or priority order. Record the audience and the next system in the chain, rather than describing the output only as a draft.
- 5Consequence if it is wrong
- The score may use weak proxies, personal data or rules salespeople cannot explain. A familiar task still needs escalation when this consequence becomes plausible.
- 6Human review
- revenue operations lead should inspect, change, reject or stop the result. The reviewer needs the source material and must be able to reject the output before it takes effect.
Possible policy routes
The task name alone cannot decide it.
A published workplace policy can return different answers for the same task. These are the practical branches worth encoding.
A routine policy route may be possible
The request may fit ordinary policy handling once the exact account is approved, only the minimum prospect personal information is used, a lead score or priority order remains within the stated purpose, and revenue operations lead reviews it before use.
Approval may be required
The request moves beyond routine handling when the account or data handling is uncertain, the score may use weak proxies, personal data or rules salespeople cannot explain, or a lead score or priority order reaches people or systems beyond the requester’s authority.
The request may need to stop or change
A stop or redesign route becomes relevant if restricted information would enter an unapproved service, the output would act before revenue operations lead can intervene, or define permitted factors and keep a person responsible for outreach priority cannot be maintained. Consider less information, a controlled account or a non-AI process.
Request checklist
Questions to ask before using the tool
- 01
Does the selected account retain or reuse anything supplied while trying to score sales leads?
- 02
Who is permitted to expose prospect profiles, engagement data and qualification criteria to this tool and for this purpose?
- 03
Does a lead score or priority order create an external statement, a decision or an automated action?
- 04
Will revenue operations lead review before the result is sent, published or acted upon?
- 05
Would another region, audience or frequency activate a different company rule?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- revenue operations analyst
- task
- Use AI to score sales leads.
- information
- prospect profiles, engagement data and qualification criteria
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Analyse
- impact
- Customer selection
- review
- Complete human review
- owner
- revenue operations lead
Useful safeguards
Controls that fit this request
- ✓
Define permitted factors and keep a person responsible for outreach priority
- ✓
Separate source material from the request record and expose only what the tool needs for a lead score or priority order.
- ✓
Write the boundary around a lead score or priority order clearly so later users do not expand the approval by assumption.
- ✓
Link the completed check to the applicable policy version and append later reassessments separately.
Questions people ask
About this AI use
Is using AI to score sales leads automatically allowed?
The task name cannot settle the answer. Apply the company’s published rules to prospect profiles, engagement data and qualification criteria, the exact account, a lead score or priority order, its audience and the proposed review.
How specific should the workplace AI request be?
Describe a lead score or priority order, identify prospect profiles, engagement data and qualification criteria, name the exact tool and account, explain who will receive or rely on the output, and state how revenue operations lead will review it.
Which evidence makes the answer reproducible?
Link the completed check to the applicable policy version and append later reassessments separately. A classification and controlled reference may be enough when copying prospect profiles, engagement data and qualification criteria would create unnecessary risk.