Set project ownership and launch date
Name one person who owns progress and records approvals. That person assigns reviewers for property data, rooms, finance, housekeeping and booking engine.
Set a realistic date and plan backwards, leaving at least two days between completed setup and launch for end-to-end tests.
Approve property identity and finance foundation
Open Settings → Property and enter official name, company, address, contacts, timezone, currency and default language. These values feed operations, documents, communication and booking surfaces.
Then review invoice issuer, tax details, sequences, payment details, document copy and language. Approve only after reading a complete test PDF.
Approval 1: property and finance
- Property and company names match official records.
- Address, timezone, currency and default language are correct.
- Tax details and number sequences were reviewed.
- A complete test PDF has visual approval.
Model the sellable property: categories, rooms and blocks
Create categories before physical rooms. A category defines the guest offer: capacity, occupancy, extra beds, size, bed type and descriptions. Avoid duplicates without a difference guests can understand.
Assign every physical room to exactly one category and reconcile counts. Use operational blocks for maintenance or out-of-order inventory; housekeeping state is not an availability block.
| Check | Expected state | Test |
|---|---|---|
| Category | Unique, understandable and sellable | Can front desk explain its difference from every other category? |
| Capacity | Standard and maximum occupancy match the room | Test family and single occupancy in search |
| Room inventory | Every physical room appears exactly once | Count each category against the property list |
| Blocks | Maintenance blocks real availability | Verify the block in calendar and availability |
Test prices, rate plans and policies as one offer
Start with a traceable base price per category. Add seasons, weekdays, overrides, rate plans and discounts. Launch with a small set of offers that guests and staff can explain.
Test every active rate on a normal weekday, strong weekend and overridden date. Review nightly price, total, cancellation, payment and inclusions.
Test personal access and roles in real work
Create one user per person. Assign roles by real tasks and avoid shared logins or default administrator access.
Test roles by having each person complete a normal workflow and confirm that unrelated sensitive actions are unavailable.
Rehearse operations and guest journey end to end
Stop testing isolated settings. Run one realistic two-night booking through guest, price, housekeeping readiness, check-in, extra, partial payment, invoice and check-out.
Also test a mobile direct booking in the preview. Category, photos, price, availability, rate, policies, extras and confirmation must arrive consistently in STRYK.
Mandatory pre-launch rehearsal
- 01Reservation
Create two nights, two guests, active rate and an extra; verify dates, availability and total.
The booking appears without conflict. - 02Arrival and housekeeping
Prioritise, assign, start, finish and return the room as ready.
- 03Stay and departure
Check in, add a charge, record partial and final payment, review PDF and check out.
- 04Mobile direct booking
Complete the guest journey on a phone and verify the reservation in STRYK.
Approve go-live and manage the first five days
Approve launch only after mandatory tests pass. Cosmetic improvements may follow; unresolved booking, availability, invoice, payment, access or housekeeping failures block launch.
Run a 15-minute review on each of the first five days. Every issue gets cause, owner, deadline and retest. Close implementation after reviewing access, balances, housekeeping handovers and booking differences.
| Area | Pass evidence | Blocks launch when… |
|---|---|---|
| Property & finance | Master data and full test PDF approved | Tax, recipient or document content is unclear |
| Rooms & availability | Inventory, capacity and blocks match | A room is missing or can be double-sold |
| Team | Every role passes its workflow | A person lacks safe working access |
| Operations | Stay lifecycle and direct path pass | A mandatory case lacks a confirmed result |
