It was never the Regulator

There are two programmes on your project.

The first is the one you showed the funder. Approval twelve weeks after submission, work starting the following month, completion on a date somebody has already committed to.

The second is the real one. It starts when the design is actually finished rather than when it was scheduled to be. It pauses when an application is returned unassessed. It stops for six weeks when somebody realises a change was major. And it ends with a building standing complete and empty while a record is reconstructed that should have been kept as it was built.

The gap between those two programmes is usually measured in quarters.

Almost everyone blames the regulator for it.

The argument

The regulator's part of your programme is published, fixed and knowable before you start.

Twelve weeks at Gateway 2. Eight at completion. Six for a major change application. About twenty six weeks across an entire project, and every one of those weeks was on the programme before anybody broke ground.

Everything else you will wait for, you made.

That is the whole of this book, and it is not an opinion. It is arithmetic.

Who this is for

A developer, a funder, or a client-side project director with a higher-risk building.

Your project is behind. You have been told the regulator is the reason. You have no way of knowing whether that is true, because nobody publishes a lead time schedule for any of this and nothing in the system is designed to tell you early.

This book is written for the person paying, not for the person doing the work.

What is in it

A twenty minute check. Twenty questions you can answer yourself without a consultant. Count your no answers, then multiply the weeks you are carrying by what a week costs you. That number is the subject of the book.

Where the time actually goes. Seven waits, in order, each with what causes it, what it costs and what removes it. The design not finished before you apply. The application that was never valid and never started the clock. Determination. Every change during construction. The building that is finished and empty while the record is assembled. Signatures from people who left the project years ago. And the second three year clock nobody is watching.

Planning, and why you are already late. The section 106 at an average of 515 days, pre-commencement conditions, and the two clocks that run on different definitions of started.

What it costs. A framework for working out what one week of delay costs on your project, then the arithmetic for every wait. With a worked example that produces fifty four avoidable weeks against twenty six statutory ones.

The lead time schedule. Working backwards from submission and from completion. What has to start when, what can be compressed with money, what can be compressed with discipline, and the four things that cannot be compressed at all.

What to do now. Four lists. This week, this month, before you submit, before you complete.

How to buy the work. The difference between an appointment and advice. The single question that sorts the market. How to scope it so you get what you think you are getting, six lines to put in the appointment, and six signs that it is going wrong.

A plain English glossary, and five working forms.

The forms

These are what turn a book into a tool.

The gate map. The lead time schedule. The delay register, where every week lost is recorded with an honest answer in the avoidable column. The declaration tracker, covering everybody who has held a principal role since the project began. And the board paper.

That last one is the most useful page in the book. Three numbers on one sheet: what a week costs, how many weeks you are carrying, and what it would cost to remove them.

Boards do not fund compliance. They fund the removal of a number they can see.

What it does not do

It tells you where the time goes and what removes it. It does not tell you how to prepare an application, how to classify a change, or how to run a design team. Those belong to the people you appoint.

Where you reach that boundary, the book says so and tells you where the full treatment is.

Honest about its limits

England. Wales operates a separate regime with different rules, numbering and deadlines.

Planning is not my discipline. Part 3 is included because a developer needs the whole picture in one place, and the book says plainly that it is context rather than advice.

And the figures carry a date. The statutory periods are fixed in law and will not have moved. The medians and approval rates are the regulator's own published data, current to the end of August 2026, and they change every quarter. The book tells you to treat the statutory period as the legal benchmark and the published median as the planning allowance, and to check the current position before relying on any figure in it.