How to review an EPC proposal before submission

Start with a decision brief

Record the bid deadline, the main technical promise and the decisions that remain open. Identify which documents define the scope and which revisions are current. A proposal review becomes less effective when different disciplines are reviewing different versions of the design basis or vendor offer.

Build a scope and interface map

List the major packages and the systems they depend on. For each interface, identify who supplies the equipment, who connects it, who provides the operating utility and who demonstrates performance. A vendor’s complete package can still leave a project-level gap if an interface is assigned to nobody.

• Confirm package battery limits against the tender requirements
• Compare vendor exclusions with the main proposal inclusions
• Identify tie-ins, utility connections and off-site responsibilities
• Record unresolved ownership of design, supply and testing activities

Test the assumptions behind the offer

Ask which operating cases, feed conditions, utility quality and site conditions underpin the proposed performance. Compare those assumptions with the information actually available. An unconfirmed assumption is not necessarily wrong, but it needs an owner, a clarification route and an understood effect on the commitment.

Make the risk register useful

Describe each issue in terms of its cause, possible consequence and action required. Distinguish a confirmed scope omission from a question that cannot yet be answered. Avoid presenting every observation as equally urgent. The team needs to know which matters could change price, scope, schedule or the technical undertaking.

Close with a clear management discussion

Present the material open points before the proposal is finalized. Explain what is resolved, what remains conditional and what evidence is still required. Management should understand the residual uncertainty rather than interpreting a completed checklist as proof that every risk has been removed.