ISO 19650 · Who writes the BEP

One owner. Several authors.

The BEP belongs to the lead appointed party, and that part is simple. The hard part is that the sections a reviewer reads first — who does what, whether they can, and whether the plan answers this EIR rather than the last one — are the sections the person holding the pen cannot write alone.

Part of the ISO 19650 toolkit.

Who is involved What each side owes Questions
Authorship

One document, four parties with a hand in it

ISO 19650-2 describes the BEP as the delivery team’s plan for how the information management side of the appointment will be carried out. Who owns it is a single line in the standard. Who has to contribute to it is spread across three of clause 5’s activities and both sides of the appointment.

01

The lead appointed party owns it

An organisation, not a person: whoever the appointing party appoints directly for this piece of work. When the client appoints its consultants one by one, that can be several firms at once — the architect, the engineer — each leading its own delivery team with its own BEP; under design and build it is usually the contractor. It establishes the pre-appointment BEP with its tender (5.3.2) and confirms it at appointment (5.4.1), and it answers for every promise in it.

02

The information management function holds the pen

The individuals the prospective lead appointed party nominates at 5.3.1. ISO 19650 names a function, not a job title, so whether the card on the door says Information Manager or BIM Manager does not matter. What matters is authority: the author has to be able to change how the task teams will work, not only describe how everyone hopes they will.

03

The task teams supply what it cannot invent

Capability and capacity are assessed by each task team (5.3.3) before the lead appointed party states them for the delivery team (5.3.4). After appointment the same teams write the TIDPs the confirmed BEP depends on (5.4.4). A BEP that asserts a capacity no task team was asked about is a promise with nobody behind it.

04

The appointing party decides whether it can be scored

It writes none of the BEP, and it shapes all of it. The tender response requirements and evaluation criteria set at 5.2.3 decide what the BEP has to contain and how it will be marked. A tender that asks for “a BEP in accordance with ISO 19650” and stops gets back the last job’s document, because nothing told the author what this job needed.

Responsibility

Written by the supplier. Made scorable by the client.

The BEP is established at clause 5.3.2 by the prospective lead appointed party, but what it has to contain and how it will be judged are decided one activity earlier, at 5.2.3, by the appointing party. Each side can make the other’s job impossible, and the two cards below are what stops that.

Appointing party

What the tender has to ask of the BEP

You do not write the BEP, but you decide whether it can be marked. A roles requirement that lists job titles is answered with an organisation chart. The EIR Health Check has a section on roles and capability.

Clause 5.2.3 · issued with the tender

  • Information management responsibilities stated as decisions and deliverables, not as job titles
  • Tender response requirements that name what the pre-appointment BEP must contain, section by section
  • Evaluation criteria published with the tender, so the response is written to be scored
  • Capability asked for as evidence — named people and comparable projects — rather than as a paragraph
  • Who holds the information management function on your side (5.1.1), so the delivery team knows who it answers to
  • Who evaluates the BEP and who agrees the confirmed one, by role, with a turnaround
Score your EIR against this →
Lead appointed party

What the BEP has to prove about who does what

The reviewer is not reading for fluency. They are checking whether the people named can deliver what the document promises, and whether it answers their EIR rather than someone else’s. The BEP Readiness Checklist covers both.

Clause 5.3.2, confirmed at 5.4.1

  • The individuals holding the information management function, named, with their profiles
  • A trace from every EIR requirement to a section of the BEP, or a reason it does not apply
  • A high-level responsibility matrix that the detailed one can grow from after appointment
  • Capability and capacity per task team, assessed by the task teams rather than asserted for them
  • Who authorizes information before it reaches the appointing party, and how long that takes
  • Nothing carried over from a previous project that this EIR did not ask for
Check your BEP against this →

A pre-appointment BEP written from the last job’s document responds to requirements the client never issued, and stays silent on half the ones they did. Nobody scores it clause by clause, so it passes.

Questions

What people actually ask

Does the client write the BEP, or the contractor?

The lead appointed party writes it, which is whoever holds the appointment, so the answer depends on the appointment rather than on the kind of firm. When the client appoints its consultants directly, each of them can be a lead appointed party with its own BEP; under design and build it is usually the contractor. The client — the appointing party — writes the EIR the BEP answers, and it can issue a BEP template with the tender: the UK BIM Framework guidance treats that as a legitimate shared resource, because it makes bids comparable. What a template cannot do on its own is say how the result will be scored. That is the job of the evaluation criteria (5.2.3).

Should the BIM Manager write it, or the Information Manager?

ISO 19650 names neither. It describes an information management function and leaves the job titles to the organisation, which is why two firms can use the same title for different jobs. The question worth asking is whether the author has authority over what the BEP commits to. On a lot of bids the BEP is written by whoever is available that week: fluent, on time, and unable to change a single thing it promises.

Does every task team need its own BEP?

No. There is one BEP per delivery team, and the lead appointed party establishes it. Each appointed party contributes to it — its capability and capacity at tender, its TIDP after appointment — and receives the lead appointed party’s own exchange information requirements (5.4.3). A package contractor that hands over a document called a BEP is usually answering that EIR. It is a useful input to the delivery team’s BEP, not a second one.

The design team had a BEP. Does the contractor inherit it?

No. When the contractor becomes the lead appointed party, whether under design and build or through novation, that is a new appointment and a new delivery team, and the BEP is established for it. On novation the architect becomes one of the contractor’s appointed parties, and its own role as a lead appointed party ends. The design-stage BEP is a good source for naming, federation and the CDE, and updating it should take work in proportion to what changed. Renaming it without that work is the fastest way to a BEP that describes a delivery team which no longer exists.

Who signs it off?

Nobody approves the pre-appointment BEP in the usual sense: it is evaluated as part of the tender response, against the criteria the appointing party published at 5.2.3, which is why a tender without criteria gets a BEP nobody can mark. The confirmed BEP is agreed at appointment (5.4.1) and becomes part of the appointment, so from then on it changes by agreement. It arrives with the detailed responsibility matrix and the task teams’ delivery plans, which the TIDP and MIDP page walks through. The ISO 19650 hub shows where all of it sits in clause 5.

Next

Find out whether yours can be scored

The BEP Readiness Checklist scores the parts a reviewer reads first — roles, responsibility, capability — in your browser, before the deadline rather than after it. If the gaps are about who rather than what, that is a half-hour conversation rather than a rewrite.

Book a 30-min call Back to the ISO 19650 hub
info@noeinsolutions.com