How to Read and Learn from IPSO Rulings

1. What IPSO is and what it regulates

The Independent Press Standards Organisation (IPSO) is the largest press regulator in the UK. It regulates most national newspapers and magazines and many regional and local titles, holding them to the Editors' Code of Practice — the industry code that sets the standards on accuracy, privacy and conduct. IPSO handles complaints from the public, can require the publication of corrections and adjudications, and runs a standards and monitoring function alongside its complaints work.

It is important to be precise about scope. IPSO is not a state regulator and it does not cover broadcasting, which is regulated by Ofcom, nor does it cover the smaller group of publishers signed up to IMPRESS. Some publishers belong to no regulator at all. So the first question when assessing any press-standards story is which regime applies. For the boundary between the two press regulators, see our guide on IPSO vs IMPRESS. This article focuses on how to understand IPSO's own decisions.

2. How the complaints process works

Understanding a ruling starts with understanding how a complaint reaches one. The process runs through recognisable stages. First, a complaint is made — usually the complainant is expected to raise it with the publication first, giving the title a chance to resolve it, though complaints can also come directly to IPSO. Second, IPSO carries out an assessment and investigation: it checks whether the complainant has standing, whether the complaint is within its remit, and whether it raises a possible breach of a specific clause of the Code.

Third comes resolution or ruling. Many complaints are settled between the parties — for example by a correction, a clarification, a private letter, or the amendment of an online article — and IPSO records the outcome in a resolution statement. Where the parties cannot agree, the matter goes to IPSO's Complaints Committee, which issues a formal ruling on whether the Code was breached. Fourth, if a breach is found, IPSO can require a remedy, such as the publication of a correction or a critical adjudication. Every published decision, whether a ruling or a resolution statement, is added to the online database.

3. Where to find rulings: the database

All of IPSO's published decisions live in the rulings and resolution statements database on its website, ipso.co.uk. This is the authoritative source, and it should always be your reference when you want to cite or understand a decision. The database is searchable and filterable — typically by publication, by Editors' Code clause, and by outcome — which lets you move quickly from a general interest to the specific decisions that bear on it.

Use the filters deliberately. If you are worried about an accuracy issue in your own work, filter for the accuracy clause and read a run of recent decisions to see how the Committee has approached similar situations. If you are researching how a particular title has fared, filter by publication. Reading a range of decisions is far more instructive than fixating on one headline case, because the value is in the pattern of reasoning across many rulings, not in any single result. Because decisions are added continually, treat the live database as the current record rather than trusting a static list published elsewhere.

4. Anatomy of a ruling: how to read one

A published IPSO decision follows a consistent structure, and knowing the parts lets you read one quickly and accurately. It sets out the complaint — who complained and what they said was wrong; the clause or clauses of the Editors' Code engaged; a summary of the correspondence and the positions of both the complainant and the publication; the Committee's findings and reasoning; and the outcome, including any remedy required.

When you read a decision, focus on a few things in order. Identify which clause was in play, because the whole analysis turns on the specific standard that clause sets. Read the reasoning, not just the outcome, because that is where the principle lives — the Committee explains why a particular claim was or was not a breach, and that explanation is the transferable lesson. Then note the outcome and remedy precisely. If you are going to describe the decision to anyone else, the reasoning and the exact outcome are what you must get right, and paraphrasing loosely is how misreporting of rulings begins.

5. Upheld, not upheld, partly upheld and resolved

The outcome labels carry precise meanings, and using them loosely is a common error. A complaint is upheld when the Committee finds the publication breached the relevant clause. It is not upheld when the Committee concludes there was no breach, regardless of how strongly the complainant felt. A complaint may be partly upheld, where some points are made out and others are not, which is why it matters to say which element succeeded rather than describing the whole thing as upheld.

Separately, many matters are resolved without a formal adjudication, where the publication and complainant agree an outcome — a correction, a clarification, an amendment — that IPSO records in a resolution statement. A resolution is not the same as an upheld breach: it reflects an agreed remedy rather than a finding of fault by the Committee. When reporting on a decision, distinguish carefully between a ruling that a clause was breached and a matter that was resolved by agreement, because conflating the two misstates what actually happened.

6. The Editors' Code clauses complaints arise under

The Editors' Code is organised into numbered clauses, and complaints are always assessed against one or more of them. It is worth knowing the shape of the Code so you can see which standard a decision applies. Clause 1 (Accuracy) is the most frequently engaged: it requires care not to publish inaccurate, misleading or distorted information, distinguishes fact from comment, and requires significant errors to be corrected promptly and with due prominence. Clause 2 (Privacy) protects private and family life, and is often weighed against the public interest.

Other clauses address specific situations: harassment; intrusion into grief or shock; reporting of suicide; children, including children in sex cases; hospitals; the reporting of crime; the use of clandestine devices and subterfuge; victims of sexual assault; discrimination; financial journalism; confidential sources; witnesses in criminal trials; and payments in connection with crime. The Code runs to sixteen clauses in total, and several of them can be outweighed by a genuine and demonstrable public interest. The precise wording changes from time to time, so read the current Code on ipso.co.uk alongside any ruling, and see our dedicated guide to the IPSO Editors' Code.

7. Remedies: corrections and adjudications

Where a breach is established or a matter is resolved, the point is to put things right, and IPSO can require specific remedies. The most common is a correction or clarification, published with due prominence — a concept that matters, because a correction buried where few will see it does not properly remedy a prominent error. In more serious cases the Committee can require the publication of a critical adjudication: IPSO's own findings, which the title must publish, and whose wording and placement IPSO can specify.

Understanding remedies helps you read a decision's real-world effect. An upheld accuracy complaint that leads to a prominent correction has a different weight from one resolved quietly by amending an online article. For journalists, the remedy is also the most practical lesson: it shows what the regulator expects when something goes wrong, and it underlines why getting corrections right in the first place matters. Our guides on corrections and clarifications and building a corrections policy go into the mechanics.

8. Resolution statements vs rulings

The database contains two kinds of document, and telling them apart is essential to reading it accurately. A ruling is a decision of the Complaints Committee that adjudicates whether the Code was breached; it contains reasoning and a finding. A resolution statement records that a complaint was settled between the parties without a Committee adjudication, usually because the publication offered a remedy the complainant accepted.

The difference matters for interpretation and for reporting. A resolution statement is not a finding that a clause was breached; it is a record of an agreed outcome. Describing a resolved complaint as one that IPSO “upheld” would be wrong. When you search the database, read the label on each entry and quote it faithfully. If you are writing about a decision, say whether it was a ruling with a finding or a resolution reached by agreement, because that distinction changes what the decision actually tells the reader.

9. Learning from patterns in rulings

The single most valuable use of the database is not to look up one dramatic case but to read across many decisions and spot the patterns. Certain issues recur again and again: claims presented as established fact when they were contested; headlines or standfirsts that go further than the article can support; a failure to distinguish comment from fact; private information published without a sufficient public-interest justification; and errors that were not corrected promptly or prominently enough once flagged.

These patterns are the real curriculum. They show, in concrete terms, where careful journalism most often slips, and they are far more useful than memorising the outcome of any individual complaint. Reading a run of accuracy decisions, for instance, teaches you how the Committee thinks about the line between a robust interpretation and a distortion, or about when a correction does enough to remedy a breach. Approached this way, the rulings database becomes a continually updated case-study library for raising standards, which is exactly what a regulator's published decisions are best used for.

10. A hypothetical worked example

To show how to read a decision, here is a purely hypothetical, illustrative scenario — it is not a real ruling and does not describe any actual complaint, complainant, publication, date or outcome. For example, a complaint might allege that a news article stated as settled fact something that was in truth disputed, and that the headline went further than the body of the piece could support. The complainant might say this engaged the accuracy clause; the publication might respond that the statement was a fair characterisation of the available evidence and that any error was minor.

Reading such a decision, you would work through it in order: identify the clause (accuracy), follow the Committee's reasoning on whether the disputed statement was presented as fact and whether the headline was supported by the text, then note the outcome and any remedy, such as a correction with due prominence. The lesson you would carry away is transferable and general — be careful to attribute contested claims and to ensure headlines are supported by the article — without needing to attach it to any named case. This is how to learn from rulings responsibly: extract the principle, and go to the real database for the genuine decisions.

11. Using rulings to improve your own practice

Rulings are most powerful when you treat them as a routine part of professional development rather than something you consult only after a complaint lands. Building a habit of reading new decisions — and discussing them in the newsroom — is one of the cheapest and most effective ways to raise standards. It turns other people's mistakes into your team's checklist, and it keeps the Code's standards live in daily editing rather than abstract.

In practice, that means a few simple disciplines: skim the recent rulings periodically for anything relevant to your beat; when a decision touches a situation you regularly face, extract the principle and add it to your own pre-publication checks; and, when a complaint does arise, read the comparable decisions before responding, so your reply is grounded in how the Committee actually reasons. Used this way, the database is not a threat but a tool — a standing, authoritative guide to what careful, defensible journalism looks like under the Editors' Code.

12. What falls outside IPSO

Finally, know the limits of what IPSO decisions can tell you. IPSO does not regulate broadcasters, whose standards are enforced by Ofcom under the Broadcasting Code, and it does not cover publishers who have joined IMPRESS or who belong to no regulator. It also does not adjudicate matters that belong to the courts: defamation, contempt and privacy litigation run on separate legal tracks, and an IPSO decision is not a court judgment.

This matters when you are describing a press-standards story or deciding where to take a concern. A complaint about a broadcast goes to Ofcom, not IPSO; a complaint about an IMPRESS-regulated title goes to IMPRESS; and a legal wrong may need a lawyer rather than a regulator. Getting the forum right is part of getting the story right, and our guide on which regulator applies walks through the distinctions in more detail.

Key terms at a glance

A quick reference to the terms you will meet in the database, so you can read and describe a decision precisely:

• Ruling — a decision of the Complaints Committee that adjudicates whether the Editors' Code was breached, with reasoning and a finding.
• Resolution statement — a record that a complaint was settled between the parties by agreement, without a Committee finding of breach.
• Upheld / not upheld — whether the Committee found a breach of the relevant clause; a complaint may also be partly upheld.
• Adjudication — IPSO's published findings that a title can be required to print, with wording and placement the regulator can specify.
• Correction or clarification — a remedy putting right an error, published with due prominence relative to the original.
• Due prominence — the principle that a remedy should be given weight and placement proportionate to the original material.
• Public interest — the justification that can, for several clauses, outweigh what would otherwise be a breach.

Reading-a-ruling checklist

When you open a decision in the IPSO database, work through these:

• Confirm whether the entry is a ruling with a finding or a resolution statement by agreement
• Identify which Editors' Code clause or clauses were engaged
• Read the Committee's reasoning, not just the outcome
• Note the exact outcome: upheld, partly upheld, not upheld or resolved
• Note the remedy, if any: correction, clarification or critical adjudication
• Check whether a public-interest justification was considered
• Read a range of comparable decisions to see the pattern, not just one case
• Extract the transferable principle and add it to your own pre-publication checks
• If describing the decision publicly, quote the outcome label and clause precisely
• Confirm IPSO is the right regulator, not Ofcom or IMPRESS, before drawing conclusions

Common mistakes to avoid

• Describing a resolved complaint as “upheld” — a resolution statement records an agreed outcome, not a Committee finding of breach.
• Reporting the outcome without naming the clause — the finding is meaningless without the specific standard it was measured against.
• Summarising from a second-hand account — go to the database and read the decision itself before you describe it.
• Treating an IPSO decision as a court judgment — it is a regulatory adjudication under the Code, not a legal ruling.
• Confusing IPSO with Ofcom or IMPRESS — the wrong regulator means the wrong standard and the wrong story.
• Generalising from a single case — one decision is not a trend; the value is in the pattern across many rulings.
• Ignoring whether a public-interest justification was considered — it is central to how several clauses are applied.
• Paraphrasing the reasoning too loosely — a slack summary can misstate the finding entirely.
• Saying a complaint “won” without specifying on which points — partly upheld is not the same as fully upheld.
• Overlooking the remedy — the correction or adjudication is often the most practical lesson in the whole decision.

Red flags in a ruling summary

• A summary that states an outcome but links to no decision in the IPSO database
• A claim about a “landmark” ruling with no clause, date or reference given
• A description that blurs a resolution statement with a Committee finding of breach
• Language implying illegality from what is only a breach of the Editors' Code
• A second-hand account that omits the publication's side of the correspondence
• Any ruling reference or outcome that cannot be verified on ipso.co.uk
• A confident assertion about “most rulings” with no basis in the actual database

Frequently asked questions