MEP Base Scope and Alternatives: Do Not Sum Mutually Exclusive BOQ Rows

AI-generated illustrative scene, not a product screenshot or a completed-project photograph. The worked calculation below uses explicit example inputs.
An estimating workbook may correctly list the work for two alternative arrangements and still produce an incorrect total. The error arises when a bottom-row sum treats every visible line as cumulative scope. A base arrangement and its replacement cannot both be included unless the project genuinely requires both. Making selection logic visible is often more useful than adding another explanatory note beside the grand total.
This example concerns quantity and labour-hour organization only. It neither selects equipment nor changes a design or commercial offer. All labour factors are hypothetical arithmetic inputs, not production norms or promised performance. An appropriately authorized team must determine whether the options are technically feasible and which scope is required.
1. Define common, replaced and additional work
Use a common-scope group for work that remains identical under either option. Use separate option groups for mutually exclusive replacement scope. Keep genuinely additive work in another group with its own selection flag. Do not use the word alternative for all three: it obscures whether a row replaces something, adds something or merely changes an assumed quantity.
The GAO Cost Estimating and Assessment Guide describes the importance of a technical baseline, estimating structure, ground rules and assumptions, and addresses analysis of alternatives. The matrix below is an original small-scale application of those general principles, not a GAO-prescribed MEP template or a substitute for project instructions.
2. Build a two-scenario labour example
Assume an approved estimating exercise compares two hypothetical distribution-package arrangements. Common work totals 120 labour-hours and is identical in both. Arrangement A has 40 repeat units at 2.0 labour-hours each. Arrangement B has 25 different repeat units at 4.4 labour-hours each. A and B serve the same defined package boundary and are mutually exclusive for this exercise. Their different unit descriptions must remain separate.
Option A labour = 40 × 2.0 = 80 labour-hours.
Option B labour = 25 × 4.4 = 110 labour-hours.
Scenario A = 120 common + 80 A = 200 labour-hours.
Scenario B = 120 common + 110 B = 230 labour-hours.
Invalid all-row sum = 120 + 80 + 110 = 310 labour-hours.
The 310-hour total does not describe either defined scenario. It includes both replacement arrangements. It is not a contingency allowance and cannot be described as a conservative estimate without changing the scope definition. A correct scope total comes first; explicit uncertainty allowances, when needed, are a separate estimating decision.

Original illustrative planning diagram. Assumptions and limitations are stated in the worked example.
3. State whether an alternative is a total or a difference
If the base scenario is A, the change in this limited labour model is 230 minus 200, or 30 additional labour-hours for B. That delta is different from B's 110-hour option-group quantity and different again from the 230-hour full-scenario total. Put the basis in the column header and transmittal: full scenario, replacement group, or change from named baseline.
Replacement change from A to B = remove 80 + add 110 = +30 labour-hours.
Check: base 200 + change 30 = alternative total 230 labour-hours.
This does not establish the overall commercial difference. Materials, access, commissioning, programme, temporary works and other affected items may change as well. The example deliberately holds common work fixed. If an alternative changes that work, move the affected lines out of the common group and recalculate both complete scenarios.
4. Add simple selection and boundary checks
A scenario column can multiply each line quantity by a zero-or-one inclusion flag. For this two-option example, exactly one of A or B must be selected. Zero selected leaves incomplete scope; both selected creates an invalid combined scope. A separate check should verify that all required common rows remain included and that each option's quantities match its stated revision.
For several independent option families, apply the exactly-one rule within each mutually exclusive family, not across the entire workbook. Some options may also be incompatible with choices in another family. Document those constraints rather than assuming every combination is buildable. When the combinations become difficult to review, present only explicitly validated scenarios instead of allowing unrestricted selections.
5. Preserve the baseline when decisions change
Keep a dated snapshot of each issued scenario with its design reference, exclusions, quantity basis and reviewer. When B is later selected, do not overwrite A's historic quantities and leave an unexplained changed total. Record the decision reference and issue a new baseline. That preserves a clear explanation of why the package changed from 200 to 230 labour-hours in this limited model.
The useful deliverable is not one crowded total sheet but a reproducible comparison: common scope 120, scenario A 200, scenario B 230, and a 30-hour replacement difference under stated assumptions. The next decision remains with the authorized project team. The estimator's role is to make each proposed scope coherent before quantities feed scheduling, procurement or commercial review.
Continue the calculation review
Sources and calculation basis
Primary references checked on 27 October 2026. The worked examples and diagrams are original illustrative calculations, not manufacturer selections or project approvals. Apply the stated limitations and the requirements governing the actual project.

Comments