How it works
Record, review, file it yourself.
Record a backflow test in Psid and review your saved details on a supported utility’s own PDF. Download the report, check its signing requirements, and submit it yourself using the utility’s current process.
01
Record the test
Everything that does not change is already saved.
- Open the assembly from today’s list, from the customer, from the site, or by searching a serial.
- The customer, service site, assembly make and model, and your certification are already attached.
- Type the readings that assembly actually needs — RP, DC, PVB and SVB each ask for their own set, to one decimal.
- Pass or fail shows as you type against Psid default criteria, not a utility determination.
- A failure is a real state: record the repair as its own entry, then retest. The initial reading is never overwritten.
02
Review the utility’s own form
Not a Psid report. Their sheet, filled.
- The official blank PDF the supported utility publishes, with its original artwork untouched.
- Your answers placed in the mapped boxes; a value too long for its box is shrunk and you are warned, never silently cut.
- Every field position was measured against the printed form and is checked in release tests.
- The same test always renders the same bytes, so the document can be reproduced exactly a year from now.
03
Download and file it yourself
Psid does not submit reports. You are the one who files.
- Download the filled PDF and a packet of copyable values. Psid has not verified which upload or entry fields Greenville Water’s portal currently accepts.
- Check the program’s current instructions and submit the report yourself using its accepted method. Greenville Water has a portal. Spartanburg Water’s form lists a C&D return address and fax; Easley Combined Utilities’ form lists no return method. Confirm signing and delivery requirements with the utility.
- For Greenville portal submissions, record the confirmation or explanation in Psid after you submit. For Spartanburg and Easley, keep your own delivery proof; in-app manual-submission recording is not available yet.
- The filing keeps a frozen snapshot of exactly what was on the form, so the record survives later edits to the customer or the device.
And around it
The parts that keep a season from going sideways.
When signal drops mid-test
An already-open readings screen can keep your changes in that browser on that device when local storage is available. Reconnect and press Upload draft to save them to Psid before leaving the screen. You cannot open the app without signal, and drafts do not sync in the background.
A queue between the truck and filing
The owner can review completed tests waiting for filing packets in one list. Team invitations and separate office logins are not available yet. An expired certification or gauge calibration holds a filing, judged against the test date. An override needs a reason and evidence, which Psid audits.
What a recorded submission means
Psid sends no report or customer copy and makes no utility portal submission on your behalf. Downloading the PDF is not filing it. Recording a submission is your statement of what you did, not the utility accepting it. A filing reads “Filed · utility pending” and stays that way.
Which assemblies, exactly
All nine assembly types can be recorded against a site, with their make, model, size, serial and location. Test entry covers RP, DC, PVB and SVB. Detector assemblies (RPDA, DCDA, Type II) and visual types (AVB, air gap) can be kept in your records, but their test entry is not built — and Greenville’s form has no bypass columns to file a detector on.