Construction Stage-Gate and Change Evidence Protocol Lead

The mandate

The defined problem is that stage-gate approvals and change orders do not consistently carry the evidence an owner needs to judge readiness and consequences. The consultant will build and pilot a protocol for agreed package interfaces. The project will not certify engineering designs or resolve contractual disputes through an assurance label.

Deliverables are a stage-gate evidence matrix, change-order decision file and a pilot-tested owner approval procedure. Each gate must state what is usable, what remains conditional and who possesses approval authority. Change files must explain the difference between an instruction needed now and a commercial consequence that still requires evidence.

The engagement starts on 19 October 2026 and ends on 18 February 2027. Milestone one on 23 November delivers sampled gate and change-file gaps. Milestone two on 11 January provides the redesigned protocol and pilot cases. Milestone three on 18 February delivers pilot findings, revised procedures and owner-team transfer. Three days weekly are expected, including approved site observation.

Acceptance belongs to the owner sponsor and designated commercial and delivery owners. They must process a fresh gate and a contested change using the protocol, identifying missing evidence, approval limits and the decision consequences. Routine cases alone do not establish acceptance; the pilot must include a conditional handover and a time-sensitive variation.

The sponsor supplies authorised package records, approval delegations and nominated users. Gurugram remains the primary location, with site travel planned in the scope. Contract negotiation, litigation support, detailed design and technology procurement are excluded. Additional package types or a request for formal technical certification require a separately authorised engagement rather than silent extension of this fee.

What you will own

• Sample stage-gate and change files to identify missing readiness and consequence evidence, classifying substantive judgement gaps separately from incomplete administrative records.
• Design the gate matrix around usable deliverables and unresolved conditions, preserving technical acceptance authority while making owner-side decisions clear and inspectable.
• Build a change-order file that links instruction, scope, time and cost evidence, preventing provisional estimates from being represented as fully agreed consequences.
• Map approval routes to the delegated register, specifying where an urgent decision can proceed and where owner consent must be obtained first.
• Pilot the protocol on a conditional handover and contested variation, observing whether users can identify both evidence limits and the available decision options.
• Revise the forms using pilot findings, removing duplicate signatures while retaining the reasoning that makes a stage or change approval defensible.
• Transfer the protocol through fresh-case execution by owner users, recording residual limitations and maintenance responsibility before final acceptance is requested.

Candidate qualifications

• Show hands-on programme assurance, project direction or commercial-interface work in construction. Explain a stage approval that lacked meaningful readiness evidence and how the owner-side decision process was improved.
• Demonstrate practical understanding of variations and provisional consequences. Candidates should describe a time-sensitive change where instruction and final commercial agreement were different decisions, and show how the distinction was retained.
• Evidence protocol design that survived real user execution rather than a workshop demonstration. Provide a pilot failure, the reason the process was impractical and the revision made without losing the control objective.
• Show clear boundaries between owner assurance, engineering certification and contract dispute resolution. Explain which professional approval you relied on and how you avoided presenting a programme review as statutory or technical sign-off.
• Provide consulting acceptance proof, including named user roles, fresh test cases and a maintenance process. Confidential access, version control and scope discipline are required; the project needs hands-on evidence design, not an unverified claim that all construction risk can be eliminated. Show how conditional readiness was documented when one package could be used but a dependent interface remained unresolved. Candidates must explain the available owner decision, the retained technical approval and the evidence that prevented a stage-gate signature from implying unrestricted completion.

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