Home / Backflow Operations / Report submission

Fill it. Review it.
Let us submit it.

The test is finished. Your evening shouldn’t disappear into copying readings onto forms and emailing reports. StrataWorks connects the field results to your configured form, then sends eligible approved reports through your email submission workflow.

Watch the product tour

How a backflow report reaches the authority

  1. Keep the readings with the assembly.

    Record the test against the correct customer, location, and assembly. The office can review the same information the field team entered.

  2. Fill the configured municipality form.

    Use the job and test information to populate the mapped report. Check the form version, assembly details, readings, signatures, and any required fields before approving it.

  3. Review and release the report.

    The report needs a completed PDF, approval, a passing eligible result, and the configured municipality recipient. Your business’s payment rules also apply; any permitted payment override needs approval. A draft or failed test is not automatically sent as an approved passing report.

  4. Send it through the configured email workflow.

    The platform emails the approved report to the municipality’s configured submission address. You don’t have to download the PDF and compose a separate email for each eligible report.

  5. Keep the report and submission history.

    Follow the work from review to sending, with the completed report and submission record alongside the job. A sent email is not proof that an authority has accepted the test. Follow up on rejections or additional requirements.

Your municipalities. Your custom forms.

StrataWorks is built for teams nationwide. You can add municipalities and custom forms in the app, including authorities outside the supplied form library. You aren’t limited to a short list of states.

Start with the authority’s current report. Add the municipality and form, configure the field mapping, and check a sample populated PDF before using that form for live jobs. Custom forms need setup and validation; uploading a PDF does not establish that its fields are correctly mapped.

Check these details before your first submission

  • The current form and any required signatures, attachments, or tester credentials.
  • The accepted submission method and current recipient address.
  • Your company’s approval and payment rules.
  • A sample report whose customer, assembly, and readings match the job.

The email workflow is for authorities that accept email submissions. If your authority requires a portal, fee, separate account, or another process, confirm that requirement with us before subscribing. National availability does not mean each authority accepts the same form or delivery method.

One workspace for the steps around the report

Customer records, assemblies, schedules, field results, reports, and invoices stay connected. The $300 monthly plan includes up to five staff logins for your office and field team, plus setup assistance. Custom imports, new forms, and optional provider services are scoped separately before work begins.

Bring one real workflow.

Tell us which authority receives your reports and which form it requires. We can review the fit before you subscribe. Please keep customer records and sensitive information out of the initial request.

Ask about your formsSee pricing and setup