Scotland: processing agreements and what they buy

This article is about Scotland, where the planning system runs on its own legislation and policy. A processing agreement is a written project plan between an applicant and a Scottish planning authority that sets out what information will be submitted, when each stage will happen, and the date by which the authority intends to decide. It buys programme certainty and a named point of contact. It does not buy a favourable decision, and nobody should sell it as though it does.

Processing agreement Scotland planning questions usually come down to one thing: whether the agreed date has any teeth. The honest answer is that its force is mostly reputational and procedural rather than legal.

What a processing agreement is

The Scottish development management regime works through a hierarchy of developments, with national, major and local categories, and a processing agreement is most useful on a major application where several consultees and a long information schedule are involved. Authorities report on their use of agreements through the annual Planning Performance Framework, which gives them a reason to agree and to stick to one.

England's nearest equivalent is the planning performance agreement, which is a charged service offered at the authority's discretion. The Scottish version is more standardised in form and more routinely offered, and it sits inside a performance reporting system that makes the agreed date visible.

For an applicant the practical gain is sequencing. You learn which consultees will be approached and when, which reports have to be in at validation rather than later, and who in the authority is responsible for chasing a late consultee response.

What goes in one

A usable agreement covers six things, and a weak one covers only the first two.

1. The parties, the site and the description of development
2. The target determination date, with the statutory period stated alongside it
3. A schedule of the documents the applicant will submit, with dates
4. The consultees to be engaged, when they will be sent the application, and the response period expected
5. Named officers on both sides, and what happens when either is unavailable
6. A review mechanism, saying how the dates are changed if something slips

The information schedule is where the value is. Put the reports in it by name, with the survey seasons that constrain them, so an ecology survey window or a traffic count in a neutral month is visible to everyone at the start rather than discovered in month three.

Who signs, and when

Sign before the application goes in, not after. An agreement negotiated during the pre-application stage can shape the submission, which is the point of it. One signed after validation is a diary entry.

Pre-application consultation is a separate statutory step in Scotland for national and major developments. A proposal of application notice has to be served on the authority at least 12 weeks before the application is made, and at least one public event has to be held. Fold that into the agreement, because the consultation report has to be submitted with the application and the 12 weeks sits on the critical path.

Signatures usually come from the applicant or agent and the head of planning or a delegated manager. Where a section 75 obligation or a road construction consent is likely, say so in the agreement and name the legal and roads contacts too.

Milestones, and what happens when one slips

Nothing automatic happens. A processing agreement is not a contract with a remedy, and neither side is in breach in the way a construction contract would be.

What a slipped milestone does is create a record. If the authority misses an internal date, the agreement gives you a documented basis for escalation inside the authority and a clear account for the Planning Performance Framework. If the applicant misses one, the authority has a documented reason why the determination date has moved, which matters when performance is reported.

That asymmetry is worth accepting rather than resenting. The agreement works through transparency.

Effect on timescales and the review or appeal route

The statutory determination periods in Scotland are shorter than people assume for local developments and longer for majors, and an agreement states the target date against that background. Where an agreement sets a later date than the statutory period, the point at which a non-determination appeal or local review becomes available can be affected, and the answer depends on the terms agreed and the current regulations.

Check that specific point with the authority before you sign. It is the one clause in a processing agreement with a real legal consequence, and it is the clause applicants skim.

The other timescale worth building in is notification to Scottish Ministers, which applies to certain categories of application and can add weeks at the end of the process. Notification of planning applications to Scottish Ministers explains when that bites, and the categories themselves follow from the development hierarchy, which the hierarchy of developments in Scotland sets out.

An illustrative example

A major residential application for 80 homes on the edge of a town, with a trunk road access, a protected species constraint and a section 75 obligation in prospect. The agreement is signed ten weeks before submission. It lists a bat emergence survey due in July, the transport assessment due at submission, the drainage impact assessment due at submission, and heads of terms to be issued within four weeks of validation. The details are illustrative.

What that agreement prevents is the common failure, which is a transport assessment submitted at validation, a roads consultee response eight weeks later asking for a different trip generation method, and a survey window missed in the meantime. The agreement does not make the roads authority answer faster. It makes the dependency visible early enough to do something about it.

Negotiating a useful one

Ask for named officers and a response time from each internal consultee. Ask for the validation requirements to be confirmed in writing as part of the agreement, because arguing about validation afterwards costs more than any other delay. Offer realistic dates for your own submissions and then hit them, because an applicant with a clean record gets more attention than one who has already moved two dates.

And push back on a template that contains only the determination date. An agreement with no information schedule and no consultee dates is a courtesy, and you can get the same thing from a phone call.

Where the application pack itself is the constraint, work out which supporting documents the scheme needs before the agreement is drafted. The list of report types by category is a reasonable starting point for that conversation, and local place plans may add policy expectations in some areas, as local place plans in Scotland describes.

PlanScope's drafting is grounded in English national policy and English local plans, so for a Scottish application the reviewer has to check the draft against National Planning Framework 4 and the relevant local development plan before it is used. Browse the report types to see what a Scottish submission pack might contain.

This is general guidance, not legal advice. Check the position with the 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.