Amenities • Scope defined
Amenities
The list below is limited to operationally supported services. Each item includes scope notes, constraints, and typical service windows.
Key facts
Service model
- Defined scope: services are listed with limits to reduce mismatch.
- Service windows: some services run by schedule; exceptions are logged.
- Safety first: restricted items and usage rules apply to protect guests and staff.
- Documentation: incident reports and service tickets are recorded when applicable.
Guest responsibilities
- Follow posted facility rules and capacity limits.
- Respect quiet hours and shared-space conduct standards.
- Report hazards promptly to reception.
- Use secure practices for devices and data on shared networks.
Rooms (reference)
Room-dependent amenities
- Workspace and lighting standard across categories.
- Consumables replenishment based on stay length and policy.
- Quiet-floor allocation is an operational control, not an amenity guarantee.
Housekeeping windows
- Scheduled windows support predictable operations.
- DND supported; welfare checks may apply for extended DND.
- Maintenance access requires approval except emergencies.
Amenities (detailed)
Business services
- Printing: limited pages; file handling per privacy rules.
- Scanning: controlled process; avoid sensitive data unless necessary.
- Shipping/receiving: acceptance during reception coverage; ID pickup required.
- Invoice support: company name capture, itemized receipts on request.
Connectivity
- Wi-Fi: acceptable-use policy; best-effort availability.
- VPN: supported as a concept; client config remains your responsibility.
- Incident response: security events logged and escalated.
- Privacy: see Privacy Policy.
Fitness access
- Access control: hours may be restricted; capacity limits apply.
- Hygiene: wipe-down rules; towels provided per policy.
- Liability: use at own risk; follow posted safety instructions.
- Downtime: equipment service windows may occur without notice.
Meeting support (limited)
- Small meetings: subject to availability; not guaranteed without coordination.
- Noise control: quiet-hour policy applies; repeated violations escalate.
- Equipment: limited; confirm requirements in writing.
- Room use: in-room gatherings may be restricted; follow policy.
Food and beverage (non-promotional)
- Availability: depends on partner operation or defined hours.
- Dietary needs: best-effort; cannot guarantee cross-contamination control.
- External food: permitted; disposal rules apply; avoid odor impact to corridors.
- Appliances: external cooking appliances restricted for safety.
Operational controls (what we explicitly do)
| Control | Purpose | How applied |
|---|---|---|
| Quiet hours | Predictable rest environment | Allocation, warnings, escalation, relocation if necessary |
| Ticket logging | Traceability of issues | Front desk logs severity, assigns, tracks closure |
| Access rules | Safety and capacity management | Hours, capacity caps, posted rules, enforcement |
| Data minimization | Reduce exposure | Collect only required fields; retention limits |
Location (reference)
Access for service delivery
- Deliveries accepted within reception coverage.
- Storage is limited; time-bound holding rules apply.
- Large items require prior notice.
Parking and drop-off
- Drop-off lane rules apply to minimize congestion.
- Parking capacity finite; allocation not implied.
- Vehicle incidents follow documented escalation path.
Pros / Cons (amenities scope)
Pros
- Defined scope reduces expectation mismatch.
- Business services aligned to invoice and documentation needs.
- Connectivity policy stated; escalation path available.
Cons / limitations
- Some services operate on limited windows.
- Equipment and meeting support are limited by design.
- Third-party food operations may vary by schedule.