The platform
One operating record, and every view onto it.
Meridian is built on a small number of shared pieces rather than a separate system per asset type. Learn how one asset works and you already know the rest.
The building blocks
Shared pieces, not six separate systems.
A work order on a yacht and a work order on a property behave the same way. That is what makes a mixed portfolio manageable by a small team.
Asset
The yacht, aircraft, property or vehicle, with its identifiers, home base, current location and assigned lead.
Operation
A unit of work: a service, a movement, a renewal, a document request, an approval. Everything else hangs off this.
Person
Crew, staff and office team, with their assignments, contracts and certification dates.
Vendor
A service provider, invited to the jobs they are doing and scoped to those jobs alone.
Document
A certificate, policy, quote or invoice, attached where it belongs and tracked if it expires.
Expense
What a job cost, recorded against the asset in the currency it was incurred in.
Connected by default
Open one job and its whole context is already there.
No cross-referencing between a spreadsheet, a folder and an email thread to reconstruct what is happening.
Operations
The board every morning starts from.
Every operational item across every asset, ranked by what needs attention, with the assigned lead and the reason anything is blocked. Open any item below to see the record behind it.
Views
Three ways to look at the same work.
The operations register is one set of data. How you read it depends on whether you are triaging today, planning a month, or checking a single asset.
Board
Work grouped by what it needs: attention, movements, work orders, waiting on someone.
List
Everything in one sortable table when you want to work through it in order.
Timeline
Work plotted forward, for seeing where jobs collide before they do.
Alongside these, a forward view shows what is coming as a calendar, an agenda or a longer-range outlook, so renewals and movements are planned around rather than reacted to.
Workflows
What the team does with it.
Maintenance and servicing
Set service schedules by date or by usage (engine hours, kilometres, airframe hours) and Meridian raises the job when either threshold is reached first. Log what was done, what it cost, and which vendor did it, against the asset’s own history.
Tasks and approvals
Raise a task or work order, assign a lead, and track it through open, scheduled, waiting, blocked and done. Work that needs the principal’s sign-off goes to an owner approval and waits there, visibly, instead of stalling in someone’s inbox.
Schedules and obligations
Registrations, surveys, certificates, insurance renewals and recurring bills all carry due dates. See them as a calendar, an agenda or a forward view, so a lapse is something you scheduled around rather than discovered.
Documents and records
Store certificates, policies, quotes, invoices and manuals against the asset or the job they belong to. Documents with an expiry date are tracked, so a certificate that is about to lapse becomes an action rather than a surprise.
Crew, staff and vendors
Keep crew and staff assignments, contracts and certification expiries per asset. Invite vendors to the specific jobs they are doing: they receive the work order, submit quotes, post updates and close out, without access to anything else.
Owner reporting
The operations board is the current position at any moment: what is open, blocked, waiting and scheduled, with spend tracked per asset in the currency each cost was incurred in. Each asset can export a handover pack covering its record. Scheduled written owner briefs are in development.
See it against your own portfolio.
A walkthrough mapped to the assets and the team you actually run, not a generic tour.