Maxxton Operations

The Setup Reality: What Happens When You Open It

You log in using a three-letter concern code, the same one used for the Maxxton Software web platform. That code determines which location's data appears. The login and password match your existing Maxxton credentials, but permissions must be arranged through support first. Once in, the dashboard presents an overview of all workorders for your location. A calendar filter lets you narrow down tasks by start date. On the right top, a profile button lets you adjust language settings or select which location you are working at today. The interface is clean, functional, and clearly built for people who need to get moving fast.

This is not a public app. It is only for Maxxton customers. Holiday parks, campsites, and vacation rental operators use it to connect their back-office systems with the people on the ground. The core logic ties directly into the Maxxton property management system, so every task you see was created somewhere else – by a front-office manager, a maintenance supervisor, or an automated schedule. The app is the field worker's window into that system. It shows what needs doing, where, and how urgent it is.

The first thing a field worker notices is the workorder list. It displays cards for each task. Each card shows the unit name, occupancy status, expected start date, and priority icons. You can unfold a card to see more details – the workorder item, the assignee, occupancy details, and the current status. The orange plus button sits at the bottom right, ready to create a new workorder on the spot. That is useful when a cleaner finds a broken fixture or a maintenance worker spots a new issue during a repair.

How the Map View Changes the Daily Workflow

The map view is where the app stops being just a list and becomes a routing tool. When you tap the map icon, all workorders appear as markers on a Google Maps overlay. Each marker sits on the actual unit location, provided the coordinates have been configured in the Maxxton Software. A red marker means at least one workorder on that unit is marked urgent. The number inside the marker shows how many tasks are waiting at that specific accommodation. Tapping a marker reveals the same information you would see in the list view – the unit name, the task details, and the status.

Here is where the original observation comes in. The map view and the priority system do not just show you where to go. They change how you decide what to do first. A list view encourages a linear approach – start at the top and work down. But the map view shows you that three tasks are clustered in the same building, while two urgent markers are spread across opposite ends of the property. The visual layout forces a different kind of decision: do you clear the urgent tasks first, even if it means walking across the entire park, or do you cluster your work by location and handle the urgent ones as you pass through? Field workers reported in the Prinsenmeer case study that this visual prioritization reduced missed tasks because they could see everything at once. The app does not tell you which route to take, but it gives you the information to choose intelligently.

The map also integrates with the housekeeping status system. In housekeeping mode, markers change color based on task progress: grey for to-do, yellow for in progress, orange for ready to be checked, and green for done. A supervisor can open the map and instantly see which units are still grey at 3 PM, then reassign cleaners to those areas. This is not a feature listed on the Play Store description. It lives in the documentation and emerges from combining the map view with the housekeeping workflow.

The Offline Sync and the Email Changelog Problem

Internet connection at holiday parks is famously unreliable. The app handles this by saving all changes locally when the network drops. A worker can complete tasks, add pictures, create workorders, and update statuses without any signal. The changes sit on the device until the connection restores, then they sync automatically. This is a deliberate design choice for the hospitality industry, where parks are often in rural or remote areas. The whitepaper confirms that offline changes are saved locally and updated once the internet connection restores. Push notifications are also part of the architecture, but they only work when the device is online.

The version history is unusually sparse. The App Store shows version 2.2.25 with "Bug fixes and performance improvements." The Play Store changelog reads "Bug fixes and improvements, other as per the email sent by Maxxton." That is the entire public record of what changed. No detailed list of fixes. No mention of new features. No UI tweaks documented. The developer sends an email to customers explaining the changes, but that email is not public. This creates a transparency gap. Field workers and managers cannot look at the changelog and know what was fixed. They have to wait for an email that might never reach them if they are not on the right distribution list. The app's update behavior is essentially opaque to the end user.

The absence of detailed version notes is not unusual for enterprise apps, but it stands out because the app is explicitly for Maxxton customers only. Those customers pay for the software. They might expect more than "bug fixes" as a summary. The Apple App Store page shows the app has not received enough ratings to display an overview. That suggests limited user engagement with the store listing itself, which reinforces the idea that most users download it once and never visit the store page again.

The Login Flow and Permission Structure

Logging in requires the concern code, which is a three-letter abbreviation for your organization. For example, if your Maxxton domain is abc.maxxton.net, your concern code is ABC. The app uses the same credentials as the main Maxxton Software. But permissions are not automatic. A user must contact support to enable access. This is a controlled rollout mechanism. It prevents unauthorized employees from seeing workorders they should not see. It also means a new field worker cannot simply download the app and start working. Someone in the back office has to flip a switch first.

Once logged in, the profile section allows language changes and location selection. The help section lists icons and their definitions, which is useful for new users. The workorder dashboard shows all tasks for the selected location. The calendar filter lets you view workorders with a start date after the selected date. The list view includes sorting options by walking route and priority. The priority order is baked in: arrival times (for changeovers) come first, then departures, then stays. This matches the operational reality of holiday parks, where incoming guests take priority over everything else.

The workorder detail view includes an "On hold" button. This is for situations where a repair cannot be completed because parts are missing. The worker can put the task on hold, and it will stay in the system until the parts arrive. This prevents tasks from being forgotten or marked complete when they are not actually done. It is a small feature, but it speaks to the app's focus on real-world maintenance workflows.

The Permission Request That Is Not Listed

The Play Store page does not list any permissions. That is unusual for an app that uses Google Maps, the camera (for adding pictures), and local storage (for offline sync). The App Store page shows that data may be collected and linked to the user's identity, including user content and identifiers. But the specific permissions – camera, location, storage – are not displayed on the Google Play listing. This might be a regional display issue, or it might mean the permissions are requested at runtime and not listed on the store page. Either way, a field worker installing the app will be prompted for camera and location access the first time they try to add a picture or open the map view.