Zebsoft Shield Levels
The Right Scale for Your Organisation
Establish, expand and coordinate governance through one connected assurance platform.
Shield Levels describe the scale, depth and reach of Zebsoft across your organisation. They provide a starting point for the responsibilities, operational controls and people you need to connect.
Each level uses the same underlying architecture, so the platform can develop as organisational complexity grows.
One platform. Different scales of operation.
What Changes—and What Stays Connected
Choose the depth of control and organisational reach you need, while retaining a common route from requirements to operational evidence.
The scope can expand
- The teams, locations and responsibility areas connected
- The Domains actively governed
- The depth of workflow, configuration and oversight
- The external interactions supported through Portals
The architecture remains consistent
- Connected requirements, records and evidence
- Defined owners and accountable decisions
- Shared operational capabilities
- Traceable work, review and improvement
Shield Levels describe platform scope. Certification and compliance remain organisational responsibilities, supported by appropriate controls, evidence and competent review.
Start with operational reality
Match the Platform to the Work You Need to Control
The right starting point depends on your present responsibilities and complexity: who needs to act, what must be governed, and where evidence and decisions must connect.
Establish
Bring documents, risks, audits and actions into a controlled baseline with clear ownership.
Expand
Extend governance across more responsibility areas and coordinate activity as the organisation develops.
Coordinate
Maintain oversight across multiple sites, functions and external stakeholders without losing local accountability.
Compare Shield Levels
Four Starting Points. One Shared Structure.
Use these descriptions to frame the conversation. Confirm the required configuration and enabled scope against your organisation’s needs.
Foundation Shield
For organisations formalising governance or bringing existing informal systems into a shared structure.
Typical fit
- Single-site or small multi-site operations
- Internal compliance teams
- Early certification or re-certification programmes
Core scope
- Core governance structure
- Document control
- Audits and actions
- Risk management
- Internal users
Growth Shield
For organisations expanding responsibility across more areas and needing greater coordination, configuration and oversight.
Typical fit
- Growing organisations
- Multiple standards or regulatory frameworks
- Increasing accountability requirements
Scope to discuss
- Additional governance Domains
- More advanced audits and tasks
- Expanded configuration options
- Greater reporting and oversight
Enterprise Shield
For complex, regulated or distributed operations extending control across sites, functions and external relationships.
Typical fit
- Multi-site or multinational organisations
- Regulated operating environments
- Extensive supplier or contractor networks
Scope to discuss
- External-party Portals
- Advanced permissions and visibility
- Cross-Domain and cross-standard traceability
- Coordinated governance across the wider ecosystem
Bespoke Shield
For organisations whose sector, operating model or assurance needs require a specifically configured approach.
Typical fit
- Sector-specific regulatory frameworks
- Specialist operational requirements
- Custom workflows and reporting
Scope to discuss
- Configuration around the agreed operating model
- Specialist workflow and reporting requirements
- The same underlying Zebsoft architecture
- Consistent ownership, evidence and control
Grow within the same platform
Extend the Scope Without Losing the Thread
Shield Levels build on a common foundation. As scope increases, retain the relationships between existing data, evidence, ownership and operational work.
Preserve context
Keep existing records and evidence connected to the responsibilities they support.
Add responsibility areas
Introduce additional Domains as the organisation’s governance needs develop.
Extend participation
Introduce relevant Portal interactions and permissions when the agreed scope requires them.
Choosing your starting point
Answer the Questions That Determine Scope
What must be controlled?
Identify the responsibility areas, standards, operational risks and evidence requirements that matter now.
Who needs to participate?
Identify internal teams, locations and external parties, together with the work and visibility each requires.
How complex is the work?
Consider review, approval, checks, escalation and reporting requirements before choosing the depth of configuration.
What should expand next?
Agree a practical initial scope and a route for adding Domains, workflows or Portal participation later.
Find the right scale
Start With Your Assurance Need
Bring your current operating model, the responsibilities you need to govern and one real control challenge. We can explore the Shield Level and configuration that fit.


