COMPACTROUTE | APPLICATION DOCUMENT & EVENT LEDGER Companion: /professional-records/application-ledger Editorial worksheet prepared 2026-11-04. Not a regulator's form. Save locally. CompactRoute does not collect or submit this sheet. CASE Profession / license category: Authority / jurisdiction: Application route being researched: Your local case/application reference (keep private): Relevant facts and unknowns: DOCUMENT (repeat per item) Document ID / title / issuer: Version / file date / local evidence reference: Supersedes which version? (preserve earlier evidence): Official instruction URL / section / date checked: Required sender and channel, as stated in that instruction: Unknown requirements needing clarification: EVENT (append; do not overwrite earlier events) Event ID / document ID and version: Date / time / timezone: Actor / action / recipient or portal: Exact status/message (or clearly labelled personal note): Evidence filename/reference / whose acknowledgement is it?: Working label: sent | received | matched to this application | complete | approved/issued | additional information requested | unresolved What the evidence establishes, including scope/conditions/effective date: What the evidence does NOT establish / conflict with earlier evidence: CLAIM CHECK (repeat for the same document/version and application) Application reference / document ID and version: For EACH claim below, record: established | not established | conflicting, the supporting event/evidence reference, exact words and their scope. Leave a claim not established if the available evidence does not address it. 1. Dispatch by the sender: 2. Receipt acknowledged by the receiving authority: 3. Matching of this item/version to this application: 4. Completeness -- specify the item OR the entire application: 5. Approval/issuance -- preserve the decision's scope, effective date, conditions and exclusions: These are separate evidence claims, not a progress bar. One supported claim does not fill the others. A delivery service's receipt is not the authority's acknowledgement. Receipt is not matching; matching is not completeness; completeness is not approval. Do not transfer evidence to a corrected version or another application unless the authority's message covers that version and application. Preserve conflicting messages instead of choosing the newest one automatically; keep the disputed claim open for clarification. NEXT ACTION Open question or missing item: Who will do what next: Evidence needed to close this item: Official deadline ONLY if identified, with source and timezone: Your own follow-up reminder (not a board deadline): Related question-brief ID / reply reference: Closure reason and evidence / reopening trigger: READING THE RECORD Sent does not establish receipt. Delivery does not establish matching to an application. Received does not establish completeness or approval. Record complete/approved only within the authority's exact stated scope. No reply, missing portal status and conflicting messages stay unresolved. Labels are editorial, not a universal sequence or official status taxonomy. Keep sensitive records securely; follow the authority's submission process. This ledger does not establish eligibility or permission to practice. WORKED COMPARISONS (fictional; not official messages or processing timelines) A. The school confirms dispatch of T-01 version 1 for application A-01. A courier reports delivery to an office. No authority reply is available. Record dispatch and the courier's limited delivery evidence. Authority receipt, application matching, completeness and approval are not established. B. The authority says: "T-01 version 1 is matched to A-01; another document is outstanding." Record matching with that exact scope. The message does not establish completeness of the entire application or approval. A later version 2 needs its own evidence; do not inherit version 1's matching. C. The authority says: "A-01 is complete for review. A decision is pending." Record completeness for review with the message reference. Approval is not established. Do not infer a start date or permission to practice. SOURCES AND LIMITS Consulted 2026-11-04: https://telehealth.hhs.gov/licensure/licensing-across-state-lines HHS updated 2025-04-30; different routes and state-specific conditions. https://www.rn.ca.gov/status.shtml California BRN transcript issuer/channel example only, not a universal rule. No update date identified in the consulted BRN text. Follow current profession/authority/route-specific instructions.