Your HR plan and your financial model live in different systems, so you spend the planning cycle collecting numbers instead of deciding what to do with them. This article shows how a driver-based HR model in CCH Tagetik connects headcount to the P&L, from model setup to scenario comparison.
Why does HR planning keep running behind the numbers?
HR and Finance often work in separate systems with disconnected data. HR knows the headcount. Finance owns the budget and the P&L. Someone stitches the two together in Excel, and by the time the result reaches the table, it describes a situation that has already changed.
You probably recognize the symptoms:
- Excel models that break as soon as they grow
- Data spread across systems that don't talk to each other
- Planning cycles so long that the numbers are old on arrival
- Limited trust in the outcome, from HR and Finance alike
These problems share one root cause. Your HR planning has no connection to your financial model, and the data lives in several places. As long as that stays true, you react to the numbers instead of steering with them. A planning platform like CCH Tagetik closes that gap with a driver-based model.
What does a driver-based HR model need?
A driver-based model calculates its results from a small set of inputs, so a change in one input changes the outcome everywhere. In CCH Tagetik you define four building blocks in the first step of the workflow. Drivers are the key variables, such as FTE and salaries. Scales are the dimensions you analyze by, such as level, role or country. Outputs are the results you want the model to calculate. Formulas hold the logic that turns drivers and scales into those outputs. For the forecasting side of the same platform, see Modeling & Forecasting with CCH Tagetik.
Tagetik offers a predefined set of driver and scale labels. You activate the ones your model needs and give each a business definition, so HR and Finance mean the same thing when they say "FTE". You can configure all of this in the Tagetik web interface or through the Excel add-in.
The workflow then runs in two phases. In the preparatory phase you define the model structure and the outputs you want. In the analysis phase you calculate, validate and analyze the results. You can run it for one entity, or once for all entities by selecting the top node.
How do you get employee data in without rebuilding Excel?
Once the structure is set, you add data. For each reporting period you enter the actual values for your drivers and scales, such as workforce numbers and salary developments, either by typing them in or by uploading them.
For employee-level data, Tagetik's ETL process (extract, transform, load) takes a CSV file. You select the file, click Run, and the data lands in the model. A control report then shows what was loaded for each employee. The report is read-only, so you can check the input before any calculation starts. If you want to run these loads yourself, our Data Loading Training on 17 November covers Quick Data Load and ETL hands-on.
What happens when you run the calculation?
One step, a data transformation package, applies your formulas to every employee in every period. It determines the relevant drivers and scales per person and writes the outputs, such as personnel costs and headcount development, into the system. The logic sits in the model instead of in individual spreadsheets, so the results follow the same rules wherever you run them.
How do you test a hiring decision before you make it?
The analysis phase starts with a data entry that lists the values for each employee. You edit them row by row and add a comment per person to document the reason. When you change the FTE of an individual, the headcount trend in the chart moves with it.
Say you want to scale up in one country or role, or freeze hiring. You change the input and see the effect on headcount straight away, without building a new version of a spreadsheet.
How does a workforce change show up in your P&L?
The last step connects headcount to finance. A Profit & Loss report shows personnel costs, lets you compare results against budget or forecast scenarios, and helps you analyze the variances. The Scenario Comparison report puts forecast, budget and actuals side by side in one P&L view, with charts that show the cost impact of your workforce decisions.
When your inputs change, you rerun the calculation to reapply the formulas, and the comparison reflects the new numbers. That makes planning a process you can repeat whenever the data changes, and it gives HR and Finance the same figures to work from. More on the planning side of the platform: Budgeting & Planning with CCH Tagetik.
See the CCH Tagetik HR module in action
Frequently asked questions
What is a driver-based HR planning model?
A driver-based model calculates results from a set of inputs called drivers, such as FTE and salaries. You analyze them by scales such as level, role or country, and formulas turn them into outputs like personnel costs. When you change a driver, every output that depends on it changes with it.
Do I have to work in the web interface, or can I use Excel?
You can use either. In CCH Tagetik you configure the model in the web interface or through the Excel add-in. The demo walks through the web interface.
How does employee data get into the model?
You can enter values per period by hand or upload them. For employee-level data, Tagetik's ETL process loads a CSV file, and a read-only control report shows what was loaded for each employee.
Can I plan per entity or for the whole group?
Both. You can run the workflow for a single entity, or once for all entities by selecting the top node.
.webp)