Turning a one-off into a routine: save and reuse your best requests
Build a small personal library of requests that work, so regular jobs take seconds.
When a request gets a great answer, save it. Next time you only change the details.
How:
- Keep a note on your phone or computer called "AI requests".
- Paste in requests that worked well.
- Replace the changing parts with [square brackets].
Example template:
Reply to this email from [who]. I want to [agree / say no politely / ask for more time]. Keep it under [100] words and friendly. Email: [paste]
Good ones to save:
- replying to emails
- weekly meal plan and shopping list
- explaining letters
- summarising meeting notes
- birthday and thank-you messages
Some assistants let you save requests inside the app too (look for "saved prompts", "shortcuts" or "Gems").
After a month you'll have a personal toolkit that turns 20-minute jobs into 2-minute ones.
Why templates work
Good requests take a little thought: who, what, background, format (lesson 7). Once you've found the version that works for a job you do often, there's no need to rethink it each time.
Build your library
Where to keep it: a notes app, a document, or your assistant's own saved prompts feature if it has one.
What a good template has:
- a short name ("Polite no")
- the request, with [brackets] for the parts that change
- any reminder for yourself ("remove client names first")
Starter templates
Meeting notes to actions
Here are my rough meeting notes. Turn them into: 1) decisions made, 2) actions with owner and deadline, 3) open questions. Notes: [paste]
Weekly meal plan
Plan [5] dinners for [2 adults, 2 children], budget [£50], [one vegetarian]. Use up [ingredients]. Give a shopping list grouped by supermarket aisle.
Explain a letter
Explain this letter in plain English. Tell me: what it's about, what I need to do, by when, and what happens if I don't. [photo/paste with personal details removed]
Polite no
Help me say no to [request] from [who]. I want to keep a good relationship. Offer [alternative, if any]. Under 80 words.
Weekly update
Turn these bullet points into a short weekly update for [my team / my manager]. Friendly and clear, under 150 words: [bullets]
Make it even faster
- Pin the note somewhere handy.
- Use your phone's text shortcuts to paste a template with a few keystrokes.
- Put the template in a project with any reference files (lesson 14).
Keep them fresh
Every couple of months, re-read your templates. Remove anything out of date and improve the ones you use most.
From prompting to workflows
Saving requests is the first step from occasional use to a genuine workflow: a repeatable sequence that reliably produces a result. People who get the most value from AI at work tend to have a handful of these for their most frequent tasks.
Designing a strong template
A reusable template should be robust to different inputs. Build in:
- Clear role and task: "You're my assistant for drafting customer replies."
- Fixed rules: tone, length, things to always or never do.
- Variable slots: [customer name], [issue], [resolution].
- An output format: so results are consistent and easy to scan.
- A quality check: "Before finishing, check the reply answers every question in the customer's message."
Example:
You're my assistant for customer replies at [business]. Tone: warm, clear, no jargon. Never promise refunds; say I'll review and reply within 2 working days if a refund is requested. Customer message: [paste]. Write a reply under 120 words. Then list any questions in their message that the reply doesn't answer.
Chaining templates
Bigger jobs can be split into a short chain, each step with its own template:
- Gather: "Summarise these three documents into key facts."
- Draft: "Using those facts, draft a one-page proposal."
- Critique: "Act as a sceptical finance manager. What's weak?"
- Finalise: "Revise the proposal to address those points."
Each step is checkable, which keeps you in control.
Where templates live
- Notes or documents: simple, works with any assistant.
- In-app features: several assistants let you save custom versions or instructions for a specific job (for example Gemini "Gems" or custom GPTs in ChatGPT). These combine a template, instructions and sometimes files.
- Team libraries: at work, a shared document of approved templates spreads good practice and keeps quality consistent.
Measuring whether it's worth it
A simple test: time a task before and after using your template for a couple of weeks. If it's not saving time or improving quality, change the template or drop it.
Pitfalls
- Stale details: old prices, job titles or policies hidden in templates.
- Over-trusting: a familiar template can make you check less carefully. Keep reading the output.
- Copying sensitive data into shared templates. Keep slots generic.
Try this prompt
Here's a request that worked well for me: [paste it]. Turn it into a reusable template with [square brackets] for the parts I'll change each time, and suggest a short name for it.
Replace the [brackets] with your own details
On haystak
Quick check · 1 of 3
What are the [square brackets] in a template for?
Next step
AI that does tasks for you (agents): when to let it, and when not to
Understand AI agents, what they can safely do for you today, and where to keep control.