Phase 1: Qualification
We confirm the property type, active channels, current systems, decision owner and reason for review.
How it works
A change is not complete until the live result is verified.
Hotel distribution work fails when diagnosis, approval, implementation and QA are treated as separate conversations. InnMetric keeps them in one controlled record.
Phase 2: Baseline
We record the current state before making a recommendation.
Phase 3: Internal verification
Public evidence shows a symptom. Authorized access is used to locate the cause.
Phase 4: Approval
No live change proceeds without the required hotel approval.
Phase 5: Repair and QA
InnMetric applies the approved change then checks the relevant system path.
Phase 6 and 7: Live verification and recurrence
We repeat the original guest-facing test then recheck on the agreed schedule.
Required before work begins
- Named hotel contact
- Named commercial or operational approver
- Agreed property and channel scope
- Agreed access method
- Confidentiality terms where needed
Baseline test conditions may include
- Stay dates and number of nights
- Adult and child occupancy
- Currency and language
- Device class
- Logged-in or logged-out state
- Direct channel and selected OTAs
- Room, rate, meal and cancellation conditions
How findings are labelled
- Confirmed defect
- Expected behavior
- Unresolved hypothesis
- Vendor dependency
- Hotel decision required
Every proposed change includes
- The problem it addresses
- The system and field affected
- Expected result
- Commercial and operational risk
- Owner
- Approval status
- Rollback note where needed
Repair and QA examples
- PMS to channel manager rate flow
- Channel manager to OTA availability flow
- Booking engine price and policy display
- OTA room and rate-plan mapping
- Reservation delivery into the PMS
We repeat the original guest-facing test. The issue closes only when the agreed outcome is verified or the remaining limitation is documented. The hotel may select a scheduled recheck or an ongoing control service. The control plan lists the exact items, cadence, owner and escalation path.
Access and security principles
- Use least-privilege access where the system supports it
- Prefer named user accounts over shared credentials
- Do not request credentials through ordinary email
- Record who approved each live change
- Remove access at the end of the agreed scope
- Do not reuse hotel data for unrelated work