If you already do this for a living: Answering each requirement. A pre-appointment BEP that restates the team’s standard approach without going through the EIR line by line tells the client nothing it can compare.
- Watch out
- What it costs
- Experienced readers
- Remember
- In BIMpedia
A tender response has to answer one question for the client: can this team deliver the information we asked for? ISO 19650 asks the prospective lead appointed party to answer with four things, written for this project and this set of requirements.
- The pre-appointment BEP: how the team will manage and deliver information.
- A capability and capacity summary: evidence that the team knows how and has the people and IT (the previous lesson).
- A mobilisation plan: how people, IT and methods will be made ready and tested before production starts.
- A risk register: what could stop the information being delivered on time, and what the team will do about it.
What goes in the pre-appointment BEP
The standard lists the points to consider. In plain terms:
- The people. Who will carry out the information management function, so the client can see it is resourced.
- The delivery strategy. How the team will meet each requirement, at the level of information need and on the dates the client set; the team’s objectives; its organisation, commercial relationships and how it splits into task teams.
- The federation strategy. How the information will be broken into models and containers that teams can own.
- A high-level responsibility matrix. Which task team is responsible for which information.
- Additions to the methods and the information standard. What the team proposes on top of the client’s rules.
- Software, hardware and IT. What the team will use, so other teams and the client can work with it.
Each arrow that crosses a lane is a handoff: one party finishes, another takes over. Dashed: information sent back for changes.
Bidder A sends a 60-page BEP from its library: company history, a description of ISO 19650, a list of software. None of it mentions the client’s 40 requirements. The client cannot tell whether the door data or the COBie it needs is priced.
Bidder B’s BEP is 18 pages. Its delivery strategy is a table of the client’s 40 requirements with, for each, the task team, the method, the milestone and any assumption. Two requirements are flagged as unclear, with a question. The client can compare B with the others line by line, and does.
Templates and headings
If the client provides a BEP template or a list of headings, use them, even if your own format is better. The client chose them so it can compare bidders. If nothing is specified, the format is the team’s choice: a document, a spreadsheet or a tool.
One plan, two versions
After the client indicates its choice, and before the appointment is signed, the BEP is revisited. Names replace roles, software versions are confirmed, the delivery strategy and high-level matrix are updated if the team changed, and accepted additions go into the project-wide standard. The result is the delivery team’s BEP, confirmed with the client and with each appointed party, and kept under change control from then on.
Key takeaways
- A tender response has four parts: the pre-appointment BEP, a capability and capacity summary, a mobilisation plan and a risk register.
- The pre-appointment BEP shows who will run information management, how each requirement will be met, how the work is split, and what the team will add to the project’s rules.
- It is a first version: after appointment the same BEP is confirmed with real names, software and a detailed responsibility matrix.
- If the client gives a template or headings, use them; it is how responses are compared.
Your notesSaved in this browser
Related tool
Assemble a BIM execution plan from editable sections, with your tool outputs as appendices.
Open BEP Builder →