Find the missing costs in a consultant's feasibility estimate

A feasibility report may estimate the supplier's part of a project while management reads the total as the amount required to begin operations. Before using the figure for approval, identify the scope boundary. Equipment supply, installation, site preparation, staff training and ongoing operation can belong to different budgets and different parties.

Read the assumptions and exclusions alongside the headline estimate. Ask the consultant to identify every cost that the business must supply, arrange or confirm separately. An exclusion is not necessarily a defect in the report if it was agreed in the engagement, but someone must own it before management relies on a complete project budget.

Record the estimate's purpose and stage. A preliminary feasibility estimate may support a decision to investigate further without supporting a fixed purchase authorization. Ask what additional design, quotations or site work is required before the amount can be treated as a procurement budget.

List the work outside the consultant's estimate and assign each item to a responsible person. Common categories to investigate include internal staff time, temporary operations, site access, utilities, data migration, training and initial stock. Include only items relevant to the actual project, with a clear basis for each amount.

Distinguish cash spending from staff capacity. An internal team may perform work without a new invoice, but its participation can delay other assignments or require temporary cover. Ask the team leader to confirm hours, timing and the work being deferred. Avoid adding a general internal-cost percentage without checking what the business will actually do.

Give unknown items an explicit status. A blank cell can be mistaken for zero when the approval total is copied into another document. Use an unresolved-cost register with the information needed, the person obtaining it and the date it must be resolved. Report the budget limitation until those items have credible estimates.

Consider an illustrative feasibility estimate showing $180,000 for supplied equipment and installation. The report excludes $25,000 of site preparation, $8,000 of staff training, $12,000 of temporary rental equipment and $15,000 of initial consumables. Adding those identified owner costs produces a $240,000 initial project requirement before any further exclusions or reserve.

A separately proposed $20,000 uncertainty reserve would take the approval envelope to $260,000. Keep that reserve visible rather than blending it into the consultant's estimate. Management should understand that $240,000 reflects identified work while the additional amount is a decision about funding uncertainty, subject to a defined approval process.

Check for double counting before accepting the bridge. Installation may already include commissioning labor, or the equipment quote may include training. Cross-reference each owner-cost item to the supplier scope. If two parties both assumed the other would provide the same work, resolve the responsibility before treating either price as complete.

Ask when the underlying quotations were obtained and how long they remain valid. A report issued this month can contain supplier prices gathered much earlier. Compare the assumed delivery period with the project's actual schedule, especially where a quote depends on a production slot or a limited price-validity window.

Verify the location and delivery terms used in each estimate. A factory price can exclude freight, insurance, unloading and local installation. Taxes, duties and other charges require the appropriate specialist review for the actual transaction; do not infer them from a generic percentage used for another project.

For foreign-currency quotations, show the original currency and the rate assumption used in the approval model. Identify who will update that assumption before a binding order. The estimate should preserve enough source detail to separate a supplier price change from a movement in the currency used for management reporting.

A project can reach technical completion before the business can use it at the expected output. Review staffing, training, testing, maintenance arrangements and the period during which old and new processes operate together. The approval budget should include the costs needed to reach the operating state assumed in the benefit case.

Ask who owns each acceptance condition. A supplier may be responsible for proving the equipment meets a specification while the business remains responsible for providing materials and trained operators. If acceptance requires a test run, identify the consumables, labor and lost production associated with that run.

Then separate initial costs from recurring operating expenses. A feasibility report can include a first-year service contract while the model assumes maintenance is free thereafter. Conversely, an operating-cost forecast may accidentally repeat a one-time commissioning payment every year. Reconcile the first-year bridge with the steady-state model line by line.

Compare the report with the commissioned scope and ask the consultant to correct unsupported totals or explain exclusions that were not apparent. Where additional work falls outside the agreed engagement, price and approve it separately. A scope review should distinguish a missing contracted deliverable from a new request made after the report arrived.

Retain the report version, source quotations, assumptions register and completed owner-cost schedule with the approval. The IRS's recordkeeping guidance describes the business documents supporting purchases and expenses. For project governance, the same evidence also lets a later reviewer understand why the approved amount differs from the consultant's headline number.

Before management authorizes spending, show the unresolved items and the commitments that can safely proceed. If a missing cost could change the decision, keep that commitment pending until the evidence is available. Update the approval bridge when a quotation becomes an order, preserving the prior estimate so changes remain explainable.