The 14-Day and 30-Day Clocks
A guide to the timing provisions in Airbnb's Host Damage Protection Terms, with the full term language and practical record-organization notes.
The anchor, stated in full
Airbnb Host Damage Protection Terms, article 2869, checked July 31, 2026, when the live page displayed "Last updated: August 1, 2026" (the operative 14-day and 30-day provisions quoted here matched the text visible on that check). Within 14 days of the Responsible Guest's checkout: best efforts to recover from the guest AND notify Airbnb of the complaint. Within 30 days of checkout: the Host Damage Protection Payment Request Form with Legitimate and Verifiable Evidence (article 2869).
That wording governs every window referred to in this article. Each other window quoted below is a separately published platform statement read against it, not a substitute for it.
The 14-day leg has two parts, not one
Section 3.1 opens by stating that "before we can consider an HDP Request, you must demonstrate that you have" met the conditions that follow, and 3.1.1 requires that the host has "pursued the rights and remedies you have against the Responsible Guest and/or Invitee" (article 2869 §§3.1, 3.1.1).
Section 3.1.2 is the timed condition, and it is compound. Within fourteen days of the Responsible Guest's checkout date the host must have "used your best efforts to recover the amount requested from the Responsible Guest," including "explaining why the Responsible Guest is responsible" and "requesting that the Responsible Guest reimburse you," and must have "notified us of your complaint against the Responsible Guest" (article 2869 §3.1.2). Read the last clause carefully. Best efforts toward the guest is one obligation. Notifying Airbnb is a second obligation inside the same window, and collapsing the leg into "message the guest" drops half of it.
Section 3.1.3 offers a consolidation route, stating that both conditions "may" be satisfied by a Resolution Center reimbursement request, "provided that your reimbursement request fulfills all of the obligations set out in Sections 3.1.1 and 3.1.2" (article 2869 §3.1.3). The proviso is the operative part: one action satisfies both only if it contains both.
The 30-day leg is about the form and the evidence
Section 3.3 states that "within thirty (30) days of the Responsible Guest's checkout date you must," then splits in two. Section 3.3.1 requires the host to "complete and file a Host Damage Protection Payment Request Form via the Resolution Center." Section 3.3.2 requires Legitimate and Verifiable Evidence "supporting the existence, extent, and amount of the Eligible Loss" (article 2869 §§3.3, 3.3.1, 3.3.2).
Legitimate and Verifiable Evidence is a defined term, not a mood. Section 3.3.3 defines it to mean that "the documents and information you provide must be true and accurate and not be doctored or falsified in any way, including by the use of artificial intelligence," and where verification fails after reasonable efforts it allows a request for additional documentation, possibly from an independent third party, a request for a different capture format, or denial of the request altogether (article 2869 §3.3.3).
Both clocks start at checkout, not at discovery
This is the most consequential detail. Both periods are measured from the Responsible Guest's checkout date, not from the moment damage is found (article 2869 §§3.1.2, 3.3). A cleaner who reports a problem four days later has not reset anything.
Where the help pages read differently
Airbnb's own pages do not all say the same thing.
The host help article says to file a reimbursement request "within 14 days of the responsible guest's checkout," and separately says that involving Airbnb Support means submitting supporting documentation "within 14 days of the damage or loss," which measures from the damage rather than from checkout (article 279). The Resolution Center adds its own outer limit: "you have up to 60 days after your reservation's checkout date" to submit a request (article 767).
Rather than guess which page controls, use what the terms say about versioning: payment requests are handled "in accordance with the version of the Host Damage Protection Terms that is in force on the date we receive the Host Damage Protection Payment Request Form" (article 2869 §10.2). The governing wording remains: Airbnb Host Damage Protection Terms, article 2869, checked July 31, 2026, when the live page displayed "Last updated: August 1, 2026" (the operative 14-day and 30-day provisions quoted here matched the text visible on that check). Within 14 days of the Responsible Guest's checkout: best efforts to recover from the guest AND notify Airbnb of the complaint. Within 30 days of checkout: the Host Damage Protection Payment Request Form with Legitimate and Verifiable Evidence (article 2869 §§3.1.2, 3.3). Confirm current requirements on the published terms.
The guest-side sub-clock
A smaller timer sits inside the first leg. A host "can send you a reimbursement request in our Resolution Center to cover the cost of the damage, and you'll have 24 hours to respond" (article 1415).
If the guest declines, pays partially, or lets the 24 hours lapse, the host "will be able to submit a reimbursement request under Host damage protection" (article 279).
What is not published
Internal review criteria, decision rates, and turnaround times beyond the factors listed in Section 4.2 are not published in the pages reviewed, so any figure of that kind is [U] (article 2869 §4.2). A third-party blog asserts an April 20, 2026 policy update introducing an AI-evidence ban; that language does exist at Section 3.3.3, but the official page's revision stamp (February 5, 2026 at first check; August 1, 2026 as of a July 31, 2026 re-check) has never shown an April date, so the April dating is ANECDOTAL (TabiVista blog, third party, article 2869).
Calendaring both clocks
Two dates, one origin. When a reservation closes, put both target dates on the stay record, and keep the condition records, inventory, and invoices attached to that same record so the second window is spent checking a set rather than building one.
StayTurn is a $39 one-time purchase that keeps each stay's turn prep, cleaner handoff, photos, receipts, notes, and costs together in one dated record you own, on your device. Your photos and files stay on your device unless you choose to send them.
StayTurn organizes evidence for export. It does not submit claims, does not give claims-handling advice, and no documentation practice determines any outcome.
StayTurn is an independent tool, not affiliated with, endorsed by, or sponsored by Airbnb or Vrbo.
Source. Airbnb Host Damage Protection Terms, article 2869. Live page checked July 31, 2026. The page displayed "Last updated: August 1, 2026." The quoted sections in this article were compared with the text displayed during that check. Platform terms can change, so operators should verify the current source directly (article 2869).
---