2026.11.04November 4, 2026

Partner lead intake, budget execution limits and a firmer grip on who owns a task

This release opens lead and project intake to integrated partners, so demand captured outside Sodtrack lands as a tracked lead with its qualifying answers and assigned provider. Budget execution hours can now be capped per account, and task access is governed by who created or owns the work rather than by where the task was raised. Sign-in, sign-out and request handling were hardened across every app, and lists and detail cards now look and behave the same wherever you are.

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

Lead intake and tracking for integrated partners (Platform API)

New

Demand captured in a partner's own channels can now flow into Sodtrack as a fully formed lead.

Leads created and read by an integrated partner. An integrated partner can now create leads and then follow them: the lead detail, its qualifying questions and answers, status history, the customer and user behind it, the service and shopping cart, and any linked project with its attachments and dynamic fields. Both sides see the same record without anyone re-keying it.
Provider assignment driven by the answers given. An incoming lead is assigned from the qualifying answers, or from a provider named directly on the request. If the named provider cannot take the work, the lead is rejected at creation with the reason, instead of being accepted and quietly stranded.

Budget execution hours, capped and explained (Admin, Network Web, Customer Web, Platform API)

New

A maximum duration for a budget execution. Budget executions are now checked against a maximum number of hours when they are saved, reviewed and executed, so an unrealistic duration cannot reach approval. The limit is set per account as a controlled rollout, so it only applies where it has been configured.
The reason shown, not just a refusal. When an execution exceeds the allowed duration, the customer-facing screens now show the exact reason returned rather than a generic failure. The hours can be corrected and resubmitted on the spot.
Global budgets protected from local edits. Administrators scoped to a single network can no longer edit budgets that belong to the whole account. Shared pricing stays owned by whoever maintains it centrally.

Who can open, change and own a task (Admin, Network Web, Provider Web, Platform API)

Improved

Creator or owner, wherever the task was raised. A task can now be opened and updated by the person who created it as well as by its owner, so work is no longer locked behind a single account. The same rule applies from leads, incidents, bookings and projects.
Network owners kept inside their network. A task owned by a network can only be assigned to that network or one of its children, so responsibility never lands outside the structure that has to deliver it. Providers keep the ability to assign a task to themselves when raising it from a lead.
A simpler set of task statuses. The interim status used while a task waited for an owner has been removed, so the status list reflects only states that mean something operationally. Existing tasks read correctly under the simplified set.
Task detail with information tabs. Task details were redesigned around shared cards and tabs, including an additional information tab, with the status control, update list and cancellation behaving identically in every app. Update counts are hidden when there is nothing to show.

Projects, quicker to create and filter (Admin, Network Web)

Improved

Create and edit a project without leaving the list. Project creation and editing now open as a side panel over the list instead of sending you to a separate page. You keep your place and your filters while setting a project up.
Applied filter chips and proper empty states. The project list now shows the filters currently applied as removable chips, and a filtered search with no matches explains itself instead of showing a blank table. Project dynamic fields read consistently across the screens that use them.

Lead detail, easier to read (Admin)

Improved

Responsive lead cards. The lead record was reorganised into cards that reflow on narrower screens, so the customer, the service and the lead's own fields stay readable at any width.
Correct outstanding amounts. Payment request amounts on a lead are now read as numbers before being totalled, so the remaining balance is accurate instead of being distorted by formatting.

Booking availability and work order quotas (Customer Web, Platform API)

Improved

Availability looked up against the exact booking. Available dates and times for a self-managed booking are now requested for that specific booking, so the slots offered always belong to the job being rescheduled.
Quotas respected across time ranges. Work order quota checks now account for full time ranges and for usage already scheduled, so availability reflects the capacity genuinely left rather than only what has been completed.
No double acceptance of the same request. When two acceptances of the same job request arrive at the same moment, only one is applied. The job can no longer be assigned twice over.

Area assignment and coverage filters (Admin, Network Web, Platform API)

Improved

Areas already assigned are shown, not hidden. The area selector now lists areas that are already associated and marks them as unavailable, instead of leaving them out. You can see why an area is not offered rather than wondering where it went.
Custom polygons no longer mask areas. Areas overlapped by a custom coverage polygon remain visible for assignment, so a provider's footprint can still be built from the standard areas underneath.
Long filter lists scroll smoothly. The variant and provider filters on the coverage screens now load further options as you scroll, so large catalogues and large networks can be filtered without hunting.

Sign-in, sign-out and request hardening (Admin, Network Web, Customer Web, Provider Web, Platform API)

Improved

Signing out really ends the session. Signing out now withdraws the stored session credentials before you leave, so a browser left behind cannot be used to resume the session.
One sign-in flow with clearer errors. All four apps now share the same authentication flow and report failures in the same terms, so a wrong password, an expired session and a blocked account each read as what they are.
Apps cannot be framed by another site. The web apps now refuse to be embedded inside another page, and responses from the platform carry additional browser-level protections. This removes a class of attack that tricks users into clicking something they cannot see.
No internal detail in failed requests. Unexpected failures now return a plain, safe message instead of leaking system detail to whoever made the request, while support keeps the reference needed to trace the case.

Everyday fixes and polish (all apps)

Improved

Resizable, better-behaved tables. Tables across Admin and Provider Web can now be resized column by column and show a proper loading state while they fetch, so wide records can be read without horizontal scrolling.
The same detail card everywhere. Detail cards in Customer Web, Provider Web and Network Web now match the ones in Admin, including in-card actions, so booking basic information and customer information read the same wherever you open them.
Workflow information in a side panel. Workflow information, checklists and the client signature on a booking now open as a side panel with their own tabs, so they can be reviewed and completed without losing the booking behind them.
Consistent wording for companies and individuals. Screens that refer to providers now use the same combined wording for companies and individual providers in every app, including the customer-facing ones. Long destination labels on a booking are shortened instead of overflowing their button.

Ready to see Sodtrack in action?

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