weekly client reports from real work

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.

step by step

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.

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.

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.

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.

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.

review with private context removed

Check time totals, names, links, commitments, and deadlines. remove unrelated clients, personal messages, internal pricing, and raw transcript text.

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.

create the reusable pipe

under Pipes → My Pipes → create your own pipe, paste:

Create a manual pipe 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 pipe manually for one week, inspect the artifact and execution log, then correct its project terms before adding a schedule.

report prompt

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.

use consultant time tracking when time is the primary output. use this workflow when the client cares more about outcomes and next steps.

get started

pipes

connect

use cases

integrations

reference

deployment

compare

resources

weekly client reports from real work

step by step

create the reusable pipe

report prompt

​step by step

​create the reusable pipe

​report prompt

step by step

create the reusable pipe

report prompt