Fifteen modules, one database, one record.
A field operation does not split into separate tools. The customer request, the technician’s work, the part taken from stock, the signed order and the invoice are the same record seen from five different jobs. That is what the platform does.
Where to start
The fifteen modules are grouped into areas. Each page describes what the screen actually does, in the words your teams use.
Operations
Requests, tickets, assignment, contractual deadlines
See the module → 02Field mode
The technician’s round, on their phone
See the module → 03Sites and assets
Geolocated sites, equipment, access instructions
See the module → 04Procedures
Work instructions, critical points, compliance
See the module → 05Proof
Signed work order, electronic signature
See the module → 06Commercial
Customer records, quotations, invoices
See the module → 07Stock
Parts, movements, issues tied to interventions
See the module → 08Scheduling
Appointments, team workload, field agents
See the module → 09Oversight
Dashboard, reports, knowledge base
See the module → 10Administration
Users, permissions, settings, audit log
See the module →The fifteen modules installed
Not all of it is useful to everyone. A subcontractor who does not invoice directly switches invoicing off; an operator who does not issue quotes never opens quotations. Modules are enabled per profile.
| Module | What it covers | Detailed on |
|---|---|---|
| Dashboard | Counters by status, overdue work, team workload, recent activity | oversight |
| Customer records | Customers, clients, contacts, full history | commercial |
| Projects | Grouping work under a site build or a framework contract | commercial |
| Quotations | Quotes, sending, chasing, electronic signature | commercial |
| Invoicing | Invoices, credit notes, payments, reminders | commercial |
| Service and work | Tickets, qualification, assignment, contractual deadlines | operations |
| Work procedures | Instructions by type of work, critical points, expected values | procedures |
| Work order | Visit report, dual signature, handed over on site | proof |
| Site register | Geolocated sites, equipment, access instructions, power | sites |
| Field mode | The technician’s round on a phone, navigation, calling | field-mode |
| Scheduling | Deadlines, workload by team and by technician | scheduling |
| Appointments | Slots agreed with the customer, internal reminders | scheduling |
| Field agents | Technicians, teams, availability, contact details | scheduling |
| Stock and movements | Parts, receipts and issues, consumption tied to work | stock |
| Administration | Users, permissions, settings, audit log, notifications | administration |
Rollout is scoped. We switch on the modules that suit the customer’s trade and the stage they are at; the rest stay available and can be enabled later, with no data migration and no second go-live. Nobody starts on fifteen modules at once, and nobody should.
Audit log and notifications run across everything. Every write is recorded, with who, when, and the value before and after. Mentions in comments alert the person concerned inside the platform, without depending on any outside messaging service.
What every module shares
One database per customer
No synchronisation between tools, no exports to reconcile. A site reference means the same thing everywhere: on the ticket, on the order, on the invoice, in stock.
Permissions by role and by scope
Dispatch, technician, project manager, management, read-only. What a role may not do is not greyed out: the form is never produced at all.
Settings that belong to you
Statuses, types of work, equipment classes, contractual deadlines, document templates: all configured without touching the code.
Printouts ready to hand over
Work order, customer report, quotation, invoice. Sober layout, legible in black and white, printable from a phone.
A trace of everything
Every status change, every assignment, every signature is timestamped and named. History does not get rewritten.
No outside dependency to run
The platform calls no third-party service to function. If the office link goes down, it is your servers that decide, not a vendor.
See the platform run on your own cases
An hour is enough: you open a request, assign it, close it and print the signed work order. Then we look at how your operation fits in: your customers, your sites, your contractual deadlines.