These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Co-living / Shared Space Mgmt
- Features
- Stays and residents
Stays and residents
Keep the booking party, stay dates, assigned space and reservation state together.
OverviewConfirmed arrivals×
Co-living / Shared Space Mgmt · Stays and residents
New
Confirmed arrivals
Checked in waits for the property manager
| Reservation number | Guest | Unit | Arrival date | Departure date | Status | |
|---|---|---|---|---|---|---|
| BKN-20118 | RSD-71264 | RSR-77661 | 12 Oct | 21 Oct | Confirmed | |
| BKN-52288 | RSD-92636 | RSR-56686 | 24 Oct | 01 Nov | Confirmed | |
| BKN-94588 | RSD-70653 | RSR-45751 | 26 Oct | 30 Oct | Confirmed | |
| BKN-71373 | RSD-87102 | RSR-32289 | 17 Oct | 19 Oct | Confirmed | |
| BKN-75161 | RSD-93307 | RSR-23344 | 03 Oct | 10 Oct | Confirmed |
6 of 6 records
RSD-71264Bookings · BKN-20118
ConfirmedUnitRSR-77661
Arrival date12 Oct
Departure date21 Oct
What you can do
Start with one reservation
A resident, group or company can be the party behind a stay. The team records that party once and links the booking to the space it will use. Arrival, departure, guest count and nightly rate stay on the reservation. A desk agent can read the stay to answer who is expected, where they will stay and when they will arrive. The property manager can review the same record before a requested stay is confirmed.
A request is a request until the team checks the interval and the space. The resource has a capacity and operating status. Two bookings for the same room over overlapping nights need a deliberate decision before either is treated as confirmed. Keep the half-open stay interval clear: departure day frees the space for the next arrival after turnover. The party size must fit the resource, and any minimum-stay rule comes from the dated rate plan used by the property.
How the work is organized
- Resident identity. Use the resident record for the booking party and its contact details; keep the reservation number as the stay reference.
- Stay decision. Review requested dates, guest count, space capacity and current reservation state before confirming.
- Arrival and departure. Work the confirmed booking through check-in and check-out while retaining the original stay context.
What to agree during setup
Decide who can create or change resident contact details, who confirms a stay, and when the desk can check someone in. Agree how a cancellation is recorded and how staff will handle a changed arrival or departure date. A property with several resource types should decide whether a rate plan is selected before the nightly rate is entered on the booking. Give staff a consistent way to identify the real booking party when one person reserves for a group.
Check the handoff on an actual case
Take a request for a shared room from Monday to Thursday. Link the named party to a space with enough capacity, then look for another confirmed or checked-in booking covering any of those nights. The property manager records the request and checks conflicting dates before confirming it. At arrival, the front desk uses the confirmed reservation number and guest details; at departure, finance can find every charge and payment evidence record through that same reservation. If a guest asks why a charge belongs to the stay, the team should not have to search by name alone.
What your team sees
- Requested stays — Work through booking parties and arrival dates before confirming a resource.
- Confirmed arrivals — Prepare the desk for residents due to use their assigned space.
- Completed stays — Review checked-out reservations with their original stay dates.
Follow the work through
Start with reservation handling, then review checkout and turnover.
What it keeps track of
Data model- Residents
- Guests, groups, companies and other booking parties.
- Bookings
- Stay and resource bookings with arrival, departure, party size and nightly rate.
- Resources
- Bookable inventory: rooms, suites, venues, tables, treatment rooms and other resources.
- Rate plans
- Dated nightly rate plans by unit type with minimum stay rules.
Who uses it
Permissions- Property Manager
- Creates and updates bookings.
- Front Desk Agent
- Reads stays and records linked amenity or service work.
- Operations Reviewer
- And Finance Officer review the records relevant to their decisions.
Set up Co-living / Shared Space Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.