Turn a planning register into a weekly project watchlist

Start with scope: what the public register can and cannot tell you

According to GOV.UK’s register finder, councils make public the plans for developments that need planning permission. The same page says the service is available in England and Wales only. For a business watchlist, that means your source is the local authority’s published planning register, accessed through the relevant council search page.

That scope matters. A planning record is evidence that a proposal has been submitted or published. It is not proof that the work will happen, that a contractor is being sought now, or that the project suits your firm. Your watchlist should therefore record public facts first, then list any business questions separately.

Decision timing also needs context. GOV.UK guidance on determining a planning application sets out statutory time limits after validation in England: 13 weeks for major development, 10 weeks for technical details consent and certain public service infrastructure development applications, and 8 weeks for other development types, with 16 weeks where an application is subject to Environmental Impact Assessment. The same guidance says a longer period can be agreed in writing with the applicant. So an older live application is not automatically late in a way you can verify from the public register alone.

• England and Wales: public register finder scope from GOV.UK.
• England: determination timing guidance from GOV.UK.
• Do not assume a missing decision means inactivity; an extension of time may exist.

Your weekly review agenda

A useful weekly review can be done in five passes. The aim is not to collect the most records. It is to keep a manageable list of applications that still deserve attention.

First, check for new records in your chosen area and project type. Add only those that appear relevant enough for a second look. Record the council, application reference, site description shown publicly, proposal summary and the date you first saw the record.

Second, review changed records already on your watchlist. Look for visible changes such as a new status, extra documents, a committee outcome or a decision notice. Only log what you can actually see on the register.

Third, list unresolved questions. Examples include whether the application is major or non-major, whether drawings clarify the scale, or whether there has been a written extension of time that is not obvious from the public-facing page. Keeping questions separate prevents guesswork creeping into your notes.

Fourth, assign the next check for each live record. That could be a recheck next week, a document review, or a later date tied to the likely decision window. In England, the GOV.UK guidance on determination periods can help you set a sensible follow-up interval after validation, but do not treat those periods as guaranteed decision dates.

Fifth, archive records that no longer deserve weekly attention. Archiving is useful when a project is outside your area, clearly mismatched to your services, refused, or unchanged for long enough that you want to move it to monthly review. Keep the archive reason short and factual.

• Pass 1: new records.
• Pass 2: changed records.
• Pass 3: unresolved questions.
• Pass 4: assigned next checks.
• Pass 5: archive with reason.

Which functions depend on the council’s actual search interface

Not every council register works the same way. GOV.UK points you to the council register, but the day-to-day monitoring experience depends on that council’s own search interface.

For example, some councils may let you filter by date received, status or application type, while others may require broader keyword or address searches. Some publish a clear list of recent applications; others make you open each record individually. Some show document tabs, neighbour comments or decision notices prominently; others make them harder to find.

That means your watchlist process should be designed around the minimum common denominator: record references, proposal text, visible dates, visible status and any new public documents. If a council offers saved searches or alerts, treat those as convenience tools rather than essential features. Your underlying review method should still work when the interface is basic.

• Possible interface-dependent functions: saved searches, alert emails, recent-application lists, date filters, map search, document tabs, status labels.
• Build your workflow so it still works with manual weekly checking.

Fictional three-record change log example

The example below is fictional and shows how a weekly change log can stay factual without pretending to know more than the register shows.

Record A: Reference 25/00123/FUL. Last week the public page showed 'validated'. This week a new drawing set appears and the status still shows live. Evidence note: documents added. Open question: do revised drawings change project scale? Next check: review the new plans this week.

Record B: Reference 25/00456/HH. Last week the record was on the live list. This week a decision notice appears. Evidence note: decision issued. Next check: archive from the weekly list and store outcome in the archive.

Record C: Reference 25/00789/OUT. Last week the application had been live for several weeks. This week there is still no decision visible. Evidence note: no visible change on the register. Open question: is there an agreed extension of time with the applicant? Next check: recheck next week rather than assuming delay. This approach reflects GOV.UK guidance that written extensions can be agreed in England.

A practical checklist for your team

Use this checklist at the same time each week so your notes are comparable.

• Open each target council register for your chosen area.
• Run the same searches each week and note the search method used.
• Add genuinely new records to the watchlist with reference, council and proposal summary.
• For each existing record, log only visible changes since last review.
• Record unresolved questions in a separate column.
• Assign one clear next check date or action to every live record.
• Use England decision-period guidance carefully and only where it applies.
• Archive low-fit, decided or no-longer-priority records with a reason.
• Keep a simple audit trail so another team member can continue the review.

Limitations and next checks

This workflow is strongest as a repeatable research habit, not as a prediction system. The public register tells you that a proposal has been made public by the council, but it does not guarantee construction, procurement activity or timing. In England, published decision periods are helpful for planning your review rhythm, yet the GOV.UK guidance also makes clear that written extensions can alter the timetable.

Your next checks should therefore stay close to the original source. Confirm the nation and council involved, revisit the public record itself, and read any newly published decision or supporting documents before drawing conclusions. If you work across England and Wales, remember that the register finder covers both nations, while the supplied determination guidance here is specifically about determining applications in England.