.jpg)
Field teams in utilities, energy distribution, and IoT-connected infrastructure do not just fix things; they are also expected to document what they found, what they did, and what the site looked like before and after the intervention. For organisations that manage thousands of smart meters across distributed locations, that documentation requirement is where the process quietly breaks down. Photos end up in messaging apps. Fault codes get scribbled on paper. GPS is never recorded. By the time a back-office reviewer tries to verify whether a repair actually happened, the evidence chain is fragmented and impossible to audit.
This guide walks you through building a complete smart meter issue logging app in Clappia, a no-code platform for field operations. The app you will build handles two distinct types of issues through a single branching form, enforces photo capture at every critical step, auto-fills asset data through lookups so technicians never have to type what the system already knows, and routes every submission for remote image verification the instant it is saved. You can have it running on your field team's phones without writing a single line of code.
The core of this setup is one field app supported by four reference data apps that act as lookups. In Clappia, these reference apps work like a live MIS or master register: their submitted records become a searchable database that the field form can query in real time, pulling in validated data without the technician having to type it manually.
Here is the full picture before you dive into the build:
App
Type
Purpose
Smart Meter Issue Log
Field app (main)
The form technicians fill in on site. Branches by issue type, captures photos and GPS, triggers approvals.
Asset and Account Master
Reference app
Stores account IDs, meter IDs, addresses, and communication status for auto-fill lookups.
Legacy SIM Reference
Reference app
Stores previously deployed SIM records so technicians can look up provider details during a repair.
New SIM Inventory
Reference app
Stores available replacement SIM numbers for validation when a SIM swap is performed.
New Meter Inventory
Reference app
Stores available replacement meter IDs for cross-check when a meter unit is swapped.
The reference apps have no workflows attached. They exist purely to be queried. The field app is where all the logic, branching, and workflow automation lives.
Before you build the main form, you need the four reference apps in place. Log in to Clappia and create each one as a separate app. These apps do not need complex layouts; their role is to hold structured records that the field app can search against.
This is the foundation of the whole system. Every field submission starts with a lookup into this app to pull the relevant account and meter details. Create a new Clappia app and add the following fields, each using a Single Line Text block:
Once the app is created, populate it by importing your existing account and asset data. You can import records in bulk using a CSV upload directly in Clappia. From this point on, when a technician searches by Account ID in the field, all the linked details auto-fill without any manual entry.
When technicians need to identify a SIM that was previously installed in a meter, they search this app. Create it with three Single Line Text blocks:
When a technician searches by SIM Number in the field app, the Provider Name auto-fills from this reference. This eliminates provider mismatches that frequently occur when technicians try to recall or guess the provider from memory.
This app tracks SIM cards that are available for replacement. It uses a Repeatable Section block to allow up to 3 SIM Number entries per submission, which suits the typical scenario where SIMs are issued to a technician in small batches. Add a Single Line Text block inside the repeatable section labelled SIM Number. When a technician fits a new SIM, they search this app to confirm the number is a valid, inventoried card before logging it.
A simple single-field app containing one Single Line Text block labelled Meter ID. When a meter unit needs to be replaced entirely, technicians search this app to validate the replacement unit against your tracked inventory before recording it. This prevents unknown or unauthorised meter IDs from entering your records.
Create a new app in Clappia and name it something clear, like Smart Meter Issue Log or Field Diagnostic Form. This is the app your technicians will open on their phones at every site visit. Build it section by section as described below.
Start with a Dropdown block labelled Zone (you can also call it Region, Circle, or Area to match your organisation's terminology). Populate the dropdown options with your operational divisions. This field makes every submission filterable by geography, which becomes very useful when supervisors review submissions or run reports.
This is the first point where the app does real work for the technician. Add a Get Data from App block and label it Account ID. Configure it to search the Asset and Account Master. In the block settings, map the following auto-fill values so they populate the moment a record is selected:
These four fields should be added as read-only Single Line Text blocks so technicians can see the auto-filled values but cannot accidentally overwrite them. The display is informational, confirming to the technician they have selected the right account before proceeding.
Below these, add an optional second Get Data from App block labelled Replacement Meter ID that searches the New Meter Inventory. This field is only used on visits where the entire meter unit is being swapped. Follow it immediately with an Image Upload block labelled Replacement Meter Photo so the technician can capture a photo of the new meter at the point of recording its ID.
Add a Dropdown block labelled Issue Type with exactly two options:
This single dropdown controls everything that appears below it. You will use Display Conditions on each of the two sections below to make only the relevant one visible based on this selection. It is the branching point that turns a generic form into a guided, context-specific workflow.
Create a new section in the app and set its Display Condition to show only when Issue Type equals Infrastructure or Supply Issue. This section handles cases where the problem is not with the meter itself, such as power supply failures, access restrictions, or installation irregularities.
Add the following fields inside this section:
GPS and photos together create an evidence chain that no paper form can replicate. The GPS timestamp and coordinates confirm when and where the visit occurred; the photos confirm what was found.
Create a second section and set its Display Condition to show only when Issue Type equals Meter Hardware Issue. In the section settings, set it to collapsed by default. This means the section is present in the form but appears as a collapsed header until the technician expands it, keeping the form clean and reducing the chance of accidental data entry in the wrong section.
This section has three logical parts: capturing the state before the fix, recording what was replaced, and documenting the state after the fix. Each part is described below.
The before-fix capture is the most important part of the audit record. It documents the condition the technician found on arrival and forms the baseline that supervisors compare against the post-fix state.
Below these, add the SIM identification fields. The technician needs to record what SIM is currently in the meter before they touch anything:
After documenting the initial state, the technician records what components were replaced. These fields are conditional: they only appear when the technician confirms a replacement was made.
Add a Yes/No block labelled SIM Replaced?. Set a Display Condition on the three fields below so they appear only when SIM Replaced? equals Yes:
Add a second Yes/No block labelled NIC Replaced?. When this equals Yes, reveal one additional field:
The after-fix capture mirrors the before section, giving supervisors a direct comparison point. It also adds a serial number verification step that is essential for confirming the right meter is in place.
Display Conditions are configured at the section or field level in Clappia's form builder. Here is a consolidated view of every conditional rule in this app:
What Is Controlled
Condition
Effect
Infrastructure or Supply Issue section
Issue Type = Infrastructure or Supply Issue
Section becomes visible; all other issue fields hidden
Meter Hardware Issue section
Issue Type = Meter Hardware Issue
Section becomes visible; all other issue fields hidden
New SIM Lookup, New SIM Photo, New SIM Provider
SIM Replaced? = Yes
Three fields appear for replacement SIM capture
NIC Type
NIC Replaced? = Yes
Dropdown appears for NIC variant selection
The approval workflow is what turns this from a data collection tool into an auditable quality assurance process. Every time a technician submits the form, their supervisor or a designated reviewer automatically receives a notification asking them to verify the uploaded photos. Here is how to configure it.
Open the app's Workflow settings and create a new workflow. Set the trigger to On Save. Add an Approval node and configure it with the following settings:
When the reviewer receives the notification, they click the submission link, which opens the full record in Clappia including all uploaded photos, GPS coordinates, and entered data. They then choose IMAGE VERIFIED or IMAGE NOT VERIFIED. Their choice is recorded against the submission and updates its status accordingly.
Also configure a separate workflow triggered On Edit with a passive start node and no further actions. This ensures that when a technician or admin edits a submitted record to correct a minor error, no new approval request is fired, keeping the reviewer's inbox clean.
The 7-day expiry window is intentional. If an approval is not acted on within a week, it expires and the submission can be escalated or re-submitted, preventing a backlog of unreviewed records from silently accumulating.
Clappia's Submission Status feature lets you track where every record sits at any point in the process. This app uses three statuses:
Status
What It Means
How It Is Set
SUBMITTED
The form has been saved by the technician. The approval request has been sent. No review action has been taken yet.
Automatically on Save
IMAGE VERIFIED
The reviewer has opened the submission, checked the photos, and confirmed they are clear and accurate.
Reviewer selects this outcome in the approval notification
IMAGE NOT VERIFIED
The reviewer has flagged the photos as unclear, missing, or not matching what was reported.
Reviewer selects this outcome in the approval notification
Admins can filter the submissions table by status at any time. Filtering for IMAGE NOT VERIFIED immediately surfaces records that need a follow-up visit or additional documentation. Filtering for SUBMITTED shows everything still waiting for review, making it straightforward to chase outstanding approvals before the 7-day expiry.
Once the app is fully built, the last configuration step is setting up user permissions. Clappia manages access at the app level, so you can give different user types exactly the right level of visibility without creating separate apps.
User Role
Recommended Access
What They Can Do
Field Technician
Submit Only
Open the app, fill in and submit forms, view their own past submissions
Supervisor or Reviewer
View and Approve
View all submissions across all technicians, action approval requests
Admin or Data Manager
Full Access
Edit reference app data, configure app settings, manage user roles, run reports
For field technicians, the Clappia mobile app, available on both Android and iOS, is the primary interface. The app supports offline mode, which is critical for meter inspection work. Technicians can fill out the entire form, upload photos, and capture GPS even in areas with no signal, such as basements, tunnels, or remote installations. All data is queued locally and syncs automatically as soon as connectivity is restored.
There is one important offline preparation step: the Get Data from App lookups rely on reference data being cached on the device. Before heading to site, technicians should open the Clappia app while connected to Wi-Fi so the reference app data syncs to their phone. Once cached, searches against the Asset and Account Master, Legacy SIM Reference, and other lookups will work without any network connection.
To see how all the pieces fit together, here is a full walkthrough of a meter hardware repair visit from start to finish.
Once your team is actively using the app, Clappia's Analytics feature lets you build dashboards directly from the submission data without exporting to a spreadsheet. For a meter diagnostics workflow, a few dashboards are immediately useful:
These are all built inside Clappia using the charts and filters in the Analytics tab of your app. No external BI tool is needed for this level of operational reporting.
Building a smart meter issue logging app with photo verification in Clappia involves five components working together: four reference apps that supply validated lookup data, one branching field form that guides technicians through either an infrastructure issue or a hardware repair, conditional fields that surface only what is needed at each step, GPS and photo capture at every critical juncture, and an approval workflow that automatically routes every submission for image verification.
The result is an end-to-end audit trail for every field visit: who attended, which meter they worked on, what they found, what they changed, what the site looked like before and after, and whether a supervisor has signed off on the evidence. This is the kind of documentation that paper forms and spreadsheets cannot reliably deliver at scale.
The setup described here applies directly to any organisation operating connected metering infrastructure, whether in electricity, gas, water, or broader IoT deployments. It also adapts to any field operation where before-and-after evidence, component tracking, and remote image verification are part of the quality assurance process.
Get started by creating your first reference app in Clappia. The entire build, from reference apps to approval workflow, can be completed in a single session without any development work.
L374, 1st Floor, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
.svg){kind=small}
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
L374, 1st Floor, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
.avif)
