Made for Administrators
Turn a Vague Request Into a Complete Intake Record
Also useful for: people in Government
You can turn an incomplete email, chat message, or verbal request into a usable intake record without guessing at missing facts or accepting unclear work.
We'll use them to write your prompt.
Make Your Play
Give us the situation. We’ll build the prompt.
You can separate confirmed facts from assumptions, expose missing approvals or deadlines, and set a clear next action.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
Make Your Play
Turn a Vague Request Into a Complete Intake Record
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Paste the full email, message, meeting note, or transcription you received. Keep any dates, names, links, and stated urgency.
0/10000
Add your turnaround standards, approval limits, request channels, ownership rules, or boundaries. Write "No formal rules provided" if you don't have them.
0/10000
Choose how you want your clarification reply to sound.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the request exactly as you received it, including any subject line, dates, links, and names. Add the intake rules you already know. If you don’t have formal rules, write “No formal rules provided.” Review every “Not provided” item before sending the drafted reply.
Advanced instructions
Add your standard turnaround times, approval limits, official request channels, service boundaries, and routing rules. You can also ask your AI assistant to format the intake record to match the fields in your existing request register.
Use this when
Use this when you receive a scattered request that doesn't clearly state the purpose, deadline, owner, approval path, deliverable, or information needed to begin.
You'll need
- Raw request
- Intake rules and context
- Reply style
You'll get
- A structured record that separates confirmed facts from unknowns, a defensible readiness decision, one visible next action, and a reply that asks only for information blocking acceptance or routing.
By the end of this playbook
You will have:
- A structured record that separates confirmed facts from unknowns, a defensible readiness decision, one visible next action, and a reply that asks only for information blocking acceptance or routing.