Finance already runs business-intelligence dashboards, but HR still builds council employment statistics from one-off spreadsheets. What should the CHRO fund?
Select an answer to reveal the explanation.
Short Explanation
If finance has a live dashboard and HR is still glue-sticking a spreadsheet the night before council, the numbers will drift. Strategy needs the same employment statistics every month, from a real feed. Fund the HR BI pipe, not another heroic spreadsheet.
Full Explanation
Funding an HR business-intelligence feed so council packets use the same employment statistics every month is correct when finance already runs live dashboards while HR rebuilds one-off spreadsheets the night before meetings. Definitions will drift and strategy debates will argue past each other without a governed feed. Rebuilding a spreadsheet for this month’s packet only recreates the problem next month. Discontinuing employment statistics because finance dashboards exist abandons people metrics council needs. A printed binder of last year’s headcount with no monthly refresh is stale evidence. Exam caveat: SPHR business intelligence for employment statistics must be reliable and repeated for strategic oversight. Operational check: build a governed HR data feed with shared definitions, refresh monthly for council, reconcile to finance where appropriate, and retire ad-hoc spreadsheet packets for civic employment reporting. Council employment statistics that change definition each month undermine strategy debates about vacancy and overtime. A governed HR BI feed matching finance’s reliability makes people numbers comparable over time and ends night-before spreadsheet governance. Assign an owner, a measure, and a review date so the choice remains visible in civic oversight.