Creating a weekly report in Microsoft 365 can consume hours if you start from scratch each time. You open Word, paste data from Outlook, Teams, and Excel, then format everything manually. Copilot can automate this process if you give it a well-structured prompt that works week after week. This article explains how to design a reusable prompt that pulls data from your calendar, email, and chats, and then generates a formatted report in one step.
The key is to write a prompt that includes placeholders for variables like the week date range, the project name, and the output format. Without these placeholders, Copilot will treat each request as a brand new task and may produce inconsistent results. A reusable prompt also saves you from typing the same instructions every Monday morning.
This guide covers the anatomy of a good prompt, the exact syntax to use, and how to store your prompt in a location Copilot can access repeatedly. You will also learn how to test and refine your prompt so it works across Word, Teams, and Outlook.
Key Takeaways: Building a Reusable Weekly Report Prompt
- Copilot prompt structure: Use a fixed instruction block plus variable placeholders like [WeekEnding] and [ProjectName] to make the prompt reusable.
- Data sources in Microsoft Graph: Reference specific locations such as “my email from last week” or “my calendar events” to ground Copilot in your tenant data.
- Storage in OneNote or SharePoint: Save the prompt as a page or document so you can copy-paste it each week without retyping.
What Makes a Prompt Reusable for Weekly Reports
A reusable prompt is a set of instructions that Copilot can interpret identically every time you use it. The challenge is that Copilot treats each conversation as a new session unless you provide clear, repeatable context. For weekly reports, the prompt must include three components:
Fixed instruction text. This part never changes. It tells Copilot what to do: summarize your week, list completed tasks, highlight blockers, and format the output as a table or bullet list. Write this exactly once.
Variable placeholders. These are tokens like [WeekEnding] or [TeamName] that you replace with the current value before sending the prompt. Copilot cannot infer the week range from context alone, so you must supply it. Use square brackets for placeholders so they stand out visually.
Data source references. Tell Copilot exactly where to look. Instead of saying “check my email,” say “find emails from [TeamName] sent between [StartDate] and [EndDate].” This grounds the response in your Microsoft 365 data. Copilot can read from Outlook, Teams, Calendar, and files stored in OneDrive or SharePoint.
Prerequisites: You need a Microsoft 365 Business Basic or higher license with Copilot enabled. The feature works in Word, Teams, and Outlook. Your organization must allow Copilot to access Microsoft Graph data. If your admin has restricted data sources, some placeholders may not work.
Steps to Create and Use a Reusable Weekly Report Prompt
- Open Copilot in Word and start a new blank document
This gives you a clean canvas to test the prompt. Do not use an existing document because leftover content can confuse Copilot. - Write the fixed instruction block
Type the following text as the core of your prompt: “Create a weekly report for the week ending [WeekEnding]. Include a summary of my top three accomplishments, a list of meetings attended, a list of emails related to [ProjectName], and a section for blockers. Format the output as a table with columns: Area, Details, Status. Use bullet points for the blocker list.” Keep this block exactly the same every week. - Insert variable placeholders for the current week
Replace [WeekEnding] with the Friday date of the current week, for example “October 27, 2025.” Replace [ProjectName] with the actual project name, such as “Project Phoenix.” Copilot uses these values to filter data. - Add data source instructions
Below the fixed block, add: “Base the accomplishments on my calendar events and emails from this week. Base the meeting list on my Outlook calendar between [StartDate] and [EndDate]. Base the blocker list on my Teams chats with [TeamName].” Replace [StartDate] and [EndDate] with Monday and Friday of the current week. - Send the prompt to Copilot
Click the Copilot icon in Word and paste the full prompt into the compose box. Press Enter. Copilot will process the request and generate the report. Review the output for accuracy. If the data is incomplete, refine the data source references in step 4. - Save the prompt template in OneNote
Open OneNote and create a new page named “Weekly Report Prompt Template.” Paste the full prompt with placeholders. Save the page. Next week, open this page, replace the placeholders with the new dates, copy the text, and paste it into Copilot. This eliminates retyping.
You can also save the prompt as a text file in SharePoint or as a Quick Part in Word. The key is to store it in a location you can open from any device. OneNote works best because it syncs across desktop, web, and mobile.
Common Mistakes and How to Avoid Them
Copilot returns generic text instead of your actual data
This happens when the data source references are too vague. Instead of saying “check my email,” specify the sender, subject keywords, or date range. Example: “Find emails from [ManagerName] sent between [StartDate] and [EndDate] that contain the word ‘approval.'”
The prompt works once but fails the next week
You likely forgot to update the date placeholders. Always replace [WeekEnding], [StartDate], and [EndDate] before sending. If you use a template in OneNote, set a weekly reminder to update the placeholders every Monday morning.
Copilot ignores the output format instruction
Copilot may produce a narrative paragraph instead of a table. Add the format instruction at the end of the prompt and repeat it: “Output the report as a table with columns Area, Details, and Status. Do not use paragraphs.” If it still fails, try saying “Create a table with three columns” in the first sentence.
The prompt is too long and Copilot truncates it
Copilot in Word has a character limit of approximately 4000 characters per prompt. Keep your fixed instruction block under 2000 characters. Use short sentences and avoid examples. If you need more detail, split the prompt into two parts: first ask Copilot to gather data, then ask it to format the report.
| Item | Static Prompt | Reusable Prompt |
|---|---|---|
| Description | Written from scratch each week with different wording | Uses a fixed template with variable placeholders |
| Time to prepare | 5-10 minutes per week | 1 minute to update placeholders |
| Consistency | Output format varies each time | Same structure and data sources every week |
| Storage method | No storage, typed each time | Saved in OneNote or SharePoint |
| Data source reliability | Inconsistent because instructions change | Fixed references produce reliable results |
After you build your reusable prompt, test it with two consecutive weeks of data. Adjust the data source references if Copilot misses emails or calendar events. Once the prompt works consistently, share the OneNote page with your team so everyone uses the same template. For advanced users, add an instruction to insert the report into a SharePoint document library automatically using Power Automate. This saves even more time and ensures the reports are stored in a central location.