Exchange Information Requirements

What is an EIR?

An Exchange Information Requirements document defines what project information is needed, why it is needed, who must provide and review it, when it must be exchanged, and how it will be accepted. It helps owners, architects, engineers, BIM teams, and contractors coordinate deliverables before design and construction information becomes incomplete, inconsistent, or late.

เอกสาร EIR ระบุข้อมูลที่โครงการต้องการ เหตุผลในการใช้ข้อมูล ผู้จัดทำและผู้ตรวจสอบ กำหนดเวลาส่งมอบ รูปแบบไฟล์ และเกณฑ์การยอมรับ เพื่อให้เจ้าของโครงการ สถาปนิก วิศวกร ทีม BIM และผู้รับเหมาทำงานร่วมกันได้อย่างชัดเจน

EIR — Exchange Information Requirements · ข้อกำหนดการแลกเปลี่ยนข้อมูลโครงการ

Why it matters

What a clear Exchange Information Requirements document does for a construction project

Reduce missing information

Define required drawings, models, schedules, properties, reports, and supporting documents before delivery.

Coordinate every discipline

Align architectural, structural, MEP, civil, landscape, interior, sustainability, and construction information.

Make deliverables measurable

Set milestones, file formats, model detail, data requirements, review responsibilities, and acceptance criteria.

Create a clear basis for the BEP

Let the appointed design or construction team explain how it will meet the EIR through its BIM Execution Plan.

Who uses an EIR

How information requirements flow from the owner to the whole project team

Owner / Appointing Party

Defines project decisions and information needs

Exchange Information Requirements (EIR)

States what information must be delivered

Lead Designer / Consultant / Contractor

Responds through the BIM Execution Plan (BEP)

Architects, Engineers, BIM Teams, and Contractors

Produce, review, coordinate, and exchange the required information

When it is used

Information requirements stay in use across the whole project lifecycle

1

Project brief and consultant appointment

2

Concept and developed design

3

Permit and authority submissions

4

Detailed design and tender

5

Construction and coordination

6

As-built information and handover

Portfolio case study

Challenge

Construction teams often begin producing drawings and models before the required information, responsibilities, exchange dates, and acceptance criteria are clearly defined.

Approach

This portfolio demo translates ISO 19650 information-management concepts into a guided workflow for Thai architects, engineers, BIM teams, and contractors.

Outcome

Users can structure construction information requirements, review missing items, preview a professional document, and download an EIR draft for further project-specific review.

Skills demonstrated

Architecture and construction workflow knowledgeBIM and ISO 19650 information managementSustainability data requirementsUX/UI designStructured data and document generationBilingual Thai and English communication

Created by

Pirawit Sukhaneskul

Architect | BIM Specialist | Sustainability Specialist

Pirawit Sukhaneskul is an architect, BIM specialist, and sustainability specialist exploring how better information requirements can improve coordination, decision-making, and environmental outcomes in the construction industry.

Ready to try it?