Projects

Good for the books, bad for the project

Mohit Saini · 12 Mar 2020 · 4 min read

Good for the books, bad for the project

Accounting for large construction and engineering projects poses a real challenge. A project may start in one financial year and finish in another. If a company waited until handover to recognise revenue, its accounts would swing wildly from year to year and periods couldn’t be compared.

So accounting standards allow revenue to be recognised as the project progresses, commonly in proportion to the cost incurred so far against the total expected cost. If 40% of the expected cost has been spent, roughly 40% of the contract value can be booked as revenue.

As an accounting convention, this works well. The trouble starts when the accounting measure becomes the target that drives the project.

Cost-weighted vs dependency-weighted

From an accounting point of view, a task’s importance is proportional to its cost. Expensive tasks move the revenue needle; cheap ones don’t.

From a project point of view, a task’s importance depends on where it sits in the chain of dependencies. A cheap task on the longest path can delay the whole project. An expensive task on a side path, done early, adds nothing to completion.

In most projects, the tasks on the longest path account for a small share of the total cost. So when resources are limited and shared (and in engineering, procurement and construction companies, design and purchasing teams usually are), prioritising work for revenue booking means neglecting the longest path.

How the cascade unfolds

Companies typically break annual revenue targets into quarterly and monthly ones and pass them down as departmental targets. Here is what follows:

  1. Start everything early. To book revenue, design and procurement start on as many projects as possible. Shared engineers multitask, and every design takes longer.
  2. Easy drawings first. Designs that need inputs from many other groups or vendors (often the critical ones) get stuck. Under pressure, drawings are released unapproved, with gaps, or the easiest ones are released first. Many drawings go through several revisions.
  3. Easy purchases first. Procurement buys items whose designs are final, which are usually not the critical ones. Items needed much later arrive at site early, while critical items are late.
  4. Expensive work first. Manufacturing and site work focus on items that book large costs, while cheaper critical items wait. Revenue is booked; erection is held up for want of parts.
  5. The tail. By the time most civil and structural work is done and most items bought, most revenue is booked. But erection is stuck, and management attention moves to the next project with more revenue to book. The site is eventually commissioned under customer pressure, with a long list of pending items.

The vicious loop

That pending list is where the cash goes. Typically 10–15% of contract value is held back as retention money until the punch list is closed. As management moves on, old projects linger with a few people still assigned, and retention money stays unpaid. These half-closed projects pile up. Receivables climb, sometimes towards a year of sales.

Rising receivables squeeze cash flow. Vendors’ advances are paid late, so their supplies slip, which delays new projects and their billing. Disputes over penalties and missing material make old sites harder to close. Every so often, management writes off part of the retention money just to close a site and release cash.

The irony: driving projects by revenue booking ends up booking less revenue than the company could have earned.

The tempting fix that doesn’t help

Many companies recognise the delivery problem but keep monthly revenue targets, and look for a better tool: integrated software that promises accounting, costing, materials and project management in one system.

The reports look impressive in the sales presentation. In practice, such tools need a detailed, stable plan up front and constant updating during execution. In engineering projects, much of the detail isn’t known until earlier stages are complete. In environments full of multitasking, the task schedules go out of date almost immediately. Middle managers see the data entry as a burden with no benefit to them. Many companies end up using these systems superficially, or not at all.

The way out: manage the project, let the accounts follow

Critical Chain Project Management addresses this through two shifts:

  1. Stop starting everything early. Control the release of projects into design and procurement according to capacity. Control the release of drawings to site, so crews don’t work on low-priority areas while critical areas wait.
  2. Stop managing by task milestones. Plan with tight task estimates and move the safety into buffers at the end of the project and where side paths join the longest path. Watch buffer consumption for early warning and for setting priorities across projects.

And replace the main progress measure:

Track % completion of the longest path against % of buffer consumed, not cost booked.

With this measure, fast progress on side paths can’t hide slow progress on the longest path. If the longest path doesn’t move, completion stays flat while the buffer is consumed, and bad news reaches management early, while there is still time to act. The familiar pattern of “90% done in one year, the last 10% in another” goes away.

Picture a project review where the cost-based report says the project is 62% complete, comfortably on track for the year’s revenue. The longest path tells a different story: the critical equipment foundation can’t start until a vendor drawing is approved, and only about 30% of the longest path is done. Meanwhile, 45% of the project buffer has already been used. On the revenue view, nothing needs attention. On the buffer view, the project is red, and the vendor drawing is the most urgent item in the company this week.

Revenue recognition doesn’t disappear; it simply stops being the steering wheel. Booked revenue is a result of managing projects well, not a way to manage them.

Related reading

Mohit Saini

Strategy, supply chain & sales transformation consultant. About · Book a discussion