The journey of the load, from the round to the transport document

1. 1

   The round and the operator's tasks

   Today

   You plan the round, the operator runs it from the phone and the outcome comes back to the office.

   • You assign tasks from the agenda and build the round; whoever has the planning permission can have the order of the stops proposed, calculated on the straight-line distance.
   • The operator opens the round in the app, completes the stop with checklist, notes and photos, or marks it «Not done» choosing the reason with one tap: customer absent, access closed, unit not found.
   • Past stops reopen with outcome, times, checklist, notes, photos and the «Not done» reason.

   Conditions. Assigning tasks and building the round needs the planning permission; the operator app is included and each operator uses their own account.

2. 2

   The load and the delivery to the plant

   Today

   Completed tasks become a load with the EER code; the closed load is discharged to a depot or a plant.

   Today

   • The load starts from the completed tasks of the round: you pick the EER code and Toitrack gathers them into a single load.
   • The office can prepare the load even for a round completed by an operator, from «Waste loads» or from the round detail.
   • You close the load and discharge it to a depot or a treatment plant. A fully discharged load reads «Discharged»; a partly discharged one shows what is left.
   • On the plant page you keep, per EER code, approvals, contracts and analyses with expiry dates and attachments, and the disposal tariffs, with the amounts hidden from users without permission.

   Coming soon

   • The «Generate delivery» action on a completed septic task, which creates the delivery to the plant and opens the waste movement.

   Conditions. It needs the waste module. Preparing the load is up to whoever plans or to the operator of the round; discharging it, to whoever plans. To pick the EER code you must be able to read them: planners and operators see them read-only.

3. 3

   The register and the MUD

   Today

   The discharge enters the chronological loading and unloading register, and from there you get the MUD summary.

   • The register is kept per local unit and year, with the annotations still to complete in plain sight. Rectifications and cancellations are registrations of their own, with the dedicated permission.
   • The MUD summary computes from the register, per local unit and year, the declarant data and the RIF, RT and DR tables, with reconciliation checks, and downloads as CSV and PDF. You verify it with your consultant: filing and signature stay with the declarant.
   • The year's register exports as XML, CSV and PDF; the «Conservation» tab prepares the package to hand to your conservation provider.
   • The calendar in Settings > Waste reminds you of the Albo annual fee, the RENTRI contribution, the MUD, the Albo renewal and the technical manager's suitability. You tick the yearly deadlines yourself when done: Toitrack checks nothing with the Albo or RENTRI.

   Conditions. It needs the waste module. Exports and the MUD summary are for whoever plans; annotating and rectifying the register belongs to whoever has the waste-closing permission; the calendar is for administrators.

4. 4

   Transport documents and the xFIR with the RENTRI connection active

   Coming soon

   This is the piece we are completing: today you record the document on the movement, digital issuing with the RENTRI connection active is coming soon.

   Today

   • On the waste movement you attach the transport document and transcribe its number: the movement becomes «ready» and, once discharged, you confirm it with the verified weight and the return date.

   Coming soon

   • The xFIR with the RENTRI connection active: you issue it from the stock, sign it with the RENTRI portal or the official app (Toitrack does not sign on your behalf) and follow its status and notifications.
   • The incoming xFIR, the one with a third-party producer and the operations under way (transshipment, technical stop, annotations), always with the RENTRI connection active.
   • The single document for septic work (article 230, paragraph 5) pre-filled and issued from the app through ViViFIR, the virtual stamping service.

   Conditions. The RENTRI connection is turned on from Settings > Waste; until then you issue the document with your own tools and record its number on the movement. It needs the waste module.

5. 5

   Vehicle changes to report to the Albo

   Today

   When the fleet changes, Toitrack reminds you what to communicate to the Albo and by when.

   • Every change opens a checklist with the 30-day deadline: waste transport vehicle added or reactivated; vehicle with an Albo enrollment number deactivated, deleted or with a changed plate.
   • The documents to attach depend on the type: for an added vehicle substitute declaration, suitability attestation, registration document and, if it belongs to someone else, the title proving you can use it; for a plate change the attestation and the registration document; for a deactivation none.
   • You find it in the vehicle detail, on the Vehicles page and among today's priorities; on the round, a notice that blocks nothing flags a vehicle with no Albo enrollment.
   • Toitrack sends nothing to the Albo: you record what you communicated.

   Conditions. It needs the waste module. An added vehicle counts if it has a declared Albo enrollment (category or number) or septic equipment; deactivation and plate change only if it has the enrollment number. Updating the status needs the write permission on vehicles.

Register, EER codes, MUD summary and calendar are described in detail on the dedicated page. Waste and RENTRI