Reservations · Independently Developed System

Reservation Coordination & Operations Tracking System

A reservation operations system I independently structured and developed — consolidating intake, calendar visibility, approval routing, payment confirmation, and access scheduling across multiple communities into one coordinated workflow instead of scattered email threads.

Independently structured workflow project — operational coordination, analytics interpretation, and reporting logic by Karla Sunga. Portfolio visuals contain fictionalized or redacted sample data for presentation purposes.

Workflow coordinationCalendar trackingApproval processOperational scheduling
Workflow Overview

Operational lifecycle.

  1. 01
    Request Intake
    intake
  2. 02
    Availability Review
    active
  3. 03
    Approval Routing
    watch
  4. 04
    Payment & Access
    active
  5. 05
    Confirmation
    resolved
Operational Dashboard

Visibility surface.

Fictionalized / redacted sample data — for presentation purposes
ksmotion · /reservation
Updated · just now
Total Reservations
29
Confirmed
26
Pending
0
Open Dates
20
Booked / Review
11
Calendar View · May 2026
3 communities
Date
Day
Sheff.
Glenn
Southlake
May 1
Fri
OPEN
BKD
OPEN
May 2
Sat
OPEN
BKD
OPEN
May 3
Sun
OPEN
BKD
OPEN
May 4
Mon
OPEN
OPEN
OPEN
May 9
Sat
BKD
OPEN
OPEN
May 16
Sat
BKD
OPEN
OPEN
May 17
Sun
BKD
OPEN
BKD
May 22
Fri
OPEN
BKD
OPEN
May 23
Sat
BKD
OPEN
BKD
May 30
Sat
BKD
OPEN
BKD
May 31
Sun
BKD
OPEN
OPEN
Reservation Detail
DateTimeCommunityResidentStatusAccessNotes
May 15:00–9:00 PMSheffieldM. PettyConfirmedNoTime Range: 5:00 PM – 9:00 PM
May 212:00–4:00 PMSheffieldB. OnabajoConfirmedNoStandard intake
May 1711:00 AM–3:00 PMSouthlakeH. NelomsConfirmedAccount #: 50-447 · Req RSV-7821
May 231:00–5:00 PMSouthlakeM. McNeilConfirmedNoPriority: High · Awaiting Robert confirm
Nov 215:00–10:00 PMSheffieldB. DayConfirmedNoAction: Send access code · Owner: Karla · Priority: Med
Operational Metrics

Sample operational health.

Representative metrics that this workflow surfaces to operations leadership.

Reservations / Mo
184
+12%
Pending Approvals
7
−3
Avg Turnaround
11h
−4h
Conflicts Avoided
23
Tracked
Process Breakdown

How the workflow operates.

Intake & Visibility01

Reservation requests are captured into a single board with community, amenity, date, and contact information.

  • Standardized intake form
  • Single board across communities
  • Auto-timestamped requests
Workflow Coordination02

Availability is reviewed against the shared calendar to prevent double-bookings before approval routing begins.

  • Shared availability calendar
  • Conflict detection
  • Pre-approval validation
Approval Routing03

Approvals are routed to the right CAM with full request context and a clear deadline for response.

  • Context-rich approval
  • Deadline visibility
  • Backup approver fallback
Follow-Up Tracking04

Payment confirmation, access scheduling, and reminders are tracked in one place through to the reservation date.

  • Payment confirmation
  • Access scheduling
  • Pre-event reminders
Reporting & Communication05

Monthly reporting summarizes amenity utilization, approval throughput, and outstanding follow-ups.

  • Amenity utilization
  • Approval throughput
  • Open follow-up list
Outcome

Centralized operational visibility and streamlined reservation coordination workflows.

Tools Used

Workflow infrastructure.

Monday.com

Reservation intake board with approval pipeline.

Microsoft 365

Shared availability calendar, Outlook coordination, and operational reporting.

Microsoft Outlook

Approval routing, confirmations, and reminders.

Excel

Payment tracking and monthly amenity reporting.

Zapier

Exploring automated handoffs between intake, approval, and confirmation steps.