A Weekly Client-Delivery Dashboard for Solo Consultants

A solo consultant rarely needs another elaborate project-management system. What the business does need is one reliable view of what has been promised, what is due next, what is blocked, and where a client decision is required.

A weekly client-delivery dashboard is that view. It is not a presentation full of charts and it is not a duplicate task database. It is a short operating record that helps you decide where to focus, what to communicate, and which commitment needs protection before it becomes late.

Testing status. This is a platform-neutral editorial framework. Practical Solo Ops has not tested every project-management product, client portal, spreadsheet, or professional-services workflow. The example below uses synthetic engagements and does not represent real clients, results, or revenue.

Source status, reviewed August 25, 2026. The U.S. Government Accountability Office Schedule Assessment Guide is written for large government programs, not one-person consultancies. Its principles about complete schedules, meaningful milestones, dependencies, status updates, and schedule risk are adapted here at a much smaller scale. NIST’s definition of a risk register is used as a reference point for maintaining risk information over time, not as a compliance requirement for solo businesses.

Decide what the dashboard must help you decide

Start with decisions, not fields.

At the end of a weekly review, the dashboard should let you answer:

Which client commitment needs action first?
Which delivery date is exposed to a dependency or unresolved decision?
What changed since the prior review?
What must the client know now rather than at the next meeting?
What work should not be started because a higher-risk item needs capacity?

The GAO Schedule Assessment Guide describes a reliable schedule as a management tool that specifies when work will occur, measures performance against an approved plan, and shows how change affects the program. It also distinguishes meaningful milestones from ordinary activities and says milestones should have clear completion conditions.

Editorial analysis. A solo consultant does not need the guide’s full scheduling discipline. The useful translation is simple: a due date without a defined deliverable, dependency, and completion condition is not a dependable commitment.

If a field does not change a decision or support a client conversation, leave it out.

Use one row per active engagement

The smallest useful dashboard has one row per active engagement, not one row per task.

Use these nine fields:

Field	Question it answers	Example value
Client / engagement	What body of work is this?	Northwind onboarding review
Next deliverable	What concrete output is next?	Findings memo v1
Completion condition	What makes it done?	Reviewed, source links present, PDF delivered
Committed date	What date did we actually agree to?	Sep 4
Next action	What is the next visible move?	Resolve three evidence gaps
Dependency / decision	What must happen outside the action?	Client confirms access scope
Risk state	Is the commitment protected?	Watch
Last meaningful change	What changed since review?	Data export arrived two days late
Communication due	Who needs an update, and when?	Client sponsor by Tuesday

The example values are illustrative. They are not a recommendation to store client names or sensitive project information in an unapproved tool. Use engagement codes or a business-controlled system when confidentiality requires it.

Keep the task list elsewhere

A dashboard is a control surface. The task list is the execution system.

Link to the authoritative task record instead of copying every action into the dashboard. If the dashboard becomes another place where tasks must be reconciled, it will create the very uncertainty it is meant to reduce.

Use this rule:

The dashboard holds the next commitment, the next action, the current risk, and the communication decision. The task system holds the detailed work.

Define delivery states without false precision

Avoid percentages such as “80% complete” unless the work is genuinely measurable. Knowledge work can appear nearly finished while one missing approval or evidence gap controls the delivery date.

Use four states instead:

State	Meaning	Required response
Protected	Next deliverable and date remain credible	Continue; no special escalation
Watch	A known condition could consume available buffer	Assign a mitigation and review date
Decision needed	Progress depends on a named choice or input	Ask the decision owner with a deadline
Replan	Current scope, date, or method is no longer credible	Present the change and obtain agreement

These states describe management action, not sentiment. “Green, yellow, red” can work, but colors alone are inaccessible and often conceal the response required.

Editorial analysis. A useful state should tell you what to do next. “Watch” without a mitigation is only anxiety recorded in a cell.

Treat milestones as evidence, not labels

The GAO guide describes milestones as zero-duration points that represent major events or accomplishments and emphasizes clear completion conditions. It also warns that too many milestones reduce their usefulness.

For solo client work, a milestone should represent a handoff, approval, or irreversible transition such as:

discovery inputs accepted;
scope baseline approved;
draft released for review;
client decision received;
production change authorized;
final deliverable accepted;
records and access closed.

“Work on report” is an activity. “Evidence-reviewed draft delivered” can be a milestone.

For every milestone, record:

the target date;
the completion condition;
the person who can confirm completion;
the upstream dependency;
the downstream commitment affected by delay.

This prevents a calendar event from being mistaken for evidence of progress.

Add a decision queue

Solo professionals often lose time not because the work is unclear, but because decisions are scattered across email, meetings, chat, and notes.

Keep a short decision queue beneath the engagement table:

Decision	Owner	Needed by	Default if unanswered	Impact
Approve interview list	Client lead	Tuesday noon	Move two interviews to phase two	Draft coverage changes
Choose launch window	Client sponsor	Thursday	Hold current manual process	Automation release moves

The default is not a threat or a hidden assumption. It is the safest documented response if the decision does not arrive. Confirm it with the client when it changes scope, timing, cost, or responsibility.

Do not record a decision as “pending.” Record the question, owner, deadline, and consequence.

Keep a compact risk and issue watchlist

NIST defines a risk register as a central record of risk information over time. A delivery dashboard needs only a small subset of that idea.

For each material risk, record:

the event or condition;
which commitment it threatens;
the earliest warning signal;
the mitigation action;
the fallback if it occurs;
the next review date.

Separate risks from issues:

A risk may happen: “The client export may arrive too late for validation.”
An issue has happened: “The export arrived without timestamps.”

An issue needs an owner and resolution path. A risk needs a trigger and mitigation.

Use the automation risk ladder when a delivery depends on a workflow that can send, publish, update, delete, or bill without review. Use the change log and rollback plan when the mitigation changes a live automation.

Run the weekly review in 20 minutes

The dashboard becomes useful through a repeatable review, not through perfect formatting.

Minute 0–4: reconcile reality

Remove completed engagements from the active view.
Confirm the next deliverable and committed date.
Update only facts that changed.
Link new evidence or decisions to the authoritative record.

Minute 4–10: scan exposure

Find every Watch, Decision needed, and Replan state.
Check whether a dependency has an owner and due date.
Identify dates with no remaining buffer.
Check whether two engagements compete for the same block of time.

Minute 10–15: choose interventions

Select the one mitigation that protects the most important commitment.
Draft decision requests that must leave today.
Move or decline lower-priority work when capacity is not credible.
Add a manual fallback when an automation is unstable.

Minute 15–20: close communication loops

Send updates that prevent surprises.
Record changed scope, date, or acceptance criteria.
Put the next dashboard review on the calendar.
Move the selected actions into the weekly operating system.

If the review regularly exceeds 20 minutes, the dashboard probably contains task detail, old engagements, or commentary that belongs elsewhere.

Use a capacity check that reflects solo work

Do not compare committed hours with every hour in the week. Client calls, administration, business development, corrections, and unexpected work consume real capacity.

Use this editorial planning formula:

Protected delivery capacity
= realistic working capacity
− fixed meetings and administration
− named risk buffer
− business-maintenance commitment

Then compare the protected capacity with the remaining effort for commitments due during the horizon.

This is not a productivity statistic. It is a planning assumption. Record the assumption and adjust it using your own completed-work evidence.

Example

A synthetic consultant has 30 realistic work hours next week, 7 hours of fixed meetings and administration, a 5-hour risk buffer, and 4 hours reserved for invoicing and pipeline follow-up.

30 − 7 − 5 − 4 = 14 protected delivery hours

If two client commitments require an estimated 18 hours, the dashboard should show a replan now. It should not hide the gap behind optimistic status labels.

Create a communication trigger for every risk state

Use a simple rule:

Protected: communicate on the agreed cadence.
Watch: communicate when the client can still help reduce exposure.
Decision needed: send one answerable question with a decision date and impact.
Replan: communicate the changed evidence, options, recommendation, and requested agreement.

Do not wait for certainty before communicating a material risk. Do not create alarm without an action either.

A useful risk update contains:

what changed;
what commitment may be affected;
what you are doing;
what you need from the client;
when the next update will arrive.

The human-review checklist is the release gate when AI assists with a client-facing status update or deliverable.

Protect client information in the dashboard

The dashboard should reveal the minimum information needed to operate the engagement.

Do not add:

passwords, tokens, recovery codes, or private keys;
full client datasets or sensitive excerpts;
confidential findings when a link to the approved record is enough;
personal information that is not necessary for the decision;
unreviewed AI summaries presented as client facts.

Record where authorized evidence lives rather than duplicating it. Apply the client-data safety checklist before placing the dashboard in an AI-enabled or third-party service.

Copyable weekly dashboard worksheet

WEEK OF:
REVIEWED BY:

ACTIVE ENGAGEMENTS

1. CLIENT / ENGAGEMENT CODE:
   NEXT DELIVERABLE:
   COMPLETION CONDITION:
   COMMITTED DATE:
   NEXT ACTION:
   DEPENDENCY OR DECISION:
   STATE: Protected / Watch / Decision needed / Replan
   LAST MEANINGFUL CHANGE:
   COMMUNICATION DUE:
   AUTHORITATIVE RECORD LINK:

DECISION QUEUE

- DECISION:
  OWNER:
  NEEDED BY:
  SAFE DEFAULT IF UNANSWERED:
  IMPACT:

RISK / ISSUE WATCHLIST

- CONDITION OR EVENT:
  TYPE: Risk / Issue
  THREATENED COMMITMENT:
  EARLY WARNING OR CURRENT EVIDENCE:
  MITIGATION:
  FALLBACK:
  OWNER:
  REVIEW DATE:

CAPACITY CHECK

REALISTIC WORKING CAPACITY:
− FIXED MEETINGS / ADMIN:
− NAMED RISK BUFFER:
− BUSINESS MAINTENANCE:
= PROTECTED DELIVERY CAPACITY:

TOP INTERVENTION THIS WEEK:
CLIENT UPDATES TO SEND:
WORK TO MOVE, DECLINE, OR REPLAN:
NEXT REVIEW DATE:

Start with the free CSV

The Free Solo Business Operations Toolkit includes a client-delivery dashboard CSV with the core fields from this guide. It contains one synthetic example row, requires no account or email address, and should be adapted to the records and confidentiality requirements of your work.

Definition of done

The dashboard is ready for weekly use when:

every active engagement has one next deliverable and committed date;
every milestone has a completion condition;
every dependency and decision has an owner;
every non-protected state has a response;
capacity is based on a recorded assumption rather than wishful availability;
client communication triggers are explicit;
sensitive detail stays in approved systems;
the dashboard links to, rather than duplicates, authoritative records;
the review produces a short list of actions in under 20 minutes.

The dashboard does not deliver client work. It makes the promises around that work visible enough to protect.

Sources

U.S. GAO, Schedule Assessment Guide: Best Practices for Project Schedules, published December 22, 2015; reviewed August 25, 2026.
U.S. GAO, accessible Schedule Assessment Guide PDF, reviewed August 25, 2026.
NIST CSRC Glossary, Risk Register, reviewed August 25, 2026.