Notice before release, comment after, and the same clock for everyone.
Every entity and vendor in the Record is told what was found before it is published, has a defined window to point to anything missed, can comment in its own words after release, and can ask for a declined decision to be reviewed. The dates are published and the same rule applies to every body of the same class.
Step by step, and the standard behind it
From draft to release and after
The steps are the same for an entity profile and a product record, and the same for a first release and a re-audit.
Declaration
Every person working on a profile declares any relationship with the body before starting.
Before work beginsNotice
The body receives the draft public channel block and indicator table through its own published accessibility route, with the correction rule and the closing date.
When the draft passes the mechanical checksThe window
Ten business days, counted in the body's local time, not extended on request. An early response does not shorten the window for further responses.
From the day notice is sentRelease
The release checklist is run by a person; the profile goes live at a permanent versioned URL.
After the window closesRelease notification
Every noticed body is told the version is live, with the URL, the correction route, and the comment route.
Within two business days of releaseComment
Published verbatim beside the element it concerns, with the Record's three-part response.
During the window, or any time after release; published within ten business daysCorrection
A published artifact, identified by URL, changes a code; a new version is issued and the earlier version stays at its URL.
Any time after release; decision within ten business daysReview
A declined correction or comment is re-decided by a second person on request, with reasons published beside the first decision.
Request within ten business days of the decision; outcome within tenUpdate notice
Before every re-audit the body receives the delta table of every code that changed, and a new window.
Per the published calendar, at least ninety days aheadRetraction
A materially wrong version is never deleted; a retraction notice at its URL links to the corrected version.
When found
What we promise, and where it is measured
Where a standard is missed, the corrections register records it.
| Item | Standard |
|---|---|
| Acknowledgment of a notice response, correction, or comment | Two business days |
| Decision on a correction request | Ten business days |
| Notice window | Ten business days |
| Release notification | Two business days after release |
| Re-audit calendar published | At least ninety days ahead |
| Comment received after release published | Ten business days |
| As-of date | On every figure, every code, and every page |
Institutions, not people
The Record documents institutions. A person's name appears only where the institution itself publishes it for the public role the Record records, and only with the role. On request from the person or the institution the name is replaced by the role, without any change to the code, because the code records whether a contact for the role is published, not who holds it. Notices go to office contacts. Comments are attributed by role.
A summary of this page in signed language
A signed-language summary of the process and of the notice text is published here so that Deaf and DeafBlind readers, and the Deaf-led bodies the Record documents, have the process in their own language.