Create Reusable Templates

On a Tuesday, you finally craft the perfect prompt for your meeting minutes: the tone is right, the structure holds, and your colleagues read the document to the end. The following Tuesday, you can’t find it. You rewrite it from memory, and the result is flat. This tiny loss repeats for every recurring task, every week, eventually adding up to hours. The solution comes down to one principle: your best prompts shouldn’t be disposable; they should become templates. This is precisely what separates occasional ChatGPT use from a productivity tool embedded in your habits.

A prompt where only the information changes

A template is a prompt with a fixed structure where only specific information varies from one use to the next. Think of it as a form: the framework is already set; you just fill in the fields. Take a sales follow-up email. Written once for a specific meeting, it looks like this:

Write a follow-up email after a sales meeting with
the CTO of Safran regarding our cybersecurity solution.
The meeting took place yesterday, it went well, but there are remaining questions
about integration with their existing IT infrastructure.

This prompt serves only one purpose, for that one client; tomorrow, with a different contact, you’ll have to retype everything. The same intent, formulated as a template, becomes an asset you’ll reuse dozens of times.

Write a follow-up email after a sales meeting.

Variables:
- Contact: [NAME, TITLE, COMPANY]
- Meeting Date: [DATE]
- Our Solution: [PRODUCT/SERVICE]
- Meeting Tone: [POSITIVE / MIXED / DIFFICULT]
- Topics Covered: [LIST OF SUBJECTS]
- Open Questions: [REMAINING QUESTIONS]
- Desired Next Step: [ACTION]

Constraints:
- Professional and warm tone
- Maximum 150 words
- Mention one positive point from the meeting
- Clearly propose the next step
- Include email subject line

The following Monday, you don’t write anything new: you replace seven brackets. The tone, length, and structure remain unchanged, which is exactly what guarantees your tenth follow-up email will be as good as your first.

Building a template in five steps

Never start from scratch. Reuse a prompt that has already produced an excellent result—you know it works, so capitalize on it. Next, identify what changes with each use: the client name, the industry, the objective. These pieces of information become your variables. Label them with brackets and descriptive uppercase text, like [CLIENT_NAME], [INDUSTRY], [OBJECTIVE], so you can see at a glance what needs filling. Everything else—tone, format, structure, exclusion rules—remains fixed. This is the part of the work you’ve permanently won. Finally, add a note for each variable indicating the type of information expected. This detail saves you from hesitating over your own template three months later, when you’ve forgotten what you meant by “context.”

Five ready-to-use templates

The following five models cover tasks that most managers repeat every month. Use them as-is, then adjust them to your internal vocabulary.

The first turns rough notes taken on the fly into a distributable document. It enforces a tabular format where useful—for decisions and actions—because those are the only lines your colleagues will actually reread, and it bans narrative discussion, which bloats minutes without ever adding value.

Write a structured meeting summary based on my notes.

Meeting: [MEETING SUBJECT]
Date: [DATE]
Attendees: [LIST OF ATTENDEES AND ROLES]
Duration: [DURATION]

My raw notes:
[PASTE YOUR NOTES HERE]

Summary Format:
1. Objective and Context (max 3 lines)
2. Decisions Made (table: Decision | Owner | Deadline)
3. Action Items (table: Action | Owner | Deadline | Priority)
4. Open Issues (list)
5. Next Meeting (date, proposed agenda)

Constraints:
- Professional and factual language
- No discussion details, only conclusions
- Use "To Be Defined" if information is missing

The second serves as prep for a product committee or strategic review. By capping strengths and weaknesses at three per competitor, it forces you to prioritize instead of producing a twenty-page catalog no one will open.

Conduct a competitive analysis for our product.

Our Product: [NAME AND SHORT DESCRIPTION]
Our Positioning: [POSITIONING]
Target Market: [MARKET SEGMENT]
Competitors to Analyze: [LIST OF COMPETITORS]

For each competitor, analyze:
1. Positioning and value proposition
2. Key strengths (max 3)
3. Identifiable weaknesses (max 3)
4. Pricing (if known)

Then provide:
- Global comparison table
- Our top 3 competitive advantages to highlight
- Our top 2 vulnerabilities to address
- Strategic recommendation in 5 lines

The third is for those managing writers, whether in-house or at an agency. A complete brief avoids the most costly round-trip of all: where the article is written, polished, delivered on time, and completely off-topic.

Write a content brief for our writing team.

Content Type: [ARTICLE / LANDING PAGE / NEWSLETTER / etc.]
Topic: [MAIN SUBJECT]
Primary SEO Keyword: [KEYWORD]
Target Audience: [PERSONA]
Objective: [INFORM / CONVERT / ENGAGE]
Target Length: [WORD COUNT]

The brief must include:
1. Proposed title (3 variants)
2. Editorial angle (how this differs from existing content)
3. Detailed outline (H2 and H3)
4. Key messages to integrate (3-5)
5. Sources or data to include
6. Final call to action
7. Suggested internal linking (2-3 links)

The fourth is a manager’s template. The SBI method structures difficult conversations, and the 200-word constraint prevents you from burying the message under hedging—the reflex that leaves an employee leaving a review without understanding what they did wrong.

Help me formulate constructive feedback.

Recipient: [NAME, TITLE, REPORTING RELATIONSHIP]
Context: [SITUATION TRIGGERING THE FEEDBACK]
What Went Well: [POSITIVE POINTS]
What Needs Improvement: [AREAS TO IMPROVE]
Desired Outcome: [DESIRED BEHAVIOR / RESULT]

Constraints:
- Use the SBI method (Situation, Behavior, Impact)
- Benevolent but direct tone
- Propose concrete improvement actions
- End on a positive and motivating note
- Maximum 200 words

The fifth moves a project from intention to execution. It explicitly requests dependencies and risks, two sections systematically omitted when drafting a plan by hand, yet these are the only factors that explain, six months later, why a project slipped.

Create a detailed project plan.

Project: [NAME AND DESCRIPTION]
Objective: [FINAL DELIVERABLE]
Team: [SIZE AND SKILLS]
Budget: [BUDGET]
Deadline: [DEADLINE DATE]
Specific Constraints: [CONSTRAINTS]

The plan must include:
1. Phase breakdown with objectives per phase
2. Deliverables table (Deliverable | Phase | Owner | Date)
3. Critical task dependencies
4. Identified risks and mitigation plans
5. Key milestones for tracking
6. Resources required per phase

Organizing your library

A template you can’t find is worthless: it’s just a disposable prompt with an extra step. So, keep yours in a place you already open every day—a dedicated Notion document or Google Doc, a simple local text file sorted by category (communication, analysis, creation), or ChatGPT’s custom instructions for preferences you apply everywhere. Whatever the medium, the sorting criterion is frequency, not theme: your five most-used templates must be accessible in under thirty seconds, or you’ll keep improvising.

When a template becomes a ChatGPT tool

ChatGPT now offers several ways to go beyond copy-pasting. Project instructions apply the same framework to all conversations within a project. In ChatGPT Work, a file template links a reference document and reusable instructions to produce the same report or spreadsheet every week without re-explaining the format. On Business, Enterprise, Healthcare, and Edu plans, a skill goes further: it describes a workflow that ChatGPT can apply automatically when your request matches its description; indeed, Codex documentation now labels former “custom prompts” as deprecated in favor of skills. Custom GPTs, long used for this role, will be retired on December 11, 2026, and replaced by plugins.

For a recurring task, ChatGPT documentation advises first refining the prompt in a normal conversation, then, once the result is reliable, scheduling a task within that same conversation.

Three templates to build this week

Identify the three tasks you delegate to ChatGPT most often. For each, retrieve your best past prompt, replace specific information with [BRACKETED VARIABLES], add the constraints that matter to you—tone, format, length—then test the result with fresh data before saving the final version.

Three pitfalls await at this stage. If you have to modify the structure every time you use it, your template is too rigid: provide optional variables rather than freezing a specific case. Conversely, a template with twenty variables fills as slowly as a prompt written from scratch, and you’ll stop opening it; aim for a handful of variables instead. Finally, don’t validate a template without testing it multiple times with different data: formulations too dependent on the first case often reveal themselves on the third try.

Your turn

Turn your best prompt into a tool. Choose the prompt you reuse most. Replace its specific information with bracketed variables, test it on three different cases, then store it in the most suitable location: your personal library, project instructions, a file template in ChatGPT Work, a skill if your plan allows, or a scheduled task if it needs to run alone.

Official sources: Prompting (ChatGPT documentation) · Skills in ChatGPT · Projects in ChatGPT · Creating and editing documents, spreadsheets, and presentations with ChatGPT Work (OpenAI Help Center)

Key takeaways

• A template is a prompt with a fixed structure where only variables change
• Build it from a prompt that has already delivered excellent results, and test it on multiple cases
• Keep variables few: an overloaded template fills as slowly as a new prompt
• Store it where you’ll find it: library, project, file template in Work, or skill depending on your plan
• For a recurring task, refine the prompt in a conversation, then schedule it