The public portal is not the system history
A public docket page shows current values. It does not necessarily expose when each value was written, whether it changed, or which credential performed the action. The dispute can be resolved only with the underlying event data.
Minimum preservation fields
| Record | What it answers |
|---|---|
| Operator and role ID | Which credential created or modified the entry |
| Event timestamp with time zone | When the write actually occurred |
| Before-and-after filed date | Whether June 15 replaced another value |
| Scan batch and image creation time | When the 83-page artifact entered imaging |
| Attachment history and document hash | Which file was connected to Correspondence |
| Envelope or submission identifier | Whether a rejected electronic source was reused |
| Reason code and notes | The stated basis for any manual correction |
The decisive test
If the authenticated event history shows ordinary June 15 intake, it should identify the source and operator path. If it shows a later creation or field edit assigning June 15, it confirms the backdating conclusion. Either result is more reliable than the current-value portal alone.