Credentials & assurance

Competence made visible—without borrowed authority.

A transparent view of relevant qualifications, professional boundaries and the verification available for each engagement.

Request a scoping call

ISO / Lead-auditor expertise

Eight standards.
One commitment to quality.

Pegasus provides lead-auditor expertise across the following management-system standards, with each audit scoped to your organisation and its requirements.

ISO 14001
Environmental management
ISO 9001
Quality management
ISO 45001
Occupational health and safety management
ISO/IEC 42001
Artificial intelligence management
ISO/IEC 27001
Information security management
ISO/IEC 20000
IT service management
ISO 22000
Food safety management
ISO 13485
Medical devices quality management

Lead-auditor expertise supports audit and assurance work. Independent certification bodies make certification decisions. Applicable editions, standard parts and sector-specific requirements are agreed in the engagement scope.

Who this helps

Built around a buying situation.

  • Procurement and due-diligence teams
  • Clients assessing competence
  • Professional and delivery partners

Useful when

The trigger is already visible.

  • An engagement requires role-specific competence evidence
  • Accreditation and qualification boundaries must be clear
  • A buyer needs to validate multidisciplinary capability

The position

Competence without borrowed authority.

Credentials support a competence decision; they do not replace one. Pegasus presents qualifications as individual professional credentials, makes documentary verification available during due diligence and distinguishes them from corporate accreditation or regulatory authorisation.

01

A defined scope and accountable decision owners

02

Controls matched to the real operating context

03

Evidence that can be reviewed, tested and improved

Scope

What the work includes.

Every engagement is scoped around authority, operating context, available evidence and the decision that must be made.

01

Technical & cyber

Technical competence and any relevant certification are checked against the network, cyber or AI-security scope before engagement.

02

SHEQ & management systems

Relevant SHEQ, fire, DSEAR and management-system competence is reviewed against the work and any client requirements.

03

Legal operations, UX & delivery

Evidence-handling, AI testing and delivery experience are considered within clearly agreed professional boundaries.

Method

A controlled route from exposure to evidence.

Decision points, responsibilities and verification stay visible from the start.

01

Discover

Define the exposure, context, evidence, owners and decision that matters.

02

Design

Select proportionate controls and make responsibilities and hold points visible.

03

Implement

Embed the agreed system into the real operating workflow.

04

Verify

Test whether controls work and whether the evidence supports the conclusion.

05

Improve

Close actions, learn from exceptions and strengthen the system over time.

Outputs

Evidence designed for use.

A scope-specific competence review

Relevant qualification evidence on request

Clear professional boundaries and specialist referral where needed

Agreed responsibilities and verification requirements

Professional boundaries

Precision includes saying what the work does not claim.

Questions answered

Before you scope the work.

Is Pegasus an accredited ISO certification body?

No. Lead-auditor qualifications are individual credentials. Pegasus can support implementation and internal assurance but does not award accredited certification.

Is Pegasus a regulated law firm?

No. Pegasus provides scoped technical evidence and case support; reserved legal activities are referred to appropriately authorised professionals.

Can certificates be checked?

Role-relevant documentary evidence, status and scope can be made available during proportionate engagement due diligence.

Start the conversation

Bring the exposure. Leave with a controlled route forward.

A first conversation is used to understand context, authority and the decision required—not to force a predetermined package.

Request a scoping call