Decision inputs
Facts that change the policy answer
The request sits in customer service and sales and connects pipeline history, activity and account attributes with a deal probability forecast. That context distinguishes it from a generic permission to use AI.
- 1Task and owner
- Sales manager wants to forecast whether a sales deal will close. Record the person who will stand behind a deal probability forecast after the tool has finished.
- 2Information involved
- Pipeline history, activity and account attributes. The classification must cover what the tool can retrieve as well as what the requester types.
- 3Tool and account
- An approved company account. Confirm the approved account, retention setting and any connected service before the request begins.
- 4Intended result
- The expected result is a deal probability forecast. State whether another person will see it, rely on it or receive an action produced from it.
- 5Consequence if it is wrong
- The score can be treated as fact and distort attention or compensation decisions. That risk sets the level of review and the person who should receive an exception.
- 6Human review
- sales leader should inspect, change, reject or stop the result. Review is meaningful only when that person has enough context and authority to change the result.
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 lower-friction route begins when the exact account is approved, only the minimum customer account information is used, a deal probability forecast remains within the stated purpose, and sales leader reviews it before use.
Approval may be required
Pause the ordinary route whenever the account or data handling is uncertain, the score can be treated as fact and distort attention or compensation decisions, or a deal probability forecast reaches people or systems beyond the requester’s authority.
The request may need to stop or change
The company may need a safer design when restricted information would enter an unapproved service, the output would act before sales leader can intervene, or show the factors and uncertainty and keep managers responsible for forecasts 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 forecast whether a sales deal will close?
- 02
Who is permitted to expose pipeline history, activity and account attributes to this tool and for this purpose?
- 03
Who receives a deal probability forecast, and what will they do with it?
- 04
Does sales leader have enough authority and time to stop the result?
- 05
When must the employee stop and run the policy check again?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- sales manager
- task
- Use AI to forecast whether a sales deal will close.
- information
- pipeline history, activity and account attributes
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Analyse
- impact
- Internal planning
- review
- Complete human review
- owner
- sales leader
Useful safeguards
Controls that fit this request
- ✓
Show the factors and uncertainty and keep managers responsible for forecasts
- ✓
Keep whole files, mailboxes and datasets out of the prompt when a short part of pipeline history, activity and account attributes is enough.
- ✓
Treat a new purpose, region, data source or recipient as a new request rather than silently extending this one.
- ✓
Keep the submitted facts, sales leader’s decision and the exact published policy version.
Questions people ask
About this AI use
Is using AI to forecast whether a sales deal will close automatically allowed?
Even an ordinary forecast whether a sales deal will close request can change route when it involves restricted information, an external audience or weak review.
When is the request detailed enough to decide?
Describe a deal probability forecast, identify pipeline history, activity and account attributes, name the exact tool and account, explain who will receive or rely on the output, and state how sales leader will review it.
What belongs in the completed policy record?
Keep the submitted facts, sales leader’s decision and the exact published policy version. A classification and controlled reference may be enough when copying pipeline history, activity and account attributes would create unnecessary risk.