Decision inputs
Facts that change the policy answer
The working material is meeting notes or a transcript; the intended result is agreed actions and a meeting summary. Recording that pair prevents a vague approval from spreading to other uses.
- 1Task and owner
- Line manager wants to summarise a manager and employee meeting. The request needs an accountable owner for agreed actions and a meeting summary, even when the tool prepares most of the first draft.
- 2Information involved
- Meeting notes or a transcript. The classification must cover what the tool can retrieve as well as what the requester types.
- 3Tool and account
- An approved company account. A personal login can handle information differently from the company-managed version of the same tool.
- 4Intended result
- The expected result is agreed actions and a meeting summary. 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 record may capture sensitive remarks or misstate what each person agreed. That risk sets the level of review and the person who should receive an exception.
- 6Human review
- meeting participants 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 lower-friction route begins when the exact account is approved, only the minimum employee personal information is used, agreed actions and a meeting summary remains within the stated purpose, and meeting participants reviews it before use.
Approval may be required
The request moves beyond routine handling when the account or data handling is uncertain, the record may capture sensitive remarks or misstate what each person agreed, or agreed actions and a meeting summary reaches people or systems beyond the requester’s authority.
The request may need to stop or change
Do not continue unchanged when restricted information would enter an unapproved service, the output would act before meeting participants can intervene, or confirm the summary with participants and limit access to those who need 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
Which approved account will perform summarise a manager and employee meeting, and what external connections can it reach?
- 02
Could meeting notes or a transcript be reduced to a short de-identified extract?
- 03
Could someone treat agreed actions and a meeting summary as final even though it was generated as assistance?
- 04
Can meeting participants inspect the complete result and its source before reliance?
- 05
Is this genuinely one request, or will repeated use turn it into an embedded process?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- line manager
- task
- Use AI to summarise a manager and employee meeting.
- information
- meeting notes or a transcript
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Draft or analyse
- impact
- Internal work
- review
- Complete human review
- owner
- meeting participants
Useful safeguards
Controls that fit this request
- ✓
Confirm the summary with participants and limit access to those who need it
- ✓
Document why each part of meeting notes or a transcript is necessary before making it available to the tool.
- ✓
Reassess the request whenever its tool, information classification, frequency or consequence changes.
- ✓
Keep the submitted facts, meeting participants’s decision and the exact published policy version.
Questions people ask
About this AI use
Is using AI to summarise a manager and employee meeting automatically allowed?
The company policy supplies the answer after it receives the real tool, data, purpose, impact and review plan. This page only prepares those facts.
How specific should the workplace AI request be?
Describe agreed actions and a meeting summary, identify meeting notes or a transcript, name the exact tool and account, explain who will receive or rely on the output, and state how meeting participants will review it.
What belongs in the completed policy record?
Keep the submitted facts, meeting participants’s decision and the exact published policy version. A classification and controlled reference may be enough when copying meeting notes or a transcript would create unnecessary risk.