A dashboard people open: the design rules behind our client reports
A monthly PDF report has a predictable life: it arrives on a Monday, gets opened once, and is never found again. A dashboard with a bookmark gets opened on a Tuesday afternoon when someone in a meeting asks a question nobody prepared for.
A PDF answers the questions its author thought of; a dashboard answers the one the reader has right now. Ours follow the same shape every time: period filters at the top, a row of the big numbers, charts that show exact values on hover, a log you can search, and a map. Light background, one typeface, the client's own colors, and plain notes on where the data comes from. That shape is why program managers bookmark the report instead of filing it.
Why PDFs die in inboxes
A PDF answers the questions the author thought of when they made it. The reader always has a different one. How did last week compare to the week before? What happened the night of the big game? Which stop is busiest after dark? The PDF cannot answer, so the reader emails the question, waits, and by the time the reply comes the meeting is over. After a few rounds of that, the report stops being opened. It is not that the reader does not care. It is that the format cannot keep up with their curiosity.
A dashboard is a report that can take a question.
The order of the page
We have built reporting dashboards for a university shuttle program, a hotel guest shuttle, a community pilot, and the lead pipelines of several trade businesses. The layout settled into the same shape every time, because the same shape is what people reach for.
- Period filters first. At the very top, before any number: this week, this month, this semester, a custom range. The first thing a reader does is set the window they care about, so that control is the first thing they see. Everything below changes when it changes.
- A row of the big numbers. A short line of tiles. Total rides, unique riders, average wait, busiest day. Or leads, replies, booked estimates, closed jobs. Each tile shows the figure for the chosen period and a small note on how it compares to the period before. A reader who looks only at this row for a moment leaves knowing the state of the program.
- Charts you can hover. Trend over time, breakdown by day of the week, breakdown by hour. Every point on every chart shows its exact value when the cursor rests on it, so nobody has to squint at an axis. The charts are drawn in the client's own colors, not a chart library's defaults.
- A log you can search. Every ride, every lead, every inspection, in a table with a search box and sortable columns. This is where "what happened that night" gets answered without an email.
- A map. Where things happened. For a shuttle, pickups and dropoffs. For a trade business, jobs by neighborhood. A map turns a list into a picture the owner can show a board or a city.
Design rules specific to reports
- Light background, always. Reports get projected in conference rooms and screenshotted into emails.
- One typeface, with the numbers set in a style where every digit is the same width, so columns line up.
- Restrained color: the brand's main color for the primary series, grays for everything else, and one warm color reserved for anything that needs attention.
- No decorative charts. If a pie chart would have two slices, it is a sentence instead.
- Method notes at the bottom in plain words: what counts as a ride, what counts as a lead, where the data comes from.
- A line saying when the data was last refreshed, so nobody has to wonder.
Why bookmarks beat attachments
The dashboard lives at a web address. It is protected, but it is always the same address and the data is always current. The program manager bookmarks it. The board member who was sent the link once finds it in their history. When someone asks a question in a meeting, the person with the laptop opens the tab and answers in the room. That is the difference between a report that documents a program and a report that helps run one.
We have watched a client go from "please send me the numbers" to "I already looked, here is what I want to change" within a couple of reporting cycles. The report did not get smarter. It got openable.
What we still send by email
A short note. A few sentences on what moved this period and why, with the link. The note is for the person who reads email on their phone in the parking lot; the dashboard is for the person who wants to look for themselves. Both get the same numbers, because both come from the same place.
This dashboard pattern sits behind the reports we deliver to a university transit program, a resort guest shuttle, and the trade businesses whose lead systems we run across Palm Beach County.
Questions people ask
Can the board or the city still get a PDF?
Yes. The dashboard prints cleanly to a PDF for any period, so the formal record still exists. The difference is that the PDF is a snapshot of the live report rather than the only version of it. The link stays current; the PDF captures a moment.
Who can see the dashboard?
Only the people the client allows. Each dashboard sits behind a login or a private link, and the client decides who gets access. A program manager, a board member and a city contact can each have their own way in without anyone emailing spreadsheets around.
How current is the data?
As current as the source. For a shuttle program the rides appear as they are completed. For a lead system the new inquiries appear the moment they arrive. A line on the page always says when the data was last refreshed, so the reader never has to guess.
Want this done for your business?
Two minute intake. A real person reads every one and replies within a business day.
Keep reading
Design that converts: the handful of rules we never break
The design rules every site and app we build follows: light backgrounds, one typeface, real icons, one action per screen, and contrast that survives Florida sun.
DesignFrom mockup to pixel perfect: how we build to an approved design
How we turn an approved mockup into a site that matches it: a section by section reconcile pass for spacing, type and color, then a check on a real phone.
DesignDark mode is not a brand: why we default to light
Why service business websites and client reports should default to a light background, where a dark screen earns its place, and how we settle it with a client.