SIX QUESTIONS YOUR HR DASHBOARD SHOULD BE ABLE TO ANSWER

Most HR dashboards report what happened last month. These six questions test whether yours can support a decision, and they expose the data work you still owe.

Emmanuel Duncan · 30 August 2026 · 6 min read

There is a version of HR reporting that looks finished and does nothing. The charts render, the colours are consistent, the figures update on schedule, and no decision in the organisation is made differently because of any of it.

The gap is rarely visual. Dashboards that fail this way usually report counts of things that happened, headcount, hires, exits, absence days, training hours, because those are the fields the HR system fills in on its own. A decision needs two fields joined together, and joining them is where the work sits.

Below are six questions. They are not a maturity model and they are not sequenced by difficulty. They are a test. Take your current dashboard, take each question in turn, and mark whether you can answer it today, answer it with a day of manual work, or cannot answer it at all.

The pattern in your answers tells you more about your analytics capability than any capability framework will.

1. Which Roles Took Longest to Fill, and What Did the Vacancy Cost in Cover?

Time to fill is a common metric. The second half of the question is the one that separates reporting from analysis, because it requires joining recruitment records to whatever you used to cover the gap: overtime, a temporary contract, an internal secondment, or work that simply did not get done.

If you can answer the first half and not the second, your recruitment data and your payroll data are not talking to each other. That is a specific, fixable problem, and it is worth more than another chart.

2. Where Is Absence Concentrated, and Is It the Same People Each Month?

Total absence days is close to useless on its own. Two organisations with identical absence rates can be in completely different situations: one where a broad group each takes a day here and there, and one where a small number of people are absent repeatedly.

The question requires you to look at absence per person over a rolling period rather than in monthly totals. The Bradford Factor is one way to do this, and it is not the only one, but any approach that distinguishes frequency from duration will do.

If your system can only give you a monthly total, you cannot separate a wellbeing issue from a scheduling issue, and any intervention you fund is a guess.

3. Which Managers Carry the Widest Spans, and How Does That Track With Their Team's Outcomes?

Span of control sits in your org hierarchy. Team outcomes, turnover, absence, vacancy duration, sit in three other places. Putting them side by side is a join across four sources, and it is one of the highest-value joins in HR because it points at structural causes rather than individual ones.

A manager with twenty-two direct reports and high turnover is not necessarily a poor manager. They may be someone who has been handed an unmanageable structure. The dashboard cannot tell you which, and it can tell you where to go and ask.

4. What Proportion of Your Workforce Has a Current, Accurate Job Description on File?

This one looks administrative. It is a data quality question wearing a compliance costume.

Job descriptions are the link between a person and a role. Almost everything interesting in workforce analytics, skills gaps, internal mobility, pay equity by work of equal value, training needs, depends on knowing what a role actually involves. When descriptions are ten years old or were copied from a template, the analysis built on them inherits that.

The proportion is easy to count and uncomfortable to publish, which is usually a sign that it is worth publishing.

5. Who Leaves Within Twelve Months of Joining, and Where Were They Hired From?

This joins your exit data to your recruitment source data. The finding it produces is one of the most directly actionable in HR: if one channel consistently supplies people who leave inside a year, you have found money you are currently spending twice.

Many organisations cannot answer it because recruitment source is captured during hiring and then never carried into the employee record. That is a five-minute change to a form and a much longer conversation about who owns the field.

6. If You Lost the Five Longest-serving People in a Department Tomorrow, What Would Stop Working?

This one cannot be answered by a dashboard at all, and it belongs on the list for that reason.

The knowledge that keeps processes running is rarely written down. It lives in the person who knows which supplier to call, which approval can be skipped in practice, and why the system does the strange thing it does every December. No HR system holds that field.

What you can do is identify where the exposure sits: departments with a long tenure profile, single points of dependency, processes with one named owner and no documented alternative. Then treat the gap as a documentation task rather than an analytics one.

Including this question on the list is a deliberate limit on what the dashboard is for. A good reporting layer should make it obvious where the numbers stop being able to help.

Reading Your Results

Group your answers.

If you can answer questions built on a single system and fail on every question requiring a join, your problem is integration, not analysis. Buying a better visualisation tool will change nothing. The work is in getting recruitment, payroll, absence and the org hierarchy to share a common employee identifier.

If you can answer most of them with a day of manual work each, you have the data and lack the pipeline. That is the most common position, and it is a good one to be in, because it means the value is already sitting in your systems and the remaining task is engineering rather than discovery.

If you cannot answer questions four and six, the issue is upstream of analytics entirely. Job descriptions and process documentation are not analytics deliverables, and no dashboard can compensate for their absence.

What to Do With the List

Run the six questions past your HR team without warning and write down the answers. Then run them past your HRIS or IT contact and see whether the two accounts match, because they frequently do not.

The output is a short list of specific joins that do not currently exist. That list is your analytics roadmap for the next year, and it will be more useful than a maturity assessment because every item on it can be finished and checked off.

Emmanuel Duncan is the founder of Aletheia Lunara Consult, a professional education and consulting practice working with organisations across Ghana and beyond on people analytics, workforce research and organisational capability.