Task 01 · Application trail
Track document events without turning a receipt into approval
Build one dated history for a specific application. The result should show which version went through which channel, what the receiving authority actually acknowledged and which document action remains open.
Download the blank event ledger (.txt)Start with one application, then add an entry per event
Label the case with profession, authority, jurisdiction, route under consideration and your own application reference if one exists. Keep license numbers and private records in your own secure file; this page does not need them.
- Document and version
- Use a document ID, file/version date and issuer. If a corrected copy replaces one, keep both entries and mark which version supersedes the other.
- Instruction being followed
- Save the official URL, section, date checked, required sender and delivery channel. Record an unknown instead of inferring a rule from another board.
- Event and evidence
- For each event record date/time with timezone, actor, action, recipient or portal, exact message and receipt/reference. A sender’s confirmation and the board’s acknowledgement are separate evidence.
- Next unresolved action
- Name who will check or supply what and what evidence would close that item. Keep an official deadline, its source and timezone separate from your own follow-up reminder.
Copy events in order rather than overwriting a status cell. If a later message contradicts an earlier one, preserve both and flag the conflict for clarification. Store a local evidence filename or reference so another reviewer can find the underlying message.
Keep these claims separate
- Sent: the sender or service records dispatch. It does not establish receipt or acceptance.
- Received: identify whose acknowledgement this is and what item it covers. A delivery receipt alone does not establish that the board matched the item to your application.
- Complete: record this only if the authority says the relevant item or application is complete, using its exact wording and scope. Do not infer it from a quiet inbox.
- Approved / issued: record only what the authority’s decision or record actually states, including effective dates, conditions and unresolved limits. A document ledger itself never grants permission to practice.
- Additional information requested / unresolved: keep the request, missing item and any stated deadline. No answer, an inaccessible portal or an ambiguous message stays unresolved.
These are evidence labels for your working record, not a universal sequence or official status taxonomy. Boards may use different terms or skip stages.
Worked example: a transcript sent, then a receipt still missing
Fictional record. Day numbers are illustrative, not actual dates, processing estimates or a board’s promised schedule. No real applicant, portal or case is represented.
- Before sending: the applicant saves the receiving authority’s current transcript instructions and identifies the required issuer/channel. The instruction reference is linked to document T-01, version 1.
- Day 1 — sent: the school confirms dispatch of T-01. Evidence S-01 is the school’s message. Board receipt remains unknown.
- Day 2 — conflicting view: the applicant’s status screen still lists the transcript as missing. Evidence P-01 preserves the exact wording and check time. The ledger does not conclude that the school failed or that the application is complete.
- Next action: prepare a narrow question asking whether the item was received and matched, citing S-01 and P-01 through the authority’s instructed channel. A personal reminder is recorded separately; no official deadline has been identified.
- If a reply arrives: append the exact answer and its scope. “Transcript received” closes the receipt question only; it does not close other requirements or record an approval.
A real example of channel specificity: California BRN’s consulted applicant page distinguishes transcripts submitted by California programs, programs in other U.S. states and programs in other countries. Check the current instructions for your own application; do not copy one board’s channel into every case.
Your finished record should answer three questions
- Which item and version does each event refer to?
- What does the evidence establish, and what is still unknown?
- What is the next document action and what evidence would close it?
The existing route workbook organizes route choices, source notes and renewals. Use this ledger for the event history after a document is prepared or requested. Keep full documents out of general email; follow the authority’s secure submission instructions.
Sources, dates and limits
Official guidance consulted November 4, 2026. This is a source consultation date, not verification of an individual license or every jurisdiction. The worksheet, event labels and examples are CompactRoute’s editorial organization, not forms prescribed by a regulator.
- HHS: Licensing across state lines → Last updated April 30, 2025. Supports the distinction between different cross-state routes and state-specific conditions; it does not approve your route or prescribe this worksheet.
- California BRN: Important Information for Applicants → No page-update date identified in the consulted text. Its transcript instructions illustrate why the issuing party and delivery channel matter. They apply to that board and application context, not all professions or jurisdictions.
Use the current instructions of the relevant regulator for your profession, route and facts. A saved page can become outdated. These records do not replace a license, registration, privilege, formal determination or other required authorization.