Vendor Coordination
Key takeaways
- Check the guest calendar before offering a contractor a visit window.
- Separate the repair approval from the visit scheduling decision.
- Give the contractor one access path and one named contact.
- Record the visit against the property so the next request starts with context.
Operating data
Playbook
Why a contractor visit needs a calendar check
A contractor visit looks like a simple appointment until it collides with a guest's nap, a work call, or a late checkout. The property manager wants the repair finished, the guest expects quiet access to the unit, and the coordinator is caught between two schedules that were never compared. A short screening step before the visit is promised prevents most of these collisions. It also gives the contractor a realistic window instead of a hopeful estimate.
The cost of skipping the check is rarely the repair itself. It is the complaint, the rescheduled visit, and the second trip fee that follow a knock at the wrong hour. A guest who booked a quiet weekend does not care that the work order was urgent to the owner. The coordinator has to hold both facts at once and choose a window that respects the stay.
Collect the guest and contractor constraints
Start with the reservation record and confirm the arrival, departure, and any approved late checkout. Note the hours when the guest is likely to be present, and ask whether a nap, a call, or a medical need makes a daytime visit difficult. Record the answer in the property file rather than leaving it in a message thread. The guest should not have to repeat the same constraint to a second coordinator.
Then collect the contractor's real availability and the access the job requires. Some repairs need the unit empty, while others only need a closet or an exterior panel. Ask how long the visit will take and whether the contractor can work around a guest. A vendor who says the job is quick may still need the water shut off for an hour.
Choose a visit window the property can keep
Offer one primary window and one fallback window instead of a broad range that hides the risk. The primary window should sit inside the guest's stated tolerance and the contractor's route. The fallback should be a real option, not a vague promise to come later. A narrow window that both sides accept is better than a wide one that nobody trusts.
If the repair is urgent, decide whether the guest can be moved or whether the work can wait for checkout. That is a property manager decision, not a coordinator guess. Write the decision and its reason into the work order so the field team understands why a visit is happening at an odd time. The guest should hear the same reasoning in plain language.
Decide who speaks to the contractor
Name one coordinator who will confirm the visit, share the access details, and receive the completion note. The contractor should not have to call three numbers to learn which door to use. Give that coordinator the authority to pause the visit if the guest reports a problem, and state the limit of that authority. A single contact reduces confusion without hiding the manager's role.
The guest also needs one contact path for questions about the visit. Put the coordinator's name and hours in the arrival message and in the work order. If the property has a smart lock, confirm that the contractor's code works only for the scheduled window. Remove or expire the code after the visit and record that it was removed.
Handle a visit that has to move
When the guest asks to move a visit, check the contractor's next available slot before replying. Do not cancel the original window until the replacement is confirmed, because a cancelled visit can turn a small repair into an emergency. If the move creates a fee, route the decision to the property manager. The coordinator can explain the constraint, but should not absorb a cost the owner has not approved.
If the contractor cancels, tell the guest what changes and what does not. A repair that was cosmetic can wait, while a failed water heater cannot. Update the work order with the new date and the reason for the change. A record that only shows the final date hides the disruption and makes the next review less useful.
Work through two visits
A guest reports a slow bathroom drain on the second morning of a five-night stay. The contractor can arrive that afternoon, but the guest has a work call from one to three. The coordinator offers four o'clock and confirms the guest will be out for dinner. The contractor completes the repair, sends a photo of the cleared drain, and the coordinator records the visit against the reservation.
In a second case, the owner approves a new refrigerator, and the delivery team can only install it on the morning of a same-day turnover. The coordinator checks the cleaner's schedule and finds the unit will be occupied until eleven. The delivery is moved to the next day, and the listing is not changed until the new appliance is actually in place. The delay is visible to the owner and no guest is surprised.
Record the visit against the property
Close the visit with three facts: who arrived, what was done, and what the guest was told. Attach the contractor's completion note or photo to the work order, not to a personal message. If the repair changed an amenity or an instruction, flag the listing and the house guide for review. The next coordinator should be able to see the change without reading the whole thread.
Review the visit record at the end of the week and look for patterns. Repeated access problems may mean the instructions are unclear, while repeated guest complaints may mean the screening step is too late. Pick one change and assign it to a named person. A small adjustment to the intake question often prevents more disruption than another reminder to the contractor.
Related services
- Reservation coordination - Contact us
Sources
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
