Home / Backflow Operations Platform

BACKFLOW OPERATIONS PLATFORM / STRATAWORKS

Backflow Testing Software
Built for the Work.

Run customers, service locations, assemblies, testing, schedules, routes, invoices, reporting, and compliance workflows from one system built around the way backflow companies actually operate.

ONE CONNECTED OPERATION

RECORDSCustomers + assemblies
FIELDSchedule → Route → Test
OFFICEReport → Invoice → Submit
Workflow overview

Available nationwide · Strong focus on South Carolina, North Carolina & Georgia

01 / The operational gap

The test is one step.
The business is the whole workflow.

Spreadsheet duplication, disconnected scheduling, and scattered customer and assembly history make even familiar work harder to coordinate. Manual route planning adds another handoff before the technician reaches the site.

Then come paper or PDF forms, report handling, invoice follow-up, and municipality submission tracking. When the office and field work from different records, the gaps follow the job.

Bring the record and the next action together.

02 / From first record to retained history

Follow the work.
Keep the context.

A backflow management software workflow built around the assembly, the visit, and everything that follows.

  1. 01

    CUSTOMER + LOCATION

    Start with the customer and the place you service.

  2. 02

    ASSEMBLY

    Keep each device connected to its location and history.

  3. 03

    SCHEDULE + ROUTE

    Organize upcoming work and technician routes.

  4. 04

    TEST

    Capture the field test against the right assembly.

  5. 05

    REPAIR / RETEST

    Carry follow-up work through to the next test.

  6. 06

    REPORT / FORM

    Prepare reports and configured jurisdiction forms.

  7. 07

    INVOICE / PAYMENT

    Connect completed work with billing and receivables.

  8. 08

    SUBMISSION + HISTORY

    Track configured submissions and retain the record.

Repair and retest steps apply when needed. Forms and submissions depend on configured jurisdiction requirements.

03 / What the platform handles

The field and office.
Working from one system.

01

Customer & assembly records

Keep customer records, service locations, assemblies/devices, and recurring test history connected. Find the context for a visit before the work begins.

02

Testing & field workflow

Give technicians a workflow for testing, repairs, and retests, with the assembly record and prior work close at hand.

03

Scheduling & routing

Plan upcoming testing, assign technicians, and organize routes. Backflow scheduling software and route planning belong alongside the work they support.

04

Forms & submissions

Manage reporting, municipality forms, and submission workflows where configured. Jurisdiction-specific requirements determine the forms and submission steps available.

05

Invoicing & receivables

Move from completed work to invoices, receivables, and payments. Keep billing follow-up connected to the operational record.

06

Search & office operations

Use operational search to find customer, location, assembly, and work records. Give the office a shared view of what the field is handling.

07

Roles, controls & auditability

Separate office and field roles with operational controls and audit history that help teams understand who did what.

08

A verified import starting point

Bring customer records through the verified Jobber customer CSV import workflow. Other data and migration needs can be reviewed during your demo.

04 / Built for real backflow operations

For the people
who keep the work moving.

From owner-operators to multi-technician teams, the work needs continuity between the next appointment and the last test.

05 / Nationwide reach. Regional focus.

National platform. Southeast-first experience.

Available nationwide with a strong focus on South Carolina, North Carolina, and Georgia.

Backflow compliance software needs to account for the jurisdiction behind the work. Municipality-specific form/submission workflows depend on configured jurisdiction requirements. We can review the municipalities and forms your team works with during a demo.

06 / Common questions

Before the demo.

What is backflow testing software?

It is software built around the records and work of a backflow testing business: customers, locations, assemblies, tests, schedules, reports, and billing. StrataWorks connects these in one operations platform.

Can this replace spreadsheets and generic field-service tools?

The platform brings backflow records and workflows together so teams can move away from spreadsheet duplication and disconnected tools. Your demo is a chance to compare your current process with the platform and identify what fits.

Does it handle backflow test forms?

Yes. The platform supports test reporting and municipality-specific forms where the required jurisdiction mappings are configured. We can review your form requirements during the demo.

Can technicians use it in the field?

Yes. Technician workflows support field testing and follow-up work, with office and field roles connected to the operational record.

Does it handle scheduling and route planning?

Yes. Scheduling, technician assignments, and route planning are part of the platform, alongside customer, location, and assembly records.

Can it handle invoices and payments?

Yes. The platform includes invoices, receivables, and payment workflows so billing and follow-up stay connected to the work.

Does it support municipality submission workflows?

Yes, where configured. Municipality-specific form/submission workflows depend on configured jurisdiction requirements. Bring the jurisdictions you work with so we can review the fit.

Is it available outside South Carolina?

Yes. It is available nationwide with a strong focus on South Carolina, North Carolina, and Georgia. Municipality requirements still need to be reviewed for your service area.

Can data be imported from another system?

A Jobber customer CSV import workflow is verified. If you use a different system or need additional records moved, we can review the export and scope the migration; other automated imports are not promised.

07 / See it in context

Bring your workflow.
See how it fits.

Tell James about your team, test volume, and the work you want to improve. He will follow up by email to arrange a demo.

No mailing list. Your information is only used to respond to this demo request.