Boundaries
RGRA clarifies written basis. It does not replace institutional functions.
RGRA is designed to sit before or beside functions that may later rely on the written record.
RGRA does not replace those functions.
It clarifies the written basis they may need before acting, reviewing, approving, closing, handing over, reporting, or escalating.
Not audit
RGRA does not perform audit testing or issue audit opinion.
Not legal advice
RGRA does not conclude liability, merits, entitlement, or legal position.
Not PMO
RGRA does not manage delivery, schedule, cost, or programme controls.
Not claims strategy
RGRA does not prepare claims, advocacy, delay analysis, or expert evidence.
Not document control
RGRA does not store, tag, migrate, or clean document systems.
Not system implementation
RGRA does not implement platforms, dashboards, workflows, or tooling.
Not free review
RGRA may read limited written context only to check fit before scoped Written Entry.
RGRA does not decide for the institution. It clarifies what the written record can support before the institution relies on it.
First written step
Send a short written background note. Do not send the full file first. RGRA will only check whether a suitable decision-bearing written flow appears to exist.