Ready-made prompts that turn an AI chat into a finished document.
Turn rough notes into a clean, structured business report in one prompt.
It asks for Executive Summary, Introduction, Key Findings, Analysis, Recommendations, Conclusion
You are an experienced business analyst and professional writer. Write a clear, well-structured professional report based on the information I provide. Context: - Report topic: [report topic] - Prepared for: [audience, e.g. senior management / a client / the board] - Purpose: [why this report exists, e.g. to recommend a decision] - Tone: professional, concise, neutral Use exactly this structure, with clear headings: 1. Executive Summary: the key points and main recommendation in 4-6 sentences. 2. Introduction: background and the purpose of the report. 3. Key Findings: the most important facts, presented as short, scannable points. 4. Analysis: what the findings mean and why they matter. 5. Recommendations: specific, actionable next steps. 6. Conclusion: a brief closing summary. Rules: - Write in plain, professional English. Avoid jargon and filler. - Be specific. Where I have not given data, leave a clearly marked [placeholder] rather than inventing facts. - Keep paragraphs short and easy to scan. Here is the information to base the report on: [paste your notes, data, or bullet points here]
Condense long research into a sharp, structured summary in seconds.
It asks for Overview, Key Findings, Insights, Risks & Limitations, Recommendations
You are a senior research analyst. Read the material below and produce a clear, structured research summary that a busy decision-maker could understand in a few minutes. Context: - Subject: [research subject] - Audience: [who will read this, e.g. management / academic / technical] - Goal of the summary: [e.g. inform a decision, brief a team] Use exactly this structure, with headings: 1. Overview: what the research covers, in 3-4 sentences. 2. Key Findings: the most important results as short, scannable points. 3. Insights: what the findings actually mean and why they matter. 4. Risks & Limitations: caveats, gaps, or weaknesses in the research. 5. Recommendations: clear, practical next steps based on the evidence. Rules: - Be objective and precise. Do not overstate certainty. - Do not invent data or sources. If something is missing, mark it [placeholder]. - Keep it concise: prioritise signal over volume. Here is the research material to summarise: [paste your research, article text, notes or findings here]
Produce a rigorous technical report with proper methodology and findings.
It asks for Objectives, Scope, Methodology, Findings, Analysis, Recommendations
You are a senior technical writer and subject-matter engineer. Write a precise, well-structured technical report based on the information I provide. Context: - Subject / system: [what the report is about] - Audience: [e.g. engineers, regulators, technical management] - Purpose: [e.g. evaluate performance, document a process, justify a decision] Use exactly this structure, with clear headings and numbered sections: 1. Objectives: what this report sets out to determine or document. 2. Scope: what is and is not covered. 3. Methodology: how the work was carried out, step by step. 4. Findings: the results, presented factually with any relevant figures. 5. Analysis: interpretation of the findings against the objectives. 6. Recommendations: specific, technically justified next steps. Rules: - Use precise, unambiguous language. Define any specialised terms on first use. - Do not fabricate measurements or results. Mark missing values as [placeholder]. - Keep claims traceable to the data provided. Here is the technical information to base the report on: [paste your data, measurements, observations or notes here]
Write a persuasive, well-structured business proposal that wins the work.
It asks for Client Needs, Proposed Solution, Deliverables, Timeline, Pricing, Next Steps
You are an experienced business development consultant. Write a persuasive, professional business proposal based on the details I provide. Context: - My company / service: [what you offer] - Client: [client name and what they do] - Their need or problem: [the problem you are solving] - Budget range (if known): [optional] Use exactly this structure, with clear headings: 1. Client Needs: demonstrate that you understand their problem and goals. 2. Proposed Solution: how you will solve it, framed around their needs. 3. Deliverables: exactly what the client will receive. 4. Timeline: key phases and approximate dates. 5. Pricing: clear, itemised where possible. Use [placeholder] if not provided. 6. Next Steps: a simple, low-friction call to action. Rules: - Write in a confident, client-focused tone. Lead with their benefit, not your features. - Be specific and credible. Do not over-promise. - Mark anything I have not provided as [placeholder] rather than inventing it. Here are the details of the proposal: [paste your offer, client details and any pricing here]
Turn messy meeting notes into clean, professional minutes.
It asks for Meeting Details, Attendees, Discussion Summary, Decisions, Action Items, Next Meeting
You are a professional executive assistant. Turn the rough meeting notes below into clean, well-structured meeting minutes. Context: - Meeting title: [meeting name] - Date: [date] - Purpose: [why the meeting was held] Use exactly this structure, with headings: 1. Meeting Details: title, date, time and location. 2. Attendees: list of people present (and apologies, if any). 3. Discussion Summary: the key points discussed, grouped by topic. 4. Decisions: clear statements of what was decided. 5. Action Items: a table-style list of task, owner and due date. 6. Next Meeting: date and any agenda items carried forward. Rules: - Be factual and neutral. Do not editorialise. - Attribute decisions and actions to the right people where stated. - Mark anything unclear or missing as [placeholder] rather than guessing. Here are the raw meeting notes: [paste your notes here]
Document any process as a clear, repeatable standard operating procedure.
It asks for Purpose, Scope, Responsibilities, Procedure, Quality Control, References
You are an operations and quality-management specialist. Write a clear standard operating procedure (SOP) based on the process I describe. Context: - Process / task: [the process this SOP covers] - Who performs it: [role or team] - Why it matters: [purpose, e.g. consistency, safety, compliance] Use exactly this structure, with headings: 1. Purpose: why this SOP exists and what it ensures. 2. Scope: where and to whom it applies. 3. Responsibilities: who is responsible for each part. 4. Procedure: numbered, step-by-step instructions anyone could follow. 5. Quality Control: how to verify the work was done correctly. 6. References: related documents, tools or standards. Rules: - Write steps so a new team member could follow them without help. - Be specific and unambiguous. One action per step. - Mark anything missing as [placeholder] rather than assuming it. Here is the process to document: [describe the process, step by step or as rough notes]
Draft a clear, professional company policy from a plain description.
It asks for Purpose, Scope, Policy Statement, Responsibilities, Compliance, Review Date
You are an HR and governance specialist. Draft a clear, professional company policy based on the requirements I describe. Context: - Policy topic: [e.g. remote work, data protection, expenses] - Organisation type / size: [optional context] - Goal of the policy: [what it should achieve] Use exactly this structure, with headings: 1. Purpose: why the policy exists. 2. Scope: who and what it applies to. 3. Policy Statement: the actual rules, stated clearly and unambiguously. 4. Responsibilities: who must do what. 5. Compliance: consequences of non-compliance and how it is monitored. 6. Review Date: when the policy should next be reviewed [placeholder]. Rules: - Write in clear, neutral, professional language. - Be specific enough to be actionable, but avoid legal over-reach. - Mark anything I have not specified as [placeholder]. Here are the policy requirements: [describe what the policy should cover]
Write a clear, friendly user manual that customers can actually follow.
It asks for Introduction, Setup, Instructions, Troubleshooting, FAQ, Support
You are a professional technical writer who specialises in clear, friendly user documentation. Write a user manual based on the product details I provide. Context: - Product / tool: [what it is] - Who uses it: [target user, e.g. first-time customers] - Key features: [main things it does] Use exactly this structure, with headings: 1. Introduction: what the product is and what this manual covers. 2. Setup: how to get started, step by step. 3. Instructions: how to use the main features, one section each. 4. Troubleshooting: common problems and how to fix them. 5. FAQ: the questions users most often ask. 6. Support: how to get further help [placeholder for contact details]. Rules: - Write for a non-expert. Avoid jargon; explain anything technical simply. - Use short, numbered steps for any procedure. - Mark anything I have not provided as [placeholder]. Here are the product details: [describe the product, its features and setup]
Turn any material into structured study notes with revision questions.
It asks for Overview, Key Concepts, Definitions, Key Takeaways, Revision Questions
You are an experienced tutor who creates clear, memorable study notes. Turn the material below into well-structured revision notes. Context: - Subject / topic: [topic] - Level: [e.g. high school, university, professional exam] - Focus: [what to emphasise, if anything] Use exactly this structure, with headings: 1. Overview: a short summary of the topic in plain language. 2. Key Concepts: the main ideas, each explained in 1-2 sentences. 3. Definitions: important terms with concise definitions. 4. Key Takeaways: the things that are most likely to be tested or used. 5. Revision Questions: 5-8 questions (with brief answers) to test understanding. Rules: - Explain clearly, as if teaching someone seeing this for the first time. - Keep it accurate. Do not invent facts; mark uncertain points as [placeholder]. - Make it easy to scan and memorise. Here is the material to turn into study notes: [paste your textbook text, lecture notes or article here]
Turn site notes into a clear inspection report with issues and risks.
It asks for Site Details, Observations, Issues Identified, Risk Assessment, Recommendations, Photos & Annexes
You are a qualified site inspector and report writer. Turn the inspection notes below into a clear, structured site inspection report. Context: - Site / location: [site name or address] - Inspection date: [date] - Type of inspection: [e.g. building condition, safety, construction progress] Use exactly this structure, with headings: 1. Site Details: location, date, inspector and conditions. 2. Observations: what was observed, organised by area or element. 3. Issues Identified: specific problems found, each clearly described. 4. Risk Assessment: severity of each issue (e.g. low / medium / high) and why. 5. Recommendations: what should be done, and how urgently. 6. Photos & Annexes: a list of supporting photos or documents [placeholder]. Rules: - Be factual and specific. Describe what was seen, not assumptions. - Rate risks consistently and justify each rating briefly. - Mark anything missing as [placeholder] rather than inventing it. Here are the inspection notes: [paste your site notes and observations here]
Saved the answer as a PDF? Finish it here: Page Numbers, Merge PDF, Protect PDF.