Network-unavailable operating procedure

This packet is designed to keep administrative intake and record handling moving when the Internet, website, local network, or responsible digital service cannot be used. Keep printed blank stock and a bound paper-continuity register in the responsible office before an outage occurs.

Reference-number rule

Write the bound register code on its cover before operational use. During an outage, the receiving records custodian assigns the next unused sequential entry and forms the paper reference:

PPR-RECORDS-TRANSPARENCY-{REGISTER}-{YYYYMMDD}-{ENTRY}

• REGISTER: 2–12 upper-case letters/digits identifying the bound office register. It is a records-control code, not an authority code.
• YYYYMMDD: local date the matter was received on paper.
• ENTRY: 4–6 digit zero-padded sequential entry from the register. Never reuse, erase, or renumber an entry. Mark voided entries “VOID” with reason, date, and initials; do not recycle the number.

Outage procedure

1. 1Open the outage log on the inside cover or next available register page. Record outage start date/time, known scope, custodian, and the last unused register entry number. Do not rely on a website, QR code, cloud file, or online lookup to perform the remaining steps.
2. 2Receive the matter on the Intake/Application sheet. Confirm the responsible mechanism if known; record only information appropriate to that mechanism. Mark privacy/classification based on the owning record rules. If uncertain, protect the record and route it for classification rather than exposing it.
3. 3Assign the next paper reference and enter it in the bound register before separating any pages. Put the same reference on every sheet and attachment. Count attachments/pages.
4. 4Complete both halves of the Receipt sheet. Give the submitter copy to the submitter and keep the office copy with the original. The receipt proves administrative receipt only; it is not approval, adjudication, status, entitlement, payment, or other substantive result.
5. 5Route the original package to the responsible office using the Routing / Processing / Custody sheet. Every physical transfer records date/time, from, to, purpose, signature/initials, and page/package condition. Where formal chain of custody is not relevant, the same fields operate as ordinary file-movement control.
6. 6The responsible operator records processing steps and administrative status without inventing unavailable digital timestamps or outcomes. Use the Notice / Administrative Conclusion sheet only for a conclusion the owning mechanism can legitimately issue. Leave signature, witness, attestation, oath, or seal fields unused unless that mechanism actually requires them.
7. 7If the owning mechanism provides correction, review, reconsideration, objection, or appeal, receive it on the Correction / Review / Appeal sheet under the same paper reference or a linked new paper reference as the owning procedure requires. The common form does not create an appeal right or deadline.
8. 8At each shift/day close, reconcile the number of used, voided, open, routed, and closed paper entries against physical files. Store originals in the controlled physical location appropriate to their classification. Never destroy a paper original merely because a scan exists.
9. 9When the responsible digital mechanism is restored, reconcile in register order. Create the digital record through the owning mechanism’s authorized import/intake path and attach the paper-origin provenance contract. Record the resulting digital reference on the Reconciliation sheet and in the bound register. Do not backdate the digital creation time; preserve the original paper-receipt time separately.
10. 10After reconciliation, a second checker or records custodian verifies the paper reference, register entry, page count, classification, digital reference, scan hash if one was made, and that no entry was skipped. Retain the original under the owning record schedule. If no authorized disposition schedule is available, hold the original; do not destroy it.

Prepared-register control

Language field: Authoritative Yisreh'eyleeth service/form name: ____________________________________________. Complete this line only from the controlled language source for the owning mechanism. Do not substitute another script.