Decision inputs
Facts that change the policy answer
The request sits in marketing and communications and connects interview notes, usage results and customer approvals with a publishable customer story. That context distinguishes it from a generic permission to use AI.
- 1Task and owner
- Customer marketer wants to draft a customer case study. Record the person who will stand behind a publishable customer story after the tool has finished.
- 2Information involved
- Interview notes, usage results and customer approvals. Include attachments and connected sources when deciding the highest information classification.
- 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 publishable customer story. Follow the result to its real endpoint so the request captures its practical effect.
- 5Consequence if it is wrong
- Customer names, metrics or quotations may not be cleared for publication. A familiar task still needs escalation when this consequence becomes plausible.
- 6Human review
- customer marketing lead should inspect, change, reject or stop the result. Make the review happen before reliance and give the reviewer a real way to stop the work.
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 customer information is used, a publishable customer story remains within the stated purpose, and customer marketing lead reviews it before use.
Approval may be required
Send the request for approval if the account or data handling is uncertain, customer names, metrics or quotations may not be cleared for publication, or a publishable customer story 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 customer marketing lead can intervene, or publish only approved facts and quotations tied to the customer’s current consent cannot be maintained. Consider less information, a controlled account or a non-AI process.
Request checklist
Questions to ask before using the tool
- 01
Which approved account will perform draft a customer case study, and what external connections can it reach?
- 02
Could interview notes, usage results and customer approvals be reduced to a short de-identified extract?
- 03
Does a publishable customer story create an external statement, a decision or an automated action?
- 04
Who replaces customer marketing lead 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
- customer marketer
- task
- Use AI to draft a customer case study.
- information
- interview notes, usage results and customer approvals
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Draft or analyse
- impact
- External publication
- review
- Complete human review
- owner
- customer marketing lead
Useful safeguards
Controls that fit this request
- ✓
Publish only approved facts and quotations tied to the customer’s current consent
- ✓
Reduce interview notes, usage results and customer approvals to the smallest useful extract and remove fields unrelated to a publishable customer story.
- ✓
Write the boundary around a publishable customer story clearly so later users do not expand the approval by assumption.
- ✓
Record the request and reviewer without copying unnecessary parts of interview notes, usage results and customer approvals into the audit trail.
Questions people ask
About this AI use
Is using AI to draft a customer case study automatically allowed?
Treat this as a request pattern. The authoritative answer comes from the current company policy and the employee’s completed submission.
What belongs in the employee’s request?
Describe a publishable customer story, identify interview notes, usage results and customer approvals, name the exact tool and account, explain who will receive or rely on the output, and state how customer marketing lead will review it.
What belongs in the completed policy record?
Record the request and reviewer without copying unnecessary parts of interview notes, usage results and customer approvals into the audit trail. A classification and controlled reference may be enough when copying interview notes, usage results and customer approvals would create unnecessary risk.