Why this is urgent right now

• Tell me briefly why you are exploring a new workforce planning approach now.
• When did a CEO or CFO last ask for workforce cost scenarios you could not produce? Options: Within the last 30 days, 1-3 months ago, 3-6 months ago, More than 6 months ago, Never directly asked
• How often do your current headcount models get updated during a typical quarter? Options: Daily, Weekly, Monthly, Quarterly, Ad hoc
• Who on your leadership team feels the most pressure from gaps in workforce forecasting? Options: CHRO, CFO, Head of FP&A, Head of HR Analytics, Business unit leader, Other
• Describe the single most important outcome you would measure to call a workforce planning project a success.

Where forecasts break when decisions matter

• Which single forecasting failure would make you walk away from a vendor or internal solution immediately? Options: Numbers that cannot be reconciled to the GL, Inability to model hiring and attrition scenarios, Outputs not credible for CFO/board decks, No way to map skills to roles, Other
• Walk me through the last time a workforce forecast led to a hiring or layoff decision you later had to reverse.
• How much did that reversal cost in cash or lost productivity, best estimate? Options: Less than 0.1% of payroll, 0.1% to 0.5% of payroll, 0.5% to 1% of payroll, More than 1% of payroll, Unknown
• What downstream processes stopped working when the forecast proved wrong? Options: Budget reconciliation, Talent sourcing and pipeline, Org redesign decisions, Compensation planning, Headcount approval cycles, Other
• If that specific failure were fixed, how would the CFO's confidence in your workforce plan change for the next quarter? Options: Significantly increase, Somewhat increase, No change, Worse

Board-ready objectives the CHRO must deliver

• If the CHRO had to present workforce scenarios to the CEO and board in 12 weeks, what one metric would they be judged on? Options: Total labor cost impact, EBITDA impact, Headcount by function, Cost per FTE, Ability to show multiple credible scenarios
• Which financial KPIs must tie directly to any headcount scenario for it to be considered credible? Options: Total labor cost, Operating margin impact, EBITDA impact, Cost per role band, Department-level budget variance
• Who will own the final signoff on those KPIs inside finance? Options: CFO, VP of FP&A, Controller, Head of Finance Systems, Shared finance and HR signoff
• At what cadence do leaders expect scenario updates during a planning cycle? Options: Weekly, Biweekly, Monthly, Quarterly, Ad hoc on request
• Would you still proceed with a POC if the platform cannot show financial impact by department in a board-ready slide? Options: Yes, No, Maybe, with conditions

Foundations: the data we need to build anything credible

• Name the one data gap today that most prevents your team from producing a CFO-ready workforce cost scenario.
• List the systems that hold your master records for headcount, compensation, and the GL. Options: Primary HRIS, Payroll system, ERP/GL, Applicant tracking system, Time and attendance, Org chart tool, Other
• Identify the owners who control access to those systems and indicate whether API credentials are available. Options: Yes, API available, Yes, SFTP or scheduled reports, No, manual exports only, Unknown
• Describe the last time your team reconciled HRIS and GL differences, what took the most time?
• Would you be able to commit dedicated resources to clean data if reconciliation showed more than 10% mismatched records? Options: Yes, full dedicated team, Yes, part-time resources, No, not available, Need to escalate

People, process, and who cares enough to win

• List the decision makers who must sign off to move from POC to rollout and the single requirement each has to be convinced.
• Walk me through how a contested assumption in the model gets resolved today.
• Estimate the number of analyst or engineering hours per week you could allocate for the POC. Options: 0-10 hours, 10-25 hours, 25-50 hours, 50+ hours
• Name the audiences who need tailored outputs versus a single CFO-facing slide. Options: CFO/FP&A, CHRO/HR Leadership, Business unit leaders, Talent acquisition, People analytics team, Other
• Can the POC proceed if business unit leaders refuse to share headcount and cost data? Options: Yes, with anonymized or sample data, No, access is required, Depends on the business unit

Alternatives you are weighing and why

• What alternatives are you currently evaluating, including internal build and incumbent vendors? Options: Incumbent vendor, Internal build, Spreadsheet-based enhancement, Consulting engagement, Do nothing / delay
• Is there an internal solution being proposed instead of partnering with an external platform? Options: Yes, No, Under consideration
• Under what conditions would you choose to stay with your current approach rather than change?
• Point to the top three capabilities that have impressed you in other solutions so far. Options: Speed of scenario runs, GL reconciliation and auditability, Flexibility of modeling rules, CFO-ready outputs, Ease of integration, Other
• For each alternative you listed, name the primary risk that would need to be resolved for you to choose it.

Hard deadlines, acceptance criteria, and decision triggers

• Assuming the POC hits agreed targets, what would stop you from signing the contract that same week?
• Provide your top three acceptance criteria the POC must meet to be judged successful.
• Please indicate the primary owner responsible for certifying that integrations are complete and accurate. Options: Head of HR Systems, VP of FP&A, IT Integration Lead, External consultant, Other
• Within what timeframe could you provide sandbox credentials and representative test data after SOW signature? Options: Within 1 week, 1-2 weeks, 2-4 weeks, More than 4 weeks, Not able to provide
• Could a security or legal review longer than 6 weeks push the project beyond your current fiscal window? Options: Yes, No, Possibly, needs negotiation

Integration endpoints and technical access patterns

• When a required system only supports manual extracts, what interim integration approach would your team accept for the POC? Options: Scheduled SFTP exports, Secure file share with agreed format, Manual uploads by your team, Mock/anonymized dataset provided by you, Not acceptable
• Provide a short checklist of the employee-level fields available in your HRIS export, for example job code, manager, location, hire date, termination date, base salary, and benefits cost.
• Identify the contact who will provide API credentials and indicate whether they manage the authentication token lifecycle. Options: Yes, they manage tokens, No, vendor must manage tokens, Unknown / need to confirm
• Select the environments your IT can provision for testing. Options: Sandbox, Staging, Production read-only, No separate environment available
• Can your team provide a realistic anonymized dataset matching production schema within two weeks if a sandbox is not available? Options: Yes, No, Yes, but needs more than two weeks, Conditional

Adoption risks and the actions that will tip the scales

• Point to the human behavior or political risk most likely to derail adoption of a new workforce planning tool.
• Explain how you currently surface model assumptions to business unit leaders and how disagreements are resolved.
• Tell me which training or change activities have proven most effective in prior HR or Finance system rollouts. Options: Role-based workshops, Office hours with analysts, Recorded training modules, Embedded templates and playbooks, Executive sponsorship communications, Other
• Outline the adoption metrics you will track in the first six months post-deployment.
• At what threshold of manager adoption would you consider the project to have stalled, and what remediation would you require? Options: Less than 20% usage, 20-40% usage, 40-60% usage, Depends by business unit

• Solution Experience — Scenario Modeling Walkthrough

• Confirm the current state and its cost
• You confirm the demonstrated scenario replaces spreadsheet rework and produces CFO-facing outputs you would trust for board-level discussion.
• Prepare a sample forecast comparison using the provided business-unit dataset and deliver the comparison to the current spreadsheet within 5 business days.
• You agree on the representative business unit, the exact datasets to supply, and the acceptance criteria for the POC.
• Agree representative business unit and success criteria
• Provide a reconciled extract of HRIS headcount, payroll cost, organizational structure, and any existing attrition assumptions for the chosen business unit.
• You identify any remaining evidence or adjustments needed before advancing to the POC decision.
• Run a baseline-to-what-if scenario using your context
• Confirm the CFO-facing metrics (for example, total workforce cost by quarter, cost per FTE, and three-year forecast variance) and the three-year planning horizon to validate against.
• Stress test attrition, hiring, and redeployment assumptions
• Schedule a follow-up session to review the delivered forecast, discuss remaining assumptions, and agree next steps for a POC.
• Validate the future state with a direct question

• Solution Experience — Scenario Modeling Walkthrough
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Connect and Map HRIS Headcount Data
• Connect and Map Finance/ERP Cost Data
• Ingest, Reconcile, and Remediate HRIS/Finance Data
• Import and Normalize Skills Taxonomy
• Configure Scenario Engine and Templates
• Build Multi-Year Workforce Forecast Model
• Configure Attrition, Hiring, and Promotion Rules
• Run Restructuring and What-If Simulations
• Produce CFO-Ready Financial Scenario Exports
• Deploy Model Access Controls and Versioning
• Train HR and Finance Power Users
• Enterprise Rollout Handover and Model Operationalization

Connect and Map HRIS Headcount Data

• For your current HRIS, which integration surface will we use (API, scheduled CSV export, SFTP feed)? Options: API, Scheduled CSV export, SFTP feed, Database replica, Other
• Which HRIS record types must be included in scope (employee active/inactive, contingent workers, contractors, contingent assignment records)? Options: Active employees, Terminated employees, Contingent workers/contractors, Position objects/org positions, Other
• How many headcount records exist in the chosen business unit snapshot (approximate count of employee rows in HRIS export)? Options: Less than 1,000, 1,000-5,000, 5,001-25,000, More than 25,000
• Provide the canonical HRIS field names we must map (employee id, job code, job family, manager id, cost center, hire date, termination date).
• List the primary org chart artifact you will supply (position hierarchy CSV, HRIS position object export, org chart PDF). Options: Position hierarchy CSV, HRIS position object export, Org chart PDF, No org chart available
• Identify any custom job code conventions or pay components (e.g., jobcode suffixes, blended pay bands) that require mapping to standard job families.

Connect and Map Finance/ERP Cost Data

• Which finance integration method will you provide for payroll and benefits cost (ERP API, GL journal extracts, payroll vendor CSV)? Options: ERP API, GL journal extracts, Payroll vendor CSV, Manual spreadsheet
• Which GL account ranges or cost center attributes should be used to map payroll expense to organizational units in the model?
• How frequently are payroll costs posted to the GL that must be reconciled (monthly close, biweekly accrual, other cadence)? Options: Monthly close, Biweekly accrual, Semi-monthly, Ad hoc
• Provide the canonical payroll cost fields available in your extract (gross pay, employer tax, benefits burden, bonus accruals, payroll period start/end).
• List any multi-currency or localized payroll regimes in the pilot BU that require FX or local statutory mapping. Options: Single currency, Multi-currency (requires FX), Country-level statutory payroll differences, Other
• Identify any finance-side business rules that affect cost allocation (e.g., pooled benefits, labor burden allocation, capitalizable labor).

Ingest, Reconcile, and Remediate HRIS/Finance Data

• When we run an initial reconciliation, which canonical source should be treated as primary for headcount-to-cost mapping (HRIS headcount snapshot, payroll journal, GL payroll accrual)? Options: HRIS headcount snapshot, Payroll journal, GL payroll accrual, Hybrid rule-based
• Which reconciliation thresholds must be met for POC acceptance (for example maximum headcount mismatch percentage or dollar variance to GL)?
• Provide examples of recurring data-quality issues in your HRIS/ERP exports (missing cost center, inconsistent job codes, duplicate employee ids).
• Specify the allowed remediation actions for mismatches (auto-map by rule, flag for manual owner review, create a ticket in your HRIS ticketing system). Options: Auto-map by rule, Flag for manual review, Create ticket in HRIS ticketing, Other
• Who in your organization will own day-one reconciliation exceptions (HR data lead, payroll lead, finance analyst)? Options: HR data lead, Payroll lead, Finance analyst, Shared ownership
• Indicate the acceptable window for reconciliation completion after a data refresh (hours/days) for the pilot BU. Options: Within 4 hours, Within 24 hours, Within 72 hours, Within 7 days

Import and Normalize Skills Taxonomy

• Which skill source will you provide for normalization (HRIS skill tags export, LMS competency report, Talent profile CSV)? Options: HRIS skill tags export, LMS competency report, Talent profile CSV, No current skill source
• Which skill identifiers do you currently use that must be mapped (skill id, skill name, proficiency level, last-assessed date)?
• Describe the expected skill taxonomy depth for the pilot BU (broad job-family skills only, granular technical skills with proficiency bands). Options: Job-family level, Role-specific granular skills, Proficiency-banded skills, Undefined
• Identify any regulatory or certification attributes that must be surfaced with skills (security clearance level, professional license id, certification expiry).
• Specify the mapping rule preference when multiple skill sources conflict (prefer HRIS, prefer LMS, prefer most recent assessment). Options: Prefer HRIS, Prefer LMS, Prefer most recent assessment, Manual adjudication
• List the sample skill taxonomy files you will upload for normalization (attach sample CSV with skill columns, provide API read access). Options: Sample CSV provided, API read access provided, No sample yet

Configure Scenario Engine and Templates

• Which scenario types must be templated for the pilot (hiring freeze, 10% workforce reduction, targeted reskilling scenario)? Options: Hiring freeze, Headcount reduction, Targeted reskilling, Growth hiring scenario, Custom
• How many baseline template parameters should be editable by power users (attrition rate, hiring lag days, salary escalation, benefit rate)? Options: 1-3, 4-6, 7-10, More than 10
• Provide the CFO-facing metrics that must appear in each scenario template (total payroll cost, FTE count by cost center, savings delta to baseline).
• Identify the required template export formats for presentations (P&L variance CSV, PPT-ready export, GL journal simulation CSV). Options: P&L variance CSV, PPT-ready export, GL journal simulation CSV, Other
• Specify whether scenario runs should preserve audit history and version tags for audit (yes/no). Options: Yes, No
• Select the max run-time expectation for large scenarios in pilot (time-to-first-results goal for 5,000 headcount rows). Options: Under 1 minute, 1-5 minutes, 5-15 minutes, Over 15 minutes

Build Multi-Year Workforce Forecast Model

• Which planning horizon should the forecast model support for the pilot BU (1 year, 3 years, 5 years)? Options: 1 year, 3 years, 5 years, Other
• How should salary inflation and merit increases be modeled (flat percentage per year, tiered by job family, driver-based by revenue growth)? Options: Flat percentage, Tiered by job family, Driver-based, Other
• Provide the expected cadence for model refresh and snapshot dates that tie to your finance close (monthly snapshot, quarter-end). Options: Monthly snapshot, Quarter-end, Biweekly, Ad hoc
• Identify any capitalizable labor or shared service allocations that must be split across GL projects in the multiyear model.
• List which headcount attributes must be time-varying in the forecast (hire date, termination date, FTE fraction, role changes).
• Estimate the maximum number of model dimensions we must support for the pilot (cost center, business unit, job family, location). Options: 1-2, 3-4, 5-6, More than 6

Configure Attrition, Hiring, and Promotion Rules

• Which historical attrition cohorts are available for modeling (12-month, 24-month, voluntary vs involuntary)? Options: 12-month, 24-month, Voluntary only, Voluntary and involuntary
• How should hiring lead time be measured for the pilot (time-to-offer, time-to-start, average offer acceptance lag)? Options: Time-to-offer, Time-to-start, Offer acceptance lag, Other
• Specify promotion/grade-change rules we should include (fixed promotion cadence, manager-initiated promotions, automatic grade progression). Options: Fixed cadence, Manager-initiated, Automatic progression, None
• Provide your target vacancy fill-rate thresholds by job family that the model should assume for capacity planning.
• Indicate required constraints on hiring in scenarios (headcount caps by cost center, budget envelope in USD).
• Who will be the owner for maintaining attrition/hiring rule sets after deployment (HR analytics lead, TA lead, finance modeller)? Options: HR analytics lead, Talent acquisition lead, Finance modeller, Shared ownership

Run Restructuring and What-If Simulations

• Which restructuring levers must be supported in the pilot (headcount reduction by percent, role consolidation, location closure)? Options: Percent reduction, Role consolidation, Location closure, Targeted team reductions
• How should severance and one-time costs be modeled when running a reduction scenario (per-head fixed cost, salary multiple, legal and outplacement buckets)? Options: Per-head fixed cost, Salary multiple, Legal/outplacement buckets, Other
• Provide the business rules for protected populations or union-covered roles that constrain automated reductions.
• List the representative simulation inputs you expect us to run during the POC (10% reduction, 20% cost save, targeted skilling reallocation).
• Indicate which stakeholders must review simulation outputs before we label a run as review-complete (CFO, CHRO, BU leader). Options: CFO, CHRO, BU leader, Finance business partner
• Specify whether simulation results need scenario traceability to source rows (yes/no). Options: Yes, No

Produce CFO-Ready Financial Scenario Exports

• Which export format does your finance team require for scenario P&L reconciliation (GL-mapped CSV, ledger journal CSV, presentation-ready slide export)? Options: GL-mapped CSV, Ledger journal CSV, PPT export, Other
• Identify required fields in the CFO export (effective date, GL account, cost center, debit/credit, commentary code).
• Describe any mandatory reconciliation steps your finance team performs on scenario exports (manual journal review, variance to prior quarter, tax provision adjustments).
• Specify the maximum allowable variance to the GL for an export to be considered CFO-ready (percentage or dollar threshold).
• Indicate if export templates must include slide-ready commentary lines for board presentations (yes/no). Options: Yes, No
• What evidence will validate that CFO-facing exports are credible for board use (e.g., reconciliation report, variance-to-GL under threshold, signed finance review)?

Deploy Model Access Controls and Versioning

• Which single sign-on (SSO) protocol will you require for pilot users (SAML 2.0, OAuth2, OpenID Connect)? Options: SAML 2.0, OAuth2, OpenID Connect, No SSO
• Which role archetypes must be defined for the pilot (model viewer, scenario author, finance approver, admin)? Options: Model viewer, Scenario author, Finance approver, Admin, Custom
• Indicate whether you require row-level or cost-center-level access controls for sensitive headcount slices. Options: Row-level, Cost-center-level, Org-unit-level, No fine-grained controls
• Provide your expected version retention policy for model snapshots (retain N versions or retain for X months). Options: Retain 5 versions, Retain 12 versions, Retain for 6 months, Custom
• List the user provisioning method we should use for the pilot (SCIM user provisioning, manual invite, CSV bulk import). Options: SCIM, Manual invite, CSV bulk import
• Identify any audit or compliance logs required (who ran scenario X, who approved export Y).

• desired_state
• current_state
• stakeholders
• gaps
• success_criteria
• decision_readiness
• desired_state
• decision_readiness
• current_state
• success_criteria
• gaps
• stakeholders
• desired_state
• success_criteria
• stakeholders
• gaps
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Subscription Agreement / Order Form
• Data Processing Agreement (DPA)
• Data Access & Authorization Agreement
• Acceptance Criteria & Sign-off
• Change Order Agreement
• Security & Compliance Addendum (conditional)
• Payment & Billing Schedule Addendum

• Go-live Health Check
• First Measurement Review
• Acceptance Gate Review
• Quarterly Outcome Review
• Annual Success Review and Lessons Learned

• Maintain a prioritized backlog of enhancement requests with target delivery windows.
• Re-confirm acceptance criteria and owners
• Formal acceptance decision recorded for each criterion documented in the Proof of Concept.
• Verification that the incumbent planning artifacts are archived or retired and fallback habits are closed.
• If required, remediation plan with dates and checkpoints to reach acceptance within a defined window.
• Publish the acceptance decision and archive the meeting evidence to the shared workspace.
• Execute the incumbent wind-down checklist and confirm archive completion in writing.
• If remediation required, open a remediation tracker entry with specific checkpoints and dates.
• Metrics dashboard review
• Confirm whether headcount forecast accuracy and user adoption are on track to meet targets.
• Update the shared dashboard with the quarter's reconciled data and distribute to stakeholders.
• Publish the prioritized enhancement backlog and scheduled delivery quarter.
• Run a short user proficiency refresher and record attendance and completion rates.
• Year-to-date outcome validation
• Confirm annual outcomes measured against the Proof of Concept targets and accept the reconciled results.
• Document and distribute a lessons-learned summary to guide future rollouts and model governance.
• Publish the annual outcome report with reconciliations and lessons learned to the shared workspace.
• Confirm the owner and SLA for the shared issue and enhancement request channel and document the process.
• Schedule the first quarterly outcome review for the new fiscal year and circulate the agenda and required data extracts.
• All production integrations validated or assigned remediation with target dates.
• Acceptance criteria from the Proof of Concept are re-confirmed with named owners.
• Short-term runbook and escalation path agreed for the next 30 days.
• Publish a one-page runbook with integration status, data reconciliation steps, and escalation contacts.
• Perform and document a full reconciliation between HRIS headcount and platform headcount for the pilot business unit.
• Log any production defects in the shared issue channel and assign a target resolution date.
• Present first-period results
• Clear understanding of where headcount and cost variances originate and which fixes will move the metrics.
• Remediation plan with target dates that aligns progress to the acceptance criteria in the Proof of Concept.
• Deliver corrected data extract and re-run the key scenarios within the agreed timeline.
• Document model assumption updates and publish a short note describing their expected impact on headcount and cost variance.
• Schedule a technical follow-up for any unresolved integration errors before the acceptance gate.
• Restate acceptance criteria from the Proof of Concept
• Present outcome data against each criterion
• Deployment and integration validation
• Data quality and reconciliation review
• Open issues and blocker burn-down
• Lessons learned
• Early adoption signals
• Pass/fail determination and documented decision
• Root-cause diagnosis
• Enhancement request triage
• Shared channel and escalation review
• Open issues and immediate remediation
• Operational adjustments and schedule
• Agree corrective actions and timeline
• Incumbent system wind-down verification
• Agree next-year monitoring cadence
• Agree short-term runbook
• Remediation plan for any failed criteria