Drafting an internal email
A low-stakes draft is easy for the sender to review before sending. Expected disposition: Proceed.
Task boundary
Drafting an internal email is assessed as a specific task and workflow, not as a general endorsement of AI for the surrounding job. A low-stakes draft is easy for the sender to review before sending.
Assumptions
- The email is an internal draft, not a notice that changes pay, access, employment, or another right.
- The sender supplies the audience, purpose, and any facts the message must contain.
- The sender reads the complete draft and remains the only person who can send it.
Decision
- Disposition: Proceed
- Pattern: Direct prompt
- Inherent risk: low
Rules that drive the decision
- Low consequence plus complete human review permits a direct-prompt drafting pattern.
- No current-source requirement or external action is delegated to the model.
Why alternatives were rejected
- An agent adds needless action risk.
- Retrieval adds no value when all facts are supplied.
Controls
- Remove confidential details that are unnecessary for drafting.
- Mark the output as a draft and check names, dates, commitments, and tone before sending.
Acceptance threshold
These are example starting thresholds for a bounded pilot of this workflow, not universal benchmarks. For drafting an internal email, the accountable owner should make them stricter when the task, consequence, or policy requires it.
- Across 20 representative messages, every required fact is present and no unsupported commitment is introduced.
- The sender can identify and correct a seeded factual error before any message leaves the draft state.
Reassess when
- The message becomes a formal employment, legal, financial, or safety notice.
- The workflow gains permission to address or send messages automatically.