Local Occupancy Tax Notice Routing for Short-Term Rentals

Methodology

1. Research question: whether a notice is tied to the correct property, entity, filing period, platform collection path, and accountable tax decision owner. The observation unit is one received tax notice or portal alert from intake through verified ownership, response, correction, and closure. Freeze property, reservation, system, local time, policy or configuration version, source identifiers, guest state, responder state, and owner map before classification under STR-R-2-1.
2. Population design for local occupancy-tax notice routing: include ordinary, incomplete, conflicting, corrected, reversed, unavailable-system, accessibility-relevant, urgent, and unresolved records. Record exclusions and missingness rather than recoding unknown cases as success or failure.
3. Source hierarchy for local occupancy-tax notice routing: distinguish guest or third-party statements, platform and device events, property instructions, building or authority notices, onsite observations, qualified findings, manager decisions, and commercial dispositions. Each artifact receives an owner, version, retrieval time, and direct claim boundary.
4. Adverse controls for local occupancy-tax notice routing: test wrong-property identity, stale policy, superseded instruction, duplicate event, unexpected sensitive data, timezone boundary, failed responder acknowledgement, guest who cannot use the ordinary path, and source change after the first decision. Predict the expected stop state before running each control.
5. Analysis plan for local occupancy-tax notice routing: report numerators with denominators, observation window, property and channel mix, exclusions, correction rate, unresolved cases, and consequence class. Read representative records beside aggregates, and treat configuration, season, occupancy, vendor coverage, policy changes, and missing artifacts as alternative explanations.
6. Field coding for local occupancy-tax notice routing: compare the first recorded state, every later correction, the evidence available at each decision point, and the final verified endpoint for one received tax notice or portal alert from intake through verified ownership, response, correction, and closure. Code whether each transition was directly observed, reported by a named source, inferred, or authorized by property owner, tax professional, platform owner, and authorized filing contact. Do not combine unavailable evidence with a negative finding. Preserve the original timezone and version alongside normalized values so reviewers can reconstruct boundary cases without silently changing what the record meant when the decision was made.
7. Falsification and consequence review for local occupancy-tax notice routing: actively search for a second property, reservation, device, notice, policy, or account that could explain an apparent match. Test whether the same outcome would have been recorded if the guest never replied, a vendor acknowledgement arrived late, an operator corrected the source, or the authorized owner rejected the proposed action. Classify consequences separately for guest access, safety, privacy, money, platform standing, property readiness, and future arrivals; one successful dimension cannot erase a failure in another.
8. Missingness protocol for local occupancy-tax notice routing: freeze the expected evidence list before retrieval and report present, absent, inaccessible, superseded, contradictory, and not-applicable counts separately. For one received tax notice or portal alert from intake through verified ownership, response, correction, and closure, do not replace a missing high-consequence record with an easier case or infer a favorable outcome from silence. Compare missingness by property, channel, local time, vendor, owner role, and case outcome. Escalate concentrated gaps to property owner, tax professional, platform owner, and authorized filing contact, because the pattern may reflect broken logging, permissions, retention, or process ownership rather than operator performance.
9. Pilot and replication for local occupancy-tax notice routing: select a declared property cohort and observation window, retain the query or export version, and give a second reviewer only the approved evidence packet and definitions. Ask that reviewer to reproduce the chronology, classifications, denominators, stop condition, owner question, authorized action, and verified endpoint for one received tax notice or portal alert from intake through verified ownership, response, correction, and closure. Record disagreements before adjudication. Dependence on memory, private messages, unrestricted credentials, or unstated local knowledge is a study defect and a reason to pause expansion, not a shortcut to agreement.
10. Tax-notice coding separates jurisdiction, issuing office, taxpayer entity, parcel or lodging account, license number, filing period, assessment type, response deadline, delivery channel, platform-collection indicator, and claimed balance. Reviewers retain the envelope, portal header, attachments, payment history, return receipt, registration record, prior correspondence, and any amended notice. They do not infer that a marketplace remitted every obligation merely because a guest receipt shows a tax line. The routing decision distinguishes informational mail, registration renewal, missing return, estimated assessment, penalty, audit inquiry, lien warning, and identity mismatch before assigning the matter to bookkeeping, an authorized filer, counsel, or the property owner.
11. The notice sample spans city, county, state, tourism-district, and special-assessment correspondence; zero-dollar filings; mixed personal and rental use; management transitions; entity conversions; platform-collected and owner-collected stays; amended returns; duplicate accounts; and notices arriving after a property sale. Reviewers compare the service address with the situs, legal entity, platform reports, general ledger, reservation export, and filing calendar without calculating tax or interpreting local law. Measures include days remaining at intake, identity-match rate, acknowledgement by the authorized recipient, unresolved document gaps, duplicate-notice frequency, and closure evidence from the issuing authority rather than an internal task marked complete.
12. Independent review: a second reviewer reconstructs a stratified local occupancy-tax notice routing subset from retained materials and written definitions. Preserve disagreements by field and reason. After an authorized action, verify the correct guest, property, system, credential, communication, and future-arrival state rather than trusting a completed label.
13. Authority boundary: remote support may preserve, compare, route, communicate approved facts, and track acknowledgements. property owner, tax professional, platform owner, and authorized filing contact retain consequential decisions. Urgency changes routing and update frequency, but does not create safety, legal, accessibility, privacy, technical, or commercial authority.
14. Limitations: for local occupancy-tax notice routing, public sources guide planning, records, privacy, security, access, communication, and safety concepts; they do not inspect a property, interpret every jurisdiction, certify a provider, establish a performance benchmark, or prove causation. Refresh this study after a relevant system, platform, property, owner, policy, vendor, or local-rule change.