Sign in

Blog · Board and management reporting

Client dashboards: build a clear account performance view

Build client dashboards from approved revenue and service workbooks. Define the audience, calculate account measures, reconcile their totals and choose the next action without confusing an account report with a client portal.

The short answerClient dashboards summarize account performance for a defined audience and reporting period. Start with approved revenue and service exports, join them at the client level, and calculate a small set of measures such as net revenue, recorded delivery hours and on-time completion. Reconcile totals to the source workbooks and calculate overall rates from totals rather than averaging client percentages.

Client dashboards turn account revenue and service records into a view that supports a specific decision. Define who will read the view, which clients and period it covers, and what action each measure can trigger. Then calculate the measures from approved exports and prove that the totals agree.

A useful account view does not need a large catalog of metrics. It needs clear definitions, a visible cutoff date and enough source detail to explain an exception. Its design starts with the question the account owner has to answer.

Choose the audience and the reporting scope

An internal relationship manager may need revenue, delivery effort and service completion. A client receiving a performance report may need an approved subset of delivery measures. Decide the audience before assembling columns; internal economics do not automatically belong in a client-facing report.

Write a scope statement above the worksheet. Include the reporting period, currency, account list, revenue basis and service population. State whether the view shows the full relationship or only a contract or business unit. Keep that scope constant when making comparisons.

For this example, a fictional US business-services firm reviews September 2026 account performance in USD. Its net revenue export already includes posted credits for that month. Its service workbook lists tasks due in the month and whether each was completed by its agreed due date. Recorded delivery hours cover the same accounts and period.

The dashboard is an account review. A broader operational dashboard owns the cross-process operating view; keep that neighboring question separate.

Prepare one row per account

Keep the revenue, time and task exports on separate source sheets. Confirm a stable client ID in each, then summarize each source to that ID before combining the summaries. Joining every invoice directly to every service task can multiply revenue and task counts.

Use net revenue from the approved accounting export rather than open opportunities or unsigned proposals. Count tasks due in the reporting period, including overdue tasks still open at the cutoff. Count an on-time completion only when its completion date meets the agreed due date. Record canceled tasks under a documented exclusion rule.

The account summary uses columns A through E below. Columns F and G are calculated. These fictional account names stand for client IDs in the source sheets.

Client Net revenue (USD) Delivery hours Completed on time Tasks due Revenue per hour (USD) On-time completion
Northline 80,000 400 18 20 200.00 90.0%
Alder 60,000 500 16 20 120.00 80.0%
Cedar 40,000 200 10 10 200.00 100.0%
Total 180,000 1,100 44 50 163.64 88.0%

For a Google Sheets workbook where Revenue columns A and B hold client ID and net revenue, aggregate the amount for the client in A2:

=SUMIFS(Revenue!$B$2:$B$1000,Revenue!$A$2:$A$1000,$A2)

SUMIFS sums values matching specified criteria. Use source ranges covering the complete approved export. The formula above assumes the source has already been restricted to the reporting month; do not silently include earlier periods.

Calculate the measures and their total rows

Enter these formulas in F2 and G2, then fill down through row 4:

=IF(C2=0,"",B2/C2)
=IF(E2=0,"",D2/E2)

Revenue per recorded hour shows revenue against measured effort. It is neither a billing rate nor profit: the revenue basis, unrecorded hours and costs can differ. A fuller realization by client review answers a separate question about earned value and discounts.

The total formulas must use summed amounts and counts:

=SUM(B2:B4)
=SUM(C2:C4)
=SUM(D2:D4)
=SUM(E2:E4)
=SUM(B2:B4)/SUM(C2:C4)
=SUM(D2:D4)/SUM(E2:E4)

SUM adds a series of numbers or cells. Here, $180,000 divided by 1,100 hours gives $163.64 per hour, rounded to two decimals. The service rate is 44 divided by 50, or 88.0%, displayed to one decimal. Keep full precision in the underlying cells. Covirage is not affiliated with Google.

Do not average the client service percentages for the total. Cedar has fewer tasks due than either of the other clients. The combined rate has to describe the actual workload, so its denominator is the total number due.

Reconcile the view before discussing account performance

Tie the $180,000 revenue total to the approved monthly revenue workbook, including credits and exclusions. Tie the 1,100 hours to the time summary, and the 50 tasks due to the service register. The 44 on-time completions must be a subset of those due tasks, never a count of all completions during the month.

Review unmatched client IDs and duplicate task IDs before presenting the view. A client absent from the time export needs investigation; blank hours should not become zero effort. A new client name in a workbook should map to its existing ID rather than create a second account.

The account owner can now investigate Alder's combination of $60,000 revenue, 500 hours and 80.0% on-time completion. The figures identify a service and effort question. They do not prove the cause. Check the underlying assignments, contract scope and recorded work with the delivery owner before promising a change.

For a trend view, keep the same client population and definitions or show changes explicitly. The worked review of five clients illustrates why timing and account context matter before interpreting movement.

Where it goes wrong

  • The audience is undefined. The report accumulates measures without a clear decision or an approved readership.
  • Invoices are joined to task rows. Many-to-many matching multiplies figures even when the final table looks tidy.
  • Completion dates replace due dates. Counting work finished this month can exclude overdue work and distort the service denominator.
  • Missing hours become zero. The account appears unusually efficient when the underlying time record is incomplete.
  • Rates are averaged. Client percentages and revenue-per-hour figures need their own underlying totals for the combined result.

Prepare your account figures in Covirage

Bring a sample of your own approved revenue and service exports to Covirage; it maps the columns, and its tools compute and check the account measures. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring your file.

See sales insights for the supporting account-performance context.

Questions people ask

What should a client dashboard include?

Include the client, period, measure definitions, source date and a few figures tied to a decision. An internal account review might show net revenue, recorded delivery hours and on-time completion. An external client version should contain only measures approved for that audience.

How is a client dashboard different from a client portal?

A dashboard is a view of selected measures. A portal is a delivery environment that may include access, documents and other services. Preparing reconciled account figures does not establish that a particular analytics product supplies a portal or publishes a client-facing dashboard.

Why should total service rates use summed counts?

Clients can have different numbers of tasks due. Averaging their percentages gives small and large workloads equal weight. Divide the total number completed on time by the total number due to report the service rate for the combined workload.