Airbnb Vendor Response: Write a Work Order That Ends with a Checked Repair.

By Sean Rakidzich.

Remote hosts often buy tools, hire cleaners, and message plumbers. Then they still cannot answer a simple question. Is this repair checked and done, or only claimed? The job is one work order at a time. Write the fields. Get acknowledgement. Record the work. Name who verifies. Keep reopen rules honest so a failed check does not. orphan the history.

This is not the water-leak alert playbook. A separate article covers the response flow. That flow runs from alert to occupancy to symptoms. Then to responder, access, vendor, work, and recheck. Here the subject is the document . How you write a single ticket. How you acknowledge it. How you complete it. How you verify it. How you reopen it. Leak response still needs a work order. This page tells you what that work order must contain. "Attended" must not pretend to mean "verified.".

Primary public facts on household leak awareness come from the. EPA WaterSense Fix a Leak Week page (accessed 2026-09-09). EPA is used for find, report, and fix culture. It is used for common leak locations. It is used for optional meter or dye checks as. identification aids for authorized persons. It is not used for STR bill savings. It is not used for guaranteed vendor response times. Editorial worksheets are operator process aids. Synthetic examples are labeled SYNTHETIC. One Reddit remote-host report is cited as anecdote only. It is not prevalence.

Core thesis. a work order is incomplete until the verification owner signs. a checked repair . A documented reopen completes a verification decision and leaves the. ticket active. Acknowledgement alone is not completion.

TL;DR: Fill eleven fields and verify before you call the ticket done.

Open one work order per asset problem. Fill eleven fields and keep them current. Asset and location. Symptom. Guest impact. Assignee. Agreed access. Approved scope and spend. Acknowledgement. Work performed. Completion record. Verification owner. Reopen condition.

Move status in plain steps. Use open. Use acknowledged. Use work done. Use verified. Or use reopened. Acknowledgement means the assignee accepted the ticket. They also accepted the access and scope terms. It is not a checked repair. Work done means work performed exists. A completion record also exists. It still waits for verification. Verified means the named verification owner confirmed the outcome. They checked it against the symptom and guest-impact fields. Reopened means the reopen condition was met. The same ticket lineage is active again. Reopen is not a close.

Do not invent universal vendor hours as industry law. Do not invent spend caps as industry law. Do not invent entry rights as industry law. Your market sets timing. Building rules set timing. Guest occupancy sets timing. Trade availability sets timing. Write your own access and spend terms on the ticket. Prefer qualified repair when the source is unclear. Use EPA Fix a Leak Week for early reporting. Use it for find-fix culture on moisture issues. Do not use it as an Airbnb SLA.

Cross-reference. Do not retell. When the symptom is a leak alert. Or when it is a wet cabinet. run your alert-response flow. Use it for occupancy, photos, and dispatch. Then park the outcome on this work order. The alert article is how you respond. This article is how you document.

Eleven fields that must stay filled.

Treat the work order as a single living document. It needs eleven required fields. Empty fields are not agile. Empty fields are how "vendor attended" becomes a false close.

1. Asset / location - which unit, room, and fixture or surface.
2. Symptom - what was observed, when, and by whom.
3. Guest impact - how the stay or next stay is affected. Operator labels. Not Airbnb categories.
4. Assignee - who owns the next action. Vendor, co-host, cleaner-as-eyes, or property contact.
5. Agreed access - who enters, how, when, with whose consent.
6. Approved scope / spend - what work is authorized. What money is authorized.
7. Acknowledgement - assignee confirms receipt of the ticket. Also confirm access and scope terms.
8. Work performed - what was actually done on site.
9. Completion record - invoice, photos, parts, time stamp. Vendor statement of work done.
10. Verification owner - named person who must confirm checked repair. Or document a reopen decision.
11. Reopen condition - what proof returns the same ticket to active work. Not a disconnected chat.

Status labels for the ticket itself should be few and. literal. Editorial status meanings (not platform rules).

• Open - fields 1 through 6 started. Work not yet acknowledged or not yet performed.
• Acknowledged - assignee accepted the ticket. Also accepted access and scope terms. Work not yet done.
• Work done - vendor or assignee recorded work performed. A completion record exists. Verification not yet signed.
• Verified - verification owner confirmed the checked repair. Match symptom and guest-impact fields. Lifecycle complete for this repair outcome.
• Reopened - reopen condition met. Ticket is active again with the same asset lineage. Lifecycle not complete.

Do not invent a sixth status called "vendor said done.". That phrase belongs inside the completion record as a claim. awaiting verification. Do not invent Airbnb statuses. If you use a PMS or spreadsheet. map these five meanings to whatever columns you already have. Keep the meanings intact.

Asset, symptom, and guest impact.

Start with where and what. Vague tickets produce wrong trades wrong access windows. and wrong closeouts.

Asset / location should name the listing or unit ID. you use internally. Name the room. Name the fixture or surface. Example shape. Unit 2B, kitchen, under-sink cabinet base, left supply side. If the building has shared risers you do not control. say so in the same field. If a mechanical closet is outside your control, say so. The assignee should not assume host authority over building valves.

Field examples that stay specific enough to act on:.

• Unit 4A, hall bath, vanity cabinet base, cold supply angle stop.
• Cottage B, exterior, hose bib at north wall, drip at connection.
• Unit 12, bedroom 2, closet bifold door latch, no moisture.
• Shared laundry closet (building). Pan under washer. Host does not control shutoff.

Symptom is observation language. Note wet versus dry now. Note active drip versus stain only. Note after which use (faucet, toilet, shower, unknown). Note odor if any. Attach photos. Note who first reported it and when. Prefer facts over guesses about pipe material.

For moisture issues. EPA Fix a Leak Week materials describe optional identification aids. One aid is a quiet-period meter check. Another is a toilet-tank dye check. Frame those as optional aids. An authorized local person or plumber may use them if. appropriate. They are not required host DIY. They are not steps this article teaches as repair. Prefer qualified repair language when the source is unclear. Prefer it when the issue is beyond simple observation.

Guest impact is an operator label so co-hosts share vocabulary. It is not an Airbnb guest-facing category. It is not a platform claim. Editorial labels you can reuse.

• None / vacant - unit empty. Impact is future-stay risk and finish damage.
• Comfort only - guest can stay. Inconvenience or noise possible.
• Partial amenity loss - a fixture or room is limited. Stay may continue with disclosure.
• Stay at risk - safety, sanitation, or major water intrusion. Relocation or early exit may be needed under your own policies.
• Next-guest blocking - current stay ends soon. Turnover or next check-in is blocked. Wait until verified dry or otherwise cleared.

Write guest impact in the ticket before you bargain over. spend. A comfort-only drip is one approval talk. A stay-at-risk active flood is another. Still. do not invent universal spend caps as industry rules. Do not invent entry authority as industry rules. Your approvals are yours.

Keep symptom and guest impact updated when new photos arrive. A ticket that still says "minor drip" while the cabinet. base is swollen is a lying document. Update the fields. Do not rely on chat memory alone.

Assignee, access, scope, and spend.

Assignee is the person accountable for the next action. It is not everyone who was CC'd. If a cleaner is only taking photos, say that. If a plumber is repairing, say that. If a co-host is coordinating both, say that. Split roles in the notes if needed. Keep one primary assignee so acknowledgement has a name.

Role splits that reduce fog:.

• Cleaner-as-eyes: photos, moisture touch test description, no repair tools.
• Property contact: building access or HOA notice only.
• Trade assignee: diagnose and repair inside approved scope.
• Co-host coordinator: owns the ticket fields and verification handoff. Not the wrench work.

Agreed access is a mini-contract inside the ticket. Use these minimum fields:.

• Who enters (name and role).
• Entry method (key, code, lockbox, guest opens door).
• Time window and time zone.
• Guest consent status if occupied (affirmed / declined / vacant N/A).
• Building or HOA notice if required.
• Purpose of this visit (observe / repair / verify).

Access notes that prevent bad visits:.

• Occupied stay: guest affirmed a 14:00 to 16:00 window. Use local time. Vendor texts on arrival. No cabinet demo without guest present. Unless guest opts out in writing on the ticket.
• Vacant turnover: lockbox code rotated after last guest. Code listed only in the access field. Not in a group chat that outlives the visit.
• Building limit: host cannot authorize riser shutoff. Building engineer contact listed. Visit purpose stays at unit fixture only until building approves.
• Verify-only visit: co-host enters with photo checklist. No parts purchase on this visit.

Access is not silent authority. This article does not invent a host right to enter. occupied units without agreement. It does not invent Airbnb emergency entry definitions. Multi-unit shutoffs may belong to a building contact you do. not control. Record that limit in the access notes. Do not instruct a cleaner to operate building water valves.

Approved scope / spend answers two questions before tools come. out. What work is authorized on this visit? What money is authorized without a further call? Write both answers on the ticket.

Scope language that stays honest:.

• Diagnose and repair under-sink supply leak. Replace supply line if failed. Stop and call if cabinet replacement needed.
• Observe and photograph only. No parts. Report findings to co-host before any repair visit.
• Replace toilet flapper if dye test by plumber confirms tank leak. Stop if wax ring or supply valve work is required.
• Repair bifold latch and align door. No paint. No hardware upgrade beyond latch kit under NTE.

Spend blanks you should fill with your own numbers. Not blog caps:

• Not-to-exceed labor and parts for this visit: ______.
• Trip fee acknowledged: yes / no / amount ______.
• After-hours premium approved: yes / no / amount ______.
• Change-order rule: stop work and call before exceeding NTE. Or before leaving approved fixture list.

Write your number. If the vendor finds work outside scope. keep the ticket acknowledged or open. Approve the change first. Do not let "while I was there" become an unapproved. close.

Cleaners as eyes versus vendors as repair. keep scope explicit. Leak spotting and photo upload can sit in a local. scope of work. Plumbing repair should not be drafted onto a cleaner by. remote chat. Electrical repair should not either. Prefer a competent tradesperson under local rules when the symptom. needs repair.

Acknowledgement is not completion.

Acknowledgement means the assignee confirms they received the ticket. They also accept the access and scope terms. That is a necessary handshake. It is not a checked repair.

Operators confuse three different events:.

• Message received ("got it").
• On-site presence ("I was there").
• Verified outcome ("cabinet dry on recheck; verification owner signed").

Only the third completes the repair-ticket lifecycle. The first two belong earlier. If your PMS marks tickets "done" when a vendor taps acknowledged. change your habit. Do this even if you cannot change the software. Keep an external verification checkbox. Or keep a second status column.

Require acknowledgement in writing inside the work order. Or paste a linked message back into the acknowledgement field. Include name. Include time stamp. Restate the access window. Restate scope and spend. If the assignee changes the window. update fields 5 and 6 before work starts. If they refuse part of the scope. update those fields too. Silent renegotiation is how you pay for a visit that. never matched the symptom.

Status transition examples (editorial, not platform rules):.

• Open to acknowledged: plumber pastes acceptance. Example quote: Accepted Unit 2B under-sink scope. NTE as written. Lockbox 10:00 to 12:00 local.
• Acknowledged stays acknowledged: plumber asks to expand to cabinet replacement. You have not approved yet. Do not mark work done.
• Acknowledged to work done: work performed field filled. Invoice and photos attached. Verification still pending.
• Work done to verified: verification owner signs checked repair. Match it against symptom and guest impact.
• Work done to reopened: verification fails or reopen condition met. Ticket active again. New acknowledgement required for return work.

SYNTHETIC example - incomplete work order (labeled SYNTHETIC. not a real property claim).

• Asset/location: SYNTHETIC Unit A, hall bath, vanity cabinet base.
• Symptom: guest photo of wet cabinet floor after sink use. Moisture sensor alert later cleared overnight.
• Guest impact: comfort only during stay. Next-guest blocking risk if still wet at turnover.
• Assignee: local plumber.
• Agreed access: vacant window 10:00 to 12:00 local; lockbox.
• Approved scope/spend: diagnose sink supply. Repair or replace supply line. NTE set by operator.
• Acknowledgement: plumber texts "confirmed, see you at 10".
• Work performed: plumber notes "tightened connection; wiped cabinet".
• Completion record: invoice paid; alert remains clear.
• Verification owner: blank.
• Reopen condition: blank.

In that SYNTHETIC case the ticket looks finished to a. busy remote host. Vendor attended. Alert cleared. Invoice paid. It is not finished. No verification owner confirmed a dry cabinet. Honest next status is still work done . It is not verified . If a cleaner later finds a damp base, reopen. Do not start a disconnected chat thread that forgets the. prior invoice.

Work performed, completion record, and verification.

Work performed is a factual description of what happened on. site. List parts replaced. List adjustments made. List tests run. Note areas left open or closed. Note whether water was present at arrival. Note whether water was present at departure. Prefer plain language. Do not accept "fixed" as the entire field.

Better work-performed lines:.

• Arrived wet at left supply nut. Replaced braided supply line. Dry wipe at departure. Ran faucet two minutes. No drip seen.
• Dye check in tank by plumber showed color in bowl. Replaced flapper. Second dye check clear. Bowl fill normal.
• No active drip on arrival. Swollen particle board at vanity base. Recommended cabinet base repair outside original scope. Stopped per NTE rule.

Completion record attaches proof artifacts. Attach the invoice or receipt. Attach before and after photos. Attach part numbers if available. Attach arrival and departure times. Attach the vendor's statement of what they believe is complete. This record is necessary. It is still insufficient alone. "Vendor said done" lives here as a claim.

Verification owner is a named person. Co-host, owner, trusted local eyes, or property contact. That person must confirm the checked repair against the original. symptom and guest-impact fields. For a wet vanity. verification means a later look that the cabinet is dry. and the symptom has not returned under normal use. It does not mean the sensor stayed quiet for an. hour. For a non-moisture ticket. Example: a broken cabinet door latch with no leak. verification means the stated symptom is resolved in person or. with clear photos from the verification owner. A vendor text alone is not enough.

Write the verification step into the ticket when you open it. not after the invoice. If nobody is named. you have already decided that acknowledgement will fake-close the job.

Checked repair sign-off (editorial checklist the verification owner completes):.

• Re-read symptom and guest-impact fields.
• Inspect or obtain current photos of the same location.
• Confirm whether the guest impact is cleared. Check the current stay. Or check the next stay.
• Mark verified only if the symptom is resolved.
• If the symptom is not resolved, document a reopen decision. Set status to reopened. Do not mark verified.
• Keep the completion record attached either way.

When the underlying issue is a household leak pattern. remember EPA's find-and-fix culture again. Report. Get qualified repair when needed. Do not treat a quiet notification as the end of. moisture risk. Meter or dye checks remain optional identification aids for authorized. persons. They are not a substitute for verification photos of the. damaged surface. They are not a reason to skip a plumber when. the source is unclear.

Reopen is a verification decision, not a close.

A reopen condition is written in advance so a failed. outcome does not become a new orphan chat. When the verification owner documents that the reopen condition is met. that completes a verification decision . It does not complete the repair-ticket lifecycle. Status becomes reopened . The work remains active.

Examples of honest reopen conditions:.

• Same location wet again within a stated observation window. This is after "work done".
• Verification owner finds symptom unchanged on first recheck.
• Guest or cleaner reports the same fixture failure. Photos match the asset field.
• Alert or sensor re-fires after a claimed repair. Visual check still shows moisture or active drip.

What to do when you reopen:.

• Keep the same work-order ID and history.
• Update symptom and guest impact with the new evidence.
• Revise scope and spend. Do this if the return visit needs a different authorization.
• Require a new acknowledgement for the return visit.
• Keep the prior completion record attached. Failed repairs are part of the truth.
• Leave status at reopened. Or move back through acknowledged and work done. Wait for a later signed check.

What reopen is not. quietly muting a sensor. paying a second vendor without linking tickets. or blaming the cleaner for a plumbing failure without updating. the document. Reopen is also not a clever way to mark the. lifecycle complete. Only verified completes the lifecycle for that repair outcome.

ANECDOTE ONLY. Not prevalence. Not causal proof. See a public r/airbnb_hosts thread. A remote host lives in Los Angeles. That host runs a property in Mexico. That host said they fired a prior local assistant. The trigger was a missed broken cabinet. And a leaking sink. There were also lukewarm cleanliness reviews. Use that as one staffing story. It shows why local eyes must report damage into a ticket. Do not treat it as a rate of cleaner failure. Do not treat it as proof that cleaners cause leaks. Do not treat it as invented dialogue. This article invents no quotes from that thread.

Work-order worksheets and status tables.

Copy these static tables into your notes doc or print. them. No scripts or forms, just fields. Label real tickets with real unit IDs. Keep SYNTHETIC examples labeled when you train a co-host.

Blank work-order field worksheet.

Status meanings.

Guest-impact levels (operator labels, not Airbnb).

Access agreement fields.

Verification checklist (print or paste).

Training tip. walk a co-host through the SYNTHETIC incomplete ticket above. Ask them to fill verification owner and reopen condition before. marking anything verified. If they mark verified from the invoice alone. the worksheet failed and the habit needs another pass. If they mark the ticket closed because they documented a reopen. correct that habit too. Reopen means active work.