Six rails, one case file

The planning submission desk exists to turn a project file into an application that an authority can read without asking for clarification. The work begins with the drawing set and the supporting statements, and it continues until the lodged pack is numbered, dated and stored in a form that can be produced again at any time. Each document is checked against the revision list, and any mismatch between the drawing title block and the covering schedule is resolved before lodgement rather than after a validation query.

A submission is not a single upload. It is a statement about a site, a use and a set of impacts, and the authority will read it as one document rather than as a folder. The desk therefore assembles the pack in the order the reader expects: application forms first, then location and block plans, then the design and access statement, then the technical reports in the sequence in which they are referenced. An index is prepared so that anyone opening the file can find a report by its reference rather than by its file name. Where a report depends on another, the dependency is noted so that a reader is not left guessing which flood assessment or transport note the applicant is relying on.

The desk also keeps the original pack after lodgement. Planning files are requested months and sometimes years later, by officers, by objectors, by appeal representatives and by the client own team. Having the lodged version to hand removes the guesswork that comes from a folder that has been edited since submission. If an amendment is needed, the desk prepares it as a separate dated revision and keeps the earlier pack intact, so the history of the application remains readable.

Clients receive a lodgement note that records the reference, the date, the documents supplied and the contact who will answer queries from the authority. That note is the starting point for the tracking work that follows, and it is the reason a client can ask where a submission stands and receive a factual answer rather than an estimate.

Renewals fail quietly. A licence that has run for years is renewed without fuss until the year when the responsible person changes, the premises are altered, or the evidence expected by the authority moves on. GHD Approvals Ltd keeps each licence on a renewal calendar with its expiry date, its conditions and the documents that were accepted at the last grant. The cycle opens well before the deadline, which is the point at which the desk can still respond to a discovery rather than rush it.

The first step in a renewal cycle is a read of the current licence against the site as it stands today. Conditions are matched to actual practice, and any change in layout, use, hours or management is noted. Where a change requires a variation rather than a renewal, the desk says so early, because a renewal application that conceals a material change tends to surface later as a problem. The client receives a short list of what must be gathered or updated, with a target date for each item that leaves time for review.

Evidence gathering is usually the slow part. Training records, insurance schedules, maintenance certificates and premises plans are held by different people, and the desk works through them systematically rather than waiting for a single complete bundle. As items arrive they are logged, and the ledger shows which items are outstanding at any point. A renewal that is ready two weeks before the deadline is a different experience for a client than one that is completed under pressure, and the calendar is designed to make the first case the normal one.

Once the renewal is lodged, the desk tracks the application through to decision, responds to requests for further information and records the outcome. The new licence is added to the calendar with its fresh expiry date, so that the following cycle opens on time and the file stays continuous.

An inspection booked too early wastes the visit; booked too late it holds up a licence or a completion. The desk books inspection windows against a readiness check, so the date offered is one that the site and the file can both support. The check covers the documents the inspector is likely to request, the physical conditions that will be examined and the people who need to be present on the day.

Readiness is assessed specifically rather than generally. If the licence conditions require records of a certain kind to be kept, the desk confirms that the records exist, are current and can be produced without a search. If a condition refers to a plan, the plan on site is compared with the plan in the file. Gaps found at this stage are closed before the booking is confirmed, and if a gap cannot reasonably be closed in time, the window is moved rather than gambled on.

The briefing note is deliberately short. It sets out the scope of the visit, the documents gathered into a single folder, the names and roles of those attending and the three or four questions most likely to arise. Clients find the note more useful than a long handbook because it can be read in a few minutes on the morning of the visit. The desk keeps a copy in the ledger alongside the booking confirmation, so the preparation itself becomes part of the record.

After the visit, the outcome and any actions are recorded. Where an inspector identifies a minor issue, the note records the response and the date by which it was addressed. That record is often valuable later, when a renewal or an appeal asks what happened at a particular inspection and whether the matter was resolved.

The compliance file check is the discipline that holds the other rails together. Before a submission is lodged, a renewal is prepared or an inspection is booked, the file is read against the applicable conditions, guidance and the standards the client has adopted. The output is a short list of findings, each with an owner and a date, and the list stays open in the ledger until every item is closed or formally deferred with a recorded reason.

A check is not a review of everything at once. The desk works from the conditions outward: each condition is read, the evidence held against it is located, and the gap between the two is described plainly. If a condition says that a system must be maintained by a competent person, the check looks for the maintenance records and the evidence of competence, not merely for a sentence confirming that both exist. That approach is slower than a tick-box audit, and it is the reason the findings tend to be useful rather than decorative.

Findings are written for two audiences. The client reads them to understand what needs to be done, and a representative or authority may later read them to understand what was known at a given date. The language is therefore direct and avoids conclusions that the file cannot support. Where an item is a matter of judgement rather than a clear gap, the check says so and explains the reasoning, so that a decision about risk can be taken by the client with the facts in view.

The file check also looks backward. Earlier findings are re-read against the current file to confirm that items marked as closed have stayed closed. This closing loop is what turns a single check into a maintained record, and it is available to clients as a standing arrangement or as a one-off review before a significant submission.

An appeal is won or lost on the paper before it reaches the hearing. The desk compiles the appeal run in the order the tribunal expects, drawing on the lodged submission, the decision notice, the officer report and any correspondence that bears on the point at issue. Each document is cross referenced to the original submission, so a representative can move from an argument to its source without re-reading a folder for an afternoon.

The run is assembled with an eye on the reader who has not seen the site. A short index opens the bundle, followed by the decision and the reports it relies on, then the applicant material in the sequence in which it was lodged. Where a document was amended, the run makes clear which version was before the decision maker, because an appeal that rests on a revised drawing the officer never saw is easy to undermine. The desk does not edit the record; it organises it so that the record can be read fairly.

The desk also prepares a timeline that sets the key dates side by side: submission, consultation, any request for further information, the officer report and the decision. A clear timeline often reveals that a point taken in the decision notice rests on an assumption that the file does not support, and it is the first thing a representative tends to ask for. The timeline is kept in the ledger with the bundle, so that later questions about the appeal can be answered from the same record.

The service covers the paper work rather than legal representation. Where a client has an advocate or a planning consultant, the desk works to their instructions and supplies the bundle in a form they can use directly. Where the client is working without representation, the run is prepared to be read by the tribunal on its own terms, with page numbers, an index and a short covering schedule that identifies what is enclosed.

Certificate collections is the shortest rail and the one clients remember. When an authority issues a certificate or a decision notice, the desk collects the document, checks it against the application and the ledger, and hands it to the named contact with a covering note. The note records the reference, the issue date and any condition that continues to apply, so that the client is not left reading the certificate alone to discover what is expected next.

The check before release is not a formality. A certificate may carry a condition that was not anticipated, a date that differs from the application or a description of the development that does not match the lodged drawings. Each of these is picked up at this stage and explained in the note. If something appears wrong, the desk raises it with the authority before the document is treated as final, which is far easier than correcting it after the client has relied on it.

Copies are filed in the ledger alongside the original correspondence, and the case is then moved to an archive state that keeps the file readable for years. The archive note records the handler, the outcome, the date of release and the next date that matters, such as a renewal or a review. That single next date is often the most valuable part of the archive, because it means the client does not have to remember to come back.

Where a client has several sites or several certificates issued across a year, the desk provides a release schedule that lists each document, its reference and its date. The schedule becomes the index for the client compliance file, and it is updated as each new certificate is collected.