Level 1 · simple request
Request access: an annotated email example
Get access before the audit starts.
The situation
IT SupportIT department
For the annual audit, you need to view the shared folder "Finance 2026". Read-only access is enough. The audit starts on Wednesday.
Strict about security: without a reason and a precise access level, the request gets rejected.
Goal
Get access before the audit starts.
The winning structure
A good email for this situation includes these elements, in this order:
- A greeting with the recipient's first name.
- The folder (Finance 2026)
- Access level (read-only)
- The reason (audit)
- The deadline (Wednesday)
- A clear ask at the end: a question or an action with a deadline.
- A short sign-off, then your name.
Common mistakes
- Leaving out the folder (Finance 2026) : « Access to what, exactly? »
- Leaving out access level (read-only) : « Read or edit? I can't guess. »
- Leaving out the reason (audit) : « Why? I need a reason. »
- Leaving out the deadline (Wednesday) : « When do you need it? »
- Opening with padding ("I hope this email finds you well") instead of getting to the point.
- A vague subject line like "Question" or "Request".
Write your own version: the recipient reacts and you get a score out of 100.
The annotated example
Try it yourself first: you'll remember more. Click to show the example.
Subject : Read-only access – Finance 2026 folder
Hi team,
- Group greeting: right for a team.
For the annual audit, I need read-only access to the shared folder "Finance 2026".
- Includes: the folder (Finance 2026).
- Includes: access level (read-only).
- Includes: the reason (audit).
The audit starts on Wednesday. Could you grant access before then?
- Includes: the reason (audit).
- Includes: the deadline (Wednesday).
- Clear ask: the reader knows what to do.
Thanks,
Alex
- Short sign-off, then the name.
Why it works : 29 words against a target of 70, 5 words per sentence on average, no filler phrases.