The 18 Property Management System (PMS) Settings Every Co-Host Must Configure
Most co-hosts already have a Property Management System (PMS). It may connect listings, sync calendars, send messages, or show a unified inbox.
That does not mean it is doing the work it could be doing for you.
An underconfigured PMS quietly creates a familiar kind of business: you are still checking calendars manually, reminding cleaners, rebuilding the same guest messages, catching gaps late, and carrying too many important details in your head. The software is there, but the operation still depends on memory.
This guide is a practical configuration checklist. It is not about choosing a new PMS or learning every button in one. It is about making sure your current system is configured around the way you co-host, so every reservation has a better chance to earn, run smoothly, and teach you something useful.
What getting the most from your PMS actually means
A well-configured PMS should help you:
Protect higher-value booking opportunities before weaker stays break them up.
Keep availability, pricing inputs, and stay rules intentional.
Turn every confirmed reservation into a coordinated plan for the guest and local team.
Reduce repeat admin without turning hospitality into generic automation.
Capture what guests and team members keep telling you, so the next stay runs better.
Add properties without simply adding the same amount of manual work.
Start with your operating playbook
Your PMS should not be configured around a generic template. Define these rules first:
Revenue goals and pricing strategy.
High-value dates, gaps, and stay rules.
Guest-message voice and hospitality style.
Property details and arrival standards.
Cleaner, vendor, and local-team workflows.
Comfort settings and smart-property rules.
Escalations, approvals, and final decisions.
That playbook is what makes automation feel like your operation rather than somebody else’s sequence of reminders.
Part 1: Protect booking opportunity
1. One calendar across every channel
Configure: A clear source of truth for availability across Airbnb, Vrbo, direct bookings, and any other channel you use.
Why it matters: A co-host should be able to answer “is this date bookable?” without comparing multiple calendars or hoping an iCal sync catches up.
Check: Are blocks, reservations, cancellations, and changes appearing where they need to appear? Does your team know which calendar is the authority when something conflicts?
2. Calendar and pricing optimization
Configure: The connection between your calendar rules, pricing approach, booking pace, and occupancy goals.
Why it matters: Pricing is not just a nightly number. A calendar strategy also considers minimum stays, booking windows, lead time, and the shape of the open calendar.
Check: Does someone review pricing and stay rules together, or are rates being changed without considering the calendar they are trying to fill?
3. Protect valuable nights
Configure: Rules that preserve high-demand dates and valuable run lengths before allowing a lower-value reservation to split them.
Why it matters: A mid-weekend arrival, an awkward one-night booking, or an untimely checkout can turn a stronger booking opportunity into two weaker ones.
Check: Have you identified dates, seasons, or stay patterns that deserve protection? Are those rules reflected in the PMS rather than remembered only when an inquiry arrives?
4. Open small gaps intentionally
Configure: Gap-night and minimum-stay rules that make short openings bookable when they are genuinely hard to fill.
Why it matters: A small orphan gap can become a booking opportunity instead of a date that quietly expires unused.
Check: When a cancellation creates a short opening, does your system have a rule for it? Is that rule temporary and strategic, rather than a permanent discount on every date?
5. Timely inquiry-response rules
Configure: Property-specific initial responses, question replies, and escalation paths for inquiries.
Why it matters: Guests are usually considering more than one place. A fast, helpful first response keeps interest moving while the guest is engaged.
Check: Is the response useful for this property, or does it read like a generic acknowledgment? Does the system know when to route a real question to you or the local team?
6. Booking confirmation as an operational trigger
Configure: A confirmed reservation should create more than a calendar event. It should trigger the information, timing, and tasks that prepare the stay.
Why it matters: If a booking confirmation only sends a receipt, you are leaving the operational value of the PMS unused.
Check: Can you trace what starts automatically when a reservation is confirmed? If the answer is “someone remembers what to do next,” this setting needs work.
Part 2: Prepare a guest-ready stay
7. Booking confirmation starts the guest-ready workflow
Configure: The confirmed reservation should begin the guest-preparation sequence, using the exact dates, guest details, property rules, and local-team context for that stay.
Why it matters: The booking is the handoff between revenue opportunity and operations. Without this trigger, the next six steps become a manual reconstruction job.
Check: Does the confirmed stay create a visible arrival plan, or does someone still need to open the booking and tell each person what happens next?
8. Cleaner and task scheduling
Configure: A booking should schedule the right cleaner, inspection, maintenance, or team task with the correct property details and time window.
Why it matters: Turnovers fail when the person doing the work learns about the stay too late or has to chase the current calendar.
Check: Do cleaners receive the right date, task list, and completion window? Do reservation changes reach them without a manual text-message relay?
9. A check-in guide sent two days before arrival
Configure: A clear, property-specific check-in guide that goes out before travel day.
Why it matters: Good instructions prevent avoidable questions about parking, doors, gates, stairs, Wi-Fi, or what to expect on arrival.
Check: Is the guide visual where it needs to be? Has it been updated after the last recurring guest question?
10. Unique access codes
Configure: Reservation-bound access codes and their timing for smart locks or access systems.
Why it matters: Access should be convenient for the guest and easy for the co-host to monitor, without sending people through old message threads to find a code.
Check: Are codes timed to the stay? Is there an operational backup for a lock problem, an early arrival request, or a team member who needs access?
11. Guest-ready comfort settings
Configure: Smart-thermostat or comfort rules that prepare the property before the guest arrives and return it to an efficient setting after departure.
Why it matters: In a hot market, a cool arrival is part of hospitality. Between stays, an eco setting can reduce unnecessary A/C use and wear.
Check: Are timing and temperatures specific to your property, climate, and guest experience? Are they timed to actual check-in and checkout rules?
12. Arrival alert
Configure: An alert when the guest first uses the access code or otherwise arrives.
Why it matters: It lets you know the guest made it in and gives you an early opportunity to handle an access issue before it becomes a bad first impression.
Check: Who receives the alert? What should happen if the guest has not arrived by a relevant point, or if a lock reports a low battery or access failure?
Part 3: Care, learn, and improve
13. Morning courtesy note
Configure: A warm, property-specific morning-after-arrival message.
Why it matters: It makes guests feel looked after and gives them a low-friction moment to flag something before a small problem becomes a larger one.
Check: Does the note sound like your hospitality style? Does it tell the guest how to reach the right person if there is an issue?
14. Twenty-four-hour turnover reminder
Configure: A pre-checkout reminder for the cleaning or local team, based on the turnover window you set.
Why it matters: The reminder protects against missed handoffs, especially when bookings change, back-to-back stays stack up, or the team is busy.
Check: Is the reminder going to the person responsible for the turnover? Does it include the information needed to complete the work?
15. Checkout instructions
Configure: A checkout message that arrives at the right time and makes the last morning clear.
Why it matters: Good checkout instructions reduce confusion, help the local team, and end the stay with the same clarity as the arrival.
Check: Are checkout time, lock-up steps, trash, parking, special property considerations, and departure expectations current?
16. Checkout and eco setting
Configure: The return to your between-stay comfort setting after checkout.
Why it matters: It closes the guest-ready routine and keeps an empty property from operating as though someone is still inside.
Check: Does the setting account for your climate, humidity, property condition, and the timing of the next turnover or arrival?
17. Post-stay thank-you and review routine
Configure: A thoughtful thank-you message and review workflow that reflects your actual hospitality standards.
Why it matters: A stay does not end at checkout. A considered closing message can reinforce the guest experience and make a review feel like a natural next step.
Check: Can you pause or change the workflow when a guest had an unresolved issue? Is the wording personal enough to sound like your brand?
18. Day-14 review and next-stay improvement routine
Configure: A review timing and operating-review rhythm that turns feedback, questions, and exceptions into an action list.
Why it matters: The best PMS setup gets better over time. Repeated questions can improve the guide. Praise can improve the listing. A recurring turnover issue can improve the workflow.
Check: Who looks at the patterns? Where are improvement decisions recorded? What changes after you identify a repeat problem or opportunity?
Your 18-setting PMS self-audit
Mark each item as one of the following:
Configured and working — it runs reliably and reflects how you operate.
Configured, but inconsistent — it works only when somebody notices or remembers.
Missing — it is manual, unclear, or not happening at all.
The goal is not to make everything automatic. Keep hospitality, approvals, owner decisions, unusual guest needs, maintenance judgment, and recovery in human hands. Systematize the repeatable information, timing, and handoffs that do not need to depend on memory.
A configured PMS gives you room to grow
The practical payoff is not “more automation.” It is more capacity.
When reservations consistently create the right next steps, you spend less time reconstructing the stay and more time on the work that needs a co-host: owners, guests, local relationships, decisions, and exceptions. That is what makes it possible to take on another property without simply adding another full layer of admin.
Need a second set of eyes on your PMS setup?
If this checklist exposed a few gaps, that is useful. You do not necessarily need new software. You may need your existing PMS configured around the way you actually co-host.
Host Sidecar helps co-hosts turn a PMS into a working operating system: booking strategy, messages, turnovers, access, team handoffs, and ongoing improvement. Focused setup help is often more accessible than people expect, and the upside of getting the routine work right can be significant.