> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Compare your weekly plans with recorded work

> Run a weekly work review that compares your planned outcomes with recorded screen activity to spot progress, blockers, and what to change next week.

Use a weekly review to compare your intended outcomes with observable work and decide what to change. Screen activity is partial evidence, not a complete measure of effort or productivity.

## Start here

Provide your three planned outcomes, the workweek dates and timezone, and known offline work. Use activity summaries for available active-time totals and source records for context.

## Copy this prompt

Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.

```text theme={"system"}
Review [week, timezone] against these planned outcomes: [list].
For each, report observed progress, evidence, blockers, and the next action.
Use activity-summary data for available active-time totals; never count
frames or search results as hours. Separate active time from elapsed spans.
Include offline work I supply and explicitly state coverage gaps.
Suggest one change to next week. Do not score my productivity.
```

## Check the result

Compare the draft with your calendar and completed artifacts. Correct project labels and add work the computer could not see. Keep one actionable change rather than a long list of judgments.

> [accordion] See a worked example
>
> | Planned outcome | Observed result | Next decision |
> | - | - | - |
> | Finish demo report | Draft exists; review still open. | Book a review block. |
> | Resolve recurring support issue | Two investigations, no verified fix. | Narrow reproduction. |
> | Prepare customer meeting | Brief and source links checked. | Keep this workflow. |

> [accordion] Go deeper: setup choices and edge cases
>
> A long open window can include idle time, interruptions, or unrelated work. Short activity can still produce an important decision. Treat time estimates as descriptive and reviewable.
>
> If the report helps for two weeks, consider scheduling a draft with a bounded date range and stable output location. Include a no-data outcome so an unavailable device does not produce a fictional weekly narrative.

## Continue

[Daily work review](https://docs.screenpipe.com/daily-work-review.md) · [reliable reports](https://docs.screenpipe.com/reliable-reports.md) · [consultant time tracking](https://docs.screenpipe.com/consultant-time-tracking.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.