Prompt Guidance
How to Schedule Weekly Project Reports with Ottermind
If you summarize similar materials every week, first complete one useful report, then schedule the stable workflow. In Ottermind, specify when to run, which sources to read, what to produce, and how to handle missing information. This tutorial uses a project progress report to explain the transition from a one-off task to recurring work.
Define the recurring task
A weekly report needs a time and time zone, source scope, report structure, and exception handling. Check both the saved schedule and the first output.
1. Complete one report manually
Prepare a project tracker and ask Ottermind to summarize completed, ongoing, overdue, and upcoming work. Confirm that the result suits the team before making it recurring. Resolve unclear sources or output expectations first.
2. Specify the schedule
Every Friday at 4 p.m. Beijing time, read the confirmed latest tracker in this project. Summarize work completed this week, overdue items, and tasks due next week. Flag risks with supporting evidence. Save a project report for my review. If information is missing or inaccessible, explain what is missing; do not present old data as this week's results.Name the time zone explicitly and define the file scope. Read the latest material is ambiguous without a project or source boundary.
3. Confirm the task exists
Inspect the task name, time, recurrence, and enabled status in the task list. Describing a schedule in chat does not by itself confirm that creation succeeded.
If external files are required, complete the appropriate connection and check its scope. Start by saving drafts; consider delivery actions after report quality is established.
4. Inspect the first run
Check execution time, source version, and report completeness. Compare dates, owners, and status changes with the tracker. For gaps, check whether files exist, permissions work, and data has been updated before changing instructions.
5. Adjust or stop recurring work
Review several runs to identify useful sections and repeated corrections. Refine length, risk categories, or repetitive wording. Pause or remove tasks when the project ends. Recurrence is useful only while the sources and instructions remain relevant.
Product reference: Schedule a weekly project report
