Smart Meter Issue Resolution Starter Pack: A Complete Clappia Template Spotlight

Every field operations team that manages connected metering infrastructure eventually builds some version of the same thing: a way for technicians to log what they found on site, document what they did, confirm the result with photos, and get the record reviewed. The question is how long it takes to build something reliable, and how much of that effort ends up being rebuilt when the first version turns out to be missing something.

This article is a spotlight on a complete, ready-to-configure starter pack for smart meter diagnostics and issue resolution, built entirely in Clappia. It covers every component in the setup: the four reference apps that anchor the data, the branching field app your technicians use on site, the conditional logic that keeps the form clean and context-specific, and the approval workflow that closes out each submission with a verified outcome. If you are setting up a field operations system for the first time, this pack gives you a complete starting point. If you already have something in place, it gives you a reference for what a complete setup looks like.

What Is in This Starter Pack

The pack consists of five Clappia apps: four reference apps and one field app. The reference apps hold the validated data your field app queries. The field app is what technicians open on their phones at every site visit. Together they form a closed system where data enters the field app through validated lookups, evidence is captured in context, and every submission is routed for review without any manual step in between.

The Four Reference Apps: Your Data Foundation

The reference apps are the reason the field app works cleanly. Rather than asking technicians to type asset details from memory or look them up in a separate system, the field app queries these apps live and fills in the relevant fields automatically. Getting the reference apps populated accurately before you launch the field app is the most important setup step.

Asset and Account Master

This app is the primary identity register for every account and meter in your network. Create it with the following fields, each as a Single Line Text block:

When a technician searches by Account ID in the field app, the Meter ID, Account Holder Name, Site Address, and Network Communication Status all populate at once. The two SIM fields are available for reference if needed but do not auto-fill into the diagnostic form directly; they serve as background context for the account record.

Legacy SIM Reference

This app holds records for SIM cards that have been installed in meters in the past. When a technician identifies the SIM currently in a meter during a repair, they search this app and the telecom provider name auto-fills in the field form, removing the need to look up or guess the provider. Create it with three Single Line Text blocks:

• SIM Number - the unique identifier of the legacy SIM card
• Provider Name - the telecom operator that issued this SIM
• SIM IP Address - the network IP assigned to the SIM; relevant for network-level diagnostics

Replacement SIM Inventory

This app tracks SIM cards available for deployment as replacements. It uses a Repeatable Section block containing a single Single Line Text block labelled SIM Number. The repeatable section allows up to 3 SIM entries per submission, which matches the typical scenario where SIMs are issued to technicians in small batches rather than individually. When a technician logs a SIM replacement, they look up the new SIM number against this app before recording it. If the number is not found, the lookup returns no result, prompting the technician to verify the SIM before continuing.

Replacement Meter Inventory

A minimal app with a single Single Line Text block labelled Meter ID. When a full meter unit replacement is performed, the technician looks up the replacement meter ID here to confirm it is a tracked, authorised asset before it enters the submission record. This prevents unrecognised equipment from being recorded without a corresponding inventory entry.

Populate your reference apps before launching the field app. The auto-fill behaviour depends entirely on the quality and completeness of the records in these apps. An incomplete Asset and Account Master means technicians fall back to manual entry, which reintroduces the data errors the lookups are designed to prevent.

The Field App: Smart Meter Issue Log

This is the app your technicians open on their phones at every site visit. It is designed to be mobile-first, work in offline mode, and guide the technician through exactly the fields relevant to their current situation without presenting anything they do not need. The form is built in sections, and the sections that appear depend entirely on what the technician selects at the Issue Type field.

Opening Section: Zone and Account Identification

The first two fields handle location and identity. A Dropdown block labelled Zone (or Region, Circle, District, whichever term matches your operational structure) lets the technician identify the operational area. Configure the dropdown options to match your zones.

Below it, an Account ID field built using a Get Data from App block searches the Asset and Account Master. On selection, four read-only fields populate automatically: Meter ID, Account Holder Name, Site Address, and Network Communication Status. These confirm to the technician that they have found the right account and give them the context they need before proceeding.

If the visit involves replacing the meter unit, an optional Replacement Meter ID Get Data from App block validates the new meter against the Replacement Meter Inventory. Immediately after it, an Image Upload block captures a photo of the replacement unit at the point of entry.

Issue Type: The Branching Point

A Dropdown block labelled Issue Type presents two options: Infrastructure or Supply Issue and Meter Hardware Issue. This selection controls which section of the form becomes visible through Display Conditions. The section that does not apply is hidden, not just greyed out. The technician works through one clear path without having to navigate around irrelevant fields.

Branch A: Infrastructure or Supply Issue

This section appears when Issue Type equals Infrastructure or Supply Issue. It handles site visits where the problem is not the meter hardware itself but something in the surrounding environment or installation. The fields capture a complete, auditable record of what was found without requiring the technician to navigate the more detailed meter diagnostic flow.

The GPS Location block is configured using Clappia's GPS Location block. It captures the device's coordinates at the moment the technician submits the form, not a manually entered address. This creates a verifiable location record that is directly tied to the submission rather than being a separate data point.

Branch B: Meter Hardware Issue

This section appears when Issue Type equals Meter Hardware Issue. It is set to collapsed by default in the section settings, so the technician expands it when they are ready to begin. It contains three sequential parts that mirror the natural order of a hardware repair: document the fault, record what was replaced, then document the resolved state.

Part 1: Before the Fix

This part captures everything about the meter's state before the technician begins work. Filling it in before touching the meter is what makes the before record meaningful; once the repair starts, the original fault display is gone.

• Fault Code (Before) - Dropdown block; list all meter error codes your equipment produces, such as Err Dash, Err 00 through Err 12, or whatever codes your meters display
• Fault Photo (Before) - Image Upload block; a photo of the meter display showing the active error
• Signal Strength (Before) - Number block; the RSSI reading at arrival; using a Number block rather than a text field prevents entries like N/A or poor, which cannot be filtered or compared in reports
• Signal Screenshot (Before) - Image Upload block; a screenshot or photo of the signal indicator

Below these, three fields handle the SIM currently in the meter:

• Old SIM Lookup - Get Data from App block searching the Legacy SIM Reference; when a record is found, the Provider Name field auto-fills from the matched entry
• Provider Name - read-only Single Line Text; populated by the lookup above; confirms the telecom provider without the technician having to look it up or recall it
• Provider Name (Manual) - Dropdown block; available when the SIM is not found in the legacy reference; configure it with the telecom providers active in your region
• Old SIM Number (Manual) - Single Line Text; a fallback entry field for when the lookup does not return a result
• Old SIM Photo - Image Upload block; a clear photo of the SIM card currently in the meter

Part 2: Replacement Checks

Two Yes/No blocks gate the replacement fields. Both default to No, so the additional fields only appear when a replacement was actually made.

SIM Replaced? When set to Yes, three fields appear via Display Condition:

• New SIM Lookup - Get Data from App block referencing the Replacement SIM Inventory; validates the replacement SIM against your tracked stock before it is recorded
• New SIM Photo - Image Upload block; a photo of the replacement SIM card
• New SIM Provider - Dropdown block; select the telecom provider for the replacement SIM

NIC Replaced? When set to Yes, one field appears:

• NIC Variant - Dropdown block; select the NIC type being installed; typical options correspond to the hardware revisions or colour-coded variants used in your network, such as Green, Blue, or Red

Part 3: After the Fix

The after-fix section documents the resolved state of the meter and adds two checks that are only relevant once the repair is complete.

• Fault Code (After) - Dropdown block; the same list as the before section, now recording the post-repair error state
• Fault Photo (After) - Image Upload block; meter display after the fix
• Signal Strength (After) - Number block; updated RSSI for direct comparison against the before value
• Signal Screenshot (After) - Image Upload block; post-repair signal screenshot
• Serial Number Match? - Yes/No block; confirms whether the serial number printed on the meter body matches what is shown on the digital display; a mismatch flags a potential asset integrity issue that needs investigation before the job can be closed
• Serial Verification Photo - Image Upload block; a photo showing both the body serial and the display serial in the same frame
• Additional Remarks - Multi-Line Text block; final notes or observations
• Technician Name - Single Line Text block
• GPS Location - GPS Location block; post-repair coordinates

Display Conditions: The Conditional Logic Reference

Clappia's Display Conditions are configured on sections and individual fields. Here is the complete set used in this starter pack:

All other fields in the form are always visible once the relevant section is open. Display Conditions are only needed where fields should be completely absent unless a specific prior answer was given.

The Approval Workflow

The approval workflow is configured in the field app's Workflow settings. It uses an On Save trigger, meaning the approval request fires automatically every time a technician saves a completed submission. There is no separate step the technician needs to take and no reminder the supervisor needs to set.

Configure the Approval node with the following settings:

A second workflow with an On Edit trigger is also included. It contains only a passive start node and no further actions. This ensures that corrections made to a submission after the initial save do not trigger a new approval request, so a typo fix or remark update does not reset the review status or fill the reviewer's inbox with duplicates.

Submission Statuses in This Pack

Clappia's Submission Status feature tracks every record through its lifecycle. This starter pack uses three statuses:

Supervisors can filter the submissions view in Clappia by any of these statuses at any time. Filtering by SUBMITTED shows every record waiting for review. Filtering by IMAGE NOT VERIFIED surfaces every job that needs a follow-up conversation with the technician or a re-visit to the site.

User Permissions and Offline Setup

Clappia manages user permissions at the app level. For this starter pack, configure access as follows:

The Clappia mobile app, available on Android and iOS, supports offline mode. Technicians can fill in the entire form, upload photos, and capture GPS without a network connection. Submissions queue on the device and sync automatically when connectivity returns. For the Get Data from App lookups to work offline, technicians need to open the app on Wi-Fi before heading to a site so the reference data is cached locally.

What to Customise for Your Organisation

This starter pack is designed to be used as-is for most connected metering and IoT field operations. A small number of elements will need to be adapted to match your specific setup:

• Zone or Region names: Update the Zone dropdown options to match your operational divisions
• Fault code list: Replace the example error codes in the Fault Code dropdowns with the actual codes your meter equipment produces
• Telecom provider options: Update the Provider Name dropdown in the manual SIM fields with the carriers active in your region
• NIC variant options: Update the NIC Variant dropdown with the hardware types or revisions you deploy
• Infrastructure issue causes: Extend or trim the Issue Cause dropdown to reflect the non-hardware scenarios your teams actually encounter
• Approval recipients: Configure the reviewer email addresses or user variables in the approval workflow to point to your actual supervisors or QA reviewers

The structure of the form, the conditional logic, the lookup configuration, and the workflow trigger all remain unchanged. Only the values inside the dropdowns and the recipient configuration need to be updated to reflect your organisation's specifics.

Deploying the Starter Pack

The deployment sequence takes each app in dependency order: reference apps first, field app second, workflow third, access last.

1. Create the Asset and Account Master, Legacy SIM Reference, Replacement SIM Inventory, and Replacement Meter Inventory apps. Add the fields described above to each.
2. Import your existing asset, account, and SIM records into the Asset and Account Master and Legacy SIM Reference. Use a CSV import for any bulk data. Add initial stock to the Replacement SIM and Replacement Meter Inventory apps.
3. Create the Smart Meter Issue Log field app. Build the Zone dropdown, Account ID lookup, Replacement Meter ID lookup, and Issue Type dropdown as described. Configure the Display Conditions on both issue sections.
4. Build the Infrastructure or Supply Issue section with all six fields. Build the Meter Hardware Issue section with the Before, Replacement, and After parts, including all Yes/No conditional fields.
5. Configure the approval workflow: On Save trigger, Image Verification approval node, IMAGE VERIFIED and IMAGE NOT VERIFIED outcomes, submission link in notification body, 7-day expiry. Add the passive On Edit workflow.
6. Set user permissions for each person on your team: Submit Only for technicians, View and Approve for supervisors, Full Access for admins.
7. Ask technicians to open the Clappia app on Wi-Fi before their first site visit to cache the reference data for offline use.

From the first submission, every visit generates a complete record: account and meter identity auto-filled, issue type clearly indicated, photographic evidence linked in context, GPS coordinates captured, and an approval outcome stored against the submission with a named reviewer. No aggregation step required between the field and the back office.

Analytics You Can Build on This Data

Once submissions are flowing, Clappia's Analytics feature lets you build live dashboards directly on the submission data. The starter pack data supports several immediately useful views:

• Open submissions by zone: filter by SUBMITTED status to see which areas have unreviewed records and how long they have been waiting
• Fault code distribution: the most frequently occurring fault codes before resolution, useful for identifying whether certain zones have chronic connectivity or hardware issues
• Signal improvement rate: compare average RSSI before and after repair; a low improvement average suggests the root cause may not be at the meter level
• Verification outcomes: the ratio of IMAGE VERIFIED to IMAGE NOT VERIFIED, broken down by technician or zone, to surface quality or training gaps
• Replacement counts: SIM and NIC replacement volume per period, useful for inventory forecasting

These dashboards update in real time from live submission data and are accessible to anyone with the appropriate permission level inside Clappia. No data export or external reporting tool is required.

Closing Notes on This Starter Pack

This starter pack covers the full lifecycle of a smart meter issue: identification, diagnosis, evidence capture, component replacement tracking, post-repair verification, and supervisor sign-off. Every element has a defined role, and each role connects to the next in a continuous chain from the technician's phone to the reviewer's inbox.

The pack is intentionally minimal in its fixed structure. The four reference apps and the field app can be recreated in Clappia without any coding. The conditional logic and approval workflow are standard Clappia features that require only configuration, not development. What you adapt to your organisation are the content values inside the fields: the zone names, error codes, carrier names, and reviewer assignments that reflect your specific operational context.

To get started, log in to Clappia and create your first reference app. The complete setup follows the deployment sequence above, and your team can begin using the field app on the same day.