Decision inputs
Facts that change the policy answer
The working material is the approved process, controls and role responsibilities; the intended result is a procedure draft. Recording that pair prevents a vague approval from spreading to other uses.
- 1Task and owner
- Process owner wants to write a standard operating procedure. The request needs an accountable owner for a procedure draft, even when the tool prepares most of the first draft.
- 2Information involved
- The approved process, controls and role responsibilities. Account for every route by which the tool receives the material, including plug-ins and linked storage.
- 3Tool and account
- An approved company account. Approval must cover the account and its settings, not merely the product name.
- 4Intended result
- The expected result is a procedure draft. Its destination matters: private working material creates a different consequence from a sent, published or automated result.
- 5Consequence if it is wrong
- A fluent procedure can still omit a safety control or assign the wrong authority. A familiar task still needs escalation when this consequence becomes plausible.
- 6Human review
- process and control owners 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 least restrictive path starts only after the exact account is approved, only the minimum internal information is used, a procedure draft remains within the stated purpose, and process and control owners reviews it before use.
Approval may be required
The request moves beyond routine handling when the account or data handling is uncertain, a fluent procedure can still omit a safety control or assign the wrong authority, or a procedure draft 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 process and control owners can intervene, or walk through the procedure with operators before approval and version it cannot be maintained. Consider less information, a controlled account or a non-AI process.
Request checklist
Questions to ask before using the tool
- 01
Is the exact account approved for write a standard operating procedure, including its plug-ins and connected sources?
- 02
Can any personal, sensitive, confidential or secret part of the approved process, controls and role responsibilities be removed?
- 03
Could someone treat a procedure draft as final even though it was generated as assistance?
- 04
Who replaces process and control owners when the request falls outside ordinary expertise?
- 05
Which change in tool, data, purpose or impact would require a fresh request?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- process owner
- task
- Use AI to write a standard operating procedure.
- information
- the approved process, controls and role responsibilities
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Draft or analyse
- impact
- Operational instruction
- review
- Complete human review
- owner
- process and control owners
Useful safeguards
Controls that fit this request
- ✓
Walk through the procedure with operators before approval and version it
- ✓
Document why each part of the approved process, controls and role responsibilities is necessary before making it available to the tool.
- ✓
Keep the use within draft or analyse and run another check if the audience, tool or intended effect changes.
- ✓
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 write a standard operating procedure automatically allowed?
Even an ordinary write a standard operating procedure request can change route when it involves restricted information, an external audience or weak review.
What belongs in the employee’s request?
Describe a procedure draft, identify the approved process, controls and role responsibilities, name the exact tool and account, explain who will receive or rely on the output, and state how process and control owners will review it.
How much of the request should the company retain?
Link the completed check to the applicable policy version and append later reassessments separately. A classification and controlled reference may be enough when copying the approved process, controls and role responsibilities would create unnecessary risk.