Every important change with person, time and area, for calm handovers.

Important changes with time, module, action, affected record and responsible person.

Because small teams also hand over shifts, change rates, correct payments and maintain guest data. A history answers questions without relying on memory.

The personal user with name and email where available. This is why individual accounts are better than one shared front-desk login.

Bookings, guests, team and permissions, settings, finance, pricing, rooms, housekeeping and distribution changes, among others.

STRYK shows the area, action, affected record, time and responsible person. There is no direct link from the log to the record; for an individual booking, you will also find the history directly in the booking.

Yes. From and to dates narrow the exact shift, week or review period that needs clarification.

Yes. For example bookings, guests, finance, settings or migration, depending on the entries that actually exist.

Yes. Creation, update, deletion, completion or specifically named business actions can be narrowed deliberately.

Yes. The selection shows people who actually have log entries in the property.

Yes. Affected record, user name and email can be searched to resolve a specific question faster.

Yes. The newest changes appear first. Filters and search quickly lead to the relevant period, employee or hotel process.

Yes. PDF, CSV and spreadsheet-compatible output use the same filters so screen and review cover the same scope.

Yes. The export includes the complete filtered selection and is not limited to the page currently visible.

No. It explains changes and responsibility but does not replace backups or required business document retention.

No. The log is evidence. Undo or versioning follows the relevant business process, such as quote drafts or a controlled import.

No. A failed change remains visible as an error. The team continues with the new state only after saving and recording have succeeded.

Rate, availability and mapping changes remain traceable with time and responsible person. For approved portal connections, the relevant history adds the concrete transmission state.

Yes. Date range, user and affected record give property and support a reliable starting point instead of a vague description.

Only roles with the relevant permission. Operational transparency does not mean every employee may see sensitive finance or administration details.

Yes. A property sees only its own changes, employees and exports. Entries from other properties appear neither on screen nor in files.

Set the range to the previous shift, filter critical modules and review open anomalies on the affected record. It does not replace handover, but makes it concrete.

No. Personal accounts make responsibility clear. A shared login can record actions but cannot provide reliable personal attribution.

No. Traceability, filters and exports are part of the single STRYK offer-with no setup fee and no hidden module price.