This video explains how to approach the ISO 19650 tender response stage and build a winning submission. The written guide below covers the key components of a compliant tender response, including the pre-appointment BIM Execution Plan, mobilization plan, risk register, team capability assessment, and how structured templates and checklists help teams respond with clarity and confidence.
Why a structured tender response wins ISO 19650 work
Winning an ISO 19650 tender is not just about submitting the right documents. It is about demonstrating that your team can plan, resource, manage, and deliver information in a structured and reliable way. The tender response phase, covered in clause 5.3 of ISO 19650-2, is where prospective appointed parties show the appointing party that they understand the Exchange Information Requirements (EIR) and have a credible plan to deliver against them. A weak tender response — one with unclear deliverables, poor resource planning, or missing risk assessment — signals to the client that the team is likely to struggle during delivery. A strong one builds confidence before the project even begins.
The challenges that undermine tender responses are familiar across the industry. Teams often do not fully understand what the client is asking for, which means they cannot describe clearly what they intend to deliver. Resource planning is frequently an afterthought rather than a structured exercise, so when deadlines approach, teams fall into firefighting mode. Risks go unidentified until they become problems, and by then the cost of managing them is far higher than it would have been with early planning. The ISO 19650 tender response process addresses all of these issues by requiring specific deliverables that force teams to think through their approach before they commit to it.
The tender response workflow follows a clear sequence. It starts with nominating an individual to fulfil the information management function. This person is responsible for ensuring that information flows between all stakeholders in a coordinated way, and their nomination signals to the appointing party that the team takes information management seriously. Next comes the pre-appointment BIM Execution Plan, which outlines how the delivery team intends to manage information throughout the project. This is not the final BEP — it is a pre-contract version that demonstrates capability and approach without committing to post-appointment detail. The team then assesses the capability and capacity of each task team, evaluating whether they have the right skills, experience, and resources to deliver what the EIR requires. Following that, the mobilization plan sets out how resources, IT systems, personnel, and workflows will be prepared before work begins. The risk register documents potential risks related to information management along with mitigation strategies, so the appointing party can see that the team has thought beyond the optimistic scenario. Finally, all of these components are compiled into the complete tender response submission.
What makes this process practical rather than bureaucratic is the use of structured templates and checklists. Each step in the tender response maps to a checklist item, so nothing slips through the gaps. Teams can track milestones, assign responsibilities, and verify that every requirement in the EIR has been addressed before the submission goes out. Using ready-made templates for the pre-appointment BEP, risk register, and mobilization plan means teams are not starting from scratch each time. They start from a proven structure and tailor it to the specific project, which is faster, more consistent, and reduces the risk of missing critical content. The tender package can also be managed with controlled access, so prospective appointed parties can see only the data relevant to their bid without visibility into competing teams, keeping the process secure and organised.
How to build a winning ISO 19650 tender response
- Nominate the information management function – Identify the person who will be responsible for coordinating information management across all stakeholders. This role is essential for demonstrating that the team has a clear point of accountability for information delivery.
- Establish the pre-appointment BIM Execution Plan – Create the delivery team’s pre-appointment BEP that outlines how information will be managed, what tools and methods will be used, and how the team intends to meet the requirements set out in the EIR. This demonstrates preparedness without committing to post-appointment specifics.
- Assess task team capability and capacity – Evaluate each task team’s skills, experience, and available resources against the requirements. This assessment shows the appointing party that the team can realistically deliver, not just theoretically.
- Establish the mobilization plan – Define how IT systems, software, personnel, and workflows will be set up and tested before project delivery begins. The mobilization plan ensures that everything is ready when work starts, rather than being configured on the fly.
- Establish the risk register – Identify potential information management risks and document mitigation strategies for each. This demonstrates proactive risk management rather than reactive problem-solving.
- Compile the complete tender response – Bring together the pre-appointment BEP, capability assessment, mobilization plan, risk register, and all supporting documentation into a single structured submission that directly addresses every requirement in the EIR.
- Use checklists to verify completeness – Review the submission against the ISO 19650 compliance checklist to confirm that every clause 5.3 requirement has been addressed before the tender is submitted.
What you’ll learn
- Where tender response fits in the ISO 19650 workflow – How the tender response phase builds on the assessment and need stage and the invitation to tender, and why the quality of the response directly affects appointment decisions.
- The pre-appointment BIM Execution Plan – What should be included in the pre-contract BEP, how it differs from the post-appointment version, and why it is the centrepiece of a credible tender response.
- Capability and capacity assessment – How to evaluate whether each task team has the right skills, tools, and bandwidth to deliver against the EIR, and how to present this assessment convincingly.
- Mobilization planning – Why preparing resources, systems, and workflows before the project starts is critical for smooth delivery, and how the mobilization plan demonstrates readiness to the appointing party.
- Risk management in tender responses – How identifying and documenting information management risks early shows maturity and gives the appointing party confidence in the team’s ability to handle challenges.
- Templates and controlled access – How standardised templates speed up the tender response process and how controlled access ensures that prospective appointed parties see only the data relevant to their bid.
Common questions
What is the difference between the pre-appointment BEP and the post-appointment BEP?
The pre-appointment BEP is created during the tender response phase and outlines how the delivery team intends to manage information if they win the work. It covers approach, methods, tools, and key roles but does not commit to the full level of detail that comes after appointment. The post-appointment BEP, created after the contract is awarded, is the detailed delivery plan that includes confirmed team structures, specific workflows, finalised technology choices, and agreed milestones. The pre-appointment version demonstrates capability; the post-appointment version commits to execution.
Why does the information management function need to be nominated at tender stage?
Nominating the person responsible for information management at tender stage shows the appointing party that the team has a clear point of accountability from day one. This person coordinates information flows, ensures compliance with the EIR, and acts as the main contact for information-related queries. Waiting until after appointment to identify this role creates a gap in coordination during the critical early stages of the project.
How detailed should the risk register be at tender stage?
The tender-stage risk register should identify the key information management risks relevant to the project and outline realistic mitigation strategies for each. It does not need to cover every possible scenario, but it should demonstrate that the team has thought critically about what could go wrong and has planned for it. Common risks include software compatibility, team availability, data handover gaps, and evolving requirements. The register is refined and expanded after appointment as the project detail becomes clearer.
Can the same tender response templates be reused across projects?
Yes. Standardised templates for the pre-appointment BEP, mobilization plan, risk register, and capability assessment can be reused as starting points for every tender. Importing templates from previous projects saves time and ensures consistency, while the team tailors the specific content to match the EIR and project context for each new bid.
Explore further
- Tender response tasks – The full expert course lesson covering each step of the ISO 19650 tender response process.
- Best BIM Execution Plan strategy – How to build a BEP that demonstrates real capability and wins confidence from appointing parties.
- EIR, PIR, and BEP documents with Plannerly – How the complete set of information requirement and response documents connects and can be managed from templates.
- ISO 19650 assessment and need / invitation to tender – The preceding stage that sets the context for everything the tender response must address.