akeye

PROPERTY MANAGEMENT use case

Connect reservation context with day-to-day property operations

A reservation affects more than a calendar slot. It gives operations teams the stay dates and accommodation context they need when planning arrivals, cleaning and other follow-up work.

Akeye keeps stay-oriented reservations associated with the organization, property grouping and accommodation unit. The wider Activity model can then coordinate operational work without claiming integrations or automation that are not part of the current public product.

Contact usAkeye for Property Management

01

A reservation-aware operating flow

The reservation establishes occupancy context; operational Activities remain explicit records owned by the team.

  1. 01

    Select the property unit

    Keep the reservation tied to its organization, Macro Unit and active Micro Unit.

  2. 02

    Record the stay

    Add check-in and check-out dates, optional times, guest counts, status, payment state and relevant notes.

  3. 03

    Review availability

    Use the date-based reservation view to understand recorded occupancy across the selected units.

  4. 04

    Coordinate follow-up

    Create and assign Activities for the operational work the team needs around that stay.

02

What the reservation record covers

The current model focuses on a clear, stay-oriented internal record.

Dates and unit relation

Reservations carry stay dates and remain linked to a specific property hierarchy and unit.

Guest and status context

Guest counts, reservation state, payment state, notes and display color support internal review.

Overlap checks

Creation checks non-cancelled reservations for conflicting date intervals on the selected unit.

Related operational work

Activities provide a separate, assignable path for cleaning, maintenance or arrival preparation.

03

What is not implied

This is an internal reservation and operations workflow, not a claim of a complete distribution platform.

  • No channel manager, booking marketplace or external calendar synchronization is promised here.
  • No automated guest email, payment collection or reservation reminder is claimed.
  • The workflow should be assessed against current access controls before Production use.

FAQ

Reservation operations FAQ

Answers about the current stay-oriented reservation scope.

What information does an Akeye reservation contain?

It can contain the related property structure and unit, stay dates, optional daily times, guest counts, status, payment state, notes and display color.

Does Akeye prevent every possible double booking?

Creation performs an application-level overlap check for non-cancelled reservations, but the public workflow does not claim a database-level race-proof guarantee.

Does a reservation automatically create cleaning work?

No automatic reservation-to-Activity workflow is claimed. Teams can create explicit Activities for the operational work they need.

Connect stays with property work

Continue with cleaning and maintenance coordination or review the complete industry guide.

Akeye for Property Management

Manage guest communication, work orders, cleaning checklists, and check-in instructions in one organized place.

Coordinate cleaning and maintenance around each property unit

Coordinate property cleaning, maintenance Activities, assignments, due dates and checklists with each accommodation unit in context.

FAQ

Start with the practical answers below, then explore an industry guide or contact Akeye to discuss how your organization works.

Review your reservation workflow

Share the internal reservation and property-operations flow you need so current fit and limitations can be discussed clearly.

Contact us