Library / Projects / KEVOS® original book

Front-End Planning by the Numbers

Project definition, estimate classes, gates and exposure windows: planning a seasonal upgrade slowly so that it can be delivered quickly

Plan slowly, deliver quickly: score project definition, read estimate classes, size the front end, and price exposure and a harvest deadline, worked through one packhouse upgrade.

10 chapters · About 105 minutes · Free to read · Intermediate project planning and capital decision practice

Start reading
KEVOS® LibraryPROJECTSENQUIRYDELIVEREDFront-EndPlanning by theNumbersKEVOS® ORIGINAL BOOK10 CHAPTERS

About this book

A capital project spends very little while it is being defined and a great deal while it is being delivered. A week of planning costs a project engineer, a consultant’s study and some meetings; a week of delivery costs contractors, equipment, site overheads and money committed that cannot be recovered. Problems found while the project is still on paper are cheap to fix, and the same problems found on site are fixed with rework, variations and lost weeks. The case for planning slowly and delivering quickly follows directly: spend the time where it is cheap, so that the expensive part is short, well understood and exposed to as little as possible.

This book works through that idea with numbers. It starts with where a project’s money and risk are exposed, then organises the front end into stages that end at gates, scores how well a project is defined with a weighted checklist in the manner of the Construction Industry Institute’s Project Definition Rating Index, and reads estimates by their class and range. It goes on to the hidden scope a front end exists to find, how much front-end work a project is worth, the exposure window of delivery, and the cost of missing a fixed deadline, then covers locking the plan in at approval, reviewing the outturn and scaling the method to smaller projects. Each chapter carries one running case, includes a plausible error and how it was found, and ends with an exercise and its worked answer.

It is for owners, managers, project managers, estimators and finance staff in small and medium Australian businesses. It assumes spreadsheet arithmetic. Probability is introduced where it is needed, through one simple schedule simulation.

The running case

Every chapter follows one fictional decision. This is an illustration. Northbank Fruit Packers, a family business in northern Victoria, packs apples and pears from its own orchards and from local growers: about 18,000 bins a season of around 400 kg each. Its six cold rooms hold 6,000 bins, so a large share of each harvest goes to hired cold storage, and its packing line is old and slow. The business plans an upgrade: four new cold rooms holding 4,000 bins, a new refrigeration plant serving the old rooms and the new, an optical grader for the packing line, and the electrical, civil and fire services work they need. The upgrade must be ready by 31 January 2028, one week before the first fruit of the 2028 harvest arrives, because the packing line can be changed only between November and January and the rooms must be at temperature before intake.

In November 2026 the concept estimate is A$5.41 million excluding GST, and the managing director proposes approving a budget of A$5.95 million at once and starting work, to give the project as much time as possible. The book follows the other path: 22 weeks and A$248,000 of front-end planning, which raises the estimate to A$6.43 million, finds the scope the concept missed, orders the long-lead equipment at approval, and delivers in 36 planned weeks. The chapters compare the two paths on cost, time and the chance of missing the harvest.

The business, its people, its projects and every number in the case are invented. None describes KEVOS® work, a real business or a real project. All amounts are Australian dollars excluding GST.

How to use the book

Read Chapter 1 first: it sets out the two paths and the numbers that later chapters build on. Chapters 2 to 5 cover the front end itself: stages and gates, scoring definition, estimate classes and the scope a front end finds. Chapter 6 asks how much front-end work is enough. Chapters 7 and 8 cover delivery, its exposure window and the deadline, and Chapters 9 and 10 cover approval, delivery control and the review afterwards. Every calculation in the book was checked by running it, and the schedule simulation uses a fixed random seed so that its results can be reproduced.

The book is one of a series of KEVOS® Library books on planning and delivering projects, written to be read together. Reference Class Forecasting by the Numbers adds the outside view: how projects like this one have actually turned out, and how to set a budget and contingency from that record. Stage Gates and Stopping Rules by the Numbers covers the decisions made at each gate, including when to stop, where this book covers what must be defined before a gate. Modular Projects by the Numbers applies short exposure windows to repeated installations on working sites, and Project Teams and Contracts by the Numbers covers the people and contract forms that carry a plan into delivery.

Source limits and professional responsibility

The method draws on published research, industry practice and government guidance, and the sources are listed with what each was used for. Published results are cited only for what they found and for the projects they studied, which were mostly larger industrial and building projects than the case. The case’s scoring index, estimate ranges, durations and costs are teaching values, not benchmarks, and a real project needs its own definition, quotes, approvals and risk assessment. Building, electrical, refrigeration and fire services work is regulated, and its design, approval, installation and commissioning are matters for the competent and licensed people responsible for them under the applicable laws, codes and standards. This book is general information about planning and approving projects. It is not engineering, legal, financial or investment advice.

Who this book is for

Owners, operations and engineering managers, project managers, estimators and finance staff who prepare, review or approve capital projects in small and medium Australian businesses, especially projects tied to a season or a fixed start date.

What you will learn

  • Explain why time spent defining a project is cheap and time spent delivering it is expensive, and measure both for a real project.
  • Organise the front end into stages with gate deliverables, and score how well a project is defined with a weighted checklist.
  • Read an estimate by its class, keep its range visible, and judge how much front-end work a project is worth.
  • Quantify the exposure window of delivery and the cost of missing a fixed deadline, using a simple schedule simulation.
  • Lock in a plan at approval with long-lead orders and change control, review the outturn honestly, and scale the method to smaller projects.

Inside this book

Chapters

  1. 01Plan slowly, deliver quickly: where a project's money is exposedNorthbank's upgrade on two paths: A$11.3k a week in the front end against A$171.7k in delivery, money spent against money committed, and a cost of waiting priced wrongly.
  2. 02Stages and gates: organising the front endFEL 1, 2 and 3 as stages with gate deliverables, Northbank's A$96k and A$152k stage budgets, and three options compared at Gate 2 on capital, payback and NPV.
  3. 03Scoring project definition with a weighted checklistA PDRI-style index of 20 weighted elements: 807 at concept, 507.5 at Gate 2, and an independent rescore that moves 185.5 to 254.5 before targeted work brings it to 202.
  4. 04Estimate classes: reading a number by how much is definedNorthbank's Class 5, 4 and 3 estimates of A$5.41m, A$5.96m and A$6.43m, their ranges, why the point rose 18.8% as definition grew, and a loan sized on the wrong class.
  5. 05Finding the hidden scope before approvalFive items worth A$990k found for A$46k of investigations, against A$1,425k and weeks of delay if found on site, and a borehole plan that missed the plant room pad.
  6. 06How much front-end planning is enoughDiminishing returns on front-end spend: an illustrative optimum of A$256.9k against A$248k spent, and a three-week gate slip that would have lifted P(miss) from 5.3% to 24.1%.
  7. 07The exposure window: delivering quickly once committedDelivery as an exposure window: 36 planned weeks against 52, holding cost of A$301.7k against A$355.8k before the harvest, and a slab poured early that cost A$130k.
  8. 08A fixed deadline: the cost of delay as a cliffA step cost of delay at 31 January 2028, A$630k plus A$41k a week, and a seeded simulation: a 44.2% chance of missing on the rush path against 5.3% on the planned path.
  9. 09Locking in the plan: long-lead orders, readiness and change after approvalWhat Gate 3 commits (A$3,200k, 51.8%), long-lead dates and the critical path, a ready-for-delivery check, and a fifth cold room at week 30 that would lift P(miss) to 39.1%.
  10. 10Reviewing the outturn and scaling the front endReady on 17 January 2028 after 41 weeks against 36, A$6,720k against a A$6,428k Class 3 point, A$292k of A$520k contingency drawn, and a scaled front end for a A$380k project.

Related Tools and Examples

References and source notes

The manuscript and worked examples are original KEVOS® writing. References inform particular concepts; their authors do not endorse this book. Web references were consulted on 28 October 2026.

  • Bent Flyvbjerg and Dan Gardner. How Big Things Get Done (2023). Supplied source, © Connaught Street Inc. and Bent Flyvbjerg, in copyright. Used only as a subject map for the idea of planning slowly and delivering quickly. No passages, chapter structure, stories, heuristics or figures are reproduced; the substance of the book rests on the other sources listed here and on its own fictional case.
  • G. Edward Gibson Jr, J. H. Kaczmarowski and H. E. Lore Jr, Journal of Construction Engineering and Management 121(3), 312–318. Preproject-planning process for capital facilities (1995). Source for pre-project planning as an owner-led process at the interface of business and engineering, also called feasibility analysis, conceptual planning and front-end planning. Used in Chapters 1 and 2 to describe what the front end is for.
  • M. R. Hamilton and G. Edward Gibson Jr, Journal of Management in Engineering 12(2), 25–33. Benchmarking pre-project planning effort (1996). Construction Industry Institute research on industrial projects that related the level of pre-project planning effort to project success. Cited in Chapter 1 for the direction of that relationship only; no effect sizes are quoted.
  • G. Edward Gibson Jr and P. R. Dumont, for the Construction Industry Institute, The University of Texas at Austin. Project Definition Rating Index (PDRI) for Industrial Projects, Research Report 113-11 (1996). Origin of the PDRI, a weighted checklist of 70 scope definition elements on a score sheet, weighted with input from experienced project managers and estimators, where a lower score means better definition. Chapter 3 describes it and builds the case's own, smaller index on the same principle. The case's elements, weights and threshold are invented and are not the PDRI's.
  • Chung Suk Cho and G. Edward Gibson Jr, Journal of Architectural Engineering 7(4), 115–125. Building project scope definition using project definition rating index (2001). Source for the buildings version of the PDRI, a weighted checklist of 64 scope definition elements, cited in Chapter 3 to show that the method has been adapted to different kinds of project.
  • G. Edward Gibson Jr, Yu-Ren Wang, Chung Suk Cho and M. P. Pappas, Journal of Management in Engineering 22(1), 35–42. What is preproject planning, anyway? (2006). Summary of five Construction Industry Institute research projects over about 14 years, covering more than 200 capital projects, which reported a positive relationship between thorough pre-project planning and project performance. Cited in Chapters 1 and 3.
  • Edward W. Merrow, John Wiley & Sons. Industrial Megaprojects: Concepts, Strategies, and Practices for Success (2011). Background on front-end loading as the strongest single influence on the outcome of large industrial projects, and on the damage done by cutting the front end short to save time or money. The argument is summarised in Chapters 1, 2 and 6; no data from the book is quoted.
  • Independent Project Analysis, Inc.. Front-End Loading (FEL) and the Stage-Gated Process (current online course description). Source for the naming of the three front-end phases used in industry practice, FEL 1 business planning, FEL 2 facility planning and FEL 3 project planning, each ending at a gate. Chapter 2 maps the case onto them.
  • AACE International. AACE International Recommended Practice 18R-97, Cost Estimate Classification System: As Applied in Engineering, Procurement, and Construction for the Process Industries (first issued 1997, revised since). Named by number and scope as the recommended practice that classifies estimates into five classes, from Class 5 (least defined) to Class 1, according to the maturity of project definition, with expected accuracy ranges that narrow as definition grows. Its tables and ranges are not reproduced; the ranges used in Chapter 4 are the fictional business's own guideline.
  • Robert G. Cooper, Business Horizons 33(3), 44–54. Stage-gate systems: a new tool for managing new products (1990). Origin of the stage-gate model in product development: work divided into stages separated by gates at which the decision to continue is made. Chapter 2 uses the idea for a capital project.
  • Infrastructure Australia. Assessment Framework (2021). Australian example of staged project development: defining problems and opportunities, identifying and analysing options, developing a business case, and post-completion review. Cited in Chapter 2 for the sequence of stages and for filtering options before a business case is developed.
  • Department of Treasury and Finance, Victoria. Gateway Review Process (current online guidance). Australian example of independent reviews at six key decision points, from concept and feasibility to benefits. Cited in Chapter 2 as a public-sector model of gate reviews; the case's gates are its own.
  • Boyd C. Paulson Jr, Journal of the Construction Division 102(4), 587–592. Designing to reduce construction costs (1976). Source for the observation that the ability to influence a project's cost is greatest early, when little has been spent, and falls steeply as the project proceeds. Used in Chapter 1.
  • Donald G. Reinertsen, Celeritas Publishing. The Principles of Product Development Flow (2009). Background on quantifying the cost of delay and on decisions that weigh time against money. Used in Chapters 7 and 8, where the case's cost of delay is a step at a seasonal deadline rather than a constant rate.
  • Safe Work Australia. Model Code of Practice: Construction work (November 2024). Named as the national model guidance for principal contractors and others carrying out construction work, including work health and safety management plans. Check with the local regulator whether it has legal effect in a given state or territory. No clauses are quoted. Victoria, where the running case is set, has not adopted the model WHS laws; it regulates under its own Occupational Health and Safety Act 2004, administered by WorkSafe Victoria.

Continue exploring

← All Library books