Civimax
Field data collection for sewer, water, and stormwater inspection contractors

An inspection form is a decision tree. Build it like one.

MACP and PACP are not questionnaires. The answer to one question decides the next five. Civimax forms carry their own rules: a defect opens the defect block, a grade 4 demands the photo, and the job status changes what the crew is even looking at. Author it once, and it behaves that way in every crew's hands.

A price on the first callMonth to monthNo per-seat chargeNothing to install

Try it right here

Change an answer. Watch the form change.

This is a manhole inspection carrying eleven rules. Set the cover to Defective, put infiltration on Gusher, grade an observation a 4, or flip the job status to Needs dig. The panel on the right is the rule list, lighting up as each one fires.

Manhole condition (MACP)
MH-2214 · Genesee at Mill · WO #312
sample form
Rules on this form
Authored once in the builder. Green means firing right now.

    The rules above are not a mock-up of the feature. This page loads the same conditional-logic engine the product runs, hands it the same rule objects the form builder saves, and renders whatever it returns.

    The logic

    What you can actually express.

    Every rule lives on the field it affects, so it travels with the form when you copy or publish it. A rule reads another answer on the form and compares it, and a field can carry several rules at once with ALL of them or ANY of them having to be true.

    Show or hide a field, or a whole section is · is not · is any of · has all of · has none of · contains · starts with
    Make a field required, or stop requiring it greater than · less than · is empty · is not empty, with numbers and dates compared properly

    Status is a trigger too

    The job status on the record is available to rules like any other answer. Mark a structure Needs dig and the excavation block appears with its own required fields. That is one form, not four.

    Sections collapse on their own

    Hide every field inside a section and the section hides itself. Crews scroll past what does not apply instead of through it.

    Rules run inside repeating blocks

    Each observation on a structure carries its own rules. Grade this one a 4 and this one demands a photo, without touching the one above it.

    One engine runs the logic in three places: the builder's preview while you author, the crew's screen in the field, and the record later if somebody corrects it. What you see in preview is what the crew gets.

    Three programs, one system

    The form is where the work happens. The asset is where it lands.

    A sewer contract is rarely one inspection. You CCTV the mains, inspect the manholes, and run SL-RAT over the same segments. Run those as three unconnected jobs and one correction, an asset ID retyped or a manhole mapped in the wrong yard, lands in one of them while the other two carry the old value to the end of the contract.

    Here the three programs point at the same assets.

    Each keeps its own form, its own crew, its own progress. Fix a structure once and the next crew opens a form that already knows it, because the fields you mapped are read off the asset as the form opens. Submit, and the record files itself and the mapped answers land on the asset in the same write, stamped with the time, the person, and the work order number. An unanswered field is skipped rather than written, so a blank never wipes what is already on the asset.

    Stand on that manhole a year later and its own history lists every record all three programs ever filed against it: the form, the date, who filed it, the work order it came from, and whether it has been corrected since. One button prints that as an asset history report with the photos in it. You still hand over the export at the end of the contract. What you also hand over is the client's own assets, each one carrying what was found on it and when.

    sample data

    What the day actually looks like

    The parts that only matter once you are out there.

    Photos climb as they are taken. Each one uploads the moment it is captured, resumably. Lose the connection and it picks up from the last acknowledged byte instead of starting the file again, and it survives a page reload.
    Pick up a half-finished inspection. Save a draft and come back to it with the repeating rows rebuilt and the photo thumbnails still there.
    Coded pick lists. Store the code, show the label. Rename a label to something the crew reads better and every record already filed keeps its code.
    GPS with the accuracy on screen. Set a target accuracy per field and the crew watches it settle, takes the best fix of the session or an average, and commits when it is good.
    Editing a label does not version the form. Change wording freely; only a structural change makes a new version, so a typo fix does not fracture the job.
    Deliverables in what the client runs. Excel with an assets sheet, a responses sheet and one sheet per repeating block. Or CSV, GeoJSON, a media bundle, and per-record PDFs with photos embedded.
    Price

    Straight answers about price.

    You already have a bill for this, so you know exactly what to compare against. We price the way we would want to be priced: simply, in writing, on the first call.

    Not per seat

    Priced by the size of what you inspect, not by counting logins. Putting the third tech in the truck on it does not change the bill.

    No setup fee, no lock-in

    Month to month, cancel any time, no multi-year contract, no implementation fee. Purchase order, invoice, and a check are all fine.

    A number on the first call

    Tell us roughly how many assets you work and how many crews you run, and you get the number in writing before you sit through a single slide.

    Send us your worst form.

    The one with the conditions nobody could make work, or the one that became four separate forms because it had to. We will build it in Civimax, put it in front of you with the rules firing, and give you a price in writing. Thirty minutes, on your screen.

    Send us your worst form

    Or write to info@civimax.com and tell us what you are running now.