The HR Intelligence engine

The HR Intelligence engine: software built for the reality of HR data.

Know your data is right. Then act on it with confidence.

To do this work faster and more accurately, I designed and built my own tool: the HR Intelligence engine. It is a browser-based, privacy-by-design analytics engine that I use to deliver my consultancy.

It does the heavy lifting of absorbing your raw HR exports (CSV or Excel), mapping the columns to over 150 canonical fields, and building a clean, historical model. Crucially, your data never leaves your machine. It reads everything in your browser, without sending your data anywhere.

The engine does not learn by itself, it does not certify accuracy, and it never makes employment decisions. Instead, it surfaces the hidden patterns and signals in your data for us to investigate together.

  1. Step 1

    Your Raw Data

    Headcount, leavers, absence, performance, and legacy spreadsheets. Drop them in exactly as they are.

  2. Step 2

    Processed In-Browser

    The engine audits, maps, collates, and links the data directly on your machine. Nothing is ever uploaded to Help Studios.

  3. Step 3

    The Output

    Ranked signals, a risk Watch Register, and a fully reconciled, board-ready export.

Tested against deliberately hostile files: nine exports carrying 24 habits of real HRIS and spreadsheet extracts (report titles above the header, totals inside the data, several date formats, differently padded ids, European number formats, a pivot-shaped file). 19 were handled correctly first time, 5 were flagged for a person to decide, and none was silently read wrong. The audit of all nine took 3.8 seconds on a laptop, including opening the browser.

See every screen

How it reads your systems

Any system. Any mix. One model.

The same person is a 'Worker' in Workday, an 'Assignment' in Oracle, and a row in a legacy spreadsheet. I map every system onto one unified vocabulary. The headcount in your board pack and the leavers in your tracker finally describe the exact same people.

You do not have to run one of these. Workday, Oracle Fusion HCM, SAP SuccessFactors, Core HR (People XD), BambooHR, iTrent, ResourceLink, ADP and Sage HR are the systems whose column names the engine already knows, and an Excel or CSV export covers everything else. Load one of them, or all of them, or a different vendor in every country — the engine merges whatever it is given into the same model, and a system it has never seen is read from its headers rather than turned away.

Each part of the HR lifecycle lives in a different system Six lifecycle stages left to right. Attract (recruitment) sits in an applicant tracking system. Join (onboarding) sits in a hand-made checklist spreadsheet. Develop (learning) sits in a learning system. Work and Leave both sit in the core HRIS, which holds headcount, absence, performance, pay and leavers; a client may run a different core HRIS in each country. Resolve (employee relations) sits in a hand-made case tracker spreadsheet. Surveys sit in a forms tool or spreadsheet outside all of these. Everything flows into one box, HR Intelligence in your browser, and out as one linked view. Attractrecruitment Joinonboarding Developlearning Workcore HR Resolveemployee relations Leaveleavers, exit Recruiting system (ATS) for example Greenhouse or Workday Recruiting Onboarding checklist a spreadsheet HAND-MADE (EUC) Learning system (LMS) for example Cornerstone or SuccessFactors Learning Core HRIS for example Workday Headcount Absence Pay Performance one per country, often Case tracker a spreadsheet HAND-MADE (EUC) Core HRIS the same system as Work Leavers Surveys: a forms tool or a spreadsheet, outside every system above Different lifecycles, different systems, and often a different HRIS per country HR Intelligence, in your browser Audit, map, collate, link. Nothing uploaded. One linked view Every lifecycle, joined on one person
Each part of the HR lifecycle lives in a different system Six lifecycle stages top to bottom. Attract (recruitment) sits in an applicant tracking system. Join (onboarding) sits in a hand-made checklist spreadsheet. Develop (learning) sits in a learning system. Work holds headcount, absence, performance and pay in the core HRIS, which a client may run once per country. Resolve (employee relations) sits in a hand-made case tracker spreadsheet. Leave (leavers) sits in the same core HRIS. Surveys sit in a forms tool or spreadsheet. Everything flows into one box, HR Intelligence in your browser, and out as one linked view. Attractrecruitment Recruiting system (ATS)Greenhouse, Workday Recruiting Joinonboarding Checklist spreadsheetHAND-MADE (EUC) Developlearning Learning system (LMS)Cornerstone, SF Learning Workcore HR Core HRIS, e.g. Workday headcount, absence,performance, pay often one per country ResolveER cases Case tracker sheetHAND-MADE (EUC) Leaveleavers Core HRISthe same system as Work Surveys a forms tool or a spreadsheet Different lifecycles, different systems, often a different HRIS per country HR Intelligence, in your browser Audit, map, collate, link One linked view Every lifecycle, joined
Each lifecycle keeps its facts in its own system. Headcount, absence, performance, pay and leavers share one core HRIS; recruitment, learning, employee relations and surveys do not. HR Intelligence reads them all in your browser and links them.

Field map

Selected system: Workday

How the selected system's column names map onto the unified model. A name in the right-hand column is that system's own word for the field; a muted name is the engine's own column, printed where that system's vocabulary has no name for this column.
Unified model Workday field
Employee ReferenceWorker_ID
DepartmentSupervisory_Organization
Job TitleJob_Profile_Name
GradeGrade
Full Time EquivalentFTE
Legal GenderGender
EthnicityEthnicity
Date of BirthDate_of_Birth
Start DateHire_Date
Manager ReferenceManager_ID
Cost CentreCost_Center_ID
LocationLocation
Leave DateTermination_Date

Workday names all 13 of these columns in its own vocabulary.

Names are read from the engine's own field registry — 180 canonical fields, a vocabulary for each of ten systems, and 1,176 spellings the mapper resolves across the headcount, absence and leavers exports. These thirteen are the engine's headcount template, kept to the columns whose own name resolves to the field they belong to. A muted name is the engine's template column rather than the system's word: that vocabulary has no name for the column, so the engine reads your header, or you map it once on upload — which is why a system listed above with a short vocabulary, or one not listed at all, still gets the same model. Load one source or every source; they merge. Headcount is not a column anywhere — the engine counts rows — and leave reason and absence days arrive with the leavers and absence workbooks.

Showing Workday field names.

Guided tour

A guided tour of the product, on real screens.

These are the real screens from the running product, on a synthetic bank called Meridian Bank. Pick a step, or use the arrow keys.

The Headlines Report for Meridian Bank: 1,299 heads and 1,274.6 FTE, absence and attrition with their status against target, and a one-sentence summary.

Step 1 of 5

Start with the answer

What does the board need to know this month?

  1. Heads and FTE, side by side 1,299 people are 1,274.6 full-time equivalents: part-time working is counted, not rounded away, and last year sits underneath.
  2. Red, amber or green against your own target The rate is judged against the target you set, not a number baked into the product, and it says so.
  3. One sentence for the board The screen writes its own summary: what needs attention, what is on target, what is for information.

Demo data — Meridian Bank, a synthetic organisation. The numbers on every step come from one run of the product.

Talk it through

Start with the question your board keeps asking, or the data problem behind it.

Contact me

The other services