Manage basecamps, temporary facilities, teams, and site services from one platform.
MX can manage the operational life of a temporary site — not just track tasks. Intake, NFC wristbands, beds, meals, laundry, issue QR codes, asset records, dashboards, and SITREPs. Run the whole camp on MX, or turn on only the parts a given camp needs.
Manage the whole site — not just the tasks.
From stand-up to demobilization: the people, the services, the assets, and the site itself.
From a yard full of assets to a working camp.
Yard management is usually the part a basecamp provider already has in hand — inventory, condition, readiness, all on home ground. What gets messy is the transition: turning a headcount into a camp, and getting power, HVAC, food, habitation trailers and sanitation mobilized, transported and set up inside the time allowed.
Size
Start from a headcount. MX can size the camp's space and asset needs from standard rules of thumb, refined with your own experience over time — or you specify the requirements directly.
Match
Requirements are mapped against your in-house asset inventory, and the shortfalls are identified: what has to come from third-party suppliers and contractors.
Move
Assets are tracked from the yard — yours or a supplier's — to the site, with ETAs that keep updating. A delivery that puts the timeline at risk shows up early, not on the day.
Hand over
On site, progress is updated from mobile as each item is installed, secured, and ready for operation, through to handover to the relevant authorities.
Badged and operational in minutes.
Drivers, technicians, contractors, vendors, and visitors all hit MX the same way — a controlled intake that captures who they are, what they can do, where they go, and how they will be tracked on-site. From the moment they hold a badge — an NFC wristband, a printed card, or one on their phone — they are operational, and it scans for site access, meals, laundry, and forms.
NFC wristbands & badges
A wristband with an NFC tag that is simply scanned. The wristband is the identity — no app, password, or login. Each one is scoped to what the person needs: full residency, or just meals or laundry.
Badges before arrival
Badges can be pre-assigned and sent straight to a person's phone before they arrive — or pre-printed, if the site prefers a card. Hours of gate-side admin are done before day one.
Companies & contractors
Vendor records carry their own roles, certifications, and access scope.
Crew rosters in bulk
When a hundred people arrive on day one, the crew roster is uploaded from a spreadsheet and duplicates against people already on record are caught automatically. Each person then picks up the same flow at the badge.
Site movement audit
Every gate, kitchen, laundry, and zone scan logged. Where everyone is, all the time.
Beds. Meals. Laundry. Issues. Access.
The operational details a basecamp lives or dies by — managed in MX, not on whiteboards and clipboards. Turn on what a given camp needs and leave the rest off.
Thousands of meals a day, on patchy signal.
A basecamp feeding thousands of people a day, in a place where the phone signal cannot be relied on. This is how the meal count stays complete, and stays auditable.
Every party manages its own.
A basecamp is rarely made up of a single contractor, with a mix of prime and subcontractors responsible for different functional areas within the camp. Each party on site — provider or client, prime or subcontractor — can be managed directly via MX's contractor portal.
↳ Same permission model as the rest of MX. A company sees its own allocation and its own people, and nothing of another's.
Command sees the whole site.
MX rolls up the activity of every gate, kitchen, laundry, asset, issue, and crew into the operational dashboards command actually uses — and into SITREP packages ready for the daily brief. The same picture spans several camps, and goes out to the clients and subcontractors who need it.
People on site
Staff, occupants, and day users counted separately — live from gate scans, with headcount by zone. Audit-retained.
Requested vs operational
The capacity the client asked for against what is actually up and running.
Anyone outside a zone
Out-of-zone scans, flagged to command as they happen.
Bed occupancy
Assigned, available, projected, off-boarded today.
Meals served
Today's totals at a glance, with anomalies surfaced.
Open laundry
What is still outstanding, and anything in dispute.
Open & blocked issues
Maintenance, facilities, access, IT — in one view.
Asset condition
Generators, water, sanitation. Inspections + history.
Daily SITREP package
Auto-assembled at 18:00 for the operational brief.
Several camps, one platform
Run and monitor more than one basecamp from the same platform — each site with its own picture, and command able to see across all of them.
Shared, not rebuilt
Clients and subcontractors are given the part of the live picture that is relevant to them, instead of a separate report someone rebuilds by hand.
What changes on site.
Less time spent counting, chasing, and reconciling — and a record of the camp that holds up afterward.
The operations a basecamp serves.
A site is stood up because there is work to do around it. MX runs the response and the recovery from the same platform as the camp.
Emergency management
Rapid deployment, field accountability, situational awareness for the response phase.
Open →Disaster recovery operations
Intake, dispatch, evidence and audit for the long phase after the response.
Open →MX+ Mobile
The app on every device at the gate, the kitchen and in the field — offline-first.
Open →See MX on
a camp like yours.
Tell us about the camps you run, and we will show you the parts of MX that fit them.