A Cornerstone compliance dashboard that survives an audit

The audit is in two weeks. Somebody from EHS or HR opens Cornerstone, pulls a transcript report of every required training, filters it in Excel, builds a pivot by site, and pastes the result into the audit pack. Next quarter, same afternoon, same pivot.

The data was never the problem: Cornerstone OnDemand knows exactly who was assigned what, when it is due and when it was completed. What is missing is one screen that answers the auditor's questions the moment they are asked. Here is what that screen needs to show – and why each tile earns its place.

The five questions every audit asks

In our experience the conversation always comes down to the same five:

1. What is our mandatory completion rate? One number, for the whole organization and for each site.
2. How many people are overdue right now – and is that better or worse than last week? A snapshot without a direction tells you nothing about whether the problem is shrinking.
3. What falls due in the next 30 days? The overdue list of next month is today's to-do list.
4. Who is exempt, and why? Exemptions are legitimate, but an auditor will ask for the reason behind every one.
5. How has the rate moved over time, per site? A site that has been climbing since spring tells a very different story from one that has been sliding.

If a dashboard answers those five without anyone running a report, the audit becomes a conversation instead of a scramble.

How Cornerstone defines "mandatory"

In Cornerstone, mandatory training lives on the learner's transcript: a training assigned as required, with a due date, and optionally recurring. An admin can also exempt a person from a required training, which leaves a dated exemption on the transcript.

That gives you a clean, auditable definition, and it is the one we use everywhere in octo.taxi: a transcript counts as mandatory when Cornerstone's required flag is set and no exemption date is recorded; required with an exemption date counts as exempted; everything else is voluntary. Write that definition down once and use it in every report – otherwise the board deck and the L&D dashboard will quietly disagree.

The completion rate itself is the share of those mandatory transcripts that are completed. The interesting part is the denominator: which people count. Leavers, deleted accounts and inactive users inflate it if nobody filters them out, so decide once that only active people count – and stick to it.

Why the trend matters more than the snapshot

An overdue count on its own is a fact. The same count next to last week's, and higher, is a warning. A compliance dashboard should always show both, and it should get the colours right: when overdue goes up, the arrow points up and the colour is red, because more overdue is bad. It sounds trivial; we have seen more than one dashboard paint a rising overdue count green because "up" was coded as good.

The same goes for the rate per site over months. A heatmap of site against month shows in one glance where a problem started and whether it is being fixed – exactly the question an auditor or a plant manager will ask next.

Names or numbers: what a manager may see

An aggregate is safe to show almost anyone. A named list of overdue people is a different thing: it is personal data, and in many European organizations it is a works council topic (we wrote about that in HR analytics your works council can sign off).

The practical answer is two views. HR and EHS see the organization in aggregates and, where their role allows it, the named list of who has a duty to act. Line managers see their own reporting line – who is due, who is overdue – and nobody else's. Anything in between, such as a ranking of managers by compliance, is better left out.

What this looks like in octo.taxi

We built the Compliance Cockpit around exactly these questions. Shown here on Tentaclemore Shipping, our fictional demo company:

• The mandatory completion rate, with overdue now against a week ago and the trend coloured by what is good, not by which way the arrow points.
• What falls due in the next 30 days, the exemptions with their reasons, and the top overdue courses.
• The completion rate per location per month as a heatmap, and per requirement tag.
• For people whose role allows it, the named list of overdue mandatory training – the people with a duty to act, never a ranking.

Line managers get the Team Cockpit: their own reporting line, who is due, whose qualification expires, and how the new joiners are doing. And an alert on a figure – for example overdue mandatory training at one site – taps the right person on the shoulder before the audit does.

The data comes from Cornerstone in near-realtime, every tile shows how old its data is, and groups too small to be anonymous are hidden. If your managers need the view inside Cornerstone itself, the compliance % article shows the embedded route too.

The honest bit

A dashboard does not make anyone complete a training. What it does is move the moment you notice a gap from "the week before the audit" to "the day it opens". That is the whole value – and it only holds if the definition of mandatory is agreed once and the data is current.

If you are still building that pivot every quarter, the limits of Reporting 2.0 are worth a read before the next one.

Your data should move freely, from A to B, in style.

---

Sources. Cornerstone: Real-Time Data Warehouse overview · Cornerstone: Reporting 2.0 – Create Report · octo.taxi: What is octo.taxi.