Methodology: The Leveller™ — Development, Purpose and Approach
- Steve Conley
- 1 day ago
- 3 min read
The Leveller™ was developed to address a persistent structural problem: the imbalance of information, understanding and practical power between individuals and the institutions with which they transact.
Most consumer-facing financial and contractual documentation is drafted by, or on behalf of, the institution issuing it. Its language, structure and emphasis tend to reflect institutional priorities: regulatory compliance, liability management, operational efficiency and internal consistency. These are legitimate concerns, but they are not the same as the practical needs of the person expected to read, understand and rely upon the document.
This imbalance is not usually the result of deliberate concealment. More often, it arises from the way institutional documentation is produced, maintained and distributed. Information may be disclosed, but still remain practically inaccessible. It may be technically available, yet too complex, fragmented or obscure for the individual to use confidently when making a decision.
The Leveller™ was built on the premise that genuine transparency requires more than disclosure. It requires independent translation: turning institutional language into clear, usable understanding.
The tool analyses documents, correspondence or contractual material provided to it and produces a structured plain-English assessment. This assessment identifies the apparent rights and obligations of each party, areas of potential risk or imbalance, possible hidden costs, missing information, and the practical questions a person may wish to ask before signing, relying upon, or acting on the material. Where relevant, it may also identify possible regulatory bodies, complaint routes or redress mechanisms that could become relevant if a dispute arises.
The output is designed to resemble the kind of practical explanation a knowledgeable independent reviewer might provide, but without the cost, delay or access barriers that often prevent individuals from obtaining professional support at the point they most need clarity.
The Leveller™ does not provide legal, financial or regulated advice. It does not determine liability, adjudicate compliance, or replace professional judgement. Its purpose is narrower but highly practical: to help a person understand what the material appears to say, what it does not say, where the balance of rights and obligations may sit, and what reasonable questions should be asked before proceeding.
In that sense, The Leveller™ is best understood as a tool for informed consent. It supports understanding before commitment, rather than redress after harm.
The wider purpose of The Leveller™ is to restore individual agency within relationships that are often asymmetric by default. Many technologies in financial services are built for institutions because institutions hold the budget, define the workflow and commission the tools. They are designed to reduce institutional cost, manage institutional risk or improve institutional efficiency.
The Leveller™ was deliberately built from the opposite direction. It is a tool for the individual, accountable to the individual, and designed to operate before a decision is made.
This orientation shaped the methodology applied in the USS member inquiry described elsewhere in this paper. The Leveller™ was not used to conduct a comprehensive audit of USS governance, nor to determine legal or regulatory compliance across the scheme as a whole. It was used as a point-in-time assessment of the materials actually provided to one member.
The purpose was deliberately modest but practically significant: to assess what an individual member, using an independent analytical tool, could reasonably establish from the documentation available to him.
That makes the test one of accessibility, not institutional intention. The central question is not whether information existed somewhere within the system, but whether the person it was intended to serve could realistically understand and use it.
.png)



Comments