Evidence & Assessment

This page defines IGSB’s evidence expectations and the high-level basis on which readiness reviews, formal assessments, and certification determinations are documented. It is provided for transparency and to support consistent, defensible treatment of evidence across engagements.

Purpose and Scope

IGSB standards require demonstrable evidence. Evidence is the basis on which any written IGSB statement is formed, whether the engagement is a readiness review, a formal assessment, or certification.

This page sets out minimum expectations for evidence quality, evidence categories, and how evidence is handled. It is intentionally high-level. It does not prescribe implementation methods, operational controls, or management processes.

Definitions and Boundaries

Readiness review

A structured review of submitted materials to identify material gaps against an IGSB standard and to indicate whether an organisation appears prepared to enter formal assessment. A readiness review is not an assessment, does not result in certification, and does not provide assurance.

Assessment

A formal evaluation of submitted evidence against a defined IGSB standard and associated assessment criteria. Assessment outcomes are recorded in writing and may support certification decisions.

Certification

A time-bound status issued by IGSB indicating that, based on evidence reviewed and recorded at the point of determination, the organisation has met the relevant IGSB standard requirements. Certification is subject to defined conditions, scope, and renewal or review requirements.

Key boundary

IGSB does not provide implementation, advisory, or remediation services. Evidence is assessed as submitted. IGSB statements are based on documented evidence treatment and are non-binding.

Evidence Principles

Evidence submitted to IGSB is expected to be relevant, traceable, sufficient, reliable, current, and internally consistent.

Relevance

Evidence directly maps to a requirement within the relevant IGSB standard and falls within the stated scope.

Traceability

Evidence can be traced to an identifiable owner, source, or system of record, with clear versioning or timestamps where applicable.

Sufficiency

Evidence is adequate in quantity and coverage to support a conclusion across the applicable scope, not isolated examples.

Reliability

Evidence is credible in origin and form. Where self-generated statements are provided, supporting artefacts are expected.

Currency

Evidence reflects the current operating state at the time of submission and is not materially outdated relative to the claim.

Consistency

Evidence does not materially contradict other submitted materials, published policies, or stated governance arrangements.

Evidence Categories

Evidence is commonly presented across multiple categories. The following list is indicative and non-exhaustive.

Governance documentation

Charters, terms of reference, delegations of authority, committee structures, role descriptions, and documented decision rights.

Policies and standards

Board-approved or management-approved policies, internal standards, mandatory controls, and documented governance requirements.

Operational procedures and controls

Procedural artefacts that demonstrate how policies and governance requirements are enacted in practice.

Records and decision logs

Minutes, decision registers, approvals, risk acceptance records, and governance reporting packs showing oversight and challenge.

Risk, compliance, and assurance artefacts

Risk registers, control assessments, internal reviews, compliance attestations, audit outputs, and remediation tracking (where applicable).

Training and competence evidence

Role-based training records, competence frameworks, induction materials, and evidence of ongoing capability maintenance.

Evidence Submission and Handling

Evidence is accepted in formats that support reliable review, traceability, and continuity of access for the duration of the engagement. Typical formats include controlled PDF documents, structured exports from systems of record, and secure document links.

Evidence submissions should include a clear index or mapping that identifies which standard requirement each artefact supports. Where narrative statements are provided, supporting artefacts are expected to substantiate the claim.

IGSB treats submitted evidence as confidential within the limits of applicable law, the Website Terms of Use, and the Legal & Governance Disclaimer. Evidence is handled on a minimum-necessary basis for the purpose of documented evaluation.

Assessment Method (high-level)

IGSB applies a consistent, documented approach to evidence evaluation across all formal assessments. The method is intentionally high-level and does not prescribe implementation activity.

  1. Intake and scope confirmation - submitted materials are logged and aligned to the defined assessment scope.
  2. Evidence mapping - artefacts are mapped to standard requirements and referenced by identifier.
  3. Evidence evaluation - evidence is evaluated against requirement intent and assessment criteria.
  4. Consolidation - findings are consolidated, contradictions are recorded, and material gaps are identified.
  5. Written statement - a formal written record documents conclusions, scope, and limitations.

Outcomes and Statements

Depending on the engagement type and evidence submitted, outcomes may include:

  • A written readiness view identifying material gaps against a specified IGSB standard
  • A documented assessment record showing requirement-level evidence treatment
  • A certification determination that is scope-bound and time-bound
  • A written statement of non-certification where requirements are not met

All IGSB outputs are written, non-binding, and limited to the evidence reviewed at the point of determination. They do not constitute audit opinions, legal opinions, or assurances of future performance.

Records, Retention, and Confidentiality

IGSB retains records necessary to support defensible evidence treatment, institutional governance obligations, and the integrity of issued statements. Retention is proportionate to the engagement type and scope.

Personal data is handled in accordance with the IGSB Privacy Policy. Organisations submitting evidence remain responsible for lawful disclosure and appropriate redaction where required.

Correspondence Protocol (email-only)

All correspondence with IGSB is conducted in writing. IGSB does not engage via telephone calls, video meetings, or live chat.

Written correspondence should be directed via the Contact page. Where an engagement proceeds, all evidence submission and outputs follow the documented written protocol for that engagement.