Installation Milestone, WIP and Cash-Cycle Model Lead

The mandate

The problem is that an installation milestone change cannot be consistently translated into WIP, job margin and collectible cash. The consultant will build that decision bridge for agreed job families. The project does not certify milestone completion or negotiate contract variations.

Deliverables are a milestone-to-finance model, a WIP judgement register and cash-cycle decision files. The model must retain contractual billing conditions and operational evidence separately. A delivery date change should alter the relevant cash and remaining-cost assumptions without automatically creating a different revenue treatment unsupported by policy.

The project covers four months from 19 October 2026 to 18 February 2027. The 23 November milestone establishes job definitions and the reconciled baseline. The 11 January milestone delivers model logic and exception tests. At the 18 February final milestone, users complete validation and receive the controlled model and maintenance pack. Three delivery days weekly include agreed job-owner workshops.

Acceptance is by the finance-commercial head and nominated installation reporting owner. They must process a fresh milestone change, reconcile WIP and cost-to-complete consequences and explain the resulting cash outlook. The test must include a disputed completion condition and an approved variation. Matching only aggregate financial totals will not establish that the model preserves the real decision.

The sponsor provides authorised job contracts, progress records, cost schedules and an internal model custodian. Mumbai is primary with scheduled regional remote sessions. System implementation, collection execution and engineering certification are excluded. Additional job families with materially different milestone mechanics need approved scope control; the true project fee pays for an accepted artifact, not unlimited job-finance support.

What you will own

• Define milestone states and billing prerequisites from authorised contracts, retaining the operational evidence needed before a finance consequence can be considered supportable.
• Reconcile sampled jobs across progress, cost and WIP schedules, classifying source gaps and policy questions instead of forcing a clean baseline through plugs.
• Build model logic for milestone delays and approved variations, separating their effect on remaining cost, valuation judgement and collectible cash.
• Create a WIP register that retains rationale and approval authority, enabling users to explain why a judgement changes rather than merely overwrite a figure.
• Test disputed completion conditions and time shifts against the model, documenting where insufficient delivery evidence prevents a confident finance conclusion.
• Validate fresh jobs with accounting and installation users, revising ambiguous assumptions while preserving legitimate differences in contract mechanics, with an accountable source owner.
• Transfer the controlled model through observed custodian execution, obtaining a reproducible milestone-change test and ownership of unresolved source limitations before final acceptance.

Candidate qualifications

• Demonstrate hands-on modelling or job finance in equipment installation or analogous contract delivery. Explain a milestone change and the different effects it had on WIP, remaining cost and cash.
• Show technical understanding of cost-to-complete and contract billing conditions. Candidates should describe a case where apparent operational progress did not support the assumed financial consequence.
• Provide a model validation example involving disputed or incomplete source evidence. Explain how uncertainty was retained and which internal authority resolved the accounting or technical question.
• Evidence consulting acceptance and internal transfer, including a fresh job processed by the model custodian. Show how version control and scope boundaries prevented the artifact from becoming an uncontrolled monthly reporting service.
• Demonstrate professional finance capability and careful handling of sensitive job records. The project does not confer engineering or contract-signing powers. Demonstrate a cost-to-complete update where an approved variation changed remaining effort before it changed a billable milestone. Explain why revised cost exposure, supported WIP and collectible cash followed different evidence and approval gates. For a variation operationally requested but not commercially approved, retain its effect as a separate scenario. Show how the custodian reran a prior job case after changing a milestone rule, identified outputs that should remain unchanged and obtained reviewer approval before releasing the revised model.

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 10 October 2026. Mandate reference PCT-CON-2026-IND-12.