RPG Excellence
Checking account…
Start assessment →
NEW STANDARDISO 9001:2026 is now publishedSee what changed and prepare your quality management system.
Read full update
RPG EXCELLENCE · AI ASSURANCE

Useful assistance. Visible limits. Accountable decisions.

RPG Excellence uses structured automation and decision support to help people organise evidence, identify priorities and prepare controlled outputs. Technology can assist the work; it does not inherit the authority or professional accountability of the user.

CORE PRINCIPLE

No automated or assisted output becomes an approved assurance conclusion merely because the platform produced it.

Approval remains attributable to an authorised person and must be supported by appropriate evidence.

CURRENT CAPABILITY REGISTER

What the platform does today—and where the boundary sits.

This register separates deterministic platform functions from future or provider-enabled generative capabilities. It will be revised when the processing method or customer data flow changes.

StatusCapabilityHow it worksHuman control
ACTIVEStructured calculations and decision support

Controlled application logic applies defined scoring, thresholds, status rules and workflow conditions.

The responsible user checks the inputs, rationale and resulting decision before approval.

ACTIVEControlled report assembly

Approved platform records are assembled into structured reports and draft narrative using application rules and templates.

Named preparers, reviewers and approvers remain responsible for the issued report.

CONTROLLED BOUNDARYAutomated prompts and recommendations

The platform highlights missing information, due activity, risk conditions and suggested next steps.

A prompt cannot approve an audit, accept a risk, close a finding or verify effectiveness.

NOT CURRENTLY RELIED UPONExternal generative-model decision making

RPG Excellence does not treat an external generative model as an autonomous assurance decision maker.

Any future provider-enabled feature must be documented, assessed and released under the controls on this page before customer use.

CONTROL FRAMEWORK

Eight guardrails applied across assisted features.

01

Defined purpose

Each assisted feature must have a stated user need, permitted use and prohibited use.

02

Minimum necessary data

Users should provide only information relevant to the task. Passwords, recovery codes, secret keys and unnecessary sensitive personal data must not be entered.

03

Evidence before output

Assisted wording does not become objective evidence. Conclusions must remain traceable to controlled records, observations, interviews, samples and applicable requirements.

04

Human review and authority

An authorised and competent person remains responsible for relevance, accuracy, context, approval and any action taken from the output.

05

Explainable calculations

Where the platform calculates risk, priority, progress or status, the relevant inputs, method and threshold should remain visible or documentable.

06

Role and tenant boundaries

Assisted functionality must not bypass subscription entitlement, organisation scope, user permissions, approval gates or administrative controls.

07

Testing before release

Material features are reviewed against intended behaviour, known failure modes, inappropriate reliance, access boundaries and representative use cases.

08

Challenge and correction

Users can reject unsuitable output and report material errors, privacy concerns or security issues for triage, correction and feature review.

DATA AND PROCESSING BOUNDARIES

Customer information is not an unrestricted AI input.

01

Purpose limitation

Information should be processed only for the documented feature purpose and within the user's authorised organisation.

02

Provider transparency

If an external model provider is introduced, RPG Excellence will identify the purpose, relevant data flow, provider role and available user controls before customer use.

03

No silent authority transfer

Introducing an assisted feature does not change user roles, subscription access, approval authority or accountable ownership.

PROHIBITED RELIANCE

What assisted functionality must not do.

FEATURE LIFECYCLE

From proposal to controlled operation.

01

Define

Purpose, users, inputs, outputs and prohibited reliance

02

Assess

Privacy, security, access, bias and failure scenarios

03

Test

Representative cases, boundary checks and human review

04

Release

Guidance, limitations, version control and monitoring

05

Review

Errors, user challenge, material changes and withdrawal

CHALLENGE, ERROR OR CONCERN

Users should question output that does not fit the evidence.

A material accuracy, privacy, security or inappropriate-reliance concern should be reported with the feature, record reference and reason for challenge. RPG Excellence can then determine whether correction, guidance, restriction or withdrawal is required.

Report a concern →

Public control statement · Version 1.0 · Reviewed 17 October 2026. This page will be updated when material functionality or processing changes.

AI Assurance and Guardrails | RPG Excellence | RPG Excellence