Back to Release Notes
2026.11.11November 11, 2026

Alerts for leads, a rebuilt project detail, and tasks that no longer need an owner

Alert rules can now watch leads and fire on their status, their own fields or the service variant behind them, so demand that stalls is surfaced instead of discovered late. Project details were rebuilt around a header, information cards and tabs for stages, notes and attachments, and tasks can now be created without an owner and edited straight from their detail. Work orders carry acquisition and external reference information, outbound automation rules can be limited by conditions, and the lead record now reads the same in every app.

Products updated: Admin · Network Web · Customer Web · Provider Web · Platform API

Alerts now watch leads (Admin, Platform API)

New

Alerting is no longer limited to work in the field: a lead can now raise an alert of its own.

  • Lead alert rules. Alert definitions can now be created against leads, alongside the entities already supported. Rules are configured in the same rules screen, so there is nothing new to learn.
  • Rules on status, lead fields and service variant. A lead alert can trigger on the lead's status, on the value of one of its dynamic fields, or on the service variant behind it. That covers both commercial follow-up and service-specific attention without needing a separate report.
  • Alerts raised automatically. When a lead matches an active definition, the alert is raised and recorded automatically against that lead. Teams see it in the same place as every other alert, with the lead it came from.

Project detail, rebuilt (Admin, Network Web)

Improved
  • Header and information cards. The project record now opens with a clear header and information cards for its basic and additional information, instead of one long form. The same layout is used in Admin and Network Web.
  • Stages with their own tasks view. The stages tab was redesigned and each stage now opens its tasks in a side panel, so you can work through a stage without losing the project behind it. Tabs adapt to the information a project actually has.
  • Notes and attachments in one place. Notes and attachments were reorganised into a single tab that reads the same as the rest of the record. Files and comments are easier to find while a project is in progress.
  • Editing from the detail. Basic information, dynamic fields and the assigned provider can now be edited from side panels on the project itself. You keep your place in the record while changing it.
  • Booking link shown only to its owner. In Network Web, the shortcut to a booking's detail from a project is hidden when the booking does not belong to you. The screen no longer offers an action it cannot complete.

Tasks without a forced owner, editable from the detail (Admin, Network Web, Provider Web, Platform API)

Improved
  • An owner is now optional. Tasks raised from leads, incidents and projects can be created without naming a responsible person, so work can be captured the moment it appears and assigned afterwards. The owner field stays available whenever you do know who should take it.
  • Editing straight from a task. A task can now be edited from its own detail in a side panel, with unchanged values preserved as they were. Lists refresh on their own after a change, so you no longer reload to see the result.
  • An owner cannot be cleared by accident. Updating a network task can no longer remove an owner that was already set; the assignment has to be changed deliberately. Responsibility stays with someone at all times.
  • Update counts and creators on the detail. Task details now show how many updates a task has received and who created it, and tasks or updates with no recorded creator read cleanly instead of showing a gap.
  • Provider task actions match reality. In Provider Web, a provider raising a task can assign it to themselves or leave it unassigned, updates are limited to tasks still pending, and cancellation was removed. Self-assignment when raising a task from a lead works again as expected.
  • Task activity recorded. Creation, updates, status changes and owner changes on a task are now recorded as activity, so the history of a task explains itself later.

Lead detail, the same record in every app (Admin, Network Web, Provider Web)

Improved
  • Customer and service cards. The customer and the service behind a lead now have dedicated cards in Admin, Network Web and Provider Web, so the essentials read identically wherever the lead is opened.
  • State flow at a glance. The lead detail layout was tightened and the state flow card makes the lead's progress visible without scrolling through history.
  • Provider Web lead brought in line. Provider Web now uses the same tabs, cards and action restrictions as the other apps, including attachments, the linked booking, budget executions, notes and the lead's own fields. Basic information loads with a proper loading state rather than appearing in pieces.

Work orders with acquisition and reference details (Admin, Network Web, Platform API)

New
  • Acquisition and external reference on a work order. Work orders can now carry an acquisition identifier and an external reference, so a job created in Sodtrack can be matched to the purchase or record it came from.
  • Reference entry limited by permission. The external reference is only offered when creating a work order to users whose permissions allow writing it, and stays hidden otherwise. This keeps the creation form short for everyone else.

Automation rules that only fire when they should (Platform API)

New
  • Conditions on outbound rules. Rules that call an external service can now carry optional conditions, and rules whose conditions do not match are skipped. Integrations receive only the events that genuinely concern them instead of everything of that type.

Bookings, incidents and availability fixes (Admin, Network Web, Provider Web, Platform API)

Improved
  • Availability searches no longer fail on an address. Searching for available dates and times no longer breaks when the address attached to the job is incomplete or unusual. Scheduling continues instead of stopping with an error.
  • Origin address on the booking detail. The booking detail in Admin now returns and shows the origin address, so jobs that move between two places read in full.
  • Partial attachment uploads on an incident. Raising a booking incident now handles the case where only some attachments upload, and missing values no longer break the form. The incident is saved with what went through and tells you what did not.

Record access, accuracy and speed (Admin, Network Web, Provider Web, Platform API)

Improved
  • Form answers stay with their record. Saved form answers, fields and options can now only be read or changed by whoever owns the record they belong to. A snapshot from one record can no longer be reached through another.
  • Stricter checks on list and search requests. Identifiers, dates and sorting options sent from list and search screens are now validated before being used, and only known sort options are accepted. Malformed requests are refused cleanly rather than returning unexpected results.
  • Consistent dates and quicker lookups. Dates and times are now handled on a single consistent clock across the platform, so timestamps read the same for everyone. Booking detail, address and user lookups return noticeably faster.
  • Steadier sign-in. The credentials used behind sign-in are now reused until shortly before they expire, and a slow response can no longer leave a sign-in hanging. Logging in is more reliable at busy moments.

Everyday polish (all apps)

Improved
  • Date pickers keep what is already selected. Calendars no longer discard values that fall on disabled dates, so an existing date stays visible while you choose a new one. This affects every app that schedules work.
  • Provider lists that load as you scroll. Provider selection in Network Web now loads further results as you scroll and can be navigated with the keyboard, so large networks can be worked through quickly.
  • Consistent tooltips and controls. Tooltips, list rows and form labels were aligned on the shared design across Admin, Network Web, Customer Web and Provider Web. Provider Web in particular now uses the shared components throughout, so it looks and behaves like the rest of the platform.

Ready to see Sodtrack in action?

Book a demo and our team will walk you through the latest features tailored to your operation.