When the case officer changes mid-application

When the case officer changed on your planning application, everything that was agreed in a phone call went with them. The file survives, the drawings survive, the consultee responses survive. The understanding about the parapet height, the officer's view that the parking provision was acceptable, the informal agreement that a transport statement would not be needed: unless one of those is in writing on the file, it has effectively been deleted.

Reallocation is common and getting more so. The practical response is to build the record as you go, so that a handover costs you a fortnight rather than a redesign.

Why applications get reallocated

Officers leave, and development management teams carry vacancies. Applications are also moved for reasons that have nothing to do with the case: a restructure, a secondment, long term sickness, an officer's caseload rebalanced after a spike in submissions, or a case escalated from a junior officer to a senior one because the site turned out to be more sensitive than the validation screen suggested.

Some reallocations are a good sign. A case moved to a principal officer usually means it is going to committee or that a section 106 agreement is in prospect, both of which need someone more senior. A case moved to an agency officer covering a vacancy is neutral. A case that has been moved twice in ten weeks is a case nobody owns, and that is the one to escalate.

You will often find out by accident, from a returned email or a consultee copy. Ask directly if you suspect it, because the clock does not stop for a handover.

What gets lost

Three categories, in descending order of pain.

Undocumented agreements. Anything discussed verbally and not confirmed in writing. The new officer has no obligation to honour it and often no knowledge of it.

Context. Why the scheme is designed the way it is, what was tried and rejected, what the previous officer said would be unacceptable. A new officer reads the current drawings and forms a fresh view, which sometimes means reopening a question you thought was closed.

Momentum. A case that was two weeks from a delegated recommendation goes back into a queue. The determination period does not restart, but in practice the work does.

What survives is everything on the public file: the application documents, the consultee responses, your own written submissions, and the officer's published notes where the authority keeps them. That is the argument for writing things down, and it is why the content of the authority's record matters, as set out in our note on the statutory planning register.

Building a written record as you go

None of this is complicated. It is a habit.

1. After every meeting or call, send a short note the same day: what was discussed, what was agreed, what each side will do next, and by when. Ask the officer to correct anything they disagree with.
2. Keep the notes short enough to be read. Half a page, bullet points, no attachments unless something was requested.
3. Send them to the officer and copy the case reference, so the email lands on the file rather than in a personal mailbox.
4. Where something material is agreed, such as the scope of a technical report or the removal of a requirement, say so plainly in the note and ask for written confirmation.
5. Keep your own chronology of the application in one document, with dates, so a new officer can be brought up to speed in one email.

Point four is the one that pays. An officer who agrees in writing that a Transport Statement is sufficient has committed the authority to a position that a successor will find hard to reverse without explaining why. An officer who says it on the telephone has committed nothing.

The same discipline serves the application itself. A Planning Statement that records the design evolution, the pre-application advice received and the changes made in response is the document a new officer will read first, and it does the handover briefing for you.

The note to send a new officer

One email, on the day you learn of the change. Keep it to four short parts:

• Where the application stands: what has been submitted, what consultees have responded, what remains outstanding.
• What was agreed with the previous officer, with dates and references to the emails on the file.
• What you are waiting for from the authority.
• An offer of a call, and a note of the determination date.

Do not use this email to reargue the merits. Its purpose is to save the officer two hours of reading and to establish that you are organised. Offer to send a consolidated document set if the file is messy, because on a large application it frequently is.

Tone matters more than usual here. The new officer has inherited a case they did not choose, probably alongside several others, and the agent who makes that easier gets better outcomes than the agent who opens with a complaint.

Whether earlier agreements survive

Legally, no officer view binds the authority. Pre-application advice is given without prejudice to the determination, and only the decision notice binds. So in strict terms nothing survives a handover except the documents.

In practice, three things carry real weight with a successor:

Where an earlier written position is reversed, ask for the reason in writing and ask which policy or consultee response has changed. Sometimes the answer is that the first officer was wrong, which is a legitimate answer. Sometimes the answer reveals that the new officer has not seen a document, which is easy to fix.

If the reversal leads to design changes, those may trigger re-consultation, and the tests are set out in our note on re-consultation after amended plans.

Escalating sensibly

Escalate on process, never on planning judgement. A team leader will not overrule a colleague's view on design. They will act on an unallocated case, an unanswered email, or a determination date about to pass with no recommendation.

The sequence that works:

First, a polite email to the officer setting out what you need and by when. Second, if nothing moves within a week, the same request to the development management team leader, copying the officer, with the chronology attached. Third, the authority's formal complaints procedure, which is about service failure rather than the planning merits. The Local Government and Social Care Ombudsman can look at maladministration once the council's own procedure is exhausted, and cannot look at whether the decision was right.

Cross-boundary applications need this twice over, with two officers who may be reallocated at different times, and the coordination is covered in our note on cross-boundary sites and applications to two councils.

Keeping the timetable intact

The statutory period runs whatever happens internally: eight weeks for most minor applications, thirteen for majors, sixteen where environmental impact assessment applies. A handover does not extend it.

Three practical moves:

Confirm the determination date in your first email to the new officer. It focuses the conversation.

Decide early whether to agree an extension of time. Authorities ask for them routinely, and refusing one on principle can leave you with a hurried refusal rather than a considered approval. Agreeing one indefinitely leaves you with nothing to press with. Agree a specific date, in writing, with what will happen by then.

Keep the non-determination appeal in reserve rather than as a threat. Mentioning it in week seven of a case that has just been reallocated rarely helps. Knowing that the option exists, and the date it becomes available, changes how you negotiate.

If you are assembling the document set for a new or resubmitted application, enter your postcode on PlanScope to see which reports the site is likely to need.

This is general guidance, not legal advice, so check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.