Guest misconduct records your team can refer back to.
Document what happened, record severity and the action taken, and keep available photos or videos with the report. Eligible administrators can also run a manual guest-name search across Hotel Central hotels.
An authenticated staff workflow for recording guest misconduct at a hotel. Reports can include guest and room details, incident date, category, staff-selected severity, description, resolution, outcome, and available photo or video attachments. Authorized staff can filter and search the records returned for their hotel. Eligible administrators have a separate manual cross-hotel guest-name lookup that returns summary information. The workflow does not automatically screen reservations, verify identity, compare photographs, block check-in, or enforce a recorded ban.
Three workflow previews: a blank misconduct report, the filters for one hotel's records, and the separate manual name lookup available to eligible administrators.
Guest Name *
Required
Incident Date *
Required
Category
Other
Severity
Medium
Description *
Sort by
No records shown
Create a report or adjust the filters.
Search Hotel Central Database
Run a manual guest-name lookup across active misconduct records.
Search the Network
Results show summary fields, not another hotel's full report or attachments.
A name result does not confirm identity
An incident is left in a message thread or one manager's memory. The next shift may not know what happened, how serious it was, or what action the hotel took.
Give authorized staff one structured report with the incident details, severity, supporting context, and recorded outcome.
incident categories available for structured staff reporting
Every step ties to a real, connected feature.
Availability depends on the hotel's subscription, page enablement, and staff permissions.
Log what happened, who was involved, immediate actions, photos or videos, severity, assignment, resolution, and a focused activity timeline.
Record guest and stay details, claim or assign ownership, keep staff notes, update status, and review an editable apology draft before using it outside the module.
Invite a guest to complete check-in details, review the submission, share a branded stay portal, and keep human conversations and service requests tied to that stay.
It is Hotel Central's guest misconduct record workflow. Staff document incidents, severity, supporting media, and outcomes. DNA refers to Do Not Accommodate; it is not biological information or an automated profiling system.
No. The current workflow does not automatically screen reservations, place room holds, or block check-in. Staff review records and make decisions under their hotel's policies.
Access depends on the hotel's entitlement, page enablement, and staff permissions. Cross-hotel search has additional administrator restrictions; access to property records does not automatically include network search.
Eligible administrators enter a guest name and run a manual search. Results show summary information such as hotel, guest name, incident date, category, severity, and outcome—not the other hotel's full report or attachments.
No. Search finds names containing the entered text. It does not verify identity or compare photographs. Staff should independently confirm relevant details before acting.
You can record Banned as an outcome and explain the decision in resolution details. The current workflow does not provide ban-expiry scheduling, countdowns, or automatic enforcement.
No. Incident Reports and Guest Misconduct are separate workflows. A misconduct report must be created separately; there is no automatic record link or transfer in the current workflow.
The current page does not provide a dedicated report export or edit-history timeline. It displays the saved report and creation time; editing updates the current record.