Applied professional course
Site Inspection, Enforcement and Development-Control Records
Carry out a structured site inspection, record evidence properly and prepare a proportionate enforcement case record.
Written teaching content: available for review
Video lessons have not yet been recorded. Written teaching content may be available for review below.
Written teaching content only. This course is not yet available: it has not been professionally reviewed, no lesson is recorded, and enrolment, payment, certificates, downloads and protected access are all disabled.
Review Written Course ContentReading only. This is not enrolment, booking, purchase, account access, a download or protected learning access.
- Written content: Available for review
- Video lessons: Not recorded
- Professional review: Not yet completed
- Enrolment: Not available
- Payment: Disabled
- Certificates: Disabled
- Downloads: Disabled
- Protected access: Disabled
Written course content
Client-style brief
A planning authority has received four complaints in one month: an extension apparently built beyond its approved footprint, a field being used for vehicle storage, an unauthorised access formed onto a rural lane, and a shopfront altered in a conservation area. The team needs consistent inspection practice and records that would survive scrutiny in a formal process.
Professional scenario
Synthetic enforcement caseload of four alleged breaches with complaint text, approved drawings where they exist, and a described site visit for each.
Planning problem
Enforcement fails on record quality far more often than on judgement. The professional problem is to establish the facts on site, record them in a defensible form, determine whether a breach exists and whether action is expedient, and to write files that another officer or a decision-maker can rely on.
Learning objectives
- Plan and carry out a purposeful site inspection with a defined evidential aim.
- Record observation, measurement and photography to an evidential standard.
- Determine whether a breach of planning control has occurred.
- Apply an expediency test and choose a proportionate response.
- Maintain a development-control record that supports later formal action.
Modules and lessons
0 of 9 lessons open
Module 1
Module 1 — Investigation and site inspection
Turn a complaint into an evidenced factual position.
Assessing what is alleged, what would need to be true for a breach to exist, checking the planning history first, and deciding priority and timing before any visit takes place.
Practical exercise: Triage the four complaints, recording the alleged breach, the history checked and the evidential aim of a visit.
Checkpoint: Each case states what facts the visit must establish, not simply that a visit is needed.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Access and conduct, what may be observed and from where, safety, structured observation against the approved drawings, and behaviour that keeps the record credible.
Practical exercise: Write a pre-visit method note and a structured observation sheet for two of the cases.
Checkpoint: The observation sheet is organised by the facts to be established.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Taking dimensions that can be reproduced, referencing them to a datum, photograph numbering, direction and date recording, and avoiding images that cannot be located later.
Practical exercise: Record a measured comparison of the extension against its approved drawing with a described photograph schedule.
Checkpoint: Each measurement and photograph can be relocated by another officer.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Example data: Four synthetic complaints, approved drawings for two of them, and Ideeplan-owned inspection sheet templates.
Module output: Inspection plan and completed site inspection records.
Module 2
Module 2 — Determining breach and expediency
Decide, with reasons, whether a breach exists and whether action is warranted.
Applying the development test, considering whether the works or use fall within a permitted route, identifying material change of use, and recording which route was relied on.
Practical exercise: Determine the position for all four cases with a written reason for each.
Checkpoint: Each determination names the test applied and the facts relied on.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
How the passage of time affects enforceability, what evidence establishes continuous use, why immunity periods differ by jurisdiction, and how to record an evidential timeline.
Practical exercise: Build an evidential timeline for the vehicle-storage case and state what further evidence would settle it.
Checkpoint: The timeline separates established fact from assertion by any party.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Harm assessment, the range of responses from no action through negotiated remedy and retrospective application to formal notice, and documenting why the chosen response is proportionate.
Practical exercise: Write an expediency assessment and recommended response for each case.
Checkpoint: Each recommendation states the harm identified and why the response matches it.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Example data: Synthetic planning history, permitted-development style teaching scenarios and an immunity timeline exercise.
Module output: Breach determination and expediency assessment for each case.
Module 3
Module 3 — Records, correspondence and case closure
Produce records and correspondence that hold up under scrutiny.
File structure, contemporaneous notes, version control, handling of third-party information, confidentiality of complainant identity and what must be retained.
Practical exercise: Assemble one complete case file to the required structure and audit it for gaps.
Checkpoint: The file could be handed to a new officer with no verbal briefing.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Writing to an alleged breacher without prejudging, giving a clear remedy and timetable, managing complainant expectations, and avoiding statements that commit the authority prematurely.
Practical exercise: Draft one letter to a site owner and one complainant update for the same case.
Checkpoint: Neither letter asserts a conclusion the file does not yet support.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Closing a case on remedy, retaining evidence, setting a re-inspection where recurrence is likely, and coding outcomes so the service can see patterns.
Practical exercise: Close two cases with evidence and set out a re-inspection trigger for one of them.
Checkpoint: Every closure names the remedy achieved and the evidence for it.
Video lesson: Not recorded — written lesson above
Resource file not yet available. The written instructions on this page are complete and can be followed without any download.
Example data: Ideeplan-owned case file structure, correspondence templates and a synthetic complainant update.
Module output: Complete enforcement case files with correspondence and closure records.
Project brief
Four synthetic alleged breaches: an over-built extension, a field in vehicle storage use, an unauthorised rural access and an altered shopfront in a conservation area.
Your role: Enforcement officer investigating and recording alleged breaches of planning control.
Information available
- Complaint text for each case.
- Approved drawings for two cases and planning history for all four.
- Described site visit observations as teaching material.
- Ideeplan-owned inspection, file and correspondence templates.
Required analysis
- Triage and evidential aim per case.
- Measured comparison against approved drawings.
- Breach determination with reasons.
- Immunity and evidential timeline for the use case.
- Expediency and proportionate response.
Required outputs
- Inspection plan and observation sheets.
- Photograph and measurement schedules.
- Breach determinations.
- Expediency assessments and recommendations.
- Two letters and two case closures.
Presentation standard: Dated, contemporaneous records; observation separated from conclusion; every photograph numbered, located and dated; no complainant identity in site correspondence.
Marking criteria
- Evidential quality: Measurements and photographs can be reproduced by another officer.
- Reasoned determination: Each breach decision names the test applied and the facts relied on.
- Proportionality: The recommended response matches the harm identified.
- Correspondence discipline: Letters are clear, neutral and do not prejudge the outcome.
- File integrity: The case file is complete, ordered and handover-ready.
Quality-assurance checklist
- Every observation is dated and attributed.
- Conclusions never appear inside observation records.
- Complainant identity is protected throughout.
- Each recommendation records the harm and the proportionality reasoning.
- Local enforcement powers, immunity periods and notice procedures are confirmed with the authority.
Common mistakes and correction tasks
- Recording 'extension too big' with no measurement. Correction: Return to the approved drawing, record dimensioned differences and reference the datum used.
- Telling a complainant that action will be taken before the file supports it. Correction: Reissue a factual update stating the stage reached and the next step only.
- Photographs with no date, direction or location reference. Correction: Re-photograph with a numbered schedule recording date, direction and position.
- Treating every breach as warranting formal action. Correction: Apply the expediency test, record the harm and select the least intrusive effective response.
Enrolment status
Enrolment is not currently available. This course is still undergoing content, media and professional review.
Register Interest is an expression of interest only. It works without an account, creates no enrolment, no reserved place and no payment order.
Protected lessons, approved videos and approved resource files are not accessible. No protected file URL, signed link or download entitlement is created.
Payments are disabled. No price, checkout, payment provider, payment order or paid-course claim exists in the Academy.
Outstanding before enrolment could open
- Outstanding — Professional content review is complete
- Outstanding — Required videos recorded, reviewed and approved, or the course approved as written-only
- Outstanding — Required practical resources approved and available
- Outstanding — Learner terms approved
- Outstanding — Privacy and data-handling requirements approved
- Outstanding — Course availability explicitly enabled by an authorised administrator
- Outstanding — Payment and refund terms approved (paid courses)
- Outstanding — Payment provider configuration complete (where payment is required)
- Outstanding — Authentication email delivery configured and tested
- Outstanding — Protected content access tested
- Outstanding — Approved delivery and support process in place
Progress, assessment and certificates
Submission access is not currently available
Lesson and course progress tracking is not active. No progress record, completion percentage or completed lesson exists for any account, and no course can record progress until enrolment opens.
Practical assessments cannot be submitted. Submission access is not currently available: there is no active enrolment, no upload configuration and no authorised reviewer workflow in operation.
No assessment has been marked, reviewed, corrected or passed. Reviewer feedback, correction tasks and pass decisions are made by an authorised human reviewer and none exists.
No certificate is issued, approved or pending. A future Academy certificate would be a course-completion certificate only — not a professional licence, statutory qualification, accreditation or government-recognised award.
Certificate verification is disabled until a certificate is genuinely issued. No verification result is produced for any reference.
Assessment formats planned for the Academy
Written briefs, required deliverables and marking criteria are published inside the course content above for open review. None of them can be submitted or marked at present.
- Practical planning task
- GIS mapping exercise
- Site-appraisal task
- Feasibility assessment
- CAD or drawing task
- Revit coordination task
- Planning-report task
- Policy-assessment task
- Transport or access analysis
- Environmental or green-infrastructure exercise
- Final course project
Outstanding before completion or a certificate could exist
- Outstanding — Learner identity verified by an authorised member of staff
- Outstanding — Learner holds a valid active or completed enrolment
- Outstanding — All required lessons completed
- Outstanding — All required practical assessments passed
- Outstanding — A recorded assessment decision exists for every required task
- Outstanding — All requested corrections completed
- Outstanding — Course content professionally reviewed and signed off
- Outstanding — Authorised reviewer has approved completion
- Outstanding — Course certificate policy approved
- Outstanding — Certificate wording approved by Ideeplan Consult
- Outstanding — Course is officially available
- Outstanding — Unique certificate numbering and a secure verification route configured
Practical resources
Resources for this course
13 resource records · 13 with a written preview · 0 with a file under preparation · Download access not yet enabled.
All demonstration material is synthetic, publicly licensed or owned by Ideeplan Consult and is labelled as demonstration material. No confidential client file, personal information, private agency document or unreleased project drawing is used.
- Written preview available — downloadable file not yet available
Practical project brief
Sets the professional situation, the role the learner takes and what must be produced.
- Resource type
- Brief
- Format
- Written brief shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — One brief governs the whole course: every lesson exercise contributes to the same final deliverable.
- Access
- No account required — written preview is public
- Four synthetic alleged breaches: an over-built extension, a field in vehicle storage use, an unauthorised rural access and an altered shopfront in a conservation area.
- Your role: Enforcement officer investigating and recording alleged breaches of planning control.
- Available information: Complaint text for each case.
- Available information: Approved drawings for two cases and planning history for all four.
- Available information: Described site visit observations as teaching material.
- Available information: Ideeplan-owned inspection, file and correspondence templates.
- Required analysis: Triage and evidential aim per case.
- Required analysis: Measured comparison against approved drawings.
- Required analysis: Breach determination with reasons.
- Required analysis: Immunity and evidential timeline for the use case.
- Required analysis: Expediency and proportionate response.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Client-style instruction and problem statement
Gives the learner the instruction as a practitioner would receive it, and names the problem to be solved.
- Resource type
- Brief
- Format
- Written statement shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — Scenario framing applies to every lesson in the course.
- Access
- No account required — written preview is public
Synthetic enforcement caseload of four alleged breaches with complaint text, approved drawings where they exist, and a described site visit for each.
Enforcement fails on record quality far more often than on judgement. The professional problem is to establish the facts on site, record them in a defensible form, determine whether a breach exists and whether action is expedient, and to write files that another officer or a decision-maker can rely on.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Module 1 learner worksheet — Module 1 — Investigation and site inspection
Lists the practical steps the learner carries out in this module, in order.
- Resource type
- Worksheet
- Format
- Written worksheet shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Inspection plan and completed site inspection records.
- Lessons supported
- 3 — Supports the 3 lessons in module 1, which build one shared output.
- Access
- No account required — written preview is public
- Triage: complaint to investigation — Triage the four complaints, recording the alleged breach, the history checked and the evidential aim of a visit.
- Conducting the inspection — Write a pre-visit method note and a structured observation sheet for two of the cases.
- Measurement and photographic discipline — Record a measured comparison of the extension against its approved drawing with a described photograph schedule.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Module 2 learner worksheet — Module 2 — Determining breach and expediency
Lists the practical steps the learner carries out in this module, in order.
- Resource type
- Worksheet
- Format
- Written worksheet shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Breach determination and expediency assessment for each case.
- Lessons supported
- 3 — Supports the 3 lessons in module 2, which build one shared output.
- Access
- No account required — written preview is public
- Is it development, and is it permitted? — Determine the position for all four cases with a written reason for each.
- Time limits, immunity and lawful use — Build an evidential timeline for the vehicle-storage case and state what further evidence would settle it.
- Expediency and proportionate response — Write an expediency assessment and recommended response for each case.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Module 3 learner worksheet — Module 3 — Records, correspondence and case closure
Lists the practical steps the learner carries out in this module, in order.
- Resource type
- Worksheet
- Format
- Written worksheet shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Complete enforcement case files with correspondence and closure records.
- Lessons supported
- 3 — Supports the 3 lessons in module 3, which build one shared output.
- Access
- No account required — written preview is public
- Building a defensible case file — Assemble one complete case file to the required structure and audit it for gaps.
- Correspondence with owners, occupiers and complainants — Draft one letter to a site owner and one complainant update for the same case.
- Closure, monitoring and recurrence — Close two cases with evidence and set out a re-inspection trigger for one of them.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Task checklist
Confirms every required piece of work has been produced before submission.
- Resource type
- Checklist
- Format
- Written checklist shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — A single task checklist tracks progress across all modules.
- Access
- No account required — written preview is public
- Inspection plan and observation sheets.
- Photograph and measurement schedules.
- Breach determinations.
- Expediency assessments and recommendations.
- Two letters and two case closures.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Example data and drawing base
Four synthetic complaints, approved drawings for two of them, and Ideeplan-owned inspection sheet templates. GIS exercises are planned around plain, checkable formats: CSV and clearly labelled local-grid JSON on the named grid IDP-LOCAL-GRID. GeoJSON is not used for local-grid training data because the format asserts WGS 84 degrees. No QGIS project file, GeoPackage or raster file is claimed.
- Resource type
- GIS exercise pack
- Format
- CSV and local-grid JSON (planned) — no GeoJSON, QGIS project, GeoPackage or raster file is claimed
- Status
- Planned
- Data classification
- Synthetic demonstration data
- Licence or ownership
- Synthetic demonstration material prepared by Ideeplan Consult. No client file, personal information, private agency document or unreleased project drawing is used.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — One demonstration data base is used by every lesson so results stay comparable.
- Access
- No account required — written preview is public
Demonstration data item What it contains and how it is used Data ownership and licence Synthetic training data prepared and owned by Ideeplan Consult. It is fictional: it is not a real client project, a real site or a real location, and it must not be presented as one. Free to study on this page; redistribution is not permitted. Module 1 input — Module 1 — Investigation and site inspection Four synthetic complaints, approved drawings for two of them, and Ideeplan-owned inspection sheet templates. Module 2 input — Module 2 — Determining breach and expediency Synthetic planning history, permitted-development style teaching scenarios and an immunity timeline exercise. Module 3 input — Module 3 — Records, correspondence and case closure Ideeplan-owned case file structure, correspondence templates and a synthetic complainant update. Lawful sourcing where real data is substituted Where a learner substitutes real data, use only openly licensed or lawfully obtained sources, record the publisher, dataset title, version and access date, and cite them in the final deliverable. Do not use restricted, confidential or personal data. Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Analysis and calculation template
Structures the analysis so assumptions are visible and checkable. Any figures used in a template are teaching assumptions, not market evidence. Local costs, policies, standards and valuation assumptions must be independently confirmed before any of this is applied to a real project.
- Resource type
- Suitability matrix
- Format
- CSV matrix (planned)
- Status
- Planned
- Data classification
- Synthetic demonstration data
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — The same analysis structure is completed progressively through the course.
- Access
- No account required — written preview is public
- Record every assumption on its own labelled row, with the source or reason beside it.
- Module 1 working section — Inspection plan and completed site inspection records.
- Module 2 working section — Breach determination and expediency assessment for each case.
- Module 3 working section — Complete enforcement case files with correspondence and closure records.
- Required output carried into the analysis — Inspection plan and observation sheets.
- Required output carried into the analysis — Photograph and measurement schedules.
- Required output carried into the analysis — Breach determinations.
- Required output carried into the analysis — Expediency assessments and recommendations.
- Required output carried into the analysis — Two letters and two case closures.
- Check row: totals, units and areas reconcile before the result is carried into the deliverable.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Final deliverable template
Sets the expected structure and presentation standard for Enforcement case file set with inspection records, determinations and correspondence.
- Resource type
- Planning-report template
- Format
- Structured document outline (planned)
- Status
- Planned
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — The final deliverable draws on every module output.
- Access
- No account required — written preview is public
- Final named deliverable — Enforcement case file set with inspection records, determinations and correspondence
- Section 1 — Inspection plan and completed site inspection records.
- Section 2 — Breach determination and expediency assessment for each case.
- Section 3 — Complete enforcement case files with correspondence and closure records.
- Must be present — Inspection plan and observation sheets.
- Must be present — Photograph and measurement schedules.
- Must be present — Breach determinations.
- Must be present — Expediency assessments and recommendations.
- Must be present — Two letters and two case closures.
- Presentation and submission standard — Dated, contemporaneous records; observation separated from conclusion; every photograph numbered, located and dated; no complainant identity in site correspondence.
- Sources and citations: list every dataset, publisher, version and access date used, and state clearly where synthetic Ideeplan training data was used.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Quality-control checklist
Professional checks to run before the work is treated as finished.
- Resource type
- Checklist
- Format
- Written checklist shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — Quality control is applied to the whole submission, not to a single lesson.
- Access
- No account required — written preview is public
- Every observation is dated and attributed.
- Conclusions never appear inside observation records.
- Complainant identity is protected throughout.
- Each recommendation records the harm and the proportionality reasoning.
- Local enforcement powers, immunity periods and notice procedures are confirmed with the authority.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Marking and review rubric
States what a satisfactory professional standard looks like for each criterion.
- Resource type
- Marking rubric
- Format
- Written rubric shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — One rubric reviews the final deliverable produced across all modules.
- Access
- No account required — written preview is public
Criterion Satisfactory standard Evidential quality Measurements and photographs can be reproduced by another officer. Reasoned determination Each breach decision names the test applied and the facts relied on. Proportionality The recommended response matches the harm identified. Correspondence discipline Letters are clear, neutral and do not prejudge the outcome. File integrity The case file is complete, ordered and handover-ready. Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Correction-task sheet
Common professional mistakes and the correction the learner practises.
- Resource type
- Correction-task sheet
- Format
- Written task sheet shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — Correction tasks address mistakes that can appear anywhere in the course.
- Access
- No account required — written preview is public
- Recording 'extension too big' with no measurement. — Return to the approved drawing, record dimensioned differences and reference the datum used.
- Telling a complainant that action will be taken before the file supports it. — Reissue a factual update stating the stage reached and the next step only.
- Photographs with no date, direction or location reference. — Re-photograph with a numbered schedule recording date, direction and position.
- Treating every breach as warranting formal action. — Apply the expediency test, record the harm and select the least intrusive effective response.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
- Written preview available — downloadable file not yet available
Submission guidance
How the finished work should be assembled and presented for professional review.
- Resource type
- Checklist
- Format
- Written guidance shown on this page
- Status
- Draft
- Data classification
- Ideeplan-owned demonstration material
- Licence or ownership
- Ideeplan Consult-owned teaching material. Free to read on this page; redistribution is not permitted.
- Related deliverable
- Enforcement case file set with inspection records, determinations and correspondence
- Lessons supported
- 9 — Submission guidance covers the single final deliverable.
- Access
- No account required — written preview is public
Dated, contemporaneous records; observation separated from conclusion; every photograph numbered, located and dated; no complainant identity in site correspondence.
Resource file not yet available. The written instructions on this page are complete and can be followed without any download, account, enrolment or payment.
Media status
Video lessons for this course
- Video lessons
- Video lesson: Not recorded — authentic professional recording required.
- Narration
- Professional narration — planned, not produced
- Captions
- Not yet produced
- Transcript
- Not yet produced
- Software demonstration
- Genuine screen capture from the real application only — no mockup, simulated interface or AI-generated screen.
- Software version and operating system
- No software version is published until it has been read from the actual recorded session. Until then the version reads “To be stated from the recorded session”.
- Production plan
- Prepared for professional review
- Enrolment, payment and downloads
- Disabled
Video lesson: Not recorded — authentic professional recording required. The written lesson on this page is complete and can be read in full without a video, an account, enrolment or payment.
Authentic software screen capture only — non-negotiable standard
Applies to every software demonstrated in the Academy, including AutoCAD, QGIS, Revit, ArcGIS, SketchUp, Lumion, Civil 3D, Rhino and any other software used. The final video must accurately represent what a learner sees when using the stated software version.
- Every demonstration is a genuine screen recording or screenshot captured from the actual installed software being taught.
- The exact software name, version, operating system and relevant workspace are stated on screen and in the lesson notes, as read from the recorded session.
- The real interface is shown: menus, panels, toolbars, properties, layer controls, settings and the command line or log.
- The real cursor, tool selection, commands, settings and the resulting output are visible.
- Capture is 16:9 and readable at 720p, with clear, unhurried cursor movement; the screen stays clear enough for learners to follow.
- The view zooms in whenever text, settings, coordinates or field values would otherwise be hard to read.
- The exact command, menu path or tool name is shown as it appears in the software.
- Useful keyboard shortcuts are shown alongside the menu path, never instead of it.
- Differences between software versions or operating systems are stated wherever the interface may display differently.
- Steps are numbered on screen, with callouts pointing at the actual control being used.
- Any annotation is added only after recording and must never alter or misrepresent the software interface.
- Captions and a complete transcript are produced before professional review.
- Any presenter window stays small, is positioned clear of technical content, and is hidden on mobile widths and on dense technical screens.
Interface visibility on every recording
- The full application interface is shown at the beginning of every demonstration, with the application identity and exact version clearly visible.
- The relevant menu bar, ribbon, toolbar or toolbox stays visible while each step is explained; the interface context is never cropped away.
- Layers, properties, project browser or data panels are shown wherever applicable.
- The command line, status bar or coordinate/CRS information is shown wherever relevant.
- Real cursor movement and visible clicks are captured, with visible cursor highlighting or click indicators.
- The selected tool and its effect are visible, and complete dialog boxes and settings are shown whenever one is opened.
- The resulting drawing, map, model or output is shown in the recording.
- Zoom is used only when necessary for small text or settings, always retaining enough context to identify the application and tool in use.
- The standard applies to every software course and is verified before any video is marked recorded or approved; if the required authentic interface is not visible, the lesson remains “Video lesson: Not recorded — authentic professional recording required.”
Never used
- Generic website mockups standing in for a software workspace.
- Simulated, redrawn, reconstructed or redesigned replica interfaces for any software.
- AI-generated software screens, panels, dialogs or map canvases.
- Generic illustrations replacing the real interface.
- Unverified screenshots taken from any source other than the recorded session.
- Fake video players, placeholder thumbnails or invented durations.
- Invented menus, tool names, command names, dialog options or keyboard shortcuts.
- Hiding important controls or covering them with a presenter window.
- Annotations that alter or misrepresent the recorded software interface.
- Claiming or implying that a simulated screen is an authentic software demonstration.
QGIS — what the recording must show
Exact QGIS version to be stated from the recorded session. Operating system to be stated from the recorded session; menu positions and file dialogs differ between systems.
- 1.Project CRS: Project Properties, the CRS tab and the selected coordinate reference system.
- 2.Layer loading: the Data Source Manager or Browser panel and the layer added to the canvas.
- 3.Layer properties: the Layer Properties dialog and each tab used in the lesson.
- 4.Symbology: the Symbology tab with the real renderer, classes and colour settings.
- 5.Attribute tables: the attribute table, field values, selection and expression use.
- 6.Processing tools: the Processing Toolbox with the tool searched and opened by its real name.
- 7.Analysis settings: every parameter in the tool dialog, including output location.
- 8.Map layout: the Print Layout window, page setup and map item.
- 9.Legend, scale and north arrow: each item added from the real layout toolbar.
- 10.Export and quality checks: the export dialog settings and a check of the exported file.
No authentic software recording or screenshot exists yet. Every software lesson remains “Video lesson: Not recorded — authentic professional recording required.”
Real professional classroom experience — every lesson
Applies to every future Academy lesson, software-based or not. The finished lesson presents as authentic professional training, professionally narrated and screen-led: video + written guide + supporting data + practical task + quality checklist + final named deliverable.
Lesson structure
- 1.Professional introduction.
- 2.Realistic project situation.
- 3.Learner role within that situation.
- 4.Problem statement.
- 5.Learning objectives.
- 6.Required software and data.
- 7.Step-by-step demonstration.
- 8.Explanation of the professional reasoning behind each action.
- 9.Practical learner task.
- 10.Checkpoint or pause activity.
- 11.Common mistake and its correction.
- 12.Quality-control review.
- 13.Final recap.
- 14.Named learner deliverable.
Video requirements
- Professional narration that is clear, natural and paced for instruction, synchronised with the screen action.
- Authentic screen recording from the actual software, with visible menus, tools, panels, commands, settings and outputs.
- Natural cursor movement and deliberate pacing, with a clear explanation of why each action is taken.
- Realistic corrections and troubleshooting shown, not edited away.
- Clear 16:9 screen capture.
- Captions and a complete transcript.
- Chapter titles and lesson sections.
- A small presenter window only where useful; it never covers technical content and is hidden on mobile or dense technical screens.
Never produced as a lesson
- Automated slideshows.
- Generic screen tours.
- Silent software demonstrations.
- Marketing videos presented as lessons.
- AI-avatar presentations.
- Simulated software tutorials.
- Fast montages without explanation.
- An invented tutor, instructor identity, voice, recording, thumbnail or completion status.
Lessons use only synthetic, publicly licensed or Ideeplan-owned examples. No confidential client information is used.
No genuine professional recording exists yet. Until one does, every lesson remains “Video lesson: Not recorded — authentic professional recording required.” Enrolment, payments, certificates and protected learner access stay disabled during this production stage.
Professional narration and screen-first production
- Every Academy lesson is planned as a professionally narrated, screen-led practical lesson with captions and a complete transcript.
- No AI avatar, virtual presenter or artificial talking head is used, and no named person is imitated. No lesson is described as human-narrated, instructor-led by a named person or personally presented unless that is factually true.
- No instructor identity is published until a real, named professional has recorded and approved the lesson.
- Recordings are screen-first: the GIS view, planning drawing, AutoCAD or Revit workspace or document remains the main subject of the frame.
- Any presenter picture-in-picture normally occupies about 8–10% of the frame, never covers technical content, and is reduced or hidden on small screens.
- The Principal Consultant portrait is reserved for approved introductions and conclusions. It is never used as a repeated course thumbnail, and the Academy remains company-first.
No lesson has been recorded and no narration has been produced. Scripts exist as production plans only, and every lesson video status remains “Not recorded”.
Demonstration material is synthetic, publicly licensed or owned by Ideeplan Consult. No confidential client file, unauthorised agency dataset or private project information is used.
Methods are jurisdiction-neutral. Learners must confirm local laws, policies and technical standards before applying them to a real project.
A production plan describes how a lesson would be recorded. It is not a recording, and it does not create an enrolment, account, payment or reserved place.
9 lesson production plans · suggested recording time about 90 minutes in total (a planning estimate, not a recorded duration) · every lesson video status: Not recorded.
Lesson 1 · Video lesson: Not recorded — authentic professional recording required.
Triage: complaint to investigation
- Learning objective
- Assessing what is alleged, what would need to be true for a breach to exist, checking the planning history first, and deciding priority and timing before any visit takes place.
- Narration focus
- Turn a complaint into an evidenced factual position.
- Screen action
- Triage the four complaints, recording the alleged breach, the history checked and the evidential aim of a visit.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Four synthetic complaints, approved drawings for two of them, and Ideeplan-owned inspection sheet templates.
- Expected learner output
- Each case states what facts the visit must establish, not simply that a visit is needed.
- Suggested length
- About 8 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Assessing what is alleged, what would need to be true for a breach to exist, checking the planning history first, and deciding priority and timing before any visit takes place.
- 2.Triage the four complaints, recording the alleged breach, the history checked and the evidential aim of a visit.
- 3.Each case states what facts the visit must establish, not simply that a visit is needed.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 2 · Video lesson: Not recorded — authentic professional recording required.
Conducting the inspection
- Learning objective
- Access and conduct, what may be observed and from where, safety, structured observation against the approved drawings, and behaviour that keeps the record credible.
- Narration focus
- Turn a complaint into an evidenced factual position.
- Screen action
- Write a pre-visit method note and a structured observation sheet for two of the cases.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Four synthetic complaints, approved drawings for two of them, and Ideeplan-owned inspection sheet templates.
- Expected learner output
- The observation sheet is organised by the facts to be established.
- Suggested length
- About 10 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Access and conduct, what may be observed and from where, safety, structured observation against the approved drawings, and behaviour that keeps the record credible.
- 2.Write a pre-visit method note and a structured observation sheet for two of the cases.
- 3.The observation sheet is organised by the facts to be established.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 3 · Video lesson: Not recorded — authentic professional recording required.
Measurement and photographic discipline
- Learning objective
- Taking dimensions that can be reproduced, referencing them to a datum, photograph numbering, direction and date recording, and avoiding images that cannot be located later.
- Narration focus
- Turn a complaint into an evidenced factual position.
- Screen action
- Record a measured comparison of the extension against its approved drawing with a described photograph schedule.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Four synthetic complaints, approved drawings for two of them, and Ideeplan-owned inspection sheet templates.
- Expected learner output
- Each measurement and photograph can be relocated by another officer.
- Suggested length
- About 12 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Taking dimensions that can be reproduced, referencing them to a datum, photograph numbering, direction and date recording, and avoiding images that cannot be located later.
- 2.Record a measured comparison of the extension against its approved drawing with a described photograph schedule.
- 3.Each measurement and photograph can be relocated by another officer.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 4 · Video lesson: Not recorded — authentic professional recording required.
Is it development, and is it permitted?
- Learning objective
- Applying the development test, considering whether the works or use fall within a permitted route, identifying material change of use, and recording which route was relied on.
- Narration focus
- Decide, with reasons, whether a breach exists and whether action is warranted.
- Screen action
- Determine the position for all four cases with a written reason for each.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Synthetic planning history, permitted-development style teaching scenarios and an immunity timeline exercise.
- Expected learner output
- Each determination names the test applied and the facts relied on.
- Suggested length
- About 8 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Applying the development test, considering whether the works or use fall within a permitted route, identifying material change of use, and recording which route was relied on.
- 2.Determine the position for all four cases with a written reason for each.
- 3.Each determination names the test applied and the facts relied on.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 5 · Video lesson: Not recorded — authentic professional recording required.
Time limits, immunity and lawful use
- Learning objective
- How the passage of time affects enforceability, what evidence establishes continuous use, why immunity periods differ by jurisdiction, and how to record an evidential timeline.
- Narration focus
- Decide, with reasons, whether a breach exists and whether action is warranted.
- Screen action
- Build an evidential timeline for the vehicle-storage case and state what further evidence would settle it.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Synthetic planning history, permitted-development style teaching scenarios and an immunity timeline exercise.
- Expected learner output
- The timeline separates established fact from assertion by any party.
- Suggested length
- About 10 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.How the passage of time affects enforceability, what evidence establishes continuous use, why immunity periods differ by jurisdiction, and how to record an evidential timeline.
- 2.Build an evidential timeline for the vehicle-storage case and state what further evidence would settle it.
- 3.The timeline separates established fact from assertion by any party.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 6 · Video lesson: Not recorded — authentic professional recording required.
Expediency and proportionate response
- Learning objective
- Harm assessment, the range of responses from no action through negotiated remedy and retrospective application to formal notice, and documenting why the chosen response is proportionate.
- Narration focus
- Decide, with reasons, whether a breach exists and whether action is warranted.
- Screen action
- Write an expediency assessment and recommended response for each case.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Synthetic planning history, permitted-development style teaching scenarios and an immunity timeline exercise.
- Expected learner output
- Each recommendation states the harm identified and why the response matches it.
- Suggested length
- About 12 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Harm assessment, the range of responses from no action through negotiated remedy and retrospective application to formal notice, and documenting why the chosen response is proportionate.
- 2.Write an expediency assessment and recommended response for each case.
- 3.Each recommendation states the harm identified and why the response matches it.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 7 · Video lesson: Not recorded — authentic professional recording required.
Building a defensible case file
- Learning objective
- File structure, contemporaneous notes, version control, handling of third-party information, confidentiality of complainant identity and what must be retained.
- Narration focus
- Produce records and correspondence that hold up under scrutiny.
- Screen action
- Assemble one complete case file to the required structure and audit it for gaps.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Ideeplan-owned case file structure, correspondence templates and a synthetic complainant update.
- Expected learner output
- The file could be handed to a new officer with no verbal briefing.
- Suggested length
- About 8 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.File structure, contemporaneous notes, version control, handling of third-party information, confidentiality of complainant identity and what must be retained.
- 2.Assemble one complete case file to the required structure and audit it for gaps.
- 3.The file could be handed to a new officer with no verbal briefing.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 8 · Video lesson: Not recorded — authentic professional recording required.
Correspondence with owners, occupiers and complainants
- Learning objective
- Writing to an alleged breacher without prejudging, giving a clear remedy and timetable, managing complainant expectations, and avoiding statements that commit the authority prematurely.
- Narration focus
- Produce records and correspondence that hold up under scrutiny.
- Screen action
- Draft one letter to a site owner and one complainant update for the same case.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Ideeplan-owned case file structure, correspondence templates and a synthetic complainant update.
- Expected learner output
- Neither letter asserts a conclusion the file does not yet support.
- Suggested length
- About 10 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Writing to an alleged breacher without prejudging, giving a clear remedy and timetable, managing complainant expectations, and avoiding statements that commit the authority prematurely.
- 2.Draft one letter to a site owner and one complainant update for the same case.
- 3.Neither letter asserts a conclusion the file does not yet support.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Lesson 9 · Video lesson: Not recorded — authentic professional recording required.
Closure, monitoring and recurrence
- Learning objective
- Closing a case on remedy, retaining evidence, setting a re-inspection where recurrence is likely, and coding outcomes so the service can see patterns.
- Narration focus
- Produce records and correspondence that hold up under scrutiny.
- Screen action
- Close two cases with evidence and set out a re-inspection trigger for one of them.
- Required software
- Spreadsheet software, Word processor, PDF reader, QGIS
- Example data
- Ideeplan-owned case file structure, correspondence templates and a synthetic complainant update.
- Expected learner output
- Every closure names the remedy achieved and the evidence for it.
- Suggested length
- About 12 minutes (planning estimate)
- Captions and transcript
- Required before professional review
- Narration
- Professional narration — not yet produced
Demonstration sequence
- 1.Closing a case on remedy, retaining evidence, setting a re-inspection where recurrence is likely, and coding outcomes so the service can see patterns.
- 2.Close two cases with evidence and set out a re-inspection trigger for one of them.
- 3.Every closure names the remedy achieved and the evidence for it.
Quality review checklist
- Technical content (map, drawing, model or document) fills the majority of the frame and stays legible at 720p.
- Presenter picture-in-picture, if used, stays at roughly 8–10% of the frame, never covers legends, dimensions, labels or annotations, and is hidden on mobile widths and dense technical screens.
- Software shown is limited to Spreadsheet software, Word processor, PDF reader, QGIS, with no suggestion of provider endorsement.
- Capture is a genuine screen recording from the real application — no mockup, simulated interface, AI-generated screen or unverified screenshot.
- The exact software name, version and, where relevant, operating system are read from the recorded session and stated on screen.
- Menus, panels, toolbars, layer controls and the command line or log are visible and legible; the view zooms in wherever text, settings or coordinates would be hard to read.
- The full application interface is shown at the beginning; menus, tools and panels stay visible throughout and the interface context is never cropped away, with zoom retaining enough context to identify the application and tool.
- Real cursor movement with visible highlighting or click indicators is captured; the selected tool, its effect, complete dialogs and the resulting output are all shown.
- The exact command, menu path or tool name is shown as it appears in the software, with useful keyboard shortcuts alongside it and alternative locations explained for other versions.
- Numbered on-screen steps and callouts point at the real controls being used; no menu, tool or command is invented.
- Until an authentic recording exists the lesson reads: “Video lesson: Not recorded — authentic professional recording required.”
- All data on screen is synthetic, publicly licensed or Ideeplan-owned, and is labelled as demonstration data.
- Narration states that methods are jurisdiction-neutral and that local laws, policies and standards must be confirmed.
- Captions and a transcript are produced before the recording can move to professional review.
- No client name, confidential file or private project information appears on screen at any point.
Course production standard
- Recordings are screen-first: the planning drawing, GIS view, AutoCAD or Revit workspace stays the main subject of the frame.
- Any presenter picture-in-picture normally occupies no more than about 8–10% of the frame and never covers maps, legends, drawings, dimensions or annotations.
- On mobile and on dense technical screens the presenter window is reduced further or hidden entirely.
- The Principal Consultant portrait is reserved for approved introductions, explanations and conclusions. It is not used as a generic thumbnail for every course.
- Narration is planned for professional human delivery. No AI narration, AI presenter or recorded lesson exists today.
No lesson has been recorded. Every lesson media status is “Not recorded”.
Any example data used in teaching is synthetic, publicly licensed or owned by Ideeplan Consult, and is clearly labelled as demonstration data. No client file, confidential document or unauthorised project material is used.
Want this course finished first?
Registering interest is not an enrolment. It tells Ideeplan Consult which subjects to complete and review first.