> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/automation/event-log.md). # Event Log The Event Log is the property-wide record of every change Revhero made, who made it, and what happened to it. The **Event Log** is the shared record of what happened on your property. Everyone working on the property can see what was changed, by whom, and what was left alone. It keeps the whole team on the same page, and it answers a question after the fact with evidence rather than memory. Every rate send, every configuration change and every sync with a connected system writes 1 line with a date and time. A **sync** is the transfer of data between Revhero and a connected system. ![Every change on one list, with who made it and whether it went through](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-d3ddec257f71e962365ab68f5a980e6e5c9db09c%2Fone-record-of-what-happened.svg?alt=media) *Every change lands on the same list, whoever or whatever made it.* It records 3 kinds of activity side by side: * **What a user did** — a rate a person changed by hand, over the recommendation. * **What the recommendations did** — rate changes that came from automated recommendation activity. * **What your business rules did** — changes your configured rules made on your behalf. You can download the log at any time. The file shows what each rate changed to, so you can compare today's file against one you downloaded earlier and see exactly how the property moved. The [Dashboard](/revhero-docs/your-hotels-performance/dashboard.md) tells you what is happening now. The Event Log tells you what already happened. Open **Event Log** in the sidebar. It opens on the current property and shows the last 7 days. ## What gets recorded | What Revhero records | What it covers | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Manual** | Every **Send** from the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md). The line shows who sent it, which dates and rooms, and the rate before and after | | **Configuration** | Publishing a [Pricing](/revhero-docs/setting-your-rates/pricing.md) structure, rate plan edits, supplement changes and room type changes. The line shows what changed and who changed it | | **Restriction** | Minimum stay updates that were sent out | | **Integration** | Syncs with your connected systems. The line shows when the sync started and when it finished | Every line carries at least 4 things: a timestamp, who or what did it, the kind of change, and how it ended. A send either went through, or it did not — and a line that did not go through carries the reason. Rate lines and restriction lines carry more. They also show the stay dates, the room, the board and the occupancy affected, and the values before and after. See [Event types](/revhero-docs/automation/event-log/event-types.md) for the full legend. The log covers 1 property at a time. Use the property selector to move between hotels. There is no combined view across a group. To audit a group, work through the properties 1 by 1, or combine the downloaded files yourself. ## Checking what happened while you were away If you want to see what other users or the system did over a weekend, open the Event Log and have a quick look. Set the date range to cover the days you missed, and read down the list. The lines are in order, newest first, so a few minutes tells you what moved and who moved it. ## Retention and downloads Entries are kept for as long as the property is active. Nothing is deleted automatically. **Download** exports the lines currently on screen as a CSV file or an Excel file, with every column. Filter first, then download. A monthly download is a sensible archive. It also gives you something to compare against: put this month's file next to last month's and the rate changes between them are visible in one place. ## If something looks wrong | What you see | Usual cause | What to do | | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | | Nothing at all for the day | The date range is too narrow, or the property really had no activity | Reset the filters and widen the dates. Also check **Last Send Date** on the Yielding Board | | Several sends that did not go through | Your channel manager rejected them. A rate plan may be inactive, or an occupancy combination may be missing | Open 1 line and read the reason. Fix the cause in the other system, then send again | | A manual send you know happened is missing | The Source filter is set to something else | Reset Source to all | | **Download** is greyed out | Your role does not include exporting | Ask an administrator at your property for download access | | The before and after values are identical | The send made no change | This is harmless. The line exists for completeness | | A day with no sync lines | A connection was paused, or its access has expired | Check the integration status in [Settings](/revhero-docs/your-hotels-setup/settings.md) | ## Related * [Event types](/revhero-docs/automation/event-log/event-types.md) — the legend for every Source and Action Type * [Filtering and search](/revhero-docs/automation/event-log/filtering-and-search.md) — finding 1 line among thousands * [Investigating a rate send](/revhero-docs/automation/event-log/investigating-a-rate-send.md) — how to answer "did my rate go out?" *** **Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20event-log%2FREADME.md) and quote this page: `event-log/README.md`. Say what you expected to find — that is the part we can fix.