Principal Financial Planning Governance Director — Wealth Event-to-Resource Forecasts

The mandate

A wealth-operations business forecasts staffing from aggregate account volumes even though the work arrives through very different events. New-account onboarding, scheduled periodic reviews and returned or exceptional cases create demand at different times and can remain open across planning periods. This five-month project begins on 26 October 2026 and produces an event-to-resource planning model, a carried-backlog ledger and an assumption-revision control book. It concerns the resources needed to perform operations, not customer investment advice or the professional determination of review obligations.

Milestone one on 11 December 2026 delivers an event-and-resource baseline separating arrivals, completions and reclassified cases by cohort. Milestone two on 5 February 2027 supplies the timed-demand forecast, backlog scenarios and approved routes for revising workload and resource assumptions. Final delivery on 26 March 2027 comprises an internally run planning cycle and tested governance transfer. Three working days weekly cover analysis and Mumbai sessions. Operating owners provide approved review schedules and effort evidence; the model must distinguish when work becomes due from when teams can actually complete it.

The CFO and wealth operations head jointly accept each stage. Baseline totals must reconcile beginning backlog, arrivals, completions and authorised signed reclassifications to ending backlog, with resource costs tied to approved finance records. Design tests shift review dates, return a completed case and constrain throughput without losing outstanding work. Final acceptance requires internal owners to refresh a withheld period, explain the financial effect of changed cohort timing and route a deliberately unsupported effort revision to the correct approver. The fee is paid 20%, 40% and 40% across accepted stages, independent of subsequent budget achievement.

The sponsor supplies historical plans, ledger and staffing records, pseudonymised event histories, authorised due-date rules and a seven-person finance-and-operations working group. Finance retains budget approval and accounting policy; operating managers own staffing and throughput commitments; professional control owners determine review requirements. Customer proposition redesign, workforce restructuring and technology procurement remain excluded. Additional centres or data periods require a written variation revising effort, calendar and acceptance samples. The transfer must leave owners able to challenge an attractive resource forecast when its apparent improvement merely pushes unresolved work beyond the visible planning horizon.

What you will own

• Establish the cohort baseline from onboarding, scheduled-review and exception events, reconciling case movements so demand arriving during a period remains distinguishable from work carried into it.
• Construct the backlog ledger with approved reclassification rules, preventing returned cases, deferred reviews or incomplete onboarding from disappearing when teams refresh the monthly resource forecast.
• Design workload timing from authorised due dates and observed effort, retaining distinct assumptions for ordinary and exceptional cases rather than treating every active account as an equal monthly demand unit.
• Build resource and financial scenarios for changed arrivals, review schedules and throughput constraints, exposing when temporary capacity pressure becomes a continuing backlog rather than an apparently lower operating requirement.
• Specify assumption-revision rights with finance and operations owners, distinguishing an evidenced workload update from a throughput promise or professional-rule change requiring a different authority's review.
• Test shifted-date, returned-case and constrained-capacity scenarios against known backlog outcomes, documenting financial consequences and approval exceptions before sponsors accept the event-to-resource planning method.
• Transfer the framework through an internally operated withheld-period cycle, leaving cohort definitions, revision evidence and remaining data limitations usable without the consultant repairing the forecast or resolving every disputed assumption.

Candidate qualifications

• Show financial planning judgement where event timing, carried work or exception demand changed the resource requirement despite a stable aggregate customer population. Explain the driver you selected, the backlog you preserved and the financial recommendation that followed. Comparable NBFC, depository, payroll or other service-operations evidence is relevant when it establishes personally accountable FP&A method rather than only participation in a wider transformation.
• Bring 18–22 years in finance with senior budgeting or governance responsibility and rigorous management-accounting competence. You must reconcile arrivals, completions and reclassifications, distinguish demand from throughput and translate evidenced resource assumptions into financial forecasts. Professional finance education or equivalent proven depth is expected; the project requires operational finance judgement rather than investment-adviser licensing or authority to determine customer-review rules.
• Explain a planning disagreement where an attractive forecast depended on deferring work, compressing effort or assuming unsupported capacity. Describe the evidence you requested, the authorised revision route and the alternative made visible to executives. Experience should demonstrate constructive challenge of operating managers while preserving their staffing decisions and the professional owner's authority over the service obligations generating the demand.
• Reserve three days weekly over five months, including onsite acceptance sessions in Mumbai, and evidence transfer of a model with testable event and assumption controls. Describe a scenario that exposed a flaw in your initial method and how internal owners later handled it independently. Practical scope control and clear writing matter because unseen cases must remain explainable without undocumented consultant adjustments or a continuing dependence on your interpretation.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 12 October 2026. Mandate reference CVU-CON-2026-IND-125.