Begin with incidents and friction
List the booking changes, missed handoffs and confusing charges that required attention during the period. Separate confirmed incidents from impressions. Record the source and the time spent only where you have actual evidence. Do not turn a handful of anecdotes into a vendor-wide reliability statistic or a claim that switching software would automatically remove all operational work.
Compare the bill with the quote
Check property count, optional components and usage-dependent charges against the configuration you intended to buy. Investigate differences before calling them errors. Keep a record of legitimate changes so the next review does not repeat the same investigation. If a service is unused, establish what depends on it before cancelling or disconnecting it.
Review the operating map
Ask whether each channel, guest task and property still has a clear owner. Update instructions after a supported feature change or a team handoff. A useful review should lead to a specific correction, a documented decision to keep the arrangement or a precise question for the provider. More reports are not inherently better management.
Choose the next small improvement
Prioritize the highest-impact observed problem that can be addressed safely. Keep unrelated live changes separate so their effects are understandable. Do not claim that a new workflow improved revenue unless you have suitable evidence. This publication’s worksheets are decision aids; they are not a substitute for actual booking, financial and operational records from your business.
Review the verdict and the cost of unresolved work
Select one repeated issue and write the observed cause, supported correction and evidence needed to judge improvement. For example, an ambiguous property label may justify a naming review, not a new software subscription. Keep the conclusion provisional until the next relevant record is checked. This prevents a monthly review from becoming a collection of confident opinions unsupported by operational evidence.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Lodgify configured plans and feature boundaries — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19
- Lodgify channel manager: merchant description, not reliability testing — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19