What To Check Before A Simple Project Dashboard For Client Work

Before you show a simple project dashboard to a client, you must verify that it tells a clear, honest story about progress, risks, and costs. This guide walks you through a practical pre-flight check: confirming the data sources are current and accurate, making sure the numbers match what the client expects, testing that the dashboard loads correctly on common screens, and preparing a short walkthrough so you can explain key points calmly. You will also learn how to spot common traps like stale dates, mismatched totals, or confusing charts. The final checklist and FAQ help you catch errors before they damage trust.

Fast Answer

Refresh all data sources in the dashboard, then compare today's figures against yesterday's totals to confirm nothing changed unexpectedly.
Open the dashboard on a phone and a laptop, click every interactive element, and read every label aloud to ensure the story is clear.

Set-up ready What to have on hand

Step-by-step Guide format

Device-specific Check official settings

Before You Start

List the exact questions the client expects the dashboard to answer, so you can verify each chart or number directly addresses one question.
Collect the source files or query names for every metric shown, so you can trace each number back to its origin if asked.
Define two or three key takeaways you want the client to remember, so the dashboard emphasizes those points visually.
Write or update a short caption for each chart that explains what changed and why it matters, because captions prevent misinterpretation.

Check first: If your dashboard shows a number that disagrees with the client's own spreadsheet, the client will lose confidence in everything else you present, even if your figure is technically correct from a different data source. Always reconcile the underlying data with the client's primary record before you open the meeting, and bring a note explaining any minor variation in rounding or timing.

Step-by-Step Instructions

Verify Data Freshness and Source Integrity

Start by confirming that every chart and table pulls from a live, updated data source rather than a cached file from last week. Open each connected spreadsheet, database query, or API endpoint and check the timestamp of the last refresh. If any source is older than your agreed-upon update frequency, run the refresh now and note the new time. Next, compare the totals on the dashboard with a simple sum of the raw data for a few sample rows. For instance, if your dashboard shows a weekly total of 42 tasks completed, add the numbers from the underlying task log to see if they match. This step matters because a single broken connection or a forgotten refresh can silently show stale numbers, and clients will assume you have been careless. Also confirm that any manual overrides or adjustments you made are clearly flagged, so a reviewer does not think the dashboard is wrong.

Tip: Create a small 'last refreshed' text box on the dashboard itself, visible to the client, so everyone can see the data is current at a glance.

Reconcile Key Metrics with Client Expectations

Before you present, gather the client's own latest spreadsheet or status report and compare every headline number on your dashboard against it. Pay special attention to totals like budget spent, hours logged, or deliverables completed, because these are the figures clients quote in their own meetings. If you discover a mismatch, determine the cause before you fix it. For example, your dashboard might count a task as complete when it is actually only in review, or the client might use a different week boundary. Adjust the dashboard's definitions to align with the client's conventions, or add a tooltip explaining the difference. This step matters because the client trusts their own numbers more than yours, and a visible discrepancy will distract from the story you want to tell. Even a small variation of one or two items can trigger a long investigation during the meeting, so resolve it now.

Tip: Put a list of definitions for every metric in a separate notes panel, including the exact counting rule, so both you and the client can see the logic.

Test All Interactions on Multiple Screen Sizes

Open your dashboard on a large monitor, a laptop, a tablet, and a phone, and test every drop-down, filter, and hover tooltip. Click each filter and apply it to see if the charts update correctly, and note any buttons that open links or show extra information. On small screens, verify that no text is clipped, no charts are squeezed beyond legibility, and that tapping a filter works without needing a mouse. Also check that the dashboard does not load excessively slowly because of heavy images or animations. This step matters because clients often view dashboards on a variety of devices, and a broken filter or a cut-off label makes the dashboard seem unfinished. If you cannot test on a physical device, use the browser's responsive mode to simulate different widths, but still try to view it on at least one small screen yourself.

Tip: Set a rule that all text on a phone must be readable without pinching, and use at least a 14-pixel font for body text in the dashboard style.

Check Chart Clarity and Color Accessibility

Look at each chart as if you are seeing it for the first time, and ask whether the main point is obvious within five seconds. Check that the title truly describes the data, the axes are labelled with units, and the legend matches the categories exactly. For bar charts, confirm the baseline starts at zero unless you have a strong reason not to, and for line charts, make sure the time axis is ordered correctly. Also verify that the colors used do not rely on red-green differences alone, because color-blind clients may not see the distinction. Run a quick grayscale check by printing the dashboard or converting it to black and white, and see if the comparison still makes sense. This step matters because a chart that confuses the viewer or hides the trend will lead to questions that waste meeting time and undermine your credibility.

Tip: Add direct labels at the end of each line or bar instead of relying on a legend, so the reader does not have to scan back and forth.

Prepare a Short Walkthrough Script with Key Takeaways

Write a three- to four-minute verbal explanation that guides the client through the dashboard in a logical order, starting with the overall health summary and then moving to the areas that need attention. For each chart, prepare one sentence that states what changed and why it matters, and for the most important number, practice saying its value out loud without hesitation. Also prepare a single sentence that describes the main caveat or limitation of the data, so you appear transparent. Rehearse this script twice, once out loud and once while clicking through the dashboard, to ensure that your clicks match your words. This step matters because a dashboard does not present itself; a confident, structured walkthrough helps the client absorb the information and reduces the chance of a chaotic, question-filled session where you forget a key detail.

Tip: Keep a printed one-page summary of your walkthrough points next to you, but do not read directly from it; just glance to stay on track.

Run a Final Sanity Check and Freeze the Version

Do one last full pass of the dashboard by clicking through every tab and refreshing the page to ensure nothing breaks. Confirm that the date shown on the dashboard matches today, and that any 'as of' stamp is correct. Then, export a static PDF or screenshot of the current view and save it with today's date, so you have a record of what you presented. If you make any last-minute changes, update the saved version as well. Also ensure that the dashboard's URL or file path is the one you will share, and that any sharing permissions are set so the client can access it. This step matters because a last-minute refresh could break a slide or a live link, and having a frozen version protects you if something goes wrong mid-presentation.

Tip: Create a simple version number like 'dashboard_v3_20250214' in the footer, so you and the client can refer to a specific release.

Quick Reference

Situation	Action	Why it helps
Client questions why a monthly total is different from their own spreadsheet.	Open your raw data source, locate the matching time period, and compare line by line with the client's file to identify the counting rule difference.	Discrepancies usually come from different definitions of 'complete' or different cutoff days, so seeing the exact rows helps you explain calmly.
A chart appears blank when you filter to a specific project.	Check the filter logic in the dashboard's data model to see if the project name is spelled exactly as it appears in the source data.	A single extra space or a slight difference in naming can prevent any records from matching the filter, resulting in an empty chart.
A tooltip shows an error message when you hover over a data point.	Right-click the visual element, open its tooltip properties, and verify that the fields used exist and have no null values for that row.	Hidden null values or missing field references cause tooltip errors, so you must inspect the specific data point to fix it before presentation.

Common Issues

The dashboard shows yesterday's numbers even though it is supposed to auto-refresh.: Check the refresh schedule in your data connection and run a manual refresh immediately before presenting. Also verify the time zone setting matches your local time, because a default time zone can shift the refresh time.
A bar chart is cut off at the top of the screen, hiding the highest value.: Adjust the layout by reducing the chart's margins or enabling a scrollable container, and test it on a smaller screen to confirm the full height is visible.
The client asks what the 'average' number means, but the dashboard does not define it.: Add a clear definition in a tooltip or a notes section that says whether it is the arithmetic mean, median, or a weighted average, and state the time period used.

Advanced Tips

Set up a scheduled email to yourself every morning with the dashboard's key numbers, so you can spot anomalies before the client does.
Use a consistent color code across all charts: for example, always use the same color for 'on track' and a different one for 'at risk', and mention the code in the narration.
Create a hidden sheet in your data source that logs every change you make, so you can answer 'why did this change?' questions without scrambling.

Final Checklist

Every number on the dashboard matches the client's primary source or has a clear explanation for any difference.
The dashboard loads in under five seconds on a mid-range phone and all filters work without errors.
All chart titles, axis labels, and tooltips are complete, accurate, and free of spelling mistakes.
You have a prepared one-minute verbal summary and a saved PDF copy stamped with today's date.

FAQ

How often should I refresh the dashboard before a client meeting?

Refresh the data at least one hour before the meeting to allow time for reconciliation. More importantly, check the 'last refreshed' timestamp on the dashboard itself. If any source is older than your agreed update cycle, refresh it now. Do not rely on automatic refreshing alone, because a connection can fail silently. A good practice is to set your scheduled refresh to run early in the morning, then manually verify that the numbers look reasonable compared to yesterday.

What if the client wants a metric that is not in my dashboard?

Do not try to add the metric on the spot because that could break the layout or introduce errors. Instead, acknowledge the request, write it down, and tell the client you will include it in the next dashboard update. Before the next meeting, add the metric using the same data source and test it thoroughly. It is better to deliver a curated dashboard with ten accurate metrics than a cluttered one with twenty that you cannot explain.

How can I convince the client that my numbers are accurate?

Show a side-by-side comparison of two or three key figures from your dashboard and the client's own records, and explain any small differences due to rounding or cutoff time. Also, display the 'last refreshed' timestamp and a short description of the data source for each metric. If the client needs proof, you can share a sample row from the raw data, but be sure to respect any confidentiality. Confidence comes from being able to trace every number back to a specific origin.