In a separate schedule
The intervention is placed in a shared calendar, while the same person is committed to a fixed-price project. Nobody sees the conflict until it costs a milestone, or an intervention postponed the day before.
Solutions Intervention management and scheduling
Intervention management almost always stumbles on two moments. Before: you schedule on a calendar that ignores the workload already planned on projects. After: you chase a signed paper slip, or a confirmation email. In pylotik, the intervention is scheduled against everyone's real workload, attached to its contract, and accepted through the client's signature: on mobile, in their portal, or by a physical signature.
The problem
An intervention gets lost in three places.
The technical act is rarely at fault. What costs is what surrounds it.
In a paper slip
The intervention slip is signed on site, photographed, sent, re-keyed. It arrives late, sometimes never, and invoicing waits for a document nobody can find when it is time to produce it.
In the contract count
How many days have been used on the maintenance contract, how many remain? The answer lives in a spreadsheet the client has never seen, and which they dispute the day they discover it.
How it works
From the catalog to client approval.
An intervention always has a frame: a contract, a technician, a date, a place. It is this frame that pylotik holds from end to end.
- A catalog per contract Each intervention type has its label, default duration, reference and daily rate. The contract says which are authorized, and who can carry them out: named people, a team, or the project team.
- Scheduling against real workload The intervention is placed by the half-day, morning or afternoon, in a people-by-days grid where absences are already greyed out. The contract, the catalog, the person, the purchase order and the remaining volume are checked at the time of scheduling.
- Workload released, not overwritten If the technician is already planned on a project, the half-day is not taken from them silently: it is released through the same circuit as leave, with the agreement of their manager and the project managers concerned, who can also impose it.
- A stated place At the client's or remote, with the address when needed. The intervention appears in the technician's calendar, in the project's and in the client's, on the supplier side.
- A declared completion The technician declares the intervention completed, from the web or from their phone, and names who approves it on the client side.
- An acceptance signed by the client The client signs, or refuses by giving their reason. A refusal sends the intervention back to its author to be presented again, rather than remaining pending.
Scheduling interventions and their signed acceptance make up a module, available from the Business tier and billed separately from the seat: only the designated technicians count. Maintenance contracts, for their part, are in the core. The client who approves, the manager who releases workload or the people who sit on a contract's committee do not need it. The details are on the pricing page.
The client's role
No paper, and no email to chase.
The acceptance of the intervention goes through the client's signature, in three ways. On site, the technician hands over their phone: the client enters their name and signs on screen, or refuses with a reason. Remotely, the person designated on the client side finds the intervention in their portal, among their other approvals, and answers the same way. Or the client signs physically, and the acceptance is recorded. Their access is free, like all client access.
What the client sees is the intervention record: its number, status, provider, contract, intervention type, technician, date, address and description. They see neither your teams' workload nor your costs. And because each approved intervention is deducted from the contract, the volume used that you read is the one they read: this is the principle of operational commitment management, one shared truth instead of two spreadsheets.
Limits
What pylotik intervention management does not do.
Better to know it before the demo than during it.
It is not a roaming field tool
No route optimization, no geolocation, no offline form, no photo attached to the intervention. If your business is serial technical intervention on a fleet of equipment, a CMMS or field service management software will serve you better: see CMMS and maintenance contract.
It is not a qualified signature
The signed acceptance in pylotik is traced: the client's name, their drawn signature, the date, and how they answered. It is neither an advanced electronic signature nor a qualified signature within the meaning of the European eIDAS regulation. It does not replace a deed that would require one.
It is not an invoicing tool
Approved interventions feed the contract's payment schedule, fixed price or time and materials, but pylotik does not issue invoices: it sends the invoicing orders to your ERP, through a connector built according to your needs, and the ERP produces the invoice.
It is not an incident tool
Handling incidents as they come, with ticket queues and service levels, belongs to a support tool or to IT service management (ITSM), as the project ticketing or ITSM guide details. pylotik steers the interventions of a contract or a project, not the incident queue of a support center. Each intervention stays attached to its contract, with its date, its status and the client's decision: see the cycle of a maintenance contract.
Frequently asked questions
What we are asked about interventions.
Does the client need an account to approve an intervention?
No. When present, they sign on the technician's phone, or physically. Remotely, they sign from their client access, which is free on every tier.
What happens if the client refuses the intervention?
They must give a reason. The intervention goes back to its author with that reason, to be corrected and presented again. The refusal stays attached to the intervention, with its date.
Can you schedule an intervention on someone already taken by a project?
Yes, but not silently. The half-day already planned on the project is released with the agreement of the manager and the project managers concerned, as for a leave request. The conflict is settled before the intervention, not after the missed milestone.
Are interventions billed at fixed price or on time and materials?
The contract says. Under fixed price, the contract has its own payment schedule; under time and materials, each approved intervention is valued at the rate of its intervention type. In both cases, the volume used can be read on both sides.
Can an intervention be approved from a phone?
Yes. The technician declares the intervention completed and has it approved from the mobile app, and the client can approve from theirs. The mobile app is a web app, which is added to the phone's home screen.
Next
Going further.
- Maintenance contract management: the frame in which interventions are counted.
- The mobile app: declare a completed intervention and have it approved on site.
- The client portal: what your client sees, approves and never sees.
- The product tour: projects, contracts, teams and finances in the same tool.
- The pricing: seats, free client access and modules.