Finding Your Way Around an Idox Planning Portal: A Guide for Applicants and Advisers

If you've submitted a planning application anywhere in England, Scotland or Wales, there's a good chance the council's online register runs on software called Idox Public Access. It's used by a large proportion of local authorities, and once you've learned to navigate one council's version, you've largely learned them all — the same layout, the same document tables, and, unfortunately, the same idiosyncrasies. South Staffordshire Council's portal is a good example to learn from, because the quirks that catch people out there are the same ones you'll meet on almost any Idox-powered site. Here's what applicants and advisers should know before relying on it.

Documents aren't always filed where you'd expect

Every document uploaded to an application gets tagged with a "Document Type" — things like Application Form, Decision Notice, Officer Report, Approved Plan, Plans and Drawings, or simply "Documents". In theory this lets you filter quickly to the document you want. In practice, the tagging is only as good as whoever uploaded the file, and it's often not very good.

A Heritage Statement, a Design and Access Statement, or even a set of structural calculations will regularly turn up filed under "Approved Plan" rather than under a category that actually describes what the document is. A Decision Notice can occasionally sit under "Documents" instead of its own category. This isn't a rare glitch — it happens often enough that you should treat the "Document Type" filter as a rough sort rather than a reliable index.

The practical upshot: if you're looking for a specific document and it's not appearing where the category suggests it should be, don't assume it's missing. Switch the filter back to "Show All" and read through the descriptions in the list instead. The description text is usually more trustworthy than the category label sitting next to it.

Superseded and Amended versions can be confusing — and easy to act on by mistake

Applications that go through revisions during the process will often have several versions of the same drawing or statement sitting in the document list side by side: an original, a "Superseded" version, and an "Amended" or current version. Idox doesn't always make it obvious at a glance which one is the live, decision-relevant version and which ones are historic.

This matters enormously if you're an adviser checking what a client's approval actually covers, or an applicant trying to confirm exactly what was approved. It's entirely possible to open a superseded plan, read it, and unknowingly base a decision on drawings that were later replaced. Always check the "Date Published" column and cross-reference against the Officer Report or Decision Notice, which will usually list the specific drawing references that were actually approved. Don't take the top result in a list at face value.

Linked and related applications can share confusingly similar documents

Where an application has a related case attached to it — a condition-discharge submission tied to the main consent, for example, or a resubmission of a previously withdrawn application — you can end up with two documents in the same list that look identical at first glance. Two rows both titled "Decision Notice" is a common one: one belongs to the application you're looking at, the other belongs to the linked case. The only way to tell them apart is to read the full description text carefully, since the category label alone won't distinguish them.

If you're advising a client and citing a decision notice or condition discharge, double-check the description in full before you rely on it — a misattributed decision notice is an easy and consequential mistake to make.

Document links are not permanent — save what matters

It's tempting to email a client, colleague, or contractor a direct link to a document on the portal rather than the PDF itself. Don't. The "View" link for each document is tied to your current browsing session and will often stop working if it's revisited later, returning a "Document Unavailable" message instead of the file. If a document matters — an approved drawing, a decision notice, a condition — download it and keep your own copy rather than relying on a bookmarked or shared link to still work next month.

The portal itself isn't always reliable to click through

Beyond the labelling issues, the interface itself can behave unpredictably during ordinary use. Selecting several documents to download together as a batch is a useful feature, but on a slow connection or a busy day the site can silently fail to register a selection, drop a tick you thought you'd made, or time out mid-download without much of an error message. If you're pulling together a set of documents — for a file note, a due diligence pack, or a client update — it's worth double-checking what you've actually got against what you intended to select before you consider the job done. Don't assume a download completed correctly just because nothing appeared to go wrong.

There's also a practical limit on how many documents you can bundle into one download at a time (commonly 25), so larger applications with dozens of attachments will need more than one pass.

A few habits worth adopting

Taken together, these quirks point to a simple set of habits for anyone using these portals regularly:

Read document descriptions, not just their category labels, when you're trying to establish what a file actually is. Check publication dates and cross-reference against the Officer Report before treating any drawing or statement as the current, approved version. Read the full description on any document that seems to duplicate another, especially on applications with a related case. Download and keep your own copies of anything that matters, rather than relying on the portal's links to still work later. And when doing a batch download, verify what actually landed in the zip file rather than trusting the interface.

None of this is a knock on any individual council — it's simply how the underlying software behaves, and the same lessons apply almost everywhere you'll encounter it. Knowing the pattern in advance saves a good deal of frustration, and the occasional costly misunderstanding, further down the line.