Good answers.
Before your first week.

It is a hotel employee scheduling system for creating, editing, reviewing, publishing, viewing, and communicating work schedules. Availability, time off, swaps, scheduled hours, and workplace messaging support that purpose. It is not a hotel reservation system, payroll engine, or clock-in system.

No. The application is a standalone PHP system with its own installation, accounts, storage, and maintenance controls. This public information website is a separate static site; it does not replace or install the scheduler.

No. Employees use a separate username and password. Email and phone may be blank. Self-registered accounts still require management approval, and temporary-password accounts must finish password setup. Email notices naturally require a usable email address.

Yes. Each department has its own roster, draft status, and publication. Publishing Housekeeping does not publish Front Desk or Breakfast drafts. A shared employee remains one person, with combined limits and cross-position conflict checks.

Yes. Every approved, active employee can choose My schedule or Team schedule. Team schedule shows published assignments across hotel departments in Day or Week views, with each department kept separate. Employees can open read-only shift details and begin an eligible same-department exchange. Coworker time-off reasons, documents, contact details, private availability, and management notes stay hidden; nonworking entries appear as OFF. A blank cell means no published entry, not confirmed availability.

A draft is saved planning work visible to permitted managers. Publication makes the reviewed department copy official for employees. Later changes remain drafts until republished. Employees should follow their published schedule, not an unapproved chat suggestion.

It can only use eligible, active, schedulable employees who pass the current rules. Availability, approved leave, category eligibility, workday limits, rest, overlap, or weekly maximums can block an assignment. Read the proposal's explanations and check actual staffing requirements before changing rules.

No. Target hours are a planning preference. Maximum hours are a hard combined weekly limit in scheduling. A valid schedule may be below target. Holding multiple positions does not create a separate allowance for each position.

An end time earlier than its start continues into the next calendar day and shows a next-day indicator. Scheduling uses the shift's start-date week and checks neighboring dates for conflicts and rest. Report views can offer separate explicit overnight-allocation choices.

Yes, for a selected department week that has never been published. Clear draft week can remove only auto-generated work or all editable entries. Review and confirm the removal. Other departments, approved absences, recurring rules, and workflow-protected entries remain. An unapplied proposal can simply be discarded.

No. Undo and Redo review eligible recorded draft changes. If affected assignments no longer match, a later publication occurred, or current rules prevent the reversal, the action is refused. Import and request workflows keep their own controls; this is not a whole-database restore.

No. It describes scheduled Saturdays, Sundays, distinct weekends, night-audit-category assignments, and hours over a selected period. It does not assign a fairness score or change schedules. Current eligibility is not reconstructed historical eligibility.

The request remains pending until an authorized manager reviews it. Approved restrictions apply to the person across positions. Conflicting draft assignments require explicit handling, and posted schedules remain unchanged until the affected department weeks are republished.

Yes. Dated recurring availability can block selected hours on selected weekdays. Employees can request a change for management approval. A full-day restriction must be deliberately reviewed when replacing it with partial-day school hours.

Yes. In Shift swaps, select Request a shift swap, then choose your own shift, the coworker, and that coworker's specific published shift. Review both assignments together before confirming and sending. You can also start by clicking a coworker's shift in Team schedule. Both people must agree to the exact pair; a changed return shift requires the requester to confirm again. Management approves to draft and separately publishes each affected week. Until then, follow the current posted schedule.

They are schedule wording, with behavior controlled by the record or configured label. Approved request-linked OFF/TRO entries are protected; simply typing an OFF/TRO label does not approve a request. An empty dash can mean unassigned, not a scheduled day off. Managers can define other permitted labels and blocking behavior.

Yes. Administrator, GM, and AGM can select enabled layouts and separate manager/employee defaults, and decide whether employees can choose another enabled view. These four personal layouts remain available in My schedule. Employees use the separate Team schedule Day and Week views to consult published coworkers' shifts across departments; editing and approval controls remain with management.

No. It opens the application's installation page. Supported Android browsers may provide an install prompt; iPhone uses Safari's Add to Home Screen workflow. The device owner approves installation and notification permissions. There is no native app-store binary supplied by this website.

The saved app/account language determines the target message language, not phone language. Automatic free-text translation still needs the selected service configured and running. A Spanish interface alone does not translate messages without that service.

The self-hosted software is free and open source. It runs separately and consumes your server's resources; managed hosted services can charge. HotelSchedule's private LibreTranslate integration must be configured, and English/Spanish directions tested. It does not silently switch to a paid provider when LibreTranslate fails.

No. In-app updates work while the app is visible and connected. Closed-app push additionally depends on server configuration, the worker, device registration, permission, connectivity, and phone settings such as Focus. Provider acceptance, a display request, and a person actually seeing an alert are different events.

The website and icon files may be current while the browser's background worker has not been verified. Save unfinished work, use the available safe reload, and download Refresh details for diagnosis. Do not treat waiting longer as proof that the worker is installing. This information website does not change that worker or resolve a live refresh fault.

The app refreshes the icon and manifest supplied by the website. The phone/browser decides when an already-installed icon or app name changes and may need an identity-update approval or re-adding a shortcut. Do not routinely clear sign-in or notification data to refresh a logo.

XLS/XLSX, CSV, recognizable seven-day PDFs and PNG/JPG/WebP images can be reviewed before importing to draft. Employee names, dates, and shifts can be corrected. Scanned PDFs and images use optional local Tesseract OCR with a source-review step; the host must install the required tools. Blank cells leave existing entries alone; conflicts prevent partial saving.

Yes. Print options include matching online shift colors, saved branding, ordinary day-off wording, and optional seasonal artwork. Use landscape and enable browser background graphics for color output. Printer and browser choices can still override colors. Employees print only their own published schedule.

It calculates scheduled hours and supports manager-entered actual totals and report comparisons. Actual totals are not clock punches, and reports are not a payroll or overtime-law engine. Break allocation and overnight reporting choices should be reviewed rather than assumed.

Administrator, GM, and AGM oversight of staff workplace conversations is disclosed. Nonparticipant oversight is read-only and recorded. Recoverable message/conversation deletion is separate from permanent retention rules; delivered copies and existing backups cannot be recalled.

The administrator checks a compatible signed Update ZIP and confirms the update after a verified safety backup. There is no manual checksum entry in the current application. Data restore replaces snapshot records rather than merging them; older code rollback can be blocked after newer protected workflows are used.

Sign in and open How-To Center for instructions filtered by account permissions. Current articles explain My schedule, Team schedule, and confirmed shift exchanges; employee essentials include Spanish text. The downloadable v1.20.0 manual and earlier training screenshots remain historical references. The owner manual is available inside the signed-in system.