Download the editable template
Use this checklist when a request arrives through a portal, inbox, support conversation or another channel. It helps preserve the original request and route it to an authorized owner.
Ungated Markdown file. No account or email address required.
How to use it
- Save a clean copy for each request or paste it into your approved case system.
- Record the original wording and received channel before interpreting the request.
- Assign an owner and document immediate security or accessibility needs.
- Move identity, scope and target-date decisions to the authorized reviewers named in your procedure.
What it includes
| Section | How to use it |
|---|---|
| Request record | Preserve the received date, channel and original wording. |
| Contact and communication | Confirm an approved reply channel and any accessibility needs. |
| Initial routing | Assign an owner and identify possible request types for review. |
| Safety checks | Avoid unnecessary identity documents, insecure file transfers and promises before review. |
About the synthetic sample
The populated example uses fictional people, organizations, identifiers and systems. It demonstrates the fields only. It is not a customer case, measured result, legal assurance or recommended decision for a real request.
Delete the sample before using the template. Do not put passwords, identity documents, response files or unnecessary personal data in it.