How to move meter rollout tracking from Excel to an app

Why switching mid-rollout feels risky

Nobody likes changing tools in the middle of a rollout. The sheet is ugly, but it's familiar, and the DISCOM review is on Thursday. The fear is a week where nobody knows the real numbers.

That week only happens if you switch everyone at once. Done one group at a time, with the sheet still running alongside, the switch is boring. Boring is the goal.

Step 1: Freeze and read your sheet

Take your current tracking sheet and list every column. For each one, note who fills it, when, and from what: the technician's call, a WhatsApp photo, the billing export.

You'll usually find three kinds of column:

• From billing, such as account number, name and address. These become the imported consumer list.
• From the field, such as meter serials, readings, seals and photos. These become the app form.
• Calculated or reporting, such as status, date installed or agency. The app should produce these, not ask for them.

Drop columns nobody uses. Every sheet has a few.

Step 2: Build the form from the field columns

Turn each field column into a form field, and decide which ones are required. Use the right type: barcode scan for serials, photo for evidence, a dropdown wherever crews type the same few values. Typed serials are where most Excel errors come from, so scanning them is the biggest single gain.

Start from a ready template if your app has one, and add only what your client needs.

Step 3: Import the consumer list

Clean the billing columns before importing: one row per consumer, account numbers as text so leading zeros survive, and no merged cells. Import them as the list crews work from. From now on, crews confirm records rather than create them.

Step 4: Pilot with one crew, in parallel

Pick one crew or one small agency, ideally a good one. For about a week, they use the app in the field while the office keeps the sheet up to date as usual. Each evening, compare the two. Differences are either app setup problems you need to fix, or sheet errors you have just caught.

Watch for:

• Jobs stuck on phones because crews didn't sync
• Fields crews find confusing, or skip with dummy values
• Photos too dark or blurry to verify
• Areas where the signal is too weak to sync during the day (fine, if the app works offline)

Step 5: Switch that group, then the next

When a day's app data matches the sheet, stop updating the sheet for that group. Their jobs now come only from the app. Move to the next crew or agency, using the first crew's leader to help train them. It is usually faster from the second group onward.

Step 6: Keep Excel where it earns its place

Most clients still want a spreadsheet. Fine. Export the app's data each week and fill the report format they expect, or build the same view in the app's reporting. The difference is that the numbers come from field records with evidence, not from retyping.

Common mistakes

• Switching everyone on day one. You lose the ability to compare.
• Copying every sheet column into the form. Crews end up filling fields nobody reads.
• Making nothing required. Then the app collects the same gaps the sheet did.
• No daily review. An app without someone approving jobs is just a faster spreadsheet.

Doing this in PIEBENCH

PIEBENCH imports consumers as service points by CSV, starts from a ready Meter Installation template, and lets an admin add fields in the form builder. The Scout Android app works offline, scans serials and refuses duplicates within a project. Supervisors approve jobs in an approval queue, and service points and work orders export to CSV for your report. For the case for switching, see Excel vs app for meter installation tracking.