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

# Weekly client reports from real work

> Build a client-ready weekly consulting report with active time, deliverables, decisions, risks, and next steps from a bounded Screenpipe work history.

This workflow is for consultants, agencies, and fractional operators whose work is spread across calls, documents, code, email, and research. The output is a client-ready draft, not an automatic status message.

```mermaid theme={"system"}
flowchart TD
    A["bounded week"] --> B["active time and project evidence"]
    B --> C["draft outcomes, decisions, and risks"]
    C --> D["consultant review"]
    D --> E["client update"]
```

## Step by step

For reports organized around support tickets, use [remote-support job logs and billing reports](/remote-support-job-reports), including HTML and CSV export prompts and a fictional billing-review example.

<Steps>
  <Step title="Agree on the format">
    Decide whether the client wants hours, outcomes, deliverables, decisions, risks, next steps, or some combination. Agree on the reporting week and the detail that must stay private.
  </Step>

  <Step title="Check capture coverage">
    Review the week in the timeline. Note missing days, unrecorded calls, travel, and work performed on another device so the report does not imply complete coverage.
  </Step>

  <Step title="Collect authoritative time">
    Run `/activity-summary` for the exact reporting window. Use its active-time totals; use AI only to suggest project labels. Keep ambiguous blocks unassigned.
  </Step>

  <Step title="Find concrete outcomes">
    Search the same window for the project code, client name, document titles, pull requests, meetings, and delivery terms. Prefer completed artifacts and accepted decisions over app usage alone.
  </Step>

  <Step title="Separate progress from activity">
    “Opened the proposal” is activity. “Delivered proposal v2” is an outcome only when the source supports delivery. Mark proposals, tentative dates, and inferred next steps clearly.
  </Step>

  <Step title="Review with private context removed">
    Check time totals, names, links, commitments, and deadlines. Remove unrelated clients, personal messages, internal pricing, and raw transcript text.
  </Step>

  <Step title="Send from the normal channel">
    Copy the approved version into email, Slack, or the client's portal. Keep sending separate from generation until several reports are consistently accurate.
  </Step>
</Steps>

## Create the reusable scheduled task

Under **Scheduled tasks → My tasks → NEW**, paste:

```text theme={"system"}
Create a manual scheduled task that writes a weekly client report to a local Markdown file.
Use /activity-summary for numeric time totals and bounded /search results for context.
Include outcomes, deliverables, accepted decisions, risks, next steps, capture gaps,
and needs-review items. Separate observed facts from inferred project labels.
Exclude unrelated clients and personal activity. Never send the report or update
the client's systems.
```

Run the generated scheduled task manually for one week, inspect the artifact and execution log, then correct its project terms before adding a schedule.

## Report prompt

```markdown theme={"system"}
Create a client-ready weekly update from the supplied bounded screenpipe data.

Output:
1. executive summary
2. verified outcomes and deliverables
3. active time by day or workstream from activity-summary
4. accepted decisions
5. risks, blockers, and questions
6. next steps with owner and date only when supported
7. capture gaps and needs-review items

Do not convert screen activity into a claim of completion.
Do not include unrelated-client or personal content.
Return a draft only; do not send it.
```

<Tip>
  Use [consultant time tracking](/consultant-time-tracking) when time is the primary output. Use this workflow when the client cares more about outcomes and next steps.
</Tip>


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