Use procurement to prepare for delivery, with lessons from nine podcast guests on package strategy, supplier evidence, contract expectations and the work that continues after award.
Updated The Major Project Podcast
From the conversations
Voices in this guide
The people and experience behind the insights. Choose a person to jump to their contribution.
PodBOK brings industry guidance together with real-world experience from major projects. Use it to inform your approach, and check the facts and requirements that apply to your project.
1.Define the delivery outcome before the package
Describe what the project needs to receive, prove and operate before deciding how to buy it. Identify acceptance evidence and the date it is needed. A purchase order is not the outcome. Practical prompt: can engineering, construction and operations agree on what completion means for this package, including documentation, spares, training and commissioning support?
Apply that question to the package: which information will let someone release fabrication, accept the equipment or put it into service? Name the recipient and the evidence they need before adding another deliverable to the list.
2.Test market capacity while options remain open
Check who can perform the work in the required period, where capacity is constrained and which assumptions suppliers challenge. Use the project's approved market-engagement process and keep a consistent record. Practical prompt: what would change if the preferred supplier could not reserve the required production slot? Keep the alternative credible before the tender strategy becomes fixed.
3.Package around interfaces as well as scope
Splitting scope can improve competition while creating coordination obligations. Combining it can reduce handoffs while concentrating exposure. Map technical and physical interfaces before choosing. Practical prompt: who supplies each input, who accepts it and who resolves a mismatch? Make the owner's retained integration work visible rather than assuming it disappears into the contract.
Walk a likely interface change through the proposed package boundaries. Identify who decides, who funds the change and who must be consulted before either party proceeds.
4.Match risk allocation to practical control
Examine which party can influence the event, obtain evidence and carry out a response. Passing wording to another party does not make the underlying uncertainty vanish. Practical prompt: if access or design information arrives late, what can the supplier actually do? Develop the commercial position with the project's authorized commercial and legal specialists, using the real delivery conditions.
5.Make the information basis explicit
List the specifications, drawings, quantities and site conditions that bidders should rely on. Distinguish approved information from assumptions and pending decisions. Practical prompt: are bidders pricing the same scope and the same uncertainty? Track clarifications in a shared record, and test whether an answer changes price, schedule, interfaces or acceptance obligations before evaluation closes.
Check a sample of the actual drawing contents against the document register before relying on it for pricing or fabrication. A complete-looking list can still conceal missing scope.
6.Compare the whole delivery proposition
Make evaluation criteria explicit before bids arrive. Review delivery capability, exclusions, execution approach, dependencies and support requirements alongside price. Practical prompt: what work must the owner perform to make this bid succeed? Normalize material differences transparently using the approved evaluation process, and record the assumptions behind the recommendation rather than hiding them in a total score.
Ask bidders to show the people and effort behind reporting, schedule updates and assurance obligations. Make those commitments visible in the evaluation and carry them into the delivery plan.
7.Plan backward from the date the site needs it
Include engineering approvals, vendor data, manufacturing, inspection, logistics, customs where applicable, site receipt and installation readiness. A dispatch date alone does not protect the construction sequence. Practical prompt: which upstream approval controls the required arrival date, and who owns it? Connect those obligations to the integrated schedule so slippage becomes visible before expediting turns urgent.
8.Verify the capability behind the promise
Ask for evidence relevant to this scope and this delivery period: proposed people, facilities, quality controls, subcontracting dependencies and available capacity. Distinguish company experience from the team assigned to your project. Practical prompt: what could you verify before award that would otherwise be discovered during execution? Record the remaining uncertainty and its response owner.
Use the receiving team’s experience to choose what to check. Follow up with current examples, proposed staff and sample submissions so the evaluation reflects the team and systems that will actually deliver this package.
9.Make award a controlled handover
Transfer the agreed scope, clarifications, obligations, interfaces, assumptions and approval routes to the people administering delivery. Include decisions made during evaluation and commitments made by the project. Practical prompt: can the package manager explain the critical obligations without reconstructing the tender history? Use a kickoff to resolve interpretation gaps before the first deliverable is due.
10.Track readiness and exceptions after award
Measure progress against evidence the next activity needs, such as approved vendor information, inspected equipment or an accepted test record. A reported percentage is useful only if its basis is clear. Practical prompt: what currently prevents installation or commissioning, who can remove it and by when? Escalate exceptions while alternatives remain and retain lessons for the next package.
Agree what evidence closes each package milestone. Delivery, installation, testing and acceptance should each have a clear basis, so an impressive progress percentage cannot hide unfinished work.
Read further
This top 10's Bookshelf
Explore the sources behind this article and related reading from our Bookshelf.
“Even though it’s called Capital Projects, that book is all about the front-end planning of projects. It’s not very technical in nature; it talks about the support mechanism required to be successful in the front-end phases. It’s geared towards executives, but still very accessible to anybody interested in capital projects. I definitely highly recommend it.”Roger Farish, on the show
Why it’s on the shelfThe IPA-rooted executive playbook for the exact phase Roger lives in, and the episode’s only book pick.
In her discussion of project decisions, Wilson challenges teams to explain why a deliverable is needed and what decision it enables. Producing more documents can consume time without helping the people who must decide what happens next.
Match the delivery strategy to what the market can undertake
Roger Farish
Farish describes helping an owner reduce the scale of a proposed project when its size and intended risk allocation made a suitable EPC competition difficult. The example connects scope and delivery strategy with the contractors available to execute the work.
Moradinezhad describes defining who is consulted, informed, deciding and acting, with authority and escalation matched to the project. Her collaborative-delivery examples show why a team still needs clear boundaries between the owner, designers and construction participants.
A contract cannot make uncertain delivery conditions disappear
Geoff Ryan
Discussing data-center delivery with uncertain costs, durations and equipment availability, Ryan challenges the idea that a lump-sum contract can remove that uncertainty. He calls for flexibility in how the project is managed as those conditions become clearer.
Ryan describes bringing construction, engineering and procurement into a path-of-construction workshop so drawings and materials can follow the intended construction sequence.
Stead describes a drawing set whose file names appeared to cover all the sheets, while the files repeated the same page. Checking the contents exposed missing drawings and work that had not reached fabrication. His review also compared extracted title-block and material information with the drawings themselves.
Ask contractors to price the controls work you require
Tarun Gohel
Gohel treats project controls requirements as work that needs people, effort and funding. In his discussion of contract alignment, he says the client should ask contractors to price their project controls activities rather than assume that putting requirements in a document makes them cost-free.
Ask the receiving team about the supplier’s track record
Leanne Allgaier
Asked how document control can inform vendor selection, Allgaier points to previous experience with the supplier’s people, past project performance and familiarity with its systems. She describes contributing that knowledge when document control is consulted during requests for quotation.
Carry the negotiation into the delivery team’s working records
Kim Essendrup
Essendrup describes delivery teams receiving a long signed contract without the context of the negotiations. A RAID log brings the risks, assumptions and dependencies into a form the team can manage during delivery.
Travis Arlitt describes progress getting stuck near completion and argues for keeping meaningful credit for final signoff. His concern is that early credit can leave finishing work without enough attention.
