One workflow for every job
Mowing, streetlight repair and snow removal have the same stages and statuses. The manager sees what is waiting for assignment, execution or control.
NexaWorks organizes greenery, cleaning, winter maintenance, roads and lighting works. Each task goes through the same workflow: order, assignment, execution, proof, manager control and billing. The module uses the same accounts and data as NexaWaste PRO.

Mowing, streetlight repair and snow removal have the same stages and statuses. The manager sees what is waiting for assignment, execution or control.
The order goes to an authorized employee or subcontractor. Everyone only sees the work assigned to them.
The employee checks off the checklist steps, adds a note and a photo. The evidence remains in the task history.
Execution and verification are separated. Only work approved by the manager is included in the calculations.
Warehouse and equipment registers keep stock of materials and their change history.
The works are connected to a specific object, for example a lamppost or a playground. The next report is in the context of previous repairs.
The order is created in the panel or from a resident's notification. It has a job type, facility, deadline and requirements.
The coordinator assigns work to an employee or subcontractor. The task appears in his view.
The employee completes the checklist, adds a note and photo, and then reports completion.
The manager approves the result or returns the task for correction with justification.
Approved work goes into the billing period at rates. The closed period is the basis for receivables.
Repairs of surfaces, signs and sidewalks go through a common workflow with a checklist and proof. Dedicated road inspection forms are in development.
Winter services have their own job type, assignment and proof of completion. Data from salt spreaders and sensors requires an adapter.
Mowing, care and planting as orders with checklist and photo. Area costs and seasonal plan are in development.
Street-lighting faults become jobs linked to the asset and its repair history. A resident report can become a task.
Cleaning streets, squares and bus stops as orders with a checklist and proof of completion.
Playgrounds, benches, bins and bus stops are recorded as assets with work and inspection histories.
Registries of crews, shift schedules and equipment are operational. Qualifications and attendance records are in development.
Materials and equipment have an inventory with a change history. Purchasing workflows are still in development.
Checklist templates and inspection records with photos are working. Conditional fields and electronic signatures are in development.
The partner sees the assigned jobs and the approved work goes to billing. Staged billing and SLA are in development.
NexaWorks is designed as a separate product on a common engine. The scope of modules is determined in the offer, and the separation of licenses for both products will support LifeNexa CORE after connection.
Yes. The dispatcher can turn a report from the resident's portal or application into a field task. The resident can see the status of their case.
No. The photo, note and confirmation in the application are proof of completion in the system. They do not replace a qualified signature or a protocol required by law.
Choose a product and a conversation topic. The request will receive a number and go to the service center; We will respond to the address provided.