“Can you send me the names of the two engineers coming to site on Tuesday?” It sounds like a straightforward request from a client. A little less straightforward if you’ve just been appointed project manager, you thought the inspection was next month, and this is the first you’ve heard about a second engineer.
You open the proposal. It allows for a site inspection but gives no date and names only one engineer. Before you reply, there are a few things you’d probably like to ask the person who bid the job. How did Tuesday come about? Who did we say we’d send? And has anyone actually booked them?
That’s the conversation I’d want to have at the bid handover. Preferably before the client rings.
Problem: The bid team moves on before the project team can ask questions
A company can spend weeks preparing a proposal. Someone reads the tender documents, talks to the client, gets prices from subcontractors and works out how the job can be done. Then the company wins the work, appoints a project manager and sends them a link to the tender folder. By Monday the people who know the most about the project are busy trying to win the next one.
Put yourself in the new project manager’s position. There are three program schedules in the folder. The latest one has “final” in the filename, but its dates don’t match the client’s letter. Do you use it? Ring the client? Start a fourth schedule? The bid manager could probably explain in a minute that the third version was prepared for an alternative the client decided against. It might take you the best part of a morning to reach the same conclusion.
The client remembers the conversation
Take that Tuesday inspection. Suppose the client’s operations manager told the bid manager that part of the plant would be shut down for maintenance. Tuesday was the one day the engineers could see the equipment without a separate shutdown. The client offered to arrange access once they had the names for the inductions. From their point of view, the next move is yours.
The shutdown explains why the date matters. Move an ordinary inspection by a week and you may inconvenience a few people. Miss this one and you may have to design around equipment you haven’t seen. The client also has every reason to wonder why they spent time explaining the arrangements to your company if they now have to explain them all again.
A reasonable assumption can become an expensive mistake
A proposal might allow for two days of engineering time for that inspection. Is that one engineer for two days or two engineers for one day? The labour total is the same. The travel cost, the skills on site and the amount of ground you can cover during the shutdown could be quite different. If you have the final price and nothing behind it, you’re left guessing what your own company intended.
Sometimes the bid team itself had to guess. A client who allows a short period for tender responses may receive a price before there’s been time to verify access or get a firm subcontractor quote. The difficulty comes when that working assumption looks just as certain as everything else in the project budget. At bid handover, I’d want the estimator to tell me where the price is most likely to change and what I can still do about it.
Solution: Arrange a bid handover while the people who priced the work are available
Give the bid manager and project manager time together
Make the bid manager responsible for arranging the handover and name the project manager who will receive it. If you know who will run the job before the tender closes, involve them in the final bid review. They may know the proposed lead engineer is already committed elsewhere. That’s a much easier conversation to have before you put the engineer’s name in the proposal.
For a small repeat job, a bid handover between the two managers could cover the order, the estimate and the first few actions in half an hour. For a multidisciplinary project, bring in the people who made the important decisions. That might mean asking the estimator to explain the fee and having the site supervisor join for the discussion about access. Each needs time to answer questions, and neither necessarily needs to stay for the whole meeting.
If the bid manager is also the project manager, think about who else starts work on Monday. The design lead may never have seen the qualifications in the tender. The person booking the site visit may never have spoken to operations. A shorter bid handover with those people can prevent just as much wasted work.
Start with the documents the client actually accepted
Before the meeting, give the project manager links to the client’s request, the submitted proposal, subsequent clarifications and the signed contract or accepted order, as applicable. Identify the revisions and dates. Save the relevant correspondence in the project files and check the incoming manager can open it. A link to a restricted estimating folder is of limited use five minutes before a client meeting.
Walk through what changed between submission and award. For example, the tender might have offered an optional second inspection. Did the client buy it? Find the answer together in the award documents. If the documents appear inconsistent, record the precise question and have the appropriate commercial contact resolve it. Until then, the engineer planning the work needs to know that the second visit is still in question.
I’d also keep the original offer alongside the agreed scope. Six months later, someone may ask why the project has only allowed for one visit when an earlier program shows two. A short note pointing to the client’s decision saves the next person having to repeat your investigation. Mark the earlier program as superseded so it doesn’t find its way back into use.
Explain what the client is trying to achieve
Give the project manager a few minutes of background they’d struggle to get from the scope. Why did the client commission this work? Who will use the result? What decision do they need to make, and when do they need to make it? For the plant inspection, the immediate deliverable might be a report. The maintenance manager may need its recommendations in time to order parts for the next shutdown. That difference affects when a draft will be useful.
Pass on the names and roles of the people involved. The operations manager who can arrange site access might have no authority to approve an additional fee. The person who approves that fee may rely on a technical adviser who has attended every tender meeting. A few words about who does what will help the project manager direct their first questions to the right person.
Be specific about what you heard. “The client asked whether we could give them preliminary findings on Friday” tells the project manager something useful. “We owe them a report on Friday” tells them something quite different. Locate the reply, check what was agreed and identify anything that still needs confirmation before somebody promises a date.
Open the estimate and show how the job was priced
One of the most useful things the estimator can do at a bid handover is open the working estimate and follow one deliverable all the way through. For the inspection, show who was allowed for, how much time they had, what travel was included and who was going to write up the findings. Then ask the project manager how they’d allocate those hours. If the two descriptions differ, you’ve found something worth discussing.
Consider a fee that includes 40 hours for a report. A project manager might reasonably give the author a budget of 40 hours. The estimator might have allowed 24 hours for writing, eight for checking and eight for responding to client comments. Give all 40 to the author and the team will appear to be within budget right up until someone has to check the report. Give the project manager that breakdown and they can brief each person properly.
Check the allowances most exposed to change since the bid was submitted. Was the specialist’s price firm? What validity period did they give you? Did they include travel? If the client took three months to award the job, someone should ring the specialist before their figure goes into a purchase order. For a detailed reference on recording the assumptions behind an estimate, see the US Government Accountability Office’s Cost Estimating and Assessment Guide.
Work backwards from the first commitment
I’d spend more of the bid handover on next Tuesday than on a milestone twelve months away. Ask what has to happen before the first visit can go ahead. In our example, the client needs the names by Thursday for inductions. One engineer needs to travel on Monday afternoon. The second needs a particular familiarity with the plant. Discover that on Wednesday and you still have choices. Discover it on Monday afternoon and your client may already be organising an escort for two people who can’t get in.
Now look further ahead. Which dates came from the client? Which did the bid team propose? Which were calculated on the assumption that the client would supply information within a week of award? Keep the tender program so the reasoning can be traced and prepare the delivery program using confirmed dates and resources. Where a date is in doubt, nominate someone to check it before the team starts planning other work around it.
Treat client inputs the same way you treat your own deliverables. If design needs an up-to-date drawing, give someone the job of requesting it, say when it’s needed, and tell them who at the client can provide it. “Client to supply drawings” can sit in a program for weeks without prompting anybody to pick up the phone.
Keep a bid handover checklist that fits on a page
I’d use a short checklist as an index to the project files. The detail can stay in the contract, estimate and program. A useful handover note tells the incoming manager where to look and draws attention to the handful of things that could catch them out. These are the prompts I’d start with.
- Client and purpose. Who needs the work, what decision depends on it, and who can give instructions?
- Scope and deliverables. What did the client accept, which options did they take up, and what did we exclude?
- Fee and resources. Where is the estimate, who did we price, and which allowances need checking?
- Dates and dependencies. What happens first, who controls access, and what information are we waiting for?
- Risks and opportunities. What worried the bid team most? Is there still time to do something about it?
- Outstanding actions. Who owns each one, when is it due, and where will the answer be recorded?
Use the discussion to fill gaps in your existing project records. If the risk register already explains the restricted access, link to the entry and check its owner. Copying it into another document gives you two versions to maintain. My post on holding a formal handover meeting covers a similar conversation when one project manager takes over from another.
Agree who owns the project when the meeting ends
Finish the bid handover by recording the transfer date and having both managers acknowledge the handover note. Write down any follow-up work the bid manager has agreed to do. For example, they might still owe you confirmation of the specialist’s travel costs. Give that action a due date and make clear that the project manager is now the contact for instructions about the work.
Then introduce the project manager to the client. If the bid manager already has a good relationship with the operations manager, a short joint call is worthwhile. The bid manager can introduce their replacement, the project manager can confirm the next step, and the client knows who will call back with the engineers’ names. That’s a much better first conversation than asking the client to start again from the beginning.
Use what you’ve learned to brief the delivery team and prepare the project management plan. Check back with the bid manager after the people doing the work have read their briefs. If the checker finds there’s no time allowed for an independent review the client specifically requested, raise it while the estimate is fresh in everyone’s mind. Also feed that issue back to the estimating team so they can allow for it the next time they price similar work.
Lesson: Give the project manager a fair start
If your company has spent weeks learning enough about a job to win it, allow the people who did that work time to hand it over. A good bid handover lets the incoming project manager ask how the team arrived at a price, why a date matters and which questions were still open when the client accepted the offer.
My test would be to put the client’s first phone call to the new project manager. Can they explain what happens on Tuesday? Can they find the allowance for the two engineers? If the names are still outstanding, can they tell the client who is confirming them and when they’ll ring back? If they can do that, they’re ready to manage the job you’ve won.



