Skip to content
RADIUSTECHNOLOGY

Our methodology

The Radius
Standard

The Radius Standard is the operating expectation Radius brings to an environment. It is not a promise that every customer receives the same technical configuration. It is a baseline: known, protected, maintained, recoverable, documented and improved — adapted to the risk and shape of the business.

  1. 01Known.
  2. 02Protected.
  3. 03Maintained.
  4. 04Recoverable.
  5. 05Documented.
  6. 06Improved.

The six principles

01

Known.

What exists, who uses it, and which suppliers sit on the path are written down — not implied.

02

Protected.

Identity, devices, configuration and backup sit inside how the environment is run, not beside it.

03

Maintained.

Patching, firmware, licences and hygiene happen on a cycle, not only after something breaks.

04

Recoverable.

Important data has a restore path that has been thought about before it is urgent.

05

Documented.

The next person — including Radius — could follow what is there without starting from rumour.

06

Improved.

Repeated faults, ageing kit and unnecessary complexity are planned out, not waited out.

A small practice and a growing firm are not the same. Controls, tooling and the depth of each area should be proportionate. What should not be proportionate is accident: if something is out of standard, that should be understood and deliberate.

Eight areas

What the standard covers.

Jump to an area, or read them in order. Each one is a management expectation, not a product SKU.

  1. 01Identity

    Accounts match employment. Privileged access is limited. Sign-in is harder to steal than a password.

  2. 02Devices

    We know what is in the estate, it is configured on purpose, and it is replaced before it becomes a surprise.

  3. 03Microsoft 365

    The tenant is administered as a business platform: identity, mail, sharing and licences — not a count of seats.

  4. 04Security

    Proportionate controls are maintained as part of operations. Security is not a product bought once and forgotten.

  5. 05Data & Backup

    Important data is identified, copied with intent, and recoverable — including after ransomware. A green job is not the test.

  6. 06Networks

    The path people use to work is documented, configured on purpose, and diagnosed across supplier boundaries.

  7. 07Operations

    The environment is watched, maintained and owned. Support is part of that rhythm, not a queue that waits for a call.

  8. 08Improvement

    The estate gets simpler, safer and cheaper to live with over time. That work is planned, not hoped for after the next outage.

How it works

A framework we can use again.

The Standard is written so it can sit behind a Technology Review, onboarding, service reviews and later reporting. It is not a score. It is a shared language for what 'good enough' looks like in this environment, and what still needs work.

  1. 01

    Understand

    The business, the people, the systems, the suppliers, and what is already going wrong.

  2. 02

    Baseline

    The environment against the Radius Standard, with exceptions named rather than ignored.

  3. 03

    Stabilise

    Urgent risk first. Access, inventory and support paths that actually work.

  4. 04

    Protect

    Proportionate controls in identity, devices, backup and configuration — then kept.

  5. 05

    Support

    Day-to-day help with ownership. Monitoring and maintenance in the same relationship.

  6. 06

    Improve

    Reviews, lifecycle, licences, automation where it earns its place, and a roadmap the business can follow.

Get started

See how your technology measures up.

The Technology Review uses the Radius Standard as a shared language for the environment as it is — not a score, a scan, or a script.