Point us to what we missed, or say what you think of what we found.
Two routes, open to every entity and vendor named in the Record on identical terms. A correction changes a code when it identifies a published artifact the audit missed. A comment is published in your own words beside the element it concerns, whether or not anything changes.
Three routes
A correction
You have found a published artifact the audit missed. Give the URL; the artifact is retrieved, captured, and coded on its own terms, and any change is recorded with its direction.
A comment
You want to say something about a finding, in your own words. It is published verbatim beside the element it concerns, with the Record's three-part response.
A review
Your correction or comment was declined. A second person re-decides it on the record as it stands, within ten business days, and the reasons are published.
Correction, comment, review, register
What changes a code
A code changes only on the basis of a published artifact on the entity's or vendor's own presence, identified by URL, that existed on or before the notice date or is published afterward. The artifact is retrieved, captured, and coded on its own terms, and the change is recorded with its direction and its cause. An assertion that an artifact exists, without a URL, is recorded and produces no change, with the reason stated. A document supplied by attachment rather than published is filed and recorded as supplied on request, because the Record documents what the public can find.
A correction received after release produces a minor version where no code changes and a major version where one does; the earlier version stays at its permanent URL.
Submit a correction
The form asks for the entity or product, the version, the indicator or element, the URL of the published artifact the correction rests on, and your name and role. It asks for nothing else. Acknowledgment within two business days; a decision within ten.
As of 13 September 2026
The correction form renders here once the plugin is active. Until then, send the entity or product identifier, the version, the element, the URL of the published artifact, and your name and role through the contact page.
Published in your own words, beside the finding
A comment attaches to one element of a profile or product record: an indicator code, an element of the public channel block, a platform row, an instrument in force, a flag on a product record, the frame statement, or the Level computation. It comes from the body's authorized contact, verified against the contact the body publishes for the role, and is attributed by role. Up to three hundred words per element and one thousand five hundred per version.
A comment is published verbatim, with only personal data redacted, under the element it concerns, labelled with the body's name and the date received. The Record's response beside it is limited to three things: the status of any artifact the comment identifies, the code decision, and the reason. A comment may say anything within its scope, including that the body considers itself to comply with a law; the statement is the body's and is labelled as such. A comment never changes a code and never delays a release.
The two-step review
A declined correction or a comment declined for publication is re-decided by a second person on request. There is no third step; the record shows the request, the decision, the review, the reasons, and the body's comment, and the reader judges.
The decision, in writing
The compiler of the profile gives the decision and its reasons in writing within ten business days, and the decision is entered in the corrections register.
Review by a second person
Within ten business days of that decision the body may ask for review, decided by the other principal of the publisher, or by a declared reviewer who had no part in the profile, within ten business days, with the outcome and reasons published beside the first decision.
No third step
The method advisory group may publish a non-binding view on the method question a review raises; its view is advisory and published.
Every request and its outcome
One row per request: date received, entity, version, element, type, outcome, the version issued if any, and the dates against the service standard. An annual summary is published with each cycle, and where the service standard is missed, this register records it.
As of 13 September 2026
The public corrections register renders here. It is empty until the first profile is released.