Describe the assemblies you test, the readings your procedure requires, and the destination for completed reports. Makeform turns that brief into an editable backflow test form for site details, assembly identification, initial and final results, repairs, gauge information, tester signoff, and office routing.
Route completed test reports to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose the closest test workflow, adjust the prompt, and send it to the Makeform builder. Each structure is an example to review against your procedure and the receiving authority's current requirements.
Prompt ready4 formats
Audience
Certified testers recording an RP or RPZ field test
Format
Mobile report with initial and final readings
Prompt size
622 chars
Brief qualitySends to builder
Example form structure
Mobile report with initial and final readings
Prompt exampleEditable in builder
Site, account, and assembly identification
Short answerFirst ask
2
Initial check and relief-valve readings
Number
3
Did any component fail its initial test?
Yes / no
4
Repair details and final retest readings
Long answer
5
Tester signoff
Signature
Suggested routing tags
Suggested
Passed
Repaired and retested
Office review
Ask for separate initial and final readings. A single result field hides whether a failed assembly was repaired and retested during the visit.
Step 1
Identify
site, account, assembly, and test equipment
Step 2
Test
component observations and initial readings
Step 3
Resolve
failure, repair, and final retest details
Step 4
Route
tester signoff, office review, and submission log
Built for field testing
A report structure that follows the actual visit.
A useful backflow report does more than mark pass or fail. It connects the right assembly to measured component readings, any corrective work, a final outcome, and the person who performed the test.
No orphaned readings
Keep the service address, device location, make, model, serial number, size, and served system beside the readings. Required identification fields reduce the chance that office staff must call the tester to determine which device was tested.
Repair fields appear when needed
Conditional logic can open parts, labor notes, repair action, and final readings after an initial failure. Passing visits stay short while repaired assemblies retain a clear before-and-after record.
Results reach the right queue
Tag submissions by authority, result, device type, or office status. Notifications can surface failed or incomplete reports quickly, while a submission log helps staff track what still needs review or delivery.
Adapt the test path
One base form for common assembly workflows.
Choose the assembly type first, then show the applicable component labels and reading sequence. Keep locally required language and thresholds under your control rather than treating one generic layout as universal.
Reduced pressure assemblies
Organize first-check, relief-valve, and second-check observations with distinct initial and final numeric fields. Include discharge or leak notes without collapsing component results into one vague comment box.
Double check assemblies
Present separate holding readings and outcomes for both checks, plus shutoff and flow observations when your test procedure calls for them. Failed components can open a focused repair path.
Vacuum breaker devices
Use labels appropriate to PVB or SVB testing, including check-valve and air-inlet observations. Conditional branches keep those questions away from unrelated assembly types.
Jurisdiction-specific reports
A water authority selection can reveal its requested account labels, attachments, or routing notes. Staff should compare the generated form with the current authority instructions before using it.
Form-building workflow
Turn your current test sheet into a field-ready form.
Start with the procedure and report fields your team already uses. Then make the form easier to complete on site without changing the meaning of the readings or implying that software determines the outcome.
Name the assembly types, component sequence, units, test reasons, and authority fields you need. Paste your own approved field labels into the prompt when exact terminology matters.
02
Separate readings from outcomes
Give each measured value its own numeric field and each component its own result choice. Add clear initial and final groups so a repair does not overwrite the original field result.
03
Add failure and repair logic
Reveal problem descriptions, parts replaced, repair notes, final readings, and retest outcomes only when relevant. Require an explanation when a test cannot be completed or a device remains failed.
04
Review before external submission
Send completed reports to the office for completeness checks and authority-specific handling. Keep submission date, reference number, response, and follow-up owner as internal tracking fields.
Paper vs generic vs generated
Choose a report method that preserves field detail.
The best format is the one your testers can complete accurately and your office can process consistently. A generated form is useful when you need structured data and conditional paths, but it still requires review against your test procedure and local instructions.
Approach
How the visit is recorded
Operational tradeoff
ApproachPaper authority sheet
How the visit is recordedTester writes identifiers, readings, repairs, and signoff on the supplied layout.
Operational tradeoffFamiliar in the field, but handwriting, duplicate entry, and office routing can add follow-up work.
ApproachGeneric digital checklist
How the visit is recordedOne set of questions covers every assembly and sends a basic pass-or-fail record.
Operational tradeoffFast to launch, but it can miss component-level values, retest history, or authority-specific fields.
Approach
Generated backflow test form
How the visit is recordedDevice choice controls the reading path; failures reveal repair and final-result sections.
Operational tradeoffStructured for routing and export, with a deliberate office review step before external delivery.
Field guide
What a backflow test form should capture.
Use these six sections as a practical starting point. The exact test sequence, terminology, thresholds, retention rules, and receiving process can vary, so align the finished form with your procedure and the current instructions for each destination.
Property and account
Connect the visit to the correct service.
Office staff need enough context to match a report with the customer, premise, and water record. Separate structured address fields from device location notes; an assembly may be behind a building, in a vault, or serving only one system at a larger site.
Customer or property name, contact, phone, and email.
Service address plus parcel, meter, account, or permit identifier when requested.
Specific assembly location, access notes, premise type, and system served.
Assembly identification
Identify the device before entering results.
Make, model, serial number, nominal size, assembly type, and orientation distinguish one device from another. Use dropdowns for controlled categories and text fields for manufacturer identifiers, with a photo option when a worn nameplate is difficult to transcribe.
Assembly type such as RP, DC, PVB, SVB, or the labels your workflow uses.
Manufacturer, model, serial number, size, orientation, and installation details.
New, existing, replaced, relocated, annual, follow-up, or other test reason.
Initial test
Give every component reading a home.
Avoid one long notes box for technical measurements. Numeric fields support consistent entry, while a nearby result choice and observation field preserve context. Labels should state the component, whether the value is initial or final, and the expected unit without embedding an unreviewed threshold.
Line or supply pressure when part of the procedure.
Separate check, relief-valve, or air-inlet readings appropriate to the assembly.
Component result, overall initial result, leaks, discharge, and unable-to-test reason.
Repair and retest
Preserve what failed and what changed.
When the initial outcome is failed, open a repair section instead of replacing the original values. Record the observed problem, cleaning or adjustment, parts used, who performed the work, and the final component readings. If repair is deferred, capture the reason and follow-up status.
Failed component, defect or observation, corrective action, and parts replaced.
Final retest values beside the original values, not over them.
Final outcome, unresolved issue, customer notification, and recommended follow-up.
Tester and equipment
Record who tested and what kit was used.
Collect the tester and equipment information required by your business or report recipient. Credential and calibration fields are records supplied by the tester; the form does not independently verify status, qualifications, equipment accuracy, or whether a report meets an authority's rules.
Tester name, company, contact, credential number, issuer, and expiration date if needed.
Test-kit manufacturer, model, serial number, and calibration or verification date.
Test date, start or completion time, tester signature, and relevant attachments.
Office and authority routing
Track the report after the field visit.
Field completion and external delivery are different stages. Add internal fields for completeness review, destination, submission method, date sent, reference number, response, resubmission reason, and follow-up owner. This creates a workable queue without claiming that delivery guarantees acceptance.
Office review status and missing-information notes.
Receiving authority, requested format, submission date, and reference number.
Response status, correction request, resubmission date, and assigned follow-up owner.
Related tools
Build the surrounding service workflow.
Connect test reporting with inspections, maintenance records, repair requests, work orders, and incident documentation using existing Makeform tools.
Practical answers for plumbers, testers, dispatchers, and office teams building a digital reporting workflow.
What is a backflow test form?
A backflow test form records the property, assembly, test equipment, measured component readings, initial outcome, repairs, final retest outcome, and tester signoff for a field visit. Testing companies may also use it to track office review and delivery to a water authority. The exact fields and terminology depend on the device, procedure, and report recipient, so a generated form should be reviewed before use.
What fields should I include for assembly identification?
Capture the service address, specific device location, account or meter identifier when requested, assembly type, manufacturer, model, serial number, nominal size, orientation, system served, and reason for the test. If a site has multiple assemblies, require a unique device identifier and location description. A photo of the nameplate and installation can help office staff resolve unclear or incomplete identifiers.
Can the form handle RP, DC, PVB, and SVB test paths?
Yes. Start with an assembly-type choice and use conditional logic to show the relevant component labels, observations, and reading fields. Keep common property, assembly, tester, and equipment fields outside those branches. Because procedures and labels can differ, enter the component sequence and units your team uses and compare the final structure with current local instructions.
How should failed tests, repairs, and retests be recorded?
Keep the initial values unchanged. A failed component should reveal fields for the observed issue, corrective action, cleaning or adjustment, parts used, repair provider, and final readings. Record a distinct final outcome after retesting. If the assembly remains failed or work is deferred, capture the reason, customer notification, follow-up owner, and target date instead of forcing a passing result.
Can I use one form for several water authorities?
Yes. Let the tester select the destination, then reveal authority-specific account labels, attachments, or internal routing notes. Maintain those branches as requirements change. Makeform can structure and route the collected information, but the form itself does not confirm that the report is complete, officially valid, or accepted. Your office should review the current receiving instructions before submission.
Can testers complete the report on a phone and attach photos?
Yes. Build a mobile-friendly sequence with short sections, numeric inputs, large result choices, signatures, and file-upload fields. Test the form on the devices your team carries, especially where gloves, poor lighting, or limited connectivity affect entry. Useful uploads include the assembly nameplate, installation context, visible damage, replacement parts, and a copy of any separate report required by the recipient.
Is the backflow test form generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect submissions without a response cap. The paid tier removes the Makeform badge. Review the generated fields against your technical procedure and each receiving authority's current requirements before putting the form into production.
Where do completed reports go after submission?
Submissions arrive in the Makeform inbox and can be routed to tools such as Google Sheets, Slack, or Zapier. A practical office flow separates completed field tests, failed or repaired devices, reports missing information, reports ready to send, and responses needing correction. Add internal status, destination, submission date, reference number, response, and owner fields so delivery work remains visible.
Replace scattered test notes with one structured report.
Generate a backflow test form your field and office teams can review together.
Unlimited free forms and responsesDevice-specific reading pathsRepair, retest, and routing fields
