Planning application statuses explained

Pending or under consideration

These labels usually indicate that a decision has not been recorded. They do not describe the officer’s likely recommendation. Read the application type, key dates and any published correspondence to understand what stage the case has reached.

Check council records and collection dates too. Information on PlanningTrack may be older than its council source. If a deadline or purchase depends on the answer, go to the official register rather than relying on a search result badge.

Approved, permitted or granted

Open the decision notice to see exactly what was decided. Approval of details required by a condition is different from permission for the original development. A broad “approved” category is useful for sorting records, but it cannot express that difference on its own.

Read any conditions and the list of approved drawings. For English planning permissions, our next-steps guide explains how to organise those documents. Other UK nations have their own procedures.

Refused or withdrawn

For a refusal, look for the formal reasons in the decision notice. Do not infer them from the number of objections, the length of time the case took or a neighbour’s account of a meeting.

A withdrawal does not tell you why the applicant withdrew, nor does it show the result of any later application. Search the address again and inspect related records. If there is an appeal, read its outcome separately from the original council decision.

Unknown, decided and other broad labels

“Decided” can describe a stage without telling you the outcome. “Unknown” may mean the source wording could not be put confidently into a standard category. Neither is a reason to guess.

PlanningTrack keeps council wording alongside broader categories where it is available. When comparing results, keep a column for application type and one for outcome. Otherwise a group of condition approvals can get mixed into a set of new development proposals.

Use your authority hub to open individual applications, and our reading guide to work through the documents. If you are comparing places, the guide to approval rates explains how application types and coverage affect comparisons.

Distinguish application progress from decisions

A register status often answers one of two questions: where is the application in the process, and what was the result? These are related but different. “Under consideration” describes a stage. “Refused” describes an outcome. A broad label such as “decided” can tell you that the process reached a decision without telling you which decision was made.

Before interpreting a status, read the application type and proposal. The same word “approved” can appear on an application for development and on a later request concerning a particular detail. If you ignore the type, you can turn approval of one limited matter into an incorrect claim that an entire development has been approved.

Keep the council’s original wording in your notes, even if you also use a simpler category for sorting. A standard category helps compare lists, while the original text preserves detail that may not fit neatly into it. If the two appear inconsistent, open the source and establish the actual position rather than choosing whichever wording supports your expectation.

For a live case, record when you checked the status. A note saying “pending” without a date becomes less useful as time passes. Add the official link so you can return to it quickly. If someone forwards your note later, the date helps them understand that it describes an observation, not a permanent characteristic of the property.

What does pending consideration mean?

“Pending consideration” generally indicates that a decision has not been recorded in the field you are viewing. It does not reveal the officer’s recommendation or establish which assessment tasks remain. Read the dates, documents and any published correspondence to find out more. A pending label on its own cannot tell you whether a drawing is missing or a response is being reviewed.

If a target date has passed, check whether the information is current and whether the timetable has changed. Do not assume the status is wrong simply because you expected a decision by now. Conversely, do not assume a collected record is fully up to date. Follow the council link when a decision or deadline matters to what you intend to do next.

For applicants, a useful enquiry identifies the reference and asks what action or information is outstanding. For neighbours, the immediate question may be whether comments are still invited and which plans are current. Those are different enquiries even though both start from the same pending record. The timescale guide explains the dates to read alongside it.

Avoid treating silence as evidence of likely approval or refusal. A public register provides published information, not a running account of every internal step. If your research reaches a limit, state that limit. “The official record was still pending when checked” is a sound observation; “the council must be about to approve it” is a prediction.

What validation and registration confirm

An application may show labels indicating that it has been received, registered or validated. Read the authority’s explanation of those terms rather than assuming they mean the proposal has passed a design assessment. Administrative progress and a substantive decision are different matters. The presence of a reference does not by itself settle whether the proposed development is acceptable.

Check which date is attached to the label. A received date may precede a valid date, while a later publication or upload date may simply describe when a document appeared online. When comparing applications, use the same milestone consistently. Otherwise a chart of apparently slow cases may mix several different measures.

If an application appears incomplete or you are waiting for confirmation, look at correspondence from the authority and your agent. Ask what specific information remains required. Avoid repeatedly resending the whole application without understanding the issue, because that can make version tracking harder. Keep a record of what was requested and what was supplied.

For people researching a neighbouring proposal, these labels are a prompt to check the current file, not to speculate about the eventual outcome. Read the proposal, application type and published consultation information. If you need help navigating the documents, use the application reading guide before drawing conclusions from an administrative badge.

Check which works or details were approved

When you see “granted”, “permitted” or “approved”, open the decision notice and match its reference to the record. Read the description of the matter decided and any conditions. Identify the approved plans where they are listed. The notice provides the detail that a search-result badge cannot carry.

Suppose a fictional site has permission for an extension and a separate record approving a material sample. Both records may be grouped as approvals in a broad dataset. They are not two separate permissions to build two extensions. Recording application type and reference alongside outcome prevents this kind of double interpretation.

Approval also does not prove that the development has been built. Planning records and physical completion answer different questions. A property researcher should compare the paperwork with the building and obtain appropriate advice where the relationship is unclear. A market analyst should avoid counting every permission as a completed project or a guaranteed construction lead.

For a project you intend to carry out in England, the post-approval guide explains how to organise the notice, conditions and drawings. For other UK nations, check the relevant procedures. In every case, read the actual record before turning a short outcome label into a statement about what can happen next.

Find refusal reasons in decision notices

A refusal status tells you the broad outcome, but the reasons need to be read in the formal notice. Find each reason and the supporting explanation in the officer report where available. Do not infer the cause from the number of objections, a local news headline or the length of the application process.

Keep the refused scheme’s drawings separate from any later proposal. They can be useful for understanding history, but they do not necessarily describe what the applicant is now pursuing. A revised application at the same address may differ in important ways. Compare it directly rather than assuming the original refusal applies unchanged to every future design.

If an appeal is recorded, read that as an additional part of the history. Identify the appeal reference, decision and documents instead of overwriting the original council outcome without explanation. A timeline that preserves both stages is more informative than a single cell that switches from refused to approved with no indication of why.

For applicants considering their next step, use the current official guidance and appropriate professional advice. A generic status guide cannot decide whether to amend, resubmit or appeal a particular case. For neighbours, avoid assuming that refusal means the site will never be developed. It describes the decision on the proposal and evidence considered in that application.

Why was a planning application withdrawn?

The status may not tell you. Withdrawal records an outcome in the application history, but it does not automatically reveal the applicant’s reason. Unless correspondence or another reliable source explains it, avoid guessing that the council forced a withdrawal, that permission was certain or that a replacement scheme is already agreed.

Search for later applications at the site, but keep the results separate. A new reference can concern a revised proposal, another type of submission or an unrelated project. Read the description and boundary to establish the connection. Do not treat a similar address as proof that the newer application replaces every aspect of the withdrawn one.

For property history, retain the withdrawn application as part of the chronology. Its documents may explain an idea that was explored, but distinguish those drawings from an approved scheme. Label downloaded folders clearly. A polished drawing from a withdrawn file can be mistaken for approved work if its reference and outcome are lost.

For statistics, explain how withdrawals are treated. Excluding them from an approval-rate denominator answers a different question from counting them as unsuccessful applications. Neither choice should be hidden. PlanningTrack’s authority percentage uses approved and refused records only; the statistics guide explains what that means for interpretation.

Distinguish prior approval, certificates and condition decisions

Some record labels describe a decision within a particular procedure rather than an ordinary full planning application. Read the application type and the wording of the decision together. A phrase that sounds like a broad permission can have a more specific meaning when attached to a certificate or an approval of details.

Do not translate every unfamiliar result into approved or refused without preserving the original wording. If you are building a research spreadsheet, include an “original outcome text” column and a “needs review” flag. It is better to leave an uncertain category visible than create a misleadingly tidy table that conceals distinctions important to the project.

For English permitted development and lawful development certificate questions, start with the permitted development guide and follow its official sources. That article explains why confirming lawfulness and assessing an application for permission are not interchangeable tasks. Other UK nations have their own rules and terminology.

If the public file is too sparse to establish the procedure, ask the authority a specific question using the reference. Describe which field or notice you cannot interpret. Avoid asking whether “the property is approved”, because properties can have many records covering different works and uses. Identify the development or document you actually mean.

What to do when two websites show different statuses

First compare the references. Similar descriptions at the same address may belong to different applications. If the references match, compare check dates and source dates. One service may have collected the record before the council updated it. A recent page view does not necessarily mean the underlying information was collected recently.

Open the official register and read the current record, including the formal notice if a decision is shown. If the council page itself contains inconsistent fields, record the discrepancy and seek clarification rather than choosing a field at random. Keep screenshots or notes with dates if you need to explain the issue to an adviser.

Avoid repeatedly refreshing a collected page as a substitute for following the source. PlanningTrack displays source links so that you can inspect the authority’s information. A data mismatch is a reason to check provenance, not proof that one outcome has been secretly reversed. Establish the underlying evidence before circulating an update.

When you correct a shared research note, explain what changed and why. “Updated after checking the official decision notice” is more useful than silently editing the outcome. Anyone who relied on the earlier note can then identify which finding needs reviewing. This is especially important when a purchase, comment deadline or project programme depends on the result.

• Read application type, original status wording and decision notice together.
• Keep council decisions, appeals and later submissions as distinct events.
• Record the official source and date checked whenever you share a status.
• Leave unknown outcomes unresolved until the evidence supports a classification.

Does an approved application mean building work has started?

No conclusion about physical progress follows from an approval badge alone. The record describes a planning decision, while the question of whether work has begun concerns events on the site. A business researching potential work or a buyer checking a property needs to keep those questions separate. Do not relabel approved applications as active construction projects without additional evidence that supports that description.

If physical progress matters, identify the reliable information you need and obtain it through an appropriate route. A dated observation may describe visible activity, but it may not establish which permission the work relates to or whether every relevant requirement has been met. Keep the observation separate from the planning record and explain the link only where you can support it.

The same caution applies in reverse. A site that appears unchanged in a photograph is not proof that a permission has expired, been abandoned or never been implemented. Those are different questions requiring their own evidence and, where relevant, professional advice. Describe the status, documents and observations you actually have. A transparent note with an unresolved question is more useful than a definite answer assembled from unrelated clues.