How a Town Planning Consultancy Replaced Spreadsheets With a Shared Timeline
Maddox Planning, a London-based town planning consultancy, worked with developers, local authorities and private clients on planning permissions while managing projects in Excel. The firm needed a clearer way to show what had to be prepared for an application, when each step was due, and how risk and timeframes would be handled. This page explains the problems that prompted the change, the workflow that replaced them, and the reported results — and gives you a checklist for judging whether a similar switch fits your own projects.
What was not working
Maddox Planning helps clients secure planning permissions. Before the change, the team tracked work in Excel spreadsheets. That setup created four recurring problems:
- No single place to see all projects together, so progress was hard to consolidate and bottlenecks were hard to spot.
- Manual entry that was slow and prone to formula errors, which disrupted timelines and created confusion for staff and clients.
- Files shared by hand, with slow updates, miscommunication and no live view of progress for clients.
- Heavy administrative work, with project managers updating spreadsheets instead of doing strategic planning, delaying decisions and momentum.
Use this as a diagnostic: if two or more of those describe your current process, a spreadsheet may be the bottleneck rather than your team.
What the team needed
The consultancy looked for a tool that could do three things: give everyone a clear visual timeline for planning applications with shared milestones and deadlines; improve transparency between internal teams and clients; and cut administrative overhead through automation and simpler collaboration.
Senior planner Ollie Cooper described the aim as producing programmes that show what must be prepared for an application and when, shared openly with clients so they can understand the work, the timeframes and the risk profile. That framing matters: the timeline is not just an internal diary, it is a client-facing explanation of the route to permission.
How the workflow changed
After the switch, work was organised around four changes:
- Shared workspace: clients and consultants work from the same live timeline, with real-time updates replacing long email threads.
- Less manual updating: automated scheduling and clear task assignments reduce overlaps and confusion, freeing managers for higher-value work.
- Earlier risk visibility: a clear timeline makes potential delays easier to identify early, so teams can adjust and prioritise critical tasks.
- Simpler tracking: instead of multiple spreadsheets, each project has clear milestones, real-time updates and a named owner for every task, which strengthens accountability.
A practical way to copy this pattern: for each application, list the preparation steps, assign an owner and date to each, share the live view with the client, and review critical-path tasks weekly for delay risk.
Reported results and a switch checklist
The account describes three outcomes after the change: administrative workload fell by 10-20%; timelines became more accurate because workflows were faster and more efficient; and greater transparency led to fewer miscommunications and project delays. Read these as one consultancy's reported experience rather than a guaranteed result for every team. If you want to make a similar claim about your own organisation, first decide how you would measure it — for example, hours spent on manual updates per project per week, before and after — and keep the baseline evidence on file so the figure can be defended. A blank worksheet for that purpose might record: baseline period, hours logged, projects covered, and the same measures after the change. Until such figures exist for your team, present the 10-20% range only as what this consultancy reported, not as your own measured outcome. The same caution applies to the timeline-accuracy and transparency points: they are qualitative observations unless you define a metric, such as the number of schedule revisions or the count of client queries about status, and track it consistently. With that framing in place, the case is useful as a pattern to test rather than a promise to repeat. The underlying mechanism is straightforward: when milestones, owners and dates sit in one shared view, the work of chasing status drops and the work of anticipating problems rises. Whether that shift shows up in your numbers depends on how disciplined the team is about keeping the view current and how much of the old spreadsheet habit lingers alongside it. A short trial on one or two live projects, measured against the baseline above, will tell you more than any general claim. Decision checklist before you switch: can every project live in one central view with milestones and deadlines? Can clients see a live timeline without you sending files back and forth? Is every task assigned to a named person? Can you spot a likely delay early enough to reprioritise? Does the change actually reduce manual updates, rather than adding a second system alongside spreadsheets?
About the consultancy
Industry: town planning consultancy. Location: London, England, UK. The core lesson is transferable even if your sector differs: replace scattered, manually updated files with one shared, visual timeline, assign every task, and use the timeline to surface risk early. That combination — visibility, ownership and live updates — is what reduced admin and improved coordination in this case.