Mga Kaso / Pag-estimate at pagpepresyo
Pag-estimate at pagpepresyo

Panatilihin ang design estimate sa loob ng aprubadong badyet

Magtakda ng investment estimate na may rate kada metro kwadrado sa likod nito, isulat kung ano ang ipinapalagay nito, presyuhan ang design estimate para sa parehong saklaw, at ihambing ito sa aprubadong bersyon sa bawat gate.

5 hakbang20 minDeveloper / KliyenteCost Consultancy / QS PracticeDesign / Engineering PracticeProject / Construction Management Firm

Paano ito gumagana, hakbang-hakbang

5 hakbang sa buong platform - ano ang gagawin mo sa bawat isa at bakit mahalaga ito.

1

Set the investment estimate as a rate, not just a total

Konseptwal na Estimate

Build the feasibility number from the building type, the gross floor area and the quality level, and read off the rate per square metre it implies as well as the total.

Bakit: A total is a fact about a building nobody has designed yet, and a design team cannot work to it. A rate per square metre is a constraint they can test every decision against, which is the whole mechanism of cost-capped design, and it stays comparable when the area moves.

PapasokBuilding type and quality levelGross floor areaLumalabasInvestment estimateRate per square metre
2

Write down what the approved number assumes

Batayan ng Estimate

Record the basis: the scope covered, the standard of finish, the price level and date, what is excluded, and where the rates came from. Keep it with the estimate rather than in the covering email.

Bakit: Every argument at the next gate is about whether the design changed or the estimate was wrong, and only the basis can answer it. Without one, a stage that comes in over is always explained as a scope change, and there is nothing on either side that can contradict that.

PapasokThe approved numberWhat it assumedLumalabasWritten basis of estimateExclusions on the record
3

Price the design estimate and name the version

Bill of Quantities (BOQ)

Price the design item by item against the same scope the basis describes, and save a named version of the bill at the moment it goes for approval so the approved state can be retrieved exactly.

Bakit: The version that was approved is the only meaningful thing to measure later movements against, and it is unrecoverable a month afterwards unless somebody named it at the time. Naming it costs a moment and turns the next comparison from an argument into a report.

PapasokDesign as it standsThe stated basisLumalabasDesign estimate priced by itemNamed version at the gate
4

Compare against the approved version at every gate

Bill of Quantities (BOQ)

Set the current bill against the version approved at the previous stage and read the difference by section: which items were added, which quantities grew, which rates moved. Work the rate per square metre out again on the current area and put it beside the one you started with.

Bakit: Nothing here declares a limit or returns a verdict, and that is the honest shape of it: the product shows you where the money went and the cap is held by people. What makes that workable is running the comparison at each gate rather than once at the end, because a section that has grown by six percent is a design conversation while a total that has grown by twenty is a re-approval.

PapasokThe bill as it stands nowThe approved versionLumalabasWhich sections movedThe rate per square metre now
5

Report the position with the movement explained

Mga Ulat

Report the stage total, the rate per square metre, the difference against the approved figure and the sections it came from, with a line on each saying whether it was a scope change, a design decision or a price movement.

Bakit: An approving body asked to consider a number will ask where it came from, and a report that answers that in advance gets a decision instead of a deferral. Naming the cause per section is also what tells the design team where the savings have to come from, which is the only useful output of the exercise.

PapasokThe gate comparisonLumalabasStage report for approvalWhere savings have to come from
Mga Module

Mga Module sa Playbook na Ito

4 / 190 na module ng platform

The market this case is written for

China

Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.

Standards it follows

  • GB 50500
  • GB 50854

You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.

The rule checks for this market come with the platform too. Switch them on once and an estimate that misses something the market expects is flagged while you are still working on it, not after the tender has gone out.

Higit pa sa Pag-estimate at pagpepresyo

Pag-estimate at pagpepresyo

Estimate from a cost database

Pull priced items from a real cost database, build the bill from them, bundle recurring bui…

4 hakbang12 minBukas
Pag-estimate at pagpepresyo

Set contingency from cost risk

Turn a single-point estimate into a range, run a Monte Carlo over the genuinely uncertain l…

3 hakbang11 minBukas