Clarity for the built environment
Menu

Tool 1 · BIM planning

BIM Team Starter

Start a staffing assessment with the asset class, the work you own, its size, model detail and delivery time. Review modeling effort and coordination capacity separately.

Free to useNo account neededInputs stay in your tab

Answer the starting questions, review the assumptions and explore your result. You can add more detail as you go.

What this tool covers: An early staffing scenario using editable productivity assumptions; actual geometry, reuse, inputs, design changes and delivery sequence can change demand. No complexity factor is applied. A hospital and a warehouse of the same area return the same effort unless you enter different rates, areas or discipline coverage.

Start with what you know

Your answers stay in this tab and can carry into related tools. Use nonconfidential labels. Reloading, leaving the journey or clearing the session removes the working answers.

Required. The asset class decides what this tool is willing to assume: the recorded productivity reference covers building floor area on a building project, so infrastructure and complex operational facilities are given no starting rate at all. It never scales a result.

Choose the work your team owns. Only the questions for that scope will appear.

Enter the total building area to model across all floors. For an average floor area instead, change the area basis under optional details. For example, 30000 m² total. Use digits without thousands separators.

Select a unit, or not sure for a useful result without this quantity.

Which disciplines need modelers? (optional)

Select only the disciplines your team will model. Each covers the stated area; adjust partial coverage under optional details. Each selected discipline gets its own visible effort weight and productivity rate below.

Landscape or infrastructure in this scope? (optional)

Optional. These are counted directly, in people, because no modeling productivity rate exists for either in any unit. They are never estimated from building area, and selecting them changes no figure for the building disciplines above. Landscape and infrastructure share one coordinator between them.

How many landscape modelers this scope needs. Entered by you; it is not derived from area, project size or documentation quantities. Leaving it blank keeps the figure unresolved rather than zero. For example, 12. Use a dot for decimals; no thousands separators.

How many infrastructure modelers this scope needs. Entered by you; it is not derived from area, project size or documentation quantities. Leaving it blank keeps the figure unresolved rather than zero. For example, 12. Use a dot for decimals; no thousands separators.

Optional model-detail context. Choosing a level fills the productivity box below with the matching architecture rate and names where that number came from; it never changes effort by itself. The number in each discipline’s box is the number calculated, and your own edit is never overwritten.

The base rate, on an architecture basis. It starts at the 300 m² per modeler-day practitioner reference, which was measured on architecture at LOD 400; choosing a model-development level above replaces it with that level’s suggestion until you type your own, after which nothing overwrites it. Each selected discipline’s own visible rate is filled from this number divided by that discipline’s effort weight, and only those per-discipline rates are calculated with. Infrastructure and complex operational facilities start empty: no rate is recorded for them, so one must be entered before modeler effort is calculated. For example, 12. Use a dot for decimals; no thousands separators.

Count independent model packages or delivery teams needing coordination at the same time. Several packages in one discipline can be separate workstreams. Landscape and infrastructure do not change this count: they are not counted as workstreams and do not select the support plan, because they carry their own single shared coordinator instead.

Select how often the team reviews information, including follow-up.

For model production, enter the available modeling window. For combined scope, this also sets weekly support duration. Modeling effort can be calculated before the duration is known. For example, 12 weeks.

Select a unit, or not sure for a useful result without this quantity.

Discipline effort weights and the productivity rates they fill

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. A weight fills the rate beside it once and takes no part in the calculation; only the rate is calculated with. Edit either. A rate you type is kept, and no later weight, base-rate or model-development change replaces it.

AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Weight = modeling effort relative to architecture, per m². 1.0 means the same effort per m² as architecture. It fills the rate beside it and takes no part in the calculation. AECEQ practice set — the tool owner’s judgement, September 2026. Not a measured rate and not a published benchmark: no located source states modeling effort per discipline. Replace any weight with your own delivery experience. For example, 12. Use a dot for decimals; no thousands separators.

The rate actually used for this discipline. It is filled from the base productivity divided by the weight beside it, and your own edit is never overwritten by a later weight, base-rate or model-development change. For example, 12. Use a dot for decimals; no thousands separators.

Use this estimate to check capacity for your next delivery package. Confirm productivity and role availability before committing.

Waiting for the local calculator.

Refine this result — optional details

Changes update the assumptions above. Calculate again after editing.

Expected roles and basic responsibilities: BIM Manager, BIM Coordinator, BIM Information Manager and BIM Modeler
BIM Manager
Plan BIM delivery and resources; maintain the BIM Execution Plan; agree methods and quality checks; resolve escalated coordination issues; report progress. Design approval and contractual acceptance stay with the appointed authorities.
BIM Coordinator
Combine discipline models; run agreed clash and model checks; lead coordination reviews; assign and track issues; verify fixes before the next exchange. Discipline teams own design decisions and model corrections.
BIM Information Manager
Manage information requirements and delivery schedules; administer agreed CDE workflows, permissions, naming, revisions and issue records; check information completeness and handover records. Technical design checking, client acceptance and IT security ownership require separate appointments.
BIM Modeler
Create and update a discipline model from approved design information; prepare agreed sheets and schedules; perform self-checks; resolve assigned modeling issues; meet agreed information requirements. Works within the agreed discipline scope; flags missing design decisions for the responsible designer.

These are basic proposed responsibilities, not contractual appointments. One person may cover several roles on a smaller project; allocate their time once and confirm competence, checking independence and approval authority. Information-management effort below covers only the allocated tasks, not an automatic full-time appointment.

Optional refinement

Only details relevant to your chosen scope appear below. Adjust them when you have better project information.

How is your building area measured? / Number of floors in scope (2 fields)

Choose one basis. Total building area already includes every floor; it will not be multiplied again.

Required for average-floor area. For total area, floors describe the breakdown and can add an explicit floor-review allowance; they do not multiply area. For example, 12. Use a dot for decimals; no thousands separators.

Productive modeling days per week / Additional model revision allowance (2 fields)

Use the days actually available for model production. Meetings and checking allocated elsewhere are separate; no further hidden utilization factor. For example, 12. Use a dot for decimals; no thousands separators.

Extra authoring effort as a percentage of first-pass modeling. Blank means 0% additional revisions; confirm this scope before committing. For example, 12. Use a dot for decimals; no thousands separators.

Coordination review allowance per floor / Architecture: modeled area coverage (2 fields)

Additional coordinator effort for floor-by-floor review when coordination is included. This explicit allowance is separate from routine weekly coordination; set 0 if already included. For example, 12. Use a dot for decimals; no thousands separators.

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Structure: modeled area coverage / Mechanical: modeled area coverage (2 fields)

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Electrical: modeled area coverage / Plumbing: modeled area coverage (2 fields)

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Fire protection: modeled area coverage / Telecommunications / ICT: modeled area coverage (2 fields)

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Blank means the full building area. Enter a smaller percentage only if this discipline covers part of the building. For example, 12. Use a dot for decimals; no thousands separators.

Landscape / infrastructure coordinator: days per week / Landscape / infrastructure coordinator: hours per day (2 fields)

The shared coordinator's working pattern. A project condition, not a methodology rule, so it is editable here: it moves the coordinator's person-day total. Reported as person-days, never converted to a five-day FTE. For example, 12. Use a dot for decimals; no thousands separators.

The declared working-day convention for that coordinator. It describes what a person-day means on this project; this methodology calculates in person-days and does not convert hours into effort. For example, 12. Use a dot for decimals; no thousands separators.

What stage are you planning? / Coordination allowance to compare (2 fields)

Choose the delivery stage; this changes the work emphasis, not a productivity multiplier.

Optional: P1 = 3, P2 = 5, P3 = 9 person-days/week. These describe different service scopes.

Existing availability / BIM Manager: weekly support allowance (2 fields)

Optional total days/week already available for these roles. This is time capacity, not headcount. For example, 12. Use a dot for decimals; no thousands separators.

Optional replacement for this role’s plan allowance. Leave blank to use the selected plan; enter 0 only if this role is outside your support scope. For example, 12. Use a dot for decimals; no thousands separators.

BIM Coordinator: weekly support allowance / BIM Information Manager: weekly support allowance (2 fields)

Optional replacement for this role’s plan allowance. Leave blank to use the selected plan; enter 0 only if this role is outside your support scope. For example, 12. Use a dot for decimals; no thousands separators.

Optional replacement for this role’s plan allowance. Leave blank to use the selected plan; enter 0 only if this role is outside your support scope. For example, 12. Use a dot for decimals; no thousands separators.

Completed package: modeled area / Completed package: actual modeler-days (2 fields)

Optional. The modeled area of one comparable package you have already delivered. Entering it with the actual days shows your observed rate beside the assumption; it never changes this result. For example, 8000 m².

Select a unit, or not sure for a useful result without this quantity.

Optional. Productive modeler-days actually recorded for that package. Separate design waiting time from productive effort. Enter both area and days to see an observed rate. For example, 12. Use a dot for decimals; no thousands separators.

What that completed package included (1 fields)

Optional nonconfidential note: the discipline, the agreed deliverables, and whether checking, sheets and revisions were inside those days.

Review assumptions and calculate

Illustration only

Worked example

30,000 m² at an assumed 300 m²/day needs 100 modeler-days per discipline. Over 10 weeks × 5 productive days, the average productive capacity is 2 modelers per discipline. Three disciplines need 300 modeler-days and 6 dedicated modelers if delivered in parallel. Coordination support is assessed separately.

The example project is separate from your answers. Any visible starter rates or productivity assumptions are labeled and editable.

How this tool works

For each discipline: area × coverage ÷ that discipline’s visible productivity rate × (1 + revision percentage / 100) gives modeler-days. Only the visible per-discipline rates are calculated with. Two things prefill them and neither enters the arithmetic: selecting a model-development level fills the visible base box with 600 / 450 / 375 / 300 m²/day for LOD 200 / 300 / 350 / 400 on an architecture basis, and each discipline’s effort weight fills its own rate with base ÷ weight. A rate you type is never overwritten by either. Infrastructure and complex operational facilities receive no starting rate, because the recorded reference is for building floor area on a building project; modeler effort stays unresolved until you enter one. Divide by available modeling days to find average capacity, then round up within each discipline only for a dedicated parallel staffing option. Coordination uses an explicit weekly allowance selected by concurrent workstreams and review pace. Additional floor reviews start at zero to avoid counting routine reviews twice.

Limitations

  • An early staffing scenario using editable productivity assumptions; actual geometry, reuse, inputs, design changes and delivery sequence can change demand.
  • No complexity factor is applied. A hospital and a warehouse of the same area return the same effort unless you enter different rates, areas or discipline coverage.

Terms used here

Starter scenario
A proposed scope or resource allowance to compare. It does not predict whole-project demand.
Open item
A cost, prerequisite or decision that has not been resolved. It is not assumed to be zero or satisfied.
Evidence basis
The origin of a figure or rule: your figures, a dated supplier reference, or an original proposed rule.

Sources and version

Methodology v2.3.0; specification/source snapshot 2026-09-18. Original proposed rules from the supplied Market Pre-assessment Methodologies v2. No external professional reviewer has approved these methods or validated market fit.

  • BIMForum Level of Development (LOD) Specification (opens in a new tab) — METH-LOD-01; observed Current published edition; the resource page does not state an exact edition date, accessed 2026-09-17; review due 2026-12-17. Describes model element content and reliability so that usable deliverables can be agreed. Used in BIM Team Starter as optional deliverable context only. Does not prescribe project-stage progression and is not evidence for any LOD-to-productivity relationship. Changing the optional model-development label never changes Team Starter productivity or effort.
  • UK BIM Framework — the information management function and resources, Guidance Part A, Edition 2 (opens in a new tab) — METH-IMF-02; observed Edition 2, February 2021, accessed 2026-09-17; review due 2026-12-17. Supports distinguishing information-management activities, responsibilities and resource assignments, which is how the tool separates role responsibilities from allocated time. Does not prescribe this tool’s role titles or any person-days/week allowance. The P1/P2/P3 weekly allocations of 3 / 5 / 9 person-days are product presets, not guidance values.
  • UK BIM Framework — processes for project delivery, ISO 19650 Guidance Part 3, Third Edition (opens in a new tab) — METH-PD-03; observed Third Edition, January 2020, accessed 2026-09-17; review due 2026-12-17. The task-team discussion at printed pages 21–22 separates capacity to manage information, to produce information and to provide IT, and links delivery planning to what information is produced, when and by whom. Supports reporting authoring effort separately from support capacity. Provides no authoring productivity rate and no staffing ratio. Team Starter does not size IT capacity, and its output is not a resource-loaded delivery programme.
  • UK BIM Framework — about information delivery planning, Guidance Part F, Edition 1 (opens in a new tab) — METH-IDP-01; observed Edition 1, September 2020, accessed 2026-09-17; review due 2026-12-17. Delivery-planning context used as process guidance for checking assumed capacity against milestones. Used as process guidance only; not a source of universal authoring productivity or staffing ratios. Team Starter does not produce a task information delivery plan or a master information delivery plan.

Service references are reviewed quarterly; software guidance monthly. Overdue records remain historical context and do not automatically price a scenario.

Can I use this to make a commitment?

Use the result to frame a discussion. Confirm scope, responsibilities and applicable requirements before procurement, contractual, financial or operational commitments.

What if I do not know an answer?

Choose not sure where offered, or leave optional figures blank. You will receive a useful scope, action plan or draft; unsupported prices and conclusions remain open.