Build a client progress report from your project tools

Context, setup, and planning

1. Identify the client, reporting period, cadence, audience, and decision the report should support.
2. Offer to learn the reporting process from the user, inspect an approved prior report, or combine both. A prior report can reveal the expected format, depth, tone, field definitions, and destination without making the user repeat them.
3. Learn which approved sources are useful. Project tools, analytics and advertising accounts, CRM records, shared documents, meeting notes, and email can help when available, but they are not prerequisites.
4. Keep every client's accounts, calculations, evidence, and output strictly separated.
5. For a new reporting process, build one client's report first so the user can correct it before applying the process across the book.
6. Present a concise plan before gathering substantial data. Confirm the sources, comparisons, and output shape, such as a document, deck, dashboard, email summary, or another format the user already prefers.

Reconcile the evidence

1. Pull independent sources in parallel when that saves time, with a clear and separate task for each source so work does not overlap.
2. Align date ranges, currencies, attribution windows, and metric definitions before comparing sources or periods.
3. Preserve source links and state where each important figure came from.
4. Flag missing, delayed, or conflicting data rather than forcing the numbers to reconcile.
5. Compare performance only where the underlying definitions are compatible.
6. Use plain client language. Lead with what changed, why it matters, and what should happen next rather than presenting a metric dump.

Draft the report

Include only sections useful for this client:

• concise executive summary;
• progress against goals and KPIs;
• completed work and important changes;
• performance with relevant comparisons;
• risks, blockers, or decisions needed;
• recommendations and clearly owned next actions;
• source notes and unresolved data issues.

Keep recommendations distinguishable from observed results. Match the accepted client voice and presentation style without inventing a conclusion the evidence does not support. Draft the highlights and useful options, but leave the strategic decision to the user.

Scale carefully

1. Let the user review the first report before producing other client reports.
2. Run the accepted process separately against each client's own connected accounts. Reports may be prepared in parallel only while maintaining strict client and account separation.
3. Match cadence and depth to the work. Useful examples include a weekly snapshot for active paid media, a fuller monthly report for a retainer, or a quarterly strategic report for SEO and content.
4. A cross-client roll-up may highlight overspend, sudden drops, or accounts needing attention, but use it only when the user has permission to compare those accounts.
5. After the report has worked several times, offer to save one reporting skill per client. Preserve its accepted sources, definitions, output format, destination, review behavior, and per-client boundaries. When useful, prepare it on the agreed Routine.
6. Never send the report or update client systems without approval.

Suggested outcome

Produce a clean client report in the accepted format. Keep sources, definitions, and uncertainty visible, and explain what changed, why it matters, and which decisions or actions follow.