These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Audits
Example screen with sample data
Audits
Plan scope, record findings by requirement and retain the close decision.
OverviewOpen findings×
Hotels and Hospitality QMS · Audits
New
Open findings
Audit findings
| Requirement | Finding | Severity | Due date | Closed at | Audit | |
|---|---|---|---|---|---|---|
| RQR-397 | FND-462 | Observation | 16 Oct | 15 Oct | ADT-55616 | |
| RQR-545 | FND-685 | Minor | 13 Oct | 15 Oct | ADT-42326 | |
| RQR-603 | FND-980 | Major | 24 Oct | 15 Oct | ADT-87442 | |
| RQR-858 | FND-555 | Observation | 14 Oct | 15 Oct | ADT-86421 | |
| RQR-556 | FND-692 | Minor | 16 Oct | 15 Oct | ADT-37702 |
6 of 6 records
RQR-397Audit findings · AF-17673
ObservationFindingFND-462
Due date16 Oct
Closed at15 Oct
AuditADT-55616
What you can do
Give each audit a defined scope
The Auditor records an audit number, scope, planned date and responsible person. The audit moves from planned to in progress, then reporting and closed. Findings belong to the audit and retain the requirement, finding, severity, due date, closed date and owner. That relationship lets a reviewer read a finding in the scope that produced it instead of treating it as an unrelated task.
When the audit enters reporting, the close workflow verifies that scope is recorded against its findings before closing the audit. The Quality Manager can review open findings and their owners while the Auditor prepares reporting. A closed audit and an open finding can be read separately because they are distinct records with distinct dates.
How the work is organized
- Set scope and assignment. Record what the audit covers, when it is planned and who performs it.
- Record each finding. Link requirement and observation to the audit and assign a person with a due date.
- Report and close. Move the audit through reporting after scope and findings are ready for review.
What to agree during setup
Agree how scope names the property, service area or standard being checked. Decide how findings are written so the requirement and observed issue can be understood later. Define when a finding is closed and how the owner records the close date. Give the Auditor enough context to distinguish an observation from a minor or major finding.
Use the audit number consistently in communications with property teams. If an audit finding also exposes a problem found during an inspection, retain the inspection and audit as their own records and agree how the team references the same operating event. The finding points to its audit and owner.
Check the handoff on an actual case
An Auditor plans a service-quality audit for a property and writes the scope before beginning. During the audit, the Auditor records a requirement and a major finding with a due date and owner. The finding remains on the audit. The Auditor moves the audit into reporting and checks the written scope against the recorded finding. When the report is complete, the audit closes with its completed date. The owner can still see the finding in the open findings list until its own close date is recorded.
Rehearse another audit whose scope is blank. It should stay out of a clean close handoff until the Auditor has recorded what was audited. Review open audits and open findings independently.
What your team sees
- Open audits — Planned, in-progress and reporting audits with scope and auditor.
- Open findings — Findings without a close date, with owner and due date.
- Critical severity — Inspection-linked issues for cross-checking a serious concern.
Follow the work through
See audit reporting and inspection review.
What it keeps track of
Data model- Audits
- Audits records for Quality & Compliance (Source).
- Audit findings
- Audit Findings records for Quality & Compliance (Source).
- People
- People records for Quality & Compliance (Source).
- Inspections
- Inspections records for Quality & Compliance (Source).
- Nonconformances
- Nonconformances records for Quality & Compliance (Source).
Who uses it
Permissions- Auditor
- Plans, records and reports the audit.
- Quality Manager
- Checks findings and follow-up.
- Property Manager
- Helps locate the service context.
Set up Hotels and Hospitality QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.