MODEL SCOPE & ESTIMATING BOUNDARIES

BIM Coordination Services — MEP Clash Review Scope

BIM coordination compares project models to identify potential conflicts between systems. Before requesting a proposal, confirm the model inputs, included trades, review responsibilities and required outputs. Coordination, quantity takeoff, priced estimating and field data collection are separate tasks.

Discuss Project Scope & Deliverables

For general contractors and subcontractors: identify the intended use of the output before agreeing the scope.

Request a Project Estimate

Share your project details. Fields marked * are required.

Contact and project details
Include + and your international calling code.

Project Drawings (optional)

PDF, CAD/BIM, Office, ZIP or image documents. Up to 5 files, 25 MB each; account limits also apply.

    Upload only documents you are authorized to share. Privacy policy. This request does not opt you into marketing messages.

    Choose the Task That Matches Your Project

    Coordination review

    Define the systems and model zones to be compared, the issue categories to report and who approves each proposed resolution. Do not assume every discipline or support detail is modeled.

    Quantity takeoff

    Define the objects or drawing items to measure, their units and the quantity schedule fields. Identify where missing model information requires drawing review, an assumption or a request for clarification.

    Priced estimating

    Confirm whether pricing is requested in addition to quantities. Agree the geography, source date, labor and material basis, allowances and exclusions. A coordinated model does not by itself establish a construction price.

    Prepare a Clear Model and Document Register

    List each discipline file, its revision and the areas it covers. State the expected model units and coordinate reference. Include drawings and specifications needed to interpret model objects, schedules or incomplete details. Identify which party provides architectural, structural, mechanical, electrical and plumbing information.

    Describe the decision the output must support: bid quantities, a coordination meeting, a specific installation interface or another agreed task. Establish the delivery format and review milestone before selecting a modeling or estimating scope.

    • Identify missing files, incomplete zones and known model limitations.
    • State which file versions can be exchanged and opened by the relevant project parties.
    • Record the required level of information for the intended use; a label alone does not prove that every needed object is modeled.
    • List access restrictions and document-sharing permissions before sending confidential material.

    Agree Deliverables and Review Responsibilities

    Use the proposal to identify the included systems, zones, model revisions and output files. Possible requirements to discuss include a model issue register, referenced screenshots, an agreed coordination report or a quantity schedule. These are scope questions, not a promise that every item is included.

    For each reported issue, agree who investigates it, who decides the design response and how acceptance is recorded. A clash-detection result identifies an issue for review; it does not establish the correct design response or replace the project’s approval process.

    Existing resources can help frame that discussion: review the BIM execution-plan resource and clash-matrix resource. Confirm how any example applies to the actual project agreement.

    Separate Field Data, Design and Fabrication Scope

    Existing-condition records may differ from site conditions. Identify the source, date and limitations of the supplied geometry. Confirm whether a site visit, survey or laser scan is included, who performs it and how access and discrepancies are handled.

    Keep field verification, engineering design, coordination review and fabrication release as separate responsibilities unless the written agreement explicitly assigns them. Do not infer engineering sign-off, sealed drawings or installation approval from a model-review or estimating deliverable.

    Where information is incomplete, record the assumption, affected area and information needed for a decision. Do not convert an unresolved issue into an approved instruction merely to complete an issue log.

    Evaluate the Proposal and Any Project Example

    Compare the accepted scope, exclusions, revision allowance, delivery format and milestones. Ask what happens if incoming models need substantial correction or new drawing revisions arrive after the baseline is agreed. Request a project-specific fee rather than assuming a universal rate.

    For an example deliverable, confirm the producing party, intended use, measurement basis and permission to share it. A sample of quantity rows does not establish model-coordination experience, field-scanning capability or a project’s financial outcome.

    Any performance or savings claim needs project records, dates, assumptions and a stated comparison. No project-specific savings, zero-change-order result or guaranteed return on investment is asserted here.

    BIM Coordination Questions Before You Request a Proposal

    Is BIM coordination the same as a quantity takeoff?

    No. A quantity takeoff measures and schedules quantities from the agreed documents or model. Coordination reviews relationships and potential conflicts between modeled systems. A priced estimate adds an agreed cost basis. Identify which task you need and which outputs the proposal actually includes.

    Which files and project information should I provide?

    Provide the current model or drawing register, discipline files, revision dates, specifications, applicable execution plan and the intended use of the output. State whether the request concerns an entire project or selected zones. Agree file formats, model units, shared coordinates and version compatibility before work starts.

    Are laser scanning, site visits or existing-condition surveys included?

    Confirm these items explicitly in the written proposal. Identify who collects existing-condition data, the access requirements, the agreed method and its limitations. A model-coordination or estimating proposal should not be assumed to include scan capture, travel or field verification.

    Does a coordination report approve engineering design or fabrication?

    Do not treat a clash report, model issue log or quantity schedule as design approval, engineering sign-off or fabrication authorization. The project must identify the parties responsible for design decisions, accepted resolutions and release milestones. An issue marked resolved still needs the approval required by the project agreement.

    What determines the fee and delivery schedule?

    Most estimates are typically $150–$1,000, depending on project size and scope, and most are returned in 24–48 hours. Ask for a project-specific proposal based on document completeness, included systems and zones, requested output, issue-review rounds and revision scope. Identify field data collection, travel and substantial model correction separately. Confirm the fee and milestones in writing. This page does not offer the service for free.

    What should an issue or clash report contain?

    Specify the location, affected systems, relevant element or drawing references, model revisions, issue description and current status. Agree the report format, tolerances and review responsibility. A screenshot without document references or an accountable decision trail may be insufficient for the buyer task.

    How should changes, addenda and unresolved questions be handled?

    Agree which document revision is the baseline, who supplies updates, how additional review rounds are priced and how unresolved issues are recorded. Keep assumptions separate from approved decisions. Where the available documents do not support a conclusion, identify the information needed instead of silently inventing a detail.

    Can coordination savings or project outcomes be guaranteed?

    No outcome is established by this page. Any claimed savings, reduced rework or return on investment needs identifiable project records, a comparison basis and stated assumptions. Assess the relevance and publication permission of a proposed case example before relying on its numbers.

    Request a Project-Specific Scope Review

    Contact the Estimating Desk

    Describe your project, available documents and the output you need. Most coordination estimates are typically $150 to $1,000 and most are ready in 24–48 hours, depending on size and scope. Confirm the accepted scope before work begins.

    info@mepestimationusa.com +1 (317) 751-5969

    Measured quantities, clear trade boundaries

    Inspect 90 selected lines and 6 cropped drawings in our coordinated MEP sample. This excerpt demonstrates the published quantity format; it does not substantiate every specialty service or a complete project price.

    Division 22: Plumbing

    Reconcile fixtures and equipment against plumbing schedules. Keep domestic water, sanitary waste and vent quantities separate by material and size; identify fittings, valves and connection boundaries. Pipe sizing and medical-gas design require the issued design and qualified review.

    Plumbing estimating scope

    19 selected source lines available in the sample.

    Division 23: Mechanical / HVAC

    Reconcile HVAC equipment tags, air outlets and ductwork against the mechanical schedules. Keep duct length, area or weight units distinct. Confirm whether hydronic or refrigerant piping, insulation, supports, controls and testing are included in the quoted scope.

    Mechanical / HVAC estimating scope

    32 selected source lines available in the sample.

    Division 26: Electrical

    Reconcile lighting and device counts against schedules. Distinguish conduit route length from conductor length, with conductor count and specified sizes recorded separately. Confirm feeds, disconnects and controls interfaces; fire alarm and low voltage require their own scope confirmation.

    Electrical estimating scope

    39 selected source lines available in the sample.

    Agree these items before the takeoff starts

    Confirm the drawing issue and addenda, measurement units, base quantities versus allowances, trade responsibility for equipment connections, and assumptions for missing information. A priced estimate also needs dated supplier pricing, labor basis, taxes, freight and exclusions agreed for your project.

    Drawing-based coordination flags scope interfaces. BIM clash detection, engineering design, specialty process systems and code certification require a separately confirmed scope and supporting documents.

    Send plans for a scoped quote

    Trace a coordination issue into the estimating handoff

    A clash status alone does not identify the bid impact. Keep an issue record with the affected systems, zone, model issue, responsible design party and resolution reference. Only an agreed revised route or detail can support a meaningful quantity comparison.

    For example, a hypothetical duct route changes from 30 LF to 42 LF after an issued resolution. Record a 12 LF length increase, then review the changed fittings, insulation, hangers and access requirements separately. The clash count is not the duct quantity, and the 12 LF change is not automatically a complete installed-cost adjustment.

    The handoff should retain the original and revised documents, unresolved design questions, the estimating cut-off date and any excluded coordination tasks. Design acceptance, fabrication release and field verification remain the responsibilities stated in the project agreement. Compare this work with the MEP estimating deliverables before requesting a price for the revised package.

    Get Your Quote