Approaches to Managing Incomplete Client Inputs Under a Fixed Price EPC Contract
Pham Van PhuongProject Manager| FUJI CAC JOINT STOCK COMPANYHo Chi Minh, Viet Nam
I’m currently facing a challenge in a Fixed Price (EPC) project: the client has not yet finalized or delivered the required inputs (requirements, technical documents, or data). This situation is creating uncertainty for both schedule planning and contractual obligations.
What would be your recommended approach. Saving Changes...
The ideal way to address such situations is to have deadlines built into the contract for client accountabilities indicating the impacts (e.g. day for a day) of delays.
If the contract does not stipulate those, then it comes down to properly analyzing and communicating the risks created by the delays to the client and other key stakeholders so they are fully aware of the impacts to the project's objectives.
Kiron
...
1 reply by Pham Van Phuong
Aug 19, 2025 11:47 PM
Pham Van Phuong
...
Thank you all for your valuable insights.
I agree that having client accountabilities and deadlines in the contract is ideal. If that is not the case, proper risk analysis and effective communication are essential to ensure the client and stakeholders clearly understand the impacts.
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
hello Pham, well, under a fixed-price EPC contract, it should come down to balancing protection and progress. The best approach I've seen are:
- Contractual safeguards defining client responsibilities, document assumptions/exclusions, and ensure a clear change order process.
- Keep an updated Risk management process, doing a gap analysis early, log missing inputs as risks, and escalating delays formally.
- During execution, move forward with documented assumptions, plan flexible schedules, and build in contingencies.
- Communication & keeping records is critical, the inputs should visible in regular meetings, track requests in writing, and preserve evidence.
If inputs remain incomplete, claims and variations are the last resort, but a proactive, collaborative approach usually prevents escalation.
...
1 reply by Pham Van Phuong
Aug 19, 2025 11:49 PM
Pham Van Phuong
...
Thank you all for your valuable insights.
Lissette’s point on balancing protection and progress resonates well with me. Documenting assumptions, keeping the risk register updated, and escalating formally while maintaining a collaborative tone are indeed very practical approaches.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Pham, this is a common problem on fixed price contracts.
I once ran a fixed price project based on 11 pages of contract requirements, resulting in a 600-page requirements document, with no changes identified, only detailing the headlines. In the end, the customer agreed to triple the budget and double the duration after lawyers discussed the gap.
The contract will not save you, as any estimate at contract closure is dead wrong.
So you need to come to a relationship and understanding with the client on how to deal with the scope elaboration, the increasing cost, and duration. And in any case, cover your ass, point out the risks, and make the sponsor carry them. Prepare for the time when it blows up. Manage the conflict.
This will become a tremendous learning experience for you. Make sure you stay mentally stable, for example, get a mentor, do meditation.
...
1 reply by Pham Van Phuong
Aug 20, 2025 12:01 AM
Pham Van Phuong
...
Thank you all for your valuable insights.
Thomas, your real-life example is especially insightful. It highlights that even well-drafted contracts cannot fully protect us, and that building a constructive relationship with the client while clearly articulating the risks is essential.
I have encountered both situations myself. In one case, the client focused almost exclusively on contractual terms, and although we were able to defend our position successfully, the process was very stressful. In another project, I addressed the issue through the relationship with the client. While the outcome was financially less favorable for us, I considered it merely a cost matter, whereas in all other respects the project benefited and the partnership was strengthened.
Saving Changes...
Pham Van PhuongProject Manager| FUJI CAC JOINT STOCK COMPANYHo Chi Minh, Viet Nam
Aug 18, 2025 7:40 AM
Replying to Kiron Bondale
...
Pham -
The ideal way to address such situations is to have deadlines built into the contract for client accountabilities indicating the impacts (e.g. day for a day) of delays.
If the contract does not stipulate those, then it comes down to properly analyzing and communicating the risks created by the delays to the client and other key stakeholders so they are fully aware of the impacts to the project's objectives.
Kiron
Thank you all for your valuable insights.
I agree that having client accountabilities and deadlines in the contract is ideal. If that is not the case, proper risk analysis and effective communication are essential to ensure the client and stakeholders clearly understand the impacts. Saving Changes...
Pham Van PhuongProject Manager| FUJI CAC JOINT STOCK COMPANYHo Chi Minh, Viet Nam
Aug 18, 2025 1:23 PM
Replying to Lissette Indhira Pimentel Sosa
...
hello Pham, well, under a fixed-price EPC contract, it should come down to balancing protection and progress. The best approach I've seen are:
- Contractual safeguards defining client responsibilities, document assumptions/exclusions, and ensure a clear change order process.
- Keep an updated Risk management process, doing a gap analysis early, log missing inputs as risks, and escalating delays formally.
- During execution, move forward with documented assumptions, plan flexible schedules, and build in contingencies.
- Communication & keeping records is critical, the inputs should visible in regular meetings, track requests in writing, and preserve evidence.
If inputs remain incomplete, claims and variations are the last resort, but a proactive, collaborative approach usually prevents escalation.
Thank you all for your valuable insights.
Lissette’s point on balancing protection and progress resonates well with me. Documenting assumptions, keeping the risk register updated, and escalating formally while maintaining a collaborative tone are indeed very practical approaches. Saving Changes...
Pham Van PhuongProject Manager| FUJI CAC JOINT STOCK COMPANYHo Chi Minh, Viet Nam
Aug 19, 2025 5:17 AM
Replying to Thomas Walenta
...
Pham, this is a common problem on fixed price contracts.
I once ran a fixed price project based on 11 pages of contract requirements, resulting in a 600-page requirements document, with no changes identified, only detailing the headlines. In the end, the customer agreed to triple the budget and double the duration after lawyers discussed the gap.
The contract will not save you, as any estimate at contract closure is dead wrong.
So you need to come to a relationship and understanding with the client on how to deal with the scope elaboration, the increasing cost, and duration. And in any case, cover your ass, point out the risks, and make the sponsor carry them. Prepare for the time when it blows up. Manage the conflict.
This will become a tremendous learning experience for you. Make sure you stay mentally stable, for example, get a mentor, do meditation.
Thank you all for your valuable insights.
Thomas, your real-life example is especially insightful. It highlights that even well-drafted contracts cannot fully protect us, and that building a constructive relationship with the client while clearly articulating the risks is essential.
I have encountered both situations myself. In one case, the client focused almost exclusively on contractual terms, and although we were able to defend our position successfully, the process was very stressful. In another project, I addressed the issue through the relationship with the client. While the outcome was financially less favorable for us, I considered it merely a cost matter, whereas in all other respects the project benefited and the partnership was strengthened.
...
1 reply by Thomas Walenta
Aug 20, 2025 4:06 AM
Thomas Walenta
...
Yes, good examples.
Other strategies I pursued were to find other sources for funds, such as your employer offering free resources (working students), or other departments that can help with SW licenses or other resources they have. You could even look at the client to exploit solutions, from the project or outside of it, for third parties. And put a value tag on the good relationship, which can mean future business (a troubled contract can sometimes be saved by extending it), and can get you out of the competitive manner of contractual relationships, or helping the client in unrelated issues. Avoid the impression of bribery in any case!
The world is full of options, if you extend your perspective beyond the project boundary, the context.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Aug 20, 2025 12:01 AM
Replying to Pham Van Phuong
...
Thank you all for your valuable insights.
Thomas, your real-life example is especially insightful. It highlights that even well-drafted contracts cannot fully protect us, and that building a constructive relationship with the client while clearly articulating the risks is essential.
I have encountered both situations myself. In one case, the client focused almost exclusively on contractual terms, and although we were able to defend our position successfully, the process was very stressful. In another project, I addressed the issue through the relationship with the client. While the outcome was financially less favorable for us, I considered it merely a cost matter, whereas in all other respects the project benefited and the partnership was strengthened.
Yes, good examples.
Other strategies I pursued were to find other sources for funds, such as your employer offering free resources (working students), or other departments that can help with SW licenses or other resources they have. You could even look at the client to exploit solutions, from the project or outside of it, for third parties. And put a value tag on the good relationship, which can mean future business (a troubled contract can sometimes be saved by extending it), and can get you out of the competitive manner of contractual relationships, or helping the client in unrelated issues. Avoid the impression of bribery in any case!
The world is full of options, if you extend your perspective beyond the project boundary, the context.
...
1 reply by Pham Van Phuong
Aug 21, 2025 2:18 AM
Pham Van Phuong
...
Thank you for the valuable perspective.
I agree that exploring support beyond the immediate project boundary can be an effective corrective measure. Leveraging resources from other departments or external stakeholders, as well as strengthening the client relationship, can indeed create win–win outcomes.
This broader lens is a helpful reminder that corrective action is not only about protecting the contract baseline, but also about finding creative paths that preserve value and strengthen long-term trust.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Pham Van Phuong In fixed-price EPC contracts, the critical point is to ensure from the outset that client inputs are clearly defined as contractual deliverables.
A good practice is to integrate these inputs into the schedule as formal predecessors and consolidate them in a responsibility matrix (RACI), validated during the project kick-off.
This way, they are not treated as a “courtesy” from the client but as measurable and monitored contractual obligations.
This preventive approach significantly reduces uncertainty, as it turns potential omissions into objective interface management points.
In short, prevention lies in contracting well and planning with rigor: what is not clearly defined in the contract and the schedule is unlikely to be recovered once the project is underway.
When prevention is not sufficient and inputs remain missing, the priority is to document dependencies, communicate impacts transparently, and activate contractual mechanisms such as hold points or interface points.
Proceeding with independent work packages or provisional assumptions should only be done with full traceability, making it clear that such scenarios are subject to revision.
The balance lies in managing risk without assuming unlimited responsibilities: in fixed-price EPC contracts, active interface management protects both the contractor and the client, preserving the relationship and the overall viability of the project.
...
1 reply by Pham Van Phuong
Aug 21, 2025 2:14 AM
Pham Van Phuong
...
Thanks for sharing,
I fully agree that a preventive approach is essential. However, I am particularly interested in exploring the corrective approach when preventive measures alone are not sufficient.
At present, my plan is to capture missing client inputs in the Risk Register (internal) and in the Issue Log (shared with the client) through the following actions:
Front-loading Work: Execute activities not dependent on missing inputs.
Wait State: Clearly tag all tasks pending client inputs.
Assumptions: Proceed based on client-provided or client-approved assumptions for missing data.
Cut-off / Freeze: Any deviation from agreed assumptions at a later stage will trigger a Change Order / Variation.
That said, I am not entirely confident how effective this approach is. Under our current fixed-price contract, many terms restrict additional cost recovery. From past projects, when I submitted change requests, we could only claim direct costs if the final deliverable deviated from the agreed assumptions. Indirect costs (such as redesign effort, extended project management, or overheads caused by delayed inputs) were much harder to claim, even though we had formally communicated the potential impacts in the change requests.
Based on this practical approach, where do you think I might still be falling short? What additional corrective steps would you recommend?
How do you typically manage such situations under strict fixed-price conditions?
Saving Changes...
Pham Van PhuongProject Manager| FUJI CAC JOINT STOCK COMPANYHo Chi Minh, Viet Nam
Aug 20, 2025 4:43 AM
Replying to Luis Branco
...
Pham Van Phuong In fixed-price EPC contracts, the critical point is to ensure from the outset that client inputs are clearly defined as contractual deliverables.
A good practice is to integrate these inputs into the schedule as formal predecessors and consolidate them in a responsibility matrix (RACI), validated during the project kick-off.
This way, they are not treated as a “courtesy” from the client but as measurable and monitored contractual obligations.
This preventive approach significantly reduces uncertainty, as it turns potential omissions into objective interface management points.
In short, prevention lies in contracting well and planning with rigor: what is not clearly defined in the contract and the schedule is unlikely to be recovered once the project is underway.
When prevention is not sufficient and inputs remain missing, the priority is to document dependencies, communicate impacts transparently, and activate contractual mechanisms such as hold points or interface points.
Proceeding with independent work packages or provisional assumptions should only be done with full traceability, making it clear that such scenarios are subject to revision.
The balance lies in managing risk without assuming unlimited responsibilities: in fixed-price EPC contracts, active interface management protects both the contractor and the client, preserving the relationship and the overall viability of the project.
Thanks for sharing,
I fully agree that a preventive approach is essential. However, I am particularly interested in exploring the corrective approach when preventive measures alone are not sufficient.
At present, my plan is to capture missing client inputs in the Risk Register (internal) and in the Issue Log (shared with the client) through the following actions:
Front-loading Work: Execute activities not dependent on missing inputs.
Wait State: Clearly tag all tasks pending client inputs.
Assumptions: Proceed based on client-provided or client-approved assumptions for missing data.
Cut-off / Freeze: Any deviation from agreed assumptions at a later stage will trigger a Change Order / Variation.
That said, I am not entirely confident how effective this approach is. Under our current fixed-price contract, many terms restrict additional cost recovery. From past projects, when I submitted change requests, we could only claim direct costs if the final deliverable deviated from the agreed assumptions. Indirect costs (such as redesign effort, extended project management, or overheads caused by delayed inputs) were much harder to claim, even though we had formally communicated the potential impacts in the change requests.
Based on this practical approach, where do you think I might still be falling short? What additional corrective steps would you recommend?
How do you typically manage such situations under strict fixed-price conditions? Saving Changes...
Pham Van PhuongProject Manager| FUJI CAC JOINT STOCK COMPANYHo Chi Minh, Viet Nam
Aug 20, 2025 4:06 AM
Replying to Thomas Walenta
...
Yes, good examples.
Other strategies I pursued were to find other sources for funds, such as your employer offering free resources (working students), or other departments that can help with SW licenses or other resources they have. You could even look at the client to exploit solutions, from the project or outside of it, for third parties. And put a value tag on the good relationship, which can mean future business (a troubled contract can sometimes be saved by extending it), and can get you out of the competitive manner of contractual relationships, or helping the client in unrelated issues. Avoid the impression of bribery in any case!
The world is full of options, if you extend your perspective beyond the project boundary, the context.
Thank you for the valuable perspective.
I agree that exploring support beyond the immediate project boundary can be an effective corrective measure. Leveraging resources from other departments or external stakeholders, as well as strengthening the client relationship, can indeed create win–win outcomes.
This broader lens is a helpful reminder that corrective action is not only about protecting the contract baseline, but also about finding creative paths that preserve value and strengthen long-term trust. Saving Changes...
"Every child is born blessed with a vivid imagination. But just as muscles grow flabby with disuse, so the bright imagination of a child pales in later years if he ceases to exercise it."
Community Champion
