Percolation Manager

The office half of the test.

Windows desktop software that turns field readings and deep test pit logs into the soil test drawing and the memorandum. It applies the same rules every time, shows its working, and leaves every number open to correction.

Status
Working
Platform
Windows · offline
REPRESENTATIVE INTERFACE — Percolation Manager laid out as it is today, with sample data.

Five steps

Readings and pit logs in. A drawing and a memorandum out.

The software walks a job through five steps in order. Nothing is produced until it is asked for, and nothing is saved anywhere you did not choose.

Step 01 · Sources

Read the Percometer, or open saved files

Read the Percometer over its cable, or open saved CSV files from as many field days as the job has. A read is saved at once, read back and compared; erasing the device stays locked until that check passes.

  • A read is offered for saving the moment it arrives
  • Erase stays locked until the saved file reads back identical
  • Open as many CSV files as the job has, or drag them onto the window
  • Open a saved project to pick a job up where it was left
REPRESENTATIVE INTERFACE — Percolation Manager laid out as it is today, with sample data.

Step 02 · Test data

See the data exactly as it arrived

See every reading exactly as the file sent it, and again as the drawing's tables. Two holes that would print under the same label are flagged before anything is built.

  • Every reading as the file sent it, flags included
  • The same readings again as the drawing's tables
  • Two holes that would print under one label are flagged
  • Neither document can be built until a clash is resolved
REPRESENTATIVE INTERFACE — Percolation Manager laid out as it is today, with sample data.

Step 03 · Project details

Set the job up once

The title block, and the septic design defaults every lot inherits: building type, bedrooms, hydraulic gradient, leaching product.

  • Title block fields for the drawing
  • Building type, bedrooms and hydraulic gradient for every lot
  • Leaching product, or let the software suggest one
  • Who dug the deep test pits, and when
REPRESENTATIVE INTERFACE — Percolation Manager laid out as it is today, with sample data.

Step 04 · Lots

One septic system per lot

One card per lot: deep test pit logs, any design that differs from the project, and the MLSS table, required ELA, product and notes as they will be drawn.

  • Deep test pit logs typed in per lot
  • Anything about a lot's design that differs from the project
  • MLSS table, required ELA, product and notes, updated as you type
  • Warnings such as groundwater less than 3 ft below grade
REPRESENTATIVE INTERFACE — Percolation Manager laid out as it is today, with sample data.

Step 05 · Test tables

Check every hole, then build

One card per hole — times, depth, final rate, dry cutoff, and every table value — then the two documents, each built only when its own button is pressed.

  • Lot and hole number, presoak, start time and hole depth
  • Final rate suggested, and editable
  • Every TIME, DEPTH, DROP, INTERVAL and RATE can be typed over
  • Drawing and memorandum each built only on their own button
REPRESENTATIVE INTERFACE — Percolation Manager laid out as it is today, with sample data.

Calculations

The rules, applied the same way on every job.

Percolation Manager follows the Connecticut DPH Technical Standards — and shows its working, so every result can be checked by hand.

Final rate

The slowest interval above the bottom 3 in. of water. Readings with 3 in. or less left are not counted, following the DPH Technical Standards (Section VIII).

Refills and top-ups

A rise of 1 in. or more is marked REFILL in place, and the lot stays one table.

Dry holes

Once the level stops changing (0.05 in. across three or more readings) the repeated rows are left off, with the cutoff shown for you to confirm.

Design percolation rate

The slowest final rate of the lot's holes, reported as its DPH rate class.

MLSS

Hydraulic factor × flow factor × percolation factor, from the pits' receiving soil depth and the hydraulic gradient, rounded half up to 0.01 ft.

Missing evidence

A limiting factor no usable pit recorded reads N/R; one looked for and not found reads N/O. Nothing is silently filled in.

Every value stays editable. Any cell in a table — TIME, DEPTH, DROP, INTERVAL or RATE — can be typed over. The typed text is what both documents print, it is marked TYPED OVER on screen, and one click puts the software's own value back. Nothing typed is ever silently recalculated.

Outputs

Two documents, each built when you ask for it.

.dwg

SOIL TESTS drawing

Drawn by AutoCAD: per lot, the deep test pit logs, perc tables, the MLSS REQUIREMENTS table and a notes box, six lots to a sheet. Every size is planned first and checked after; a drawing where anything came out larger than planned is not saved.

.docx

Memorandum

A cover letter, then one page per lot with its pit logs and perc tables. Written directly as a Word file — Word itself is not needed to produce it.

SAMPLE OUTPUT — one lot's block on a SOIL TESTS sheet, illustrative values. The real sheet adds the deep test pit logs and a notes box.
SAMPLE OUTPUT — a memorandum page, one per lot. Written as a .docx; Word is not needed to produce it.

Your data

Offline by design. Nothing goes to the cloud.

The software has no account, no cloud service and no internet connection. Every file it writes is one you chose to save.

No internet needed

No sign-in, no licence server, no cloud service. It runs the same on a laptop away from the office as at a desk.

Verified before erase

A device read is saved and read back before the device can be erased, so a test cannot be lost between the field and the file.

One project file

A saved project holds the original CSV data and everything typed in, so a job still opens after its files have moved.

Clashes caught

Two field days that both started at 1A would print the same label. The software flags it and will not build either document until it is resolved.

Requirements

What it needs to run.

The drawing is produced by AutoCAD itself, so the sheets keep every layer, style and block of the template. If your office has its own sheet standards, tell us about them.

Ask about your sheet format
Operating system
Windows
Install
Per-user installer, no administrator rights
Drawing output
Needs AutoCAD on the same PC
Memorandum output
No Word installation needed
Internet
Not needed — no account, no cloud service
Device data
Reads the Percometer over USB, and saved CSV files

Next step

See it run on a real job.

A demonstration walks a percolation job through all five steps — from device data to a finished drawing and memorandum — so you can judge it against how your office works today.