Copilot in Word

Create a business proposal template for [TYPE — consulting / project / partnership / grant]. Include: (1) Cover page, (2) Executive summary, (3) Problem statement, (4) Proposed solution, (5) Methodology and approach, (6) Timeline and deliverables, (7) Team and qualifications, (8) Pricing, (9) Terms and conditions, (10) Appendices. Format with proper headings and professional styling.

Convert these notes into an FAQ document with clear questions and concise answers. Group related questions under headings. Start with the most commonly asked questions. Include 10-15 Q&A pairs. Each answer should be 2-3 sentences maximum.

Draft a standard operating procedure (SOP) for [PROCESS NAME] based on these notes. Include: (1) Purpose and scope, (2) Prerequisites, (3) Step-by-step procedure with numbered steps, (4) Common exceptions and how to handle them, (5) Who to contact for help. Use clear, non-technical language. Format with headings and bullet points.

Summarise this document into an executive summary for [AUDIENCE — leadership / board / client]. Include: (1) The headline finding or recommendation (one sentence), (2) 3-5 key takeaways as bullet points, (3) Recommended next steps. Keep the entire summary under 200 words. Prioritise decisions over details.

Write formal meeting minutes for [MEETING NAME] held on [DATE]. Include: (1) Meeting details (date, time, location, attendees, apologies), (2) Agenda items discussed with summary, (3) Motions or decisions with voting results if applicable, (4) Action items with owners and deadlines, (5) Next meeting date, (6) Approval section. Format as an official record.

Make this document more concise and direct. Cut unnecessary words, merge redundant sections, and remove filler phrases. Keep all essential information and key points. Target a [PERCENTAGE — 30% / 50%] reduction in word count. Use active voice throughout.

Rewrite this policy document in plain English: [PASTE OR DESCRIBE POLICY]. Keep all requirements and obligations exactly the same but: (1) Replace jargon with simple words, (2) Break long sentences into shorter ones, (3) Use bullet points instead of dense paragraphs, (4) Add headings for each major section, (5) Include a quick reference summary at the top. Target: readable by someone with no specialist knowledge.

Draft a formal business letter from [SENDER] to [RECIPIENT] regarding [PURPOSE]. Include proper formatting, clear purpose, supporting details, call to action.

Design the structure for a [REPORT TYPE — annual / quarterly / research / audit / project completion] report about [TOPIC]. Include: (1) Recommended sections with headings, (2) What to include in each section, (3) Target length per section, (4) Charts or visuals to include, (5) Appendices needed. Optimise the flow so the most important findings are early in the document.

Review this document and suggest improvements to clarity, tone, and structure. Focus on: (1) Sentences that are too long or confusing, (2) Passive voice that should be active, (3) Sections that could be reordered for better flow, (4) Missing information the reader would expect. Present your suggestions as specific edits, not general advice.

Rewrite this section in plain English for [AUDIENCE — non-technical staff / customers / new hires]. Remove jargon and acronyms (or explain them on first use). Keep the meaning exactly the same but make it easy to understand on first read. Aim for an 8th-grade reading level.

Create a handover document for my role as [ROLE]. Include: key responsibilities, important contacts, active projects, pending decisions, file locations, tips and gotchas.