Appearance
Everest: Listings Management
Purpose: Where property and marketing teams manage the physical portfolio, developments and apartments and their data, and publish adverts out to the property portals and the Way of Life website.
Primary users: Way of Life property and marketing staff.
See it live: sign in at the Olympus launchpad, olympustech.ai, then open Everest. See Accessing the systems.
In Everest's screens, "properties" are labelled Developments and "units" are labelled Apartments. It's the source of the listing data that ends up on Rightmove, Zoopla, On The Market and the website.
Sign-in
What it does: Login via Microsoft (Azure) single sign-on or email and password, with the usual forgot/reset flow.
Who uses it: All internal staff.
Key rules:
- Single sign-on is the main route; a small list of accounts can bypass it.
- Access is role-based (Super Admin, Admin, Property Manager, plus two API roles), and each role carries a fixed, granular set of permissions, for example who can edit apartments, delete developments, sync listings to portals, or restore earlier versions.
Dashboard & stats
What it does: A landing dashboard of operational tiles, apartments on the market, ready to publish, pending approval, average days on market, sync errors, and more, each drilling into its own detail page.
Who uses it: Property managers and admins monitoring portfolio health.
Key rules: Figures are cached and refreshed hourly. The "days on market" reporting threshold defaults to 10 days.
Developments
What it does: Manage each development, its detail page, images, documents and downloads, with archive and restore.
Who uses it: Property managers and admins.
Key rules: Developments largely originate from the source accounting system (keyed by their Qube reference) rather than being created by hand in Everest. A daily check flags developments ready to be decommissioned.
Apartments
What it does: Manage the apartments within a development, create, edit (with live validation as you type), view, archive, restore, download documents, and reorder photos.
Who uses it: Property managers and admins.
Key rules:
- There's a global "All Apartments" list as well as the per-development view.
- Deposits are calculated automatically, defaulting to five weeks' rent.
- An apartment that isn't a draft but has incomplete data can't be published to a portal, and staff are notified when that's the case.
Listings & platform sync
What it does: Push a single apartment onto the portals and website, update it, remove it, or schedule it to go live on a future date.
Who uses it: Staff with the "synchronise to platforms" permission.
Key rules:
- Four destinations: Rightmove, Zoopla and On The Market (external portals) and the website (internal). Each can be turned on or off independently.
- Scheduled listings go live on their chosen date via an automated job that runs every 15 minutes.
Listing freshness, refresh & bulk resync
What it does: Keeps listings looking current. A per-apartment refresh, and a bulk resynchronise that removes and re-adds every apartment in a development so the adverts resurface as "new".
Who uses it: Property managers and admins with the sync permission.
Key rules:
- Refresh targets apartments that have been on the market and unchanged for 14 days or more.
- To stay within the portals' limits, the jobs are spread out with randomised delays rather than fired all at once. A daily job (evening) refreshes eligible apartments automatically.
Website content (Storyblok) & channels
What it does: Publishes a development's data to Storyblok, the content system behind the Way of Life website, and manages the named "website channels" that route listings on the site.
Who uses it: Staff with the property-update and Storyblok permissions.
Key rules: Only the internal "website" destination uses channels; the external portals ignore them. The content published here is what the Marketing Websites render, they read it from Storyblok rather than calling Everest live.
Replica & automated listings
What it does: Creates "replica" listings, extra portal adverts for the same apartment, to improve visibility and ranking on the portals. Supports manual and bulk sync/remove, plus an on-demand "fetch" that reads portal rankings and creates the replicas automatically.
Who uses it: Staff with the replica-listing permission.
Key rules:
- Only one automated import runs at a time, and the requester is emailed if it fails.
- Replicas no longer present in the ranking data are removed; inactive replicas are flagged after 30 days and cleared after 90.
Content pools
What it does: Shared description templates applied to many apartments in a development that match set criteria (bedrooms, furnished state, floorplan type), with their own media and documents.
Who uses it: Content editors and property managers.
Key rules: A content pool describes a typical apartment matching its filters, not a specific one.
AI descriptions
What it does: Generates, shortens or lengthens the short and long descriptions for developments, apartments and content pools, and can weave in nearby area highlights.
Who uses it: Content editors with the AI-descriptions permission; the brand tone is set per building in Olympus Frontend.
Key rules: Off by default and enabled per environment via a feature flag.
Reference data
What it does: Manages the supporting lookup data attached to developments and apartments, owners, agents, furniture packs, perks, apartment types, development types, and points of interest.
Who uses it: Admins, each area behind its own "manage" permission.
Key rules: Everything supports archive and restore. Furniture packs and perks are inherited from development down to apartment and can be ordered.
Revisions & restore
What it does: Version history for developments and apartments, view earlier versions and restore one, alongside archive/restore across most records.
Who uses it: Staff with the relevant "restore" permissions.
Key rules: History keeps the last seven versions per record, pruned after a year. Restoring a version re-saves the record and triggers the downstream listing sync.
Bulk upload
What it does: CSV upload to create or update many apartments at once (with a column-mapping step), and a separate bulk upload of ERV (Estimated Rental Value) data.
Who uses it: Admins with the bulk-upload permission.
Key rules: Downloadable sample files are provided, and the mapping is validated before anything is saved.
Notifications
What it does: An in-app alert centre flagging data and sync problems, incomplete apartments that can't be published, "let" apartments still live on portals, and apartments with sync errors.
Who uses it: Property managers and admins.
Key rules: Alerts are generated by scheduled checks running through the day.
Media management
What it does: Upload and replace images (per collection) and documents on developments, apartments and content pools, and reorder apartment photos manually or automatically.
Who uses it: Property managers and content editors with the update permission.
Search
What it does: Fast search and filtering across everything in Everest, apartments, developments and all the reference data.
Who uses it: All internal users, on the list and filter screens.
Key rules: Powered by Meilisearch.
Public API
What it does: A token-secured external API to list and show developments and apartments, update them, view performance stats, and trigger a sync. This is what feeds the Way of Life website and partner integrations.
Who uses it: Approved API consumers (the two API roles).
Key rules: Access tokens expire after 30 days. Records are keyed by their Qube reference, and visibility can be restricted to specific apartments.
Behind the scenes: automation
Everest runs a number of scheduled jobs so staff don't have to: publishing scheduled listings, refreshing stale ones, pulling Rightmove performance stats, recomputing dashboard tiles, flagging problems as notifications, and housekeeping. Worth knowing these run on their own, a listing appearing, refreshing or being flagged isn't always someone pressing a button.
Integrations used by Everest
| System | What it's used for |
|---|---|
| Meilisearch | Powering search |
| Microsoft / Azure AD | Staff single sign-on |
| Rightmove / Zoopla / On The Market | Publishing and refreshing apartment adverts |
| Storyblok | Publishing listings to the public website |
Related documentation
- Everest Media Pool V2
- Bulk Upload CSV Fields
- Automated / Replica Listings UAT test plans
- Terminology Alignment, Everest