Cornerstone compliance %: the one number every manager asks for

In a recent workshop with a large enterprise, an HR leader asked us for something that sounds trivial: show every manager how compliant their team is – not how many of their people have ticked every box, but how much of the required training their team has actually completed, across their direct reports and everyone below them. Not a spreadsheet. Not a report they run. Just a number, per manager, that is always right.

It is the most reasonable ask in the world. It is also one of the trickier numbers to get cleanly out of Cornerstone OnDemand (CSOD). Here is why, and the two honest ways to actually get it.

What "compliance %" even means

Before the hard part, the fuzzy part: "compliant" is not a field you can read off a record. It is a definition you have to pin down first.

For most organisations it is a completion rate – how much of the required training a group has actually completed, on time – not a headcount of who is fully finished. A team sitting at 72% has done roughly seven in ten of its required trainings; a single person's number is their own required training completed versus assigned. It measures how compliant people are, not how many are. And every part of even that hides a choice:

• Required by what? Training that was assigned, training flagged as required – what different organisations call compulsory or mandatory training – certifications that must stay current, or some blend. These live in different places in CSOD.
• Finished how? A completed transcript is a status code, not a label. A certification has an expiry. "Done" for a course and "still valid" for a certification are different questions.
• On time or ever? A completion after the due date may satisfy the auditor and fail the KPI, or the reverse. The deadline logic is yours to decide.
• Which people? This is the one that turns a simple metric into a hard one – more below.

None of this is a criticism of Cornerstone. It is just the reality that a single "compliance %" is a computed number, assembled from several fields with rules you choose, not a value sitting in a column.

Why the manager rollup is the hard part

Cornerstone genuinely helps here – up to a point. A manager can open the "View Your Team" area and see a summary of their direct reports' training, and the team training reports will draw a pie chart of where those people stand. Your HR compliance team, separately, gets an org-wide compliance dashboard that consolidates training across departments and locations.

The specific thing the workshop asked for falls in the gap between those two. It is:

• Per manager, self-service, not an admin running a central report.
• Cascading – not just direct reports, but the indirect reports beneath them too, every person down the reporting line. A director four or five levels up should see the compliance of their whole area, the couple of hundred people beneath them, not only the handful who report to them directly. The most common way managers phrase it: "direct reports is good, but can we go beyond, down the whole hierarchy?" Native manager views tend to stop at that first level down.
• A single, current percentage you can drill – start at the area's top-line number, then follow it down to find the one team, or the one person, dragging it below the line. Not a page of transcripts to eyeball.

Native manager views tend to stop at direct reports and at "here are the rows"; the org-wide view lives with HR, not with each manager. Rolling a clean compliance percentage down an entire reporting tree, scoped to whoever is looking at it, is exactly the combination Cornerstone does not hand you off the shelf. And because "compliant" is computed from scattered data (as above), and because getting broad data out of Cornerstone has its own limits, the number that sounds like one click is genuinely several problems stacked together.

The two honest ways to get it

There is no single right answer, because there are two different audiences asking, and they want the same number in two different places.

The HR and compliance view – org-wide. When the question is "where does the whole organisation stand, and where are the gaps," that is a reporting-and-dashboard job. This is what octo.taxi does: it syncs your Cornerstone data and gives compliance and completion analytics across the org, sliceable by department, location, or manager, current after every sync – the single source of truth for the numbers HR and the board care about.

The manager view – inside Cornerstone. When the question is "what is my team's compliance percentage, right now, without leaving the portal," that is a role-aware job, and it belongs where the manager already works. That is what Octily's Cornerstone MicroApps are for – the Team Training Progress MicroApp gives each manager their own live compliance and completion percentage, embedded in Cornerstone: their direct reports, or their whole area of indirect reports several levels down, a top-line number they can drill into, filtered to the required (compulsory) training that actually counts. Role-aware, self-service, no report to run.

Together they cover both sides of the same question: HR gets the rollup across everyone, every manager gets their own slice of it, and neither has to become a reporting expert to see a number they should have had all along.

The honest bit

The reason "what percentage of my team is compliant?" is hard in Cornerstone is not that the data is missing – it is all there. It is that the answer is a computed rollup: a definition of compliant, applied across a reporting tree, scoped to whoever is asking, kept current. That is real work, and it is precisely the kind of work we have built to disappear – as an org-wide view in octo.taxi, and as a manager's own view through MicroApps.

So the next time someone asks for the number that sounds like one click, you will know why it isn't – and that it can still feel like one.

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

---

Sources. Cornerstone compliance management · Managing compliance training in Cornerstone.