← Field Ops

Ener.co Field Tools — Team Lead Guide

Five tools, one job: get a site surveyed, measured, scheduled, cleaned, coated, and proven. The forms are built to be self-explanatory — this guide just covers the handful of things that aren't obvious on first use.

How the five fit together — left to right is roughly the order a site moves through
1 · First visit
Survey (Scout)
Capture every unit & coil with photos + nameplates.
2 · Plan
M&V Plan
Pick measured units, sensor kit & baseline timeline.
3 · Schedule
Game Plan
Day-by-day: which units, what order, what to load.
4 · Do the work
QC
Prove each coil is cleaned/coated; close out the day.
5 · Prove it
Spot Check
Measure real efficiency after treatment.
Getting in: everything opens from the Field Ops launcher (/field/) — four tiles: Scout, Game Plan, QC, and M&V Install. Add it to your phone's home screen once and it works like an app, including offline — anything you enter with no signal saves on your phone and syncs the moment you're back online. The first time you open QC or Game Plan it asks for your name — pick your existing name from the list, don't re-type a new spelling.
Quality Control · /qc/

QC — prove the work, close the day

Three forms live here: Cleaning QC (per coil), End of Day (per building, once a day), and Building Sign-off (whole-building, at the end). Coating QC is coming. You navigate Customer → Building → Unit, then pick a form. Most fields explain themselves — here's what to actually pay attention to.

How you use it

  1. Open QC from Field Ops, pick your name once.
  2. Tap your customer → building → the unit you're working.
  3. Choose Cleaning QC for a coil, or End of Day / Building sign-off for the building.
  4. Fill it in (or talk it in — see voice notes), capture the required photos, pick a verdict, submit.

Worth knowing the non-obvious bits

  • One full proof is required on a Cleaning QC. You need at least one of: the airflow (CFM) traverse, the approach-temp reading (unit running), or the rinse pH/TDS before-vs-after. Any one is enough — pick whatever the site allows.
  • Finish a traverse face completely. The 5-point traverse wants all 5 points before AND after. A half-filled face is blocked on purpose — a missing point would post a fake airflow drop. Empty/extra face cards are just dropped.
  • Tell it "jumped" vs "running." If you read the coil cold with the compressor off (fan only) that's jumped; warmed-up with it running is running. The app corrects the density math for you — just pick the right one. For a running read: fan at 100%, let it run a few minutes, not too windy, moderate outside temp.
  • Before & after full-coil photos are required to submit a Cleaning QC. Nameplate photo is optional if Scout already has one.
  • Voice fill. Tap the record bar, talk through your readings, then "Fill form with AI" drops them into the fields. No audio is saved — just the text.
  • Saved forms = pick up where someone left off. Every form auto-saves to the server as you go. On the QC home screen, "📝 Saved forms" lists anything started-but-not-submitted — by anyone. If a guy starts a unit and is out the next day, you open it, his entries + photos are right there, you finish it. The record still credits the tech who did the work; you're stamped as the finisher.
  • Not in the plan? Add it. A customer, building, or unit that isn't listed can be added right in the field — it flags the office to reconcile it later.
  • Passing a Cleaning QC auto-ticks Game Plan's "Clean QC" box. Don't double-enter — QC is the source of truth, Game Plan just reflects it.
  • "Submitted" tab on the home screen shows every form the moment it lands, any project — handy to confirm something actually went through.
If you're offline: the form still saves on your phone and a banner shows the unsynced count. It sends automatically when you get signal — you can't lose a day by being on a roof with no bars.
Game Plan · /qc/?intent=gameplan

Game Plan — your day-by-day schedule

The plan for the job: which units, in what order, how long each takes, and what chemicals to load. It's your read-only roadmap — you tick off steps as you go, the office owns everything else.

How you use it

  1. Open Game Plan from Field Ops (it runs inside the QC app, same name/login).
  2. Read the Site Info card up top — access, water/electrical, contact, ops notes.
  3. Work down the day cards: each unit shows tonnage, coil type, nameplate, condition scores, and the hour split (clean / coat).
  4. As you complete work, tap the step boxes: Fins Cleaned Clean QC Coated Coat QC.
  5. Check the Chemicals — What to Load card before you head out.

Worth knowing the non-obvious bits

  • It's read-only — the office owns the schedule. You can't move days or reassign units; the only thing you write is the step checkboxes.
  • "Clean QC" and "Coat QC" tick themselves when you pass the matching QC form. Don't hand-check them — let QC drive it so the records line up.
  • A unit isn't "done" until QC is in. Clean-only jobs finish at Clean QC; clean+coat jobs need Clean QC and Coat QC. "Cleaned" alone doesn't close a unit.
  • "Next up" for tomorrow comes from the QC End-of-Day form. When you flag tomorrow's units there, Game Plan soft-bumps them to the front of the next day — it's a nudge, not a hard lock.
  • Chemicals card tells you exactly what to load: EnerCoat, Nu-Brite, Etcher, EnerZyme.
  • Tap a unit's photo for the full-size survey shot, and use Print (top right) if you want a paper copy for the truck.
Scout · /scout/survey.html

Survey (Scout) — the first visit

Capture the whole site so the proposal and M&V plan can be built: the building, every unit, and every coil — with photos, nameplates, and condition scores. You flow Customer → Building → Units → Coils.

How you use it

  1. Start a New Survey — enter client name and your name.
  2. Fill Building Info: address (tap to auto-locate), access, utilities, contact.
  3. + Add Unit for each piece of equipment; capture the unit tag + nameplate.
  4. Per unit, add its coil(s) and shoot the photo slots; score the condition.
  5. Save as you go; Mark Complete when the building's done.

The photo slots each has a job

Wide
The whole coil in its setting — context & access.
Nameplate
Model / serial / tonnage — the data source (read by AI).
Coil Face
Straight-on fins/tubes — for debris & corrosion.
Close-up
The worst damage/fouling — backs up the scores.
Obstacles
Anything in the way — feeds access & install planning.

Worth knowing the non-obvious bits

  • The nameplate photo auto-reads the data. Online, capturing a crisp nameplate fills in manufacturer / model / serial / tonnage for you. A blurry nameplate means bad unit data downstream — get it sharp. (Offline, it queues and reads on sync.)
  • Pick the right Survey Context up front — Cold Start / Equipment List Verification / M&V Extension. It changes how the proposal and baseline tools read everything you capture.
  • Voice notes auto-fill. Record a quick description of the unit and parse it into the fields with AI.
  • Condition scores (1–5) for debris, corrosion, fin straightening, and access aren't just notes — they feed the schedule's hour estimates and the work plan.
  • Auto-saves and works offline. Watch the sync dot/banner — green is synced, amber is pending. Don't assume a survey is uploaded until it's green.
  • Flag "can't shut down" / access limits. Operational constraints you note here drive how the office schedules the coating work.
M&V Plan + Install · /scout/install.html

M&V Plan — measure the savings

For jobs where we have to prove the efficiency gain. The plan picks the few "holdback" units that get sensors and a baseline before any coating, lays out the sensor kit for each, and sets the timeline. In the field, the M&V Install tile walks you through deploying those sensors.

How you use it

  1. Review the plan in Game Plan → M&V Plans: which units are holdbacks, the sensor kit & BOM, and the timeline.
  2. Open M&V Install from Field Ops (or the plan's Open Install Checklist link).
  3. Work the per-unit checklist: mount each sensor where it says, confirm with a photo.
  4. Once sensors report, the baseline clock starts — no coating on holdback units until baseline is approved.

Worth knowing the non-obvious bits

  • Holdback units come first and stay clean. They get sensors and a ~30-day baseline before treatment — that's the "before" half of the proof. Don't coat a holdback unit until the office approves its baseline.
  • The plan is auto-built and read-only. It's generated from the proposal + your survey. If something's wrong, it's fixed at the source (survey/proposal) and regenerated — not edited in the field.
  • Sensor placement is spelled out per unit (e.g. evap inlet/outlet RH, condenser outlet temp) with a mounting photo slot. Follow the kit — CT size and sensor roles are chosen for that specific unit.
  • Data-gap flags aren't errors. Missing FLA or model just lowers confidence (CT sizing falls back to tonnage). Good survey data = a tighter kit, so it pays to survey well.
  • The Install Checklist is its own tool (M&V Install tile), separate from Game Plan — it tracks install progress per unit, not the coating schedule.
Spot Check · a measurement, logged as an M&V record

Spot Check — prove the number

A quick, real efficiency measurement after treatment (or as a periodic check) — an actual reading with handheld meters or a short Monnit deploy, not a visual look. Heads-up: it's not its own app tile. You take the reading on site and log it as an M&V record (Type = Spot Check) so it lands next to the pre-coating baseline.

How you use it

  1. On a treated unit, get it running steadily under good conditions (see below).
  2. Measure the real efficiency (EER) with the handheld meter / temporary sensor.
  3. Log it as an M&V record — Date, Type = Spot Check, EER, Outdoor Temp, Outdoor RH.
  4. The Improvement % fills in automatically against that unit's pre-coating baseline.

Worth knowing the non-obvious bits

  • It's a higher bar than QC. QC proves the coil is clean/coated; a spot check proves the efficiency number. Different question, real instruments.
  • Conditions have to be valid — same idea as the QC airflow read: unit running steadily a few minutes, fan at 100%, wind under ~10 mph, ambient roughly 60–100°F. Outside that window the reading is flagged low-confidence.
  • Improvement % only computes if a pre-coating baseline exists for that unit. No "before," no comparison — so the baseline has to be captured first.
  • Capture the conditions, not just the number. Outdoor temp & RH are logged with the reading so it can be matched to the baseline at the same weather — a number without its conditions can't be compared fairly.