What is a project dashboard for?
A country director oversees many projects, donors and sites. They cannot read every report. A dashboard answers one question: where should I look today? It points to the project that is behind, the budget line that is off track, the approval that is stuck, or the incident that needs a decision.
It does not answer why. That is for the project manager and the underlying records. A good dashboard makes the director ask better questions, and a bad one makes them think they already know the answer.
Think of it as a cockpit panel. A pilot does not read the whole manual in flight; they watch a few dials and know when to look closer. A country director needs the same: a few dials that are reliable, current and tied to real records.
Before you design the page, ask the director three questions: What decisions do you make each week? What do you ask the team most often? What has surprised you in the past? The answers tell you which signals to show.
Which five signals matter most?
| Signal | Show | Question it answers |
|---|---|---|
| Results | Headline indicators against target, with the period | Are we delivering what we promised? |
| Money | Spent and committed against budget, against time elapsed | Are we on track to spend well? |
| Approvals | Number of items waiting, and the oldest | What is stuck, and for how long? |
| Risks and incidents | Top open risks, open incidents | What could hurt us, or already has? |
| Deadlines | Next donor report and other due dates | What is coming? |
Each signal needs a status the director can read in a second: on track, watch, or off track. Define in advance what each status means, with rules rather than moods.
How many numbers is too many?
If a director cannot read the page in two minutes, it is too long. Limit it to one screen. Choose the two or three indicators per project that best show delivery. Our article on output, outcome and impact indicators can help you choose.
Avoid decoration. A chart that adds no decision value should go. Show the date of the data on every panel, so a stale number is not mistaken for a current one.
Test the page with the director. Print it, give it to them with no explanation, and ask what they would do next. If they cannot tell, change the page. Repeat after a month, when real use shows which panels they read and which they skip. Remove what is never used.
Use plain labels, such as “Waiting for approval” rather than internal codes. Use the same colours and words for status in every project, so a red light always means the same thing.
What should the director be able to do from it?
A dashboard that only displays leaves the director with questions and no path. Each item should link to the record behind it:
- From a results signal, open the indicator and its approved data.
- From a money signal, open the budget line and its entries.
- From an approvals signal, open the waiting item.
- From a risk signal, open the risk and its owner.
- From a deadline, open the report and its status.
If a figure cannot be traced to a record in two clicks, people will stop trusting it.
Add one more habit: when the director acts on a dashboard signal, record what was decided. A short note such as “asked finance to review travel line; report due Friday” turns a glance into a management routine, and later shows how the dashboard was used.
What are the common mistakes?
- Mixing data of different ages. Money may be current to yesterday, and results to last quarter. Show both dates.
- Counting what is not approved. A number that includes unreviewed field data can mislead. Show approved results, and say so.
- No owner. Every status needs a named person who answers for it.
- Treating the page as a decision. A green light does not mean the work is good. It means the numbers you chose to watch look fine.
- Too many projects on one page. Give each project its own page, and add a portfolio page that only shows the exceptions.
Our article on grant budget monitoring month by month shows what sits behind the money signal.
One more point: review the rules behind each status twice a year. A target that was fair in the first month may not be fair in the tenth, and a threshold that nobody trusts will be ignored. Write the rules on the page or in a short note next to it, so every reader knows why a project is amber.
Where EMPOBase fits
In EMPOBase, the Overview dashboard summarizes available project information and items needing attention, such as pending approvals and recent activity. What a person sees depends on their role and on the records available to them. A dashboard summary does not replace the source record or an approval step, so you open the module to review the record before you act. See the platform overview for the modules behind it.