Who is scheduled to check out soon? How to see due‑outs fast and plan turnovers with confidence
Guests scheduled to check out soon are your “due‑outs” or departures—people slated to leave today or within your selected window. Most PMS dashboards and reports label them as Due Out or Departures so you can plan housekeeping and settle folios before rooms are resold (Pearson front‑office text; UniFocus GUESTS screen; Cloudbeds Departures Report).
What does “due‑out” actually mean?
In hotel and PMS terminology, a “due‑out” guest is someone scheduled to depart at the end of their booked stay—commonly the current day—unless they extend (Pearson front‑office text; OPERA Due‑Outs guidance). Most systems surface them as a status on the in‑house list or a Departures/Due‑Out report so front office and housekeeping can coordinate.
Checkout time conventions vary by brand and platform, but two patterns come up repeatedly in public guidance:
- Airbnb’s default if a host does not set times is 3:00 p.m. check‑in and 11:00 a.m. checkout (Airbnb help).
- Training and industry texts often cite 10:00 or 11:00 a.m. as standard ranges, with noon also seen in some brands (training workbook examples; brand standards examples). One scrape‑based blog analysis reported 11:00 a.m. as the single most common checkout across a large hotel sample; methodologies vary, so treat that as indicative rather than definitive (StayAPI analysis).
The takeaway: “Due‑out” is a status, not an exact minute. Your PMS defines the guest as due‑out on the set date; your published checkout time shapes when the room turns.
Where do I see who’s scheduled to check out soon?
Different systems present the list in familiar places:
- A Departures or Due‑Out report filtered to today or a date range (Cloudbeds Departures Report).
- A GUESTS/Stay status page with a “Due out” filter (UniFocus console).
- An in‑house list that flags “Due‑Outs Not Checked Out” to catch potential overstays (OPERA guidance).
If you operate short‑term, mid‑term, and long‑term rentals, the same principle applies: pull a departures view for each line of business and combine it into a single turnover plan. For short‑term rentals, pair the due‑out list with your cleaners’ assignments so rooms that can be resold are cleaned first—housekeeping check‑out priorities are a classic best practice to avoid lost revenue (housekeeping planning reference).
For mixed portfolios, you can also centralize this view in tools that coordinate STR/MTR/LTR in one account.
What should be on my daily departures checklist?
Use a consistent, short routine each morning and a pre‑audit at end of day to avoid surprises. The night‑audit step of verifying scheduled departures and posting charges is a long‑standing control (night audit procedures).
- Confirm today’s due‑outs, notes, holds, and any late checkout requests (Airbnb encourages reasonable checkout steps and automated reminders to guests; align your list with that tone, not chore lists that create friction—see Airbnb’s “clear and simple checkout” guidance: host resource).
- Pre‑assign priority cleaning for check‑outs first so arrivals aren’t delayed (housekeeping planning reference).
- Identify folios with balances and payment method on file when your PMS provides it (many systems expose this in Departures/Due‑Out reports; see examples like Visual Matrix report index).
- Note potential extensions and communicate cutoffs.
- If you use channel managers or booking platforms, verify that changes are reflected into your PMS view before you dispatch cleaners.
How do checkout times affect staffing?
Published checkout times define when rooms are likely to be empty, but they’re not guarantees. Common settings land around 10:00–11:00 a.m. with many platforms and brands using 11:00 a.m. as a baseline (Airbnb default 11:00 a.m.; training text ranges). One scrape analysis found 11:00 a.m. the single most common time across thousands of hotels (StayAPI analysis). Because local policies and brand standards vary—some brand documents set “no earlier than 11:00 a.m.”—calibrate cleaner start times and buffer windows to your own portfolio (brand standards example).
What tools can I use to track due‑outs and turn them into work?
Here is a simple comparison of common ways operators assemble the “who’s leaving soon” picture and act on it.
| Option | Where you’ll find the list | What it’s best for | Watch‑outs |
|---|---|---|---|
| PMS Departures/Due‑Out report | Reports or Front Desk module with filters like “Departures today/this week” (e.g., Cloudbeds Departures Report; UniFocus status filter) | Fast daily snapshot for staffing, folio close‑out | Overstays/extensions can change after print—refresh before dispatch |
| In‑house list with Due‑Out status | Live “Due Out”/“Departures” column and “not checked out” flags (OPERA example) | Real‑time exceptions—catch late departures, extensions | Needs tight front‑desk habits to update status quickly |
| Housekeeping app/room status board | Color‑coded “dirty checkout” vs “stayover” priorities (housekeeping planning reference) | Cleaning order and turnover readiness | Only as accurate as your due‑out list and inspector updates |
| Calendar/Gantt by unit | Visual gaps for turnovers across STR/MTR/LTR | Weekly forecasting and supply planning | Easy to miss folio tasks and notes without a departures report |
| Manual spreadsheet | Roll‑up across multiple systems | Temporary bridge when systems don’t integrate | Prone to stale data; double‑entry risk |
If you consolidate STR, MTR, and LTR work in one place, review solutions that coordinate departures, guest messaging across channels, cleaner dispatch, and owner statements. For an example of a unified approach, see pages like AI guest messaging software and Airbnb cleaning & turnover software. Rentology is property‑management software for short‑term, mid‑term, and long‑term rentals in one account and it connects to OwnerRez, Hospitable, and Beds24 for bookings and guest messages per its documentation.
How should I handle late checkouts and extensions?
- Late checkout requests: On platforms like Airbnb, guests can request a later checkout time; hosts may allow it and may charge extra, but policies vary by host and market (Airbnb help). Decide in advance what you’ll allow on sold nights versus vacant nights, and communicate clearly in the reservation thread.
- Extensions: If a due‑out asks to extend, update the stay in your PMS and remove the unit from the day’s turnover queue. Systems that retain “Due‑Out Not Checked Out” flags help you spot where the record wasn’t updated even though the guest stayed longer (OPERA guidance).
- Overstays: During your audit, verify scheduled departures and post charges correctly to avoid unintentional no‑post or incorrect room/tax after the planned date (night audit procedures).
How do I turn due‑outs into clean, ready homes faster?
- Lock in a housekeeping priority: “Check‑outs first” is the classic rule so new arrivals aren’t delayed (housekeeping planning reference).
- Send clear, minimal checkout steps: Airbnb’s current host guidance emphasizes clear and reasonable checkout instructions and automated reminders rather than long chore lists (Airbnb checkout guidance). Align your message templates accordingly.
- Close the loop with codes and inspectors: If you use smart locks, combine auto‑revocation with cleaner/vendor codes and photo checklists so status flips to “ready” as soon as inspection is done.
- Use AI/message routing where appropriate: An assistant that triages “running late” or “can I leave my bags?” frees humans to coordinate cleaners. For an example of this kind of workflow in a multi‑rental‑type platform, see AI property management software.
What goes wrong in practice
- Stale lists: Someone exports the departures report at 7 a.m., a guest extends at 9 a.m., and a cleaner drives to a room that won’t turn. Refresh before dispatch.
- Unclear checkout time: A listing or lease mentions one time, an auto‑message another. Guests leave later because the message they saw last wins. Standardize and audit templates.
- Overstay blind spots: A guest hasn’t checked out in the system, but the folio still posts as if they left. Night audit catches it, but housekeeping already cleaned around luggage. Train on status changes and use “Due‑Out Not Checked Out” flags where available (OPERA guidance).
- Chore‑list friction: Excessive checkout asks lead to pushback and later departures. Current platform guidance stresses reasonable steps and automated reminders (Airbnb checkout guidance).
- Cross‑system drift: Channel calendar shows a late checkout add‑on; the PMS doesn’t. Reconcile changes at handoff times (morning dispatch, pre‑audit).
How do I set up a simple due‑out workflow that scales?
- Standardize your times and templates
- Publish a consistent checkout time across listings/leases and auto‑messages. If you host on Airbnb and do not set times, its default is 3:00 p.m. check‑in and 11:00 a.m. checkout (Airbnb help). If you choose different times, reflect them everywhere.
- Make the departures report your single source of truth
- Use the PMS Departures/Due‑Out report as the authoritative list each morning, then refresh it before cleaners leave. Where your system provides balances and payment methods on that report, work those first (Visual Matrix report examples; Cloudbeds Departures Report).
- Tie housekeeping to due‑outs, not just to the calendar
- Prioritize check‑outs so you can resell or welcome arrivals on time (housekeeping planning reference). Use photo checklists and “dirty checkout/ready” codes to avoid ambiguity.
- Add exception handling for late departures and extensions
- Keep a live “Due‑Out Not Checked Out” view where your PMS offers it (OPERA guidance). Staff should know who can approve extensions and how to update the record immediately.
- Close the loop in your audit
- Verify scheduled departures and post final charges during the night audit to prevent mis‑posting after the planned date (night audit procedures).
If you want to coordinate STR, MTR, and LTR departures, guest communications, and cleaner assignments under one roof, review options purpose‑built for multi‑rental‑type portfolios; for example, see software for small Airbnb management companies. Rentology is one such platform and, per its documentation, is built for operators managing short‑term, mid‑term, and long‑term rentals in one account.
Do sources agree on exact checkout times?
Not entirely. Training materials often cite 10:00 or 11:00 a.m. as common, some brand standards state policies like “no earlier than 11:00 a.m.,” and one scrape across thousands of hotels reported 11:00 a.m. as most common (training workbook example; brand standards example; StayAPI analysis). Airbnb’s default for hosts who do not set times is 11:00 a.m. (Airbnb help). Because policies differ by property and channel, treat the due‑out date as the trigger, and use your published local checkout time to schedule cleaners.
Sources
- Professional Front Office Management (Due‑Out definition and front‑office practices): https://www.pearson.de/media/muster/ext/9781292056050.pdf
- UniFocus GUESTS console (Due‑out status): https://help.unifocus.com/help/Content/Guest/GUESTS-console-screen.htm
- Cloudbeds Departures Report: https://myfrontdesk.cloudbeds.com/hc/en-us/articles/25909039849371-Departures-Report
- OPERA Departures Not Checked Out: https://synxis-d2dv.dusit.com/OperaHelp/departures_not_checked_out.htm
- Housekeeping planning and room status priorities: https://www.swfwmd.state.fl.us/sites/default/files/store_products/champ_housekeeping_booklet_0.pdf
- Night audit procedures (verify scheduled departures): https://help.execu-tech.com/execusuite/default.aspx?pageid=night_audit_procedures1
- Airbnb default checkout and host options: https://www.airbnb.com/help/article/3433
- Airbnb “clear and simple checkout” host guidance: https://www.airbnb.ae/resources/hosting-homes/a/a-clear-and-simple-checkout-584
- Brand standards example (checkout time policy): https://s3.amazonaws.com/busites_www/resourceville/1-brand/52-resourceville/margaritaville_brand_operations_standards_1618867927.pdf
- Scrape‑based analysis of common check‑in/checkout times: https://stayapi.com/blog/hotel-check-in-time
FAQ
Q: What does “due‑out” mean in a PMS? A: It’s the status for guests scheduled to depart on the current date (or within the selected window). You’ll usually find them on a Departures or Due‑Out list so front office and housekeeping can prepare the turnover (Pearson front‑office text; Cloudbeds Departures Report).
Q: What time do most guests check out? A: Conventions cluster around late morning. If a host on Airbnb does not set times, the default is 11:00 a.m. checkout (Airbnb help). Training materials often cite 10:00–11:00 a.m., and some brands set “no earlier than 11:00 a.m.”—policies vary (training example; brand standards example).
Q: Where do I find today’s departures in my system? A: Look for a Departures/Due‑Out report or a GUESTS/Status screen with a “Due out” filter. Some systems also flag “Due‑Outs Not Checked Out” to highlight overstays (UniFocus; OPERA guidance).
Q: How should I handle late checkout requests? A: Decide ahead of time what you allow on sold vs. vacant nights and communicate clearly in writing. Airbnb notes hosts may permit late checkout and may charge extra; align policies with your cleaning schedule and local norms (Airbnb help).