The Four Levels at a Glance
| Level | In one line | What you'll see | Usual next step |
|---|---|---|---|
| S4 Strong | In place, managed, right-sized | Evidence on request, an owner, a schedule, recent testing | Keep it there; review on a cadence |
| S3 Adequate | Fundamentals exist, management is incomplete | Works most of the time; gaps in coverage, testing or documentation | Close the specific gap |
| S2 Limited | Partial, inconsistent, or aging into risk | Depends on who is around; known problems with no plan | Put a process and an owner in place |
| S1 Priority | Absent or unreliable | No working practice, or one that fails when tested | Fix first; this is where incidents start |
The levels apply to each area separately. A single organization is almost never at one level everywhere: it is common to see strong endpoint protection next to untested backups and no written incident plan. That spread is exactly what the assessment is meant to show.
S4 Strong
The practice is in place, actively managed, and appropriate for the organization's size and risk. "Actively managed" is the key part: someone owns it, it runs on a schedule, and there is recent proof that it works.
- Infrastructure: servers are within a supported lifecycle and running a supported, patched operating system.
- Security: systems are patched automatically and vulnerabilities are actively identified and remediated.
- Operations: documentation is current, accessible, and maintained.
- Governance: access is restricted based on role and reviewed regularly.
S4 doesn't mean perfect or expensive. A ten-person office with a well-run, modest setup can be S4 in most areas.
S3 Adequate
The fundamentals exist, but management is incomplete. This is the most common level in organizations that have an IT provider but no regular review. The practice usually works; the risk sits in what isn't covered or hasn't been tested.
- Infrastructure: servers are aging or approaching end of warranty but remain operational.
- Security: patching and scanning occur but remediation is inconsistent.
- Operations: documentation exists but is outdated or incomplete.
- Governance: role-based access exists but is not routinely reviewed.
Moving to S4 is usually about routine, not new tools: a schedule, a test, an owner, a record.
S2 Limited
The practice is partial, inconsistent, or aging into risk. Things work because a particular person remembers to do them, or because nothing has gone wrong yet.
- Infrastructure: servers are out of warranty or running unsupported operating systems.
- Security: many systems are behind on updates and vulnerabilities are handled reactively.
- Operations: documentation is minimal.
- Governance: access controls are defined but loosely enforced.
Moving to S3 means turning the practice into a process: writing down how it's done, assigning it, and covering the systems that were left out.
S1 Priority
The practice is absent, or unreliable enough that it belongs at the top of the remediation list. These are the areas where incidents begin and where recovery goes badly.
- Infrastructure: server reliability presents a direct risk to business operations.
- Security: patch and vulnerability gaps create active exposure to known exploits.
- Operations: knowledge gaps significantly increase time-to-resolution.
- Governance: users have broad or excessive system access.
Moving off S1 comes first in any plan, even ahead of improving areas that are already S3. Getting every S1 area to S2 usually reduces more risk than any single upgrade elsewhere.
See where each area of your environment sits
Rate 68 areas against these four levels and get a scored, client-ready report.
From Levels to a Maturity Score
Each level is a number: S4 is 4, S3 is 3, S2 is 2, S1 is 1. Averaging the in-scope areas gives a score for each domain and an overall figure on a 4.00 scale. That figure maps to a band (Strong Alignment from 3.50, Developing Alignment from 2.75, Needs Attention from 1.90, and Priority Focus below that), described on the maturity assessment model page.
An illustrative example, a 25-person professional services firm on its first assessment:
| Domain | Average | What drove it |
|---|---|---|
| Infrastructure | 3.1 | Modern hardware; backups never test-restored |
| Cybersecurity | 2.8 | Good endpoint protection; MFA missing on remote access |
| Operations | 2.6 | Responsive help desk; almost no documentation |
| Governance | 1.9 | No incident plan, no access reviews, no named owner |
| Overall | 2.6 | Needs Attention: governance is the place to start |
The overall number is useful for trend lines. The domain and area levels are what drive the plan.
Four Levels Compared With Five-Level Models
Many maturity models, including those that follow the Capability Maturity Model's lead, use five levels, often named along the lines of Initial, Managed, Defined, Quantitatively Managed and Optimizing. Those models describe how mature an organization's processes are and suit large organizations with formal process programs. For an advisory review of a small or mid-sized environment, a four-level scale tied to observable states is quicker to apply and harder to fudge, because there is no middle level to default to.
As a rough guide only: S1 corresponds to the bottom level of a five-level model, S2 to a practice that's repeatable but not standardized, S3 to a defined, documented practice, and S4 to one that's measured and managed.
Frequently Asked Questions
What is a good IT maturity score?
On a 4.00 scale, 3.5 or above is strong, and most organizations that have never been assessed land between 2.0 and 3.0. The trend matters more than the starting point: a steady climb quarter over quarter is the sign of a well-run program.
Should every area be at S4?
No. The target depends on the organization's risk. A practice handling patient data needs S4 on access control and encryption; the same practice may be fine at S3 on managed print. Agree on targets per area with leadership.
How long does it take to move up a level?
Moving from S1 to S2 is often days or weeks: turn on MFA, start a backup test, write the first version of a plan. Moving from S3 to S4 takes longer because it relies on habits, such as reviews and testing, that need a few cycles to prove themselves.
Who decides which level an area is at?
The assessor, by matching what they observe to the written description for each level. Fixed descriptions keep two assessors, or the same assessor in two quarters, from scoring the same environment differently.