Understanding planning · England
Planning approved: conditions and what happens next
Planning permission can include conditions, approved drawings and requirements for different stages of work. Read the decision notice and identify anything that needs approval before building starts.
Save your decision notice
Start with the formal notice rather than the status badge or a committee headline. Check the reference, description of development and date. Make sure you are reading the permission for your scheme rather than a related application.
Save the notice with the drawings it identifies. If your working folder contains several versions, create a separate folder for the approved set and retain the original filenames. It is much easier to prevent a mix-up now than resolve one after a builder has priced an older plan.
Sort conditions by when they apply
Read each condition in full, including the reason. Some require action before development begins, others before occupation or at another stage, and some control how the development is used. Where approval of details is required, check the authority’s process for applying to discharge the condition.
Build a small tracker with the condition number, requirement, timing, person responsible and evidence of approval. Copy the actual wording into the tracker rather than shortening “before commencement” to “later”.
If you are unsure how a condition applies to your programme, resolve that with your adviser and the authority before the relevant work. The government’s conditions guidance explains the English framework.
Check proposed changes against approved drawings
Materials change, costs move and a window that worked on paper may become inconvenient. Keep a list of proposed departures from the approved scheme. Ask your adviser which changes need a further planning process before agreeing them on site.
Give the builder and designer the same approved drawing set. Include later written approvals for condition details. A shared folder is helpful only if someone is responsible for keeping it current.
Keep planning and other approvals together
Planning permission and building regulations approval are separate. Depending on the project, other permissions, agreements or private rights may also need to be addressed. An approved planning record does not answer every question about whether work can begin.
Make a project checklist with your advisers and assign each item to a person. Keep planning decisions, condition approvals and the other project documents clearly labelled so that “approved” always points to a particular document.
Find related applications through the authority hub and check the official council record for the latest position. Our status guide explains why an approval badge alone is not enough.
Create an approval file before discussing a start date
Put the formal decision notice and the drawings it identifies in one clearly named folder. Include the application reference and decision date in the folder name. Keep the complete notice rather than only a screenshot of the approval status. The detail you need for a project is often in the conditions, plan list and wording that does not appear in a search result.
Separate the approved set from earlier design versions. It is reasonable to retain old drawings for history, but they should not sit beside the current construction information without labels. A builder pricing from revision A while a designer develops revision C can create confusion even before anyone reaches the site. Establish which set is being used for each purpose.
Add a one-page index listing the notice, drawing numbers, relevant supporting documents and any later approvals. Record where each item came from and when it was checked. The index should help another person find the evidence quickly. It does not need to restate every condition or reproduce the entire application history.
Before announcing a firm start date, review the file with the people responsible for the project. Ask which requirements must be addressed first and who is handling them. This turns the approval into an organised next stage rather than an assumption that every remaining task will happen automatically.
| Field | What to record | Why it helps |
|---|---|---|
| Permission reference | The application and formal decision date | Keeps later submissions tied to the correct permission. |
| Condition number | The exact condition being addressed | Prevents one approval being treated as covering every condition. |
| Requirement and timing | Actual wording where timing matters | Avoids turning a pre-stage requirement into an undefined later task. |
| Owner | The person responsible for preparing the information | Makes handovers and dependencies visible to the team. |
| Submission | Reference, date and documents supplied | Distinguishes information sent from approval received. |
| Decision evidence | The issued decision and approved details | Shows what was actually agreed and any qualifications. |
| Next action | The remaining task or confirmation needed | Keeps an unresolved issue visible in the programme. |
Check approved works against your building plans
Read the description of development and compare it with the current design brief. Projects can evolve during an application, and the final permission may concern a different arrangement from the first sketch or the version originally priced. Do not assume a familiar address and an approval badge establish that every planned element is included.
Check the application type as well. A record approving a particular detail may relate to an earlier permission rather than grant permission for the whole development. Keep the relationship between those records explicit. The status guide explains why broad outcome labels need to be read alongside the type and notice.
Identify any part of the project that is not clearly covered by the documents you have. Put those items into a question list for your adviser. Avoid resolving uncertainty by assuming a feature is too small to matter or must have been understood by everyone involved. A clear question asked early is easier to deal with than an undocumented assumption discovered during construction.
If several permissions exist for the site, ask which scheme the project is proceeding under and how relevant later decisions relate to it. Do not combine the most attractive parts of different approved drawings into a new design without advice. Keep the intended scheme identifiable through its actual references and approved documents.
Build a planning condition tracker
Read every condition and extract its requirement, timing and any information to be approved. Use the actual wording when timing is important. A condition applying before commencement should not become a vague task labelled “sort materials later”. If you do not understand a requirement, flag it for clarification rather than shortening it into something that sounds easier.
A useful tracker has columns for condition number, requirement, timing, responsible person, submission reference, decision evidence and outstanding action. The distinction between submission and decision is important. Sending details to the authority may be a necessary step, but it is not the same as receiving the relevant approval.
Assign responsibility deliberately. The architect may prepare some details, a specialist another report and the applicant the overall coordination. Do not assume a task belongs to someone simply because their profession appears related to it. Confirm what each person has agreed to do and what information they need from others.
Review the tracker before the relevant stage of work. Conditions can operate at different points, so one check at the start of the project may not be enough. Use the tracker to bring upcoming requirements into the programme. It should support decisions, not become a static document that nobody opens after the first meeting.
- Read approved documentsNotice, scope and approved drawing references.
- Assign condition tasksCondition requirements, timing and owners.
- Arrange required approvalsRequired details and other project arrangements.
- Update project recordsCurrent drawings, changes and completion records.
This diagram is a project organisation aid, not permission to begin work. Follow the actual notice, relevant conditions and professional advice for the scheme. Some requirements apply at different stages, so keep the tracker active through the project rather than treating the first approval as the end of all checks.
What does discharge of planning conditions involve?
Where a condition requires approval of details, identify the authority’s current submission process and the information needed for that condition. Read the requirement precisely. A broad report or a generic product brochure may not answer the specific question in the notice. Ask your adviser to explain how the proposed submission addresses each relevant part.
Keep a condition submission tied to the original permission and condition number. If several conditions are addressed together, make the organisation clear. Someone reviewing the material should be able to locate the evidence for each condition without guessing which drawing or paragraph is intended to answer it.
When a decision is issued, read what it actually approves and retain the associated documents. Do not assume approval of one submission deals with every outstanding condition on the site. Update the tracker with the reference, date and any qualification. A green tick is useful only if it points to evidence that explains what has been completed.
If details are revised or the project changes, ask whether the existing approval remains applicable. Keep superseded submissions separate from current information. Government guidance on planning conditions explains the English framework, but your project team needs to interpret the actual conditions and decisions for the scheme you intend to carry out.
Allow time for materials and design approvals
A condition concerning materials can affect procurement as well as paperwork. Identify which details need to be settled and when they are needed on site. Ask the designer what information is required from suppliers and whether samples, specifications or drawings are relevant. Avoid ordering a large quantity on the assumption that an unspecified alternative will be accepted.
Keep product references and submitted details together. A colour name alone may not identify a particular product, finish or manufacturer. If a supplier changes the specification, ask the designer to review the substitution against the relevant approval before it becomes part of the build. Record the decision rather than relying on a brief conversation at delivery.
The same principle applies to other details required by conditions. Work backwards from the stage at which the information is needed and identify dependencies. A specialist may need a survey, another design decision or access to the site before preparing a submission. A realistic programme makes those dependencies visible rather than assuming every detail can be resolved at the last moment.
Do not treat this as an invitation to make technical decisions from a checklist. The tracker helps organise responsibilities and evidence. The design and assessment still need the appropriate expertise. If a condition’s wording is unclear, seek clarification before commissioning work that might not address what the authority requires.
What if you want to change the approved plans?
Changes are common during detailed design and pricing. Record them as they arise rather than allowing the working drawings to drift quietly away from the approved scheme. Include the reason, affected drawing and proposed replacement. This gives your adviser a clear basis for assessing what further planning process, if any, may be required.
Avoid deciding that a change is minor solely because it is inexpensive or visually small. Cost and planning significance are different questions. A change to an opening, position or use can need careful consideration even when it seems straightforward to a builder. Describe the actual difference and obtain advice on the relevant route.
If a further application or approval is needed, keep its reference connected to the original permission. Update the drawing register only when the position is clear, and retain the evidence for the change. People working on site should not have to infer which version applies from the date a file was last emailed.
Communicate approved changes to everyone who needs them. Replace the relevant working information deliberately and record which earlier sheets are superseded. A central folder helps, but only if someone maintains it and the team knows to use it. Version control is a practical construction issue as well as a document-management habit.
Check other requirements before starting work
Planning permission and building regulations approval answer different questions. Depending on the project, other consents, agreements or private rights may also need attention. Ask your professional team to identify the requirements that apply rather than assuming the planning decision covers everything needed to start or complete the work.
Keep those requirements in a separate project checklist with owners and evidence. This prevents the same word “approved” being used ambiguously in meetings. When someone says a task is finished, ask which document or decision confirms it. That is an organisational habit, not a demand to create unnecessary paperwork.
For a small project, one person may coordinate several tasks. For a larger one, responsibilities may be spread across designers, consultants, contractors and the applicant. Either way, confirm who is checking the overall sequence. Gaps often arise when each participant assumes another person is handling the requirement between their own pieces of work.
If the project is being bought or sold with permission, explain which stage the paperwork has reached. A permission, an outstanding condition submission and an issued approval of details are different assets in the file. Give advisers complete documents so they can explain their relevance to the transaction rather than relying on a sales description.
Worked example: organising an approved extension
Imagine a fictional extension with a decision notice naming three approved drawings and a condition requiring specified details before a particular stage. The first task is to assemble those documents, identify the exact timing requirement and agree who prepares the details. Do not replace the condition’s wording with a general assumption that it can wait until the builder arrives.
Next, compare the approved design with the contractor’s pricing set. Suppose the contractor has priced an earlier window arrangement. Record the discrepancy and ask the designer to issue coordinated information. This is easier to fix before ordering than after several people have acted on different drawings.
Now put the required submission and other project tasks into the programme. Mark uncertain dates as assumptions and identify what evidence will allow the next step. If a detail is still awaiting approval, the programme should show that explicitly rather than presenting the project as fully ready because the main permission has been granted.
Finally, agree how changes and decisions will be recorded during the build. A short shared register of current drawings, condition approvals and outstanding questions can be enough. The purpose is to make sure the actual construction team can find and follow the documents that describe the project, without relying on the applicant’s memory of earlier conversations.
Keep records through completion and future ownership
Save decision notices, approved drawings and later approvals in a durable folder structure. Keep original filenames or identifiers alongside any simplified labels. If you change email accounts or move project information between services, make sure the final evidence does not remain scattered across inaccessible inboxes.
As work progresses, retain relevant professional records and correspondence through the appropriate project process. Do not assume photographs alone establish every aspect of compliance, but keep useful contextual information where your advisers recommend it. Label dates and subjects so the material can be understood later.
Before handing over or selling, prepare an index that explains the references and relationships between documents. A future reader should be able to distinguish the original permission, approved changes and evidence relating to conditions. Avoid presenting an unsorted archive as if its size demonstrates completeness.
If a later question arises, return to the specific documents rather than a remembered approval status. Good records do not guarantee there will be no questions, but they make those questions easier to investigate. They also help a future designer understand which scheme was approved and which later changes were formally considered.
- Keep the decision notice and identified approved plans together.
- Track condition wording, timing, responsibility, submissions and decisions separately.
- Review design changes before allowing working drawings or procurement to drift.
- Confirm other project requirements with the appropriate professionals.
- Retain an indexed record that another person can follow after the project ends.
How long does planning permission last?
Read the time-limit wording in the actual permission and obtain advice about what it means for your project. Do not use a generic number of years as a substitute for the notice, particularly where the application type or site history is unusual. Keep the relevant condition and decision date visible in the programme, and raise any uncertainty early enough for your adviser to consider the position.
If the question is whether an older permission has been implemented or remains capable of being used, that requires evidence and appropriate advice. A photograph of an unchanged site, an approval badge or a neighbour’s recollection may not settle it. Keep records of relevant decisions and professional advice together, and avoid assuming that any activity on site necessarily answers the legal question. For a purchase or a significant project commitment, give your adviser the complete notice and history rather than asking them to interpret an isolated status label.
Sources & scope
The procedural guidance in this article applies to England. Scotland, Wales and Northern Ireland have their own planning systems. For a decision about your own project, check the current official guidance and the council record.
