What a BIMs Force Request Is and Why It Matters
A BIMs force request is a formal change-driven mechanism that instructs the project team to implement specific Building Information Modeling (BIM) requirements or updates mid-project. It is commonly used when an owner or project stakeholder needs a model element, level of detail (LOD), coordinate system, naming standard, or workflow to be altered after the baseline BIM Execution Plan (BEP) has been established. The request documents the need, the rationale, scope, impacts on time and budget, and the acceptance criteria, creating an auditable record that supports coordination, quality control, and risk management.
When a BIMs Force Request Is Typically Used
Project teams introduce a BIMs force request when a predefined BIM requirement no longer fits project conditions or when new requirements emerge that were not addressed in the original contract documents. Typical scenarios include updated design deliverables, changes to LOD for specific systems, corrections to clash findings, or adjustments to model unit standards. Because BIMs force requests explicitly record the change rationale and downstream effects, they help avoid misunderstandings, manage expectations, and preserve liability clarity among owners, architects, engineers, and contractors.
Common Triggers for a BIMs Force Request
- Change in design intent that impacts model detail or classification
- Revision of modeling standards or naming conventions mid-project
- Correction of model errors or omissions discovered during coordination
- Requirement to adopt a new file format, version, or IFC export configuration
- Adjustment to coordination milestones or model delivery cadence
Core Components of a BIMs Force Request
A well-structured BIMs force request includes a clear description of the required BIM change, the business or technical reason, the affected models or disciplines, related contract clauses, and the expected outcomes. It should specify performance metrics such as required LOD, file naming patterns, issue tracking IDs, and verification methods. Including an impact analysis—covering time, cost, coordination dependencies, and risk—enables the project team to make informed decisions about approval and implementation.
Elements to Include
- Title, unique identifier, and date
- Initiator and approval authorities
- Detailed description of the BIM change required
- Rationale and reference to contract or project requirements
- Affected models, objects, deliverables, and disciplines
- Required LOD, geometry, attributes, and metadata expectations
- Impact assessment: schedule, cost, coordination, and risk
- Verification, acceptance criteria, and sign-off process
- Implementation timeline and version control instructions
BIMs Force Request vs Related Change Mechanisms
On many projects, the BIMs force request operates alongside change orders, request for information (RFI) processes, and specification updates. While an RFI seeks clarification, a BIMs force request specifies a concrete BIM action. Change orders typically address contractual time and cost adjustments, whereas a BIMs force request focuses narrowly on BIM deliverables and model requirements. Understanding these distinctions helps teams route requests through the correct governance path and ensures appropriate accountability.
Comparison of Change Instruments
| Instrument | Primary Purpose | Typical Outcome | Governance Context |
|---|---|---|---|
| BIMs Force Request | Mandate specific BIM deliverables or model changes | Updated model with required LOD, attributes, and metadata | BIM management and coordination team |
| Change Order | Adjust time, cost, or scope under contract | Contractual amendment and associated payments | Contractor and owner / project controls |
| RFI | Clarify ambiguous information or resolve gaps | Written response and updated documentation | Design and coordination team |
| Specification Revision | Update technical requirements or performance criteria | Amended specification documents | Owner and design team |
Best Practices for Drafting and Managing BIMs Force Requests
To ensure BIMs force requests are effective, teams should align them with the project-level BIM Execution Plan and coordinate protocols. Use a standard template that captures context, precise requirements, measurable acceptance criteria, and stakeholder responsibilities. Route requests through established review and approval workflows, and track them in a common issue coordination system so status and decisions remain visible. Couple each request with model version tags and a clear implementation schedule to minimize disruption and rework.
Checklist for a Strong BIMs Force Request
- Clear title and unique ID
- Concise description of the BIM change required
- Reference to affected models, objects, and disciplines
- Specified LOD, coordinate system, units, and naming conventions
- Impact on schedule, budget, and coordination dependencies
- Verification methods, testing steps, and acceptance criteria
- Defined approval authorities and signatories
- Version control, issue linkage, and timestamps
Practical Outcomes and Acceptance Criteria
Once a BIMs force request is approved, the implementation team updates the relevant models to the required LOD, applies naming and metadata rules, and records the change in the model’s revision history. Verification often involves automated checks (e.g., property validation, geometry and LOD audits) and manual peer reviews. Acceptance is typically confirmed when the updated model passes defined checks and is formally signed off by the authorized approvers. Project teams should log completed force requests as part of the as-built model documentation to support operations, maintenance, and future renovations.