> ## 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.

# daily work review

> Turn a day of screen and meeting activity into a private recap, standup draft, or open-loops list.

{/* https://screenpi.pe */}

a daily review helps when work is spread across terminals, documents, browsers, calls, and messages. screenpipe reconstructs the day; you decide what it means and what is safe to share.

## choose the output

| output          | useful when                           | keep private by default                          |
| --------------- | ------------------------------------- | ------------------------------------------------ |
| personal recap  | remembering progress and context      | detailed app, document, and conversation history |
| standup draft   | reporting work to a team              | unrelated projects and personal activity         |
| open-loops list | planning tomorrow                     | guesses about commitments or owners              |
| weekly review   | spotting patterns across several days | raw screen or transcript excerpts                |

## step by step

<Steps>
  <Step title="check the day">
    Open the timeline and confirm the expected work periods were captured. gaps should appear as gaps in the report.
  </Step>

  <Step title="run a manual pipe">
    Use **Day Recap** on Home. use **Time Breakdown** when you need an app and project view, or **Missed To-Dos** when you need open loops. review the result before turning it into a recurring pipe.
  </Step>

  <Step title="ask for observed work and open loops">
    Include completed work, decisions, blockers, unfinished tasks, and likely next actions. require the result to distinguish direct evidence from inference.
  </Step>

  <Step title="edit the draft">
    Remove private details, correct project names, and delete activity that is not relevant to the audience.
  </Step>

  <Step title="save or share deliberately">
    Keep a personal recap in a local file, or copy the shorter standup into your team's tool. a generated draft should not post itself on the first run.
  </Step>
</Steps>

## current Home shortcuts

<CardGroup cols={2}>
  <Card title="Day Recap" icon="calendar-days">
    accomplishments, key moments, and unfinished work
  </Card>

  <Card title="Time Breakdown" icon="clock">
    app, category, and project breakdown for a bounded day
  </Card>

  <Card title="Missed To-Dos" icon="list-check">
    likely unresolved commitments from recent work
  </Card>

  <Card title="Automate My Work" icon="bolt">
    one repeated workflow and a testable automation candidate
  </Card>
</CardGroup>

## prompt for a private recap

```markdown theme={null}
Review today's bounded screenpipe data.

Create:
1. completed work, grouped by project
2. meetings, decisions, and commitments
3. blockers and unresolved questions
4. open loops with the source time range
5. suggested priorities for tomorrow

Rules:
- report capture gaps as gaps
- do not infer completion from merely viewing a task
- mark suggested priorities as suggestions
- avoid quoting private messages unless necessary
```

## prompt for a standup draft

```markdown theme={null}
Turn today's verified recap into a standup under 150 words:
- completed
- next
- blockers

Include only work appropriate for my team channel.
Do not include personal activity, unrelated clients, or uncertain commitments.
Return a draft for review; do not send it.
```

## schedule it later

after several accurate runs, schedule the pipe near the end of your workday. save the full result locally and keep external posting as a separate, reviewed step.

<Tip>
  if the report needs billable totals, use [consultant time tracking](/consultant-time-tracking). if it should become long-term AI context, use [local agent memory](/agent-memory-workflow).
</Tip>