Practice clear, client-facing BIM English for EIR, BEP, CDE, coordination, and handover.
Prompt Generator
Answer first, then reveal the model answer and compare your structure.
Explain EIR To A New Client
Your client asks: What is an EIR, and why do we need it before tender?
Speak for 45 seconds. Use one definition, one project action, and one reason.
An EIR is the client's exchange information requirements. It explains what information is needed, why it is needed, when it should be delivered, and what standards or formats the team must follow. Issuing it before tender helps bidders respond clearly and lets the client compare their BIM capability.
Respond To A BEP Challenge
A project manager says: The BEP is too long. What should we check first?
Speak for 45 seconds. Use one definition, one project action, and one reason.
I would check whether the BEP clearly answers the EIR. The most important points are roles and responsibilities, BIM uses, information delivery dates, CDE workflow, quality checks, and any assumptions or exclusions.
Clarify CDE Rules
A subcontractor asks where to upload a model that is not ready for approval.
Speak for 45 seconds. Use one definition, one project action, and one reason.
Please upload it to the agreed work-in-progress or shared area according to the CDE workflow. Do not publish it for approval until the model has been checked, named correctly, and given the right status.
Asset Handover Briefing
The facilities team asks why asset data needs to be defined early.
Speak for 45 seconds. Use one definition, one project action, and one reason.
Asset data should be defined early because the project team can only deliver useful handover information if they know what the operator needs. AIR helps us avoid collecting too much data, too little data, or data in the wrong format.
Polite Coordination Disagreement
A designer says the clash is minor and can wait until construction.
Speak for 45 seconds. Use one definition, one project action, and one reason.
I understand it may look minor now, but it affects the coordination sequence. Could we log it in the CDE, assign an owner, and agree whether it needs to be resolved before the next information exchange?
Meeting Phrase
Clarify scope
Could we confirm which information requirements apply to this exchange and which party is responsible?
Coordination Phrase
Raise an issue
I suggest we log this in the CDE, assign an owner, and agree the status before the next model issue.