Offline-First Field Service Reporting App for Elevator Maintenance

How Azati built a configurable mobile reporting app that lets elevator maintenance technicians save service reports offline and submit them when connectivity returns

Elevator maintenance teams need to document completed work using the required report format, even when technicians cannot rely on an internet connection. Paper-based reporting makes that process harder to manage as forms change, while an online-only application can leave technicians unable to submit information from disconnected locations.

For a client in Germany, Azati built a custom field reporting solution combining a mobile application for technicians, a web interface for administrators, and a backend connecting the two. Administrators could configure report forms centrally, while technicians could complete and save reports offline and submit them when connectivity became available. The solution was developed from scratch in under six months.

While this engagement was built for elevator maintenance specifically, the same approach based on configurable server-driven forms plus offline-first mobile reporting applies to any field service operation where connectivity can't be assumed.

Discuss your field reporting needs

Built for two constraints at once

Forms that change, and connectivity that can't be guaranteed, are solved in one application, not two separate fixes

Server-driven report forms

Administrators can configure and publish the active report structure through a web interface

Built from scratch in under 6 months

Web administration, mobile reporting, and backend developed as one solution

The project's specifics

Case study at a glance: Azati developed a mobile and web reporting application for elevator maintenance and repair specialists in Germany. The solution replaced paper-based reporting with configurable digital forms, allowing technicians to complete and save service reports offline and submit them when connectivity became available.

A technician finishing an inspection in an elevator shaft rarely has a signal. Paper forms don’t care. They get filled in anyway, then re-entered into a system back at the office, introducing a second point of failure for every report. A purely online mobile app solves the re-entry problem but recreates the original one: no connection, no way to record the work at all.

The business challenge: Field technicians needed to complete service reports using the current required format. Paper-based reporting made the process dependent on physical forms, while changing report requirements created an additional operational challenge.

Why this is difficult: Elevator maintenance work does not guarantee a reliable internet connection. A digital reporting application therefore had to support offline work without making connectivity a prerequisite for recording completed maintenance activities. At the same time, administrators needed to manage changing report formats without relying on a permanently fixed mobile form.

What was at stake: The organization needed a practical way to standardize digital reporting while accommodating changing form requirements and the connectivity constraints of field work.

Technology stack

React Native

React

Redux

JavaScript

React Native AsyncStorage

How can elevator maintenance companies build an offline-first reporting app with configurable service forms?

An offline-first field reporting app can let elevator maintenance technicians complete and save service reports on their devices, then submit them when connectivity becomes available. A web administration interface can allow authorized staff to configure and publish report forms, while the mobile application retrieves available updates when it can connect. This approach combines adaptable reporting with the ability to work without a continuous internet connection.

In this engagement, Azati built a web administration interface, a mobile application, and a backend to connect form management with field reporting.

How Azati addressed the challenge

Server-driven form configuration

Azati developed a web administration interface (server-driven UI) where authorized administrators could assemble service reports from predefined field types and publish the active form. Available fields included text, numerical inputs, predefined selections, photo attachments, and signatures.

Business outcome: Administrators could manage report structures centrally, making the reporting workflow more adaptable when information requirements changed.

Supported field types:

Text and numerical fields
Select fields with predefined answer options
Photo attachments
Signature fields

Offline-first mobile reporting

Technicians can complete and save service reports on their mobile devices without an active internet connection.

Azati developed a mobile application using React Native, allowing elevator maintenance specialists to open the available form, enter service information, and save completed reports locally. Reports awaiting submission remained in the app’s local storage (AsyncStorage) until a connection became available.

Business outcome: Technicians could record service information at the point of work without relying on continuous connectivity.

Report submission and form updates

Technicians can submit completed reports when an internet connection is available, while the mobile application checks for available form updates when it is opened.

Azati implemented a workflow that allowed reports to be sent when connectivity was available or retained locally for later submission. The application also checked for updated form configurations when opened and retrieved available updates when a connection permitted.

A backend connected the mobile application with the web administration interface, transferring form configurations and storing submitted reports for administrators to access.

Business outcome: Field reporting could accommodate disconnected working conditions while connecting submitted reports with the central administration interface.

Handling edge cases: offline synchronization and data integrity

Building for disconnected field environments requires solving data synchronization challenges before they reach production.

Azati’s architecture addressed three critical technical risks:

Schema evolution and local drafts. When administrators update report templates via the server-driven UI, local drafts stored on technician devices are safely isolated from breaking schema changes and gracefully update when reconnected.
Resilient payload queuing. Completed reports are stored locally and queued for upload. When connectivity returns, a background process syncs queued reports automatically, without requiring the technician to reopen the app or retry manually.
Auditability and compliance. Every submitted report retains metadata from when it was completed in the field, including a local timestamp, device identifier, and sync timestamp, so you can verify a report's origin against when and where it was actually filled out, not just when it reached the server.

Need a field reporting workflow that works offline?

If your technicians work in locations with unreliable connectivity, or your inspection and service forms change more often than your mobile application can comfortably accommodate, Azati can help assess the workflow and define a suitable solution.

Discuss your custom field service application

Business impact

Reporting can continue without continuous connectivity

Technicians can complete and save service reports on their devices, then submit them when a connection is available.

Report structures can adapt to changing requirements

Administrators can configure and publish the active report form through the web interface rather than relying exclusively on fixed paper forms.

Field reporting and administrative review are connected

The mobile application, backend, and web interface connect report completion in the field with access to submitted reports in the administration interface.

The available project information does not quantify changes in administrative effort, reporting errors, paperwork costs, or maintenance downtime.

What Azati delivered

Component	Delivered capability	Operational relevance
Web administration	Configure and publish report forms	Accommodates changing information requirements
Mobile application	Complete and save service reports	Supports reporting at the point of work
Local storage	Retain reports awaiting submission	Allows work to continue without an active connection
Form configuration	Supports text, numerical, selection, photo, and signature fields	Accommodates different report structures
Backend	Transfers form configurations and stores submitted reports	Connects field reporting with administrative review

Who benefits from offline-first field service reporting?

This approach is relevant to organizations that rely on technicians working at customer sites, industrial facilities, or other locations where internet connectivity is inconsistent.

Typical use cases include:

Elevator maintenance and repair

Digital service reports for technicians working in buildings and elevator shafts.

Industrial field service

Inspection, maintenance, and repair reporting across distributed facilities.

Equipment servicing

Structured service records that technicians need to complete on site.

Infrastructure inspection

Digital forms for recording observations, measurements, photographs, and approvals in locations with limited connectivity.

It is particularly relevant to operations teams that need configurable reporting formats and cannot assume that every technician will have a reliable connection throughout the working day.

Why configurable forms and offline-first reporting matter

Field reporting applications face two separate constraints: the information technicians must collect can change, and the network connection needed to transmit that information may not always be available.

A fixed-form application can make changes to reporting requirements dependent on software updates. An online-only workflow, meanwhile, can prevent technicians from recording information when a connection is unavailable.

Azati addressed both constraints in one custom solution. The web administration interface allowed administrators to configure and publish report structures, while the mobile application could retain unsubmitted reports locally and retrieve available form updates when connectivity permitted.

This combination is relevant to organizations that need to adapt field reporting without assuming continuous connectivity. The appropriate implementation still depends on how form changes, stored drafts, data synchronization, and access controls must work in the client’s operating environment.

When to consider an offline-first field reporting application

A custom offline-first reporting solution may be worth evaluating when:

Field connectivity is unreliable. Technicians must record service or inspection information in buildings, industrial facilities, or other locations where a continuous connection cannot be assumed.
Reporting forms change. Operations teams need to update fields and answer options without relying exclusively on permanently fixed mobile forms.
Field and office workflows need to connect. Technicians enter information on site, while administrators need a central interface for managing forms and reviewing submitted reports.
The workflow is too specific for a generic form tool. The organization needs a mobile reporting process tailored to its service procedures and administrative requirements.

Before choosing an implementation, clarify how offline drafts should behave when forms change, how unsent reports are synchronized, what information must be protected on devices, and whether reports require audit trails or legally defined signatures.

Where could AI extend an offline-first field service app?

The application already connects configurable service forms, mobile report capture, local storage, and centralized administration. These components provide a starting point for exploring AI-assisted reporting and access to maintenance knowledge.

The opportunities below were identified as potential extensions for applications of this type, and were not part of the delivered project.

AI-assisted report completion and validation. AI could help technicians turn dictated notes into structured report fields, identify missing information, and flag inconsistencies before submission. Where processing takes place on a server, reports would need to be uploaded first. On-device assistance would require a separately designed and validated approach. Technicians remain responsible for checking the content.

Builds on configurable forms and structured service reports.
Technical document and photo intelligence. Where technicians attach photos or reference equipment documentation, computer vision and document processing could help extract relevant information, identify visible issues for further inspection, or associate records with equipment identifiers. Feasibility would depend on image quality, document formats, available reference data, and the specific maintenance task. AI-generated findings should support, not replace, technical inspection and approval.

Builds on the existing photo-attachment fields and the wider reporting workflow.
AI-assisted access to maintenance knowledge. Technicians could search manuals, troubleshooting guides, and approved maintenance procedures using natural-language questions rather than navigating documents manually. A knowledge retrieval layer could return relevant passages with links to their sources, subject to the organization’s access rules. For disconnected work, access to previously downloaded or cached material would need to be designed separately.

Builds on the mobile reporting workflow, extended with a governed knowledge layer.
Reporting analytics and recurring-issue detection. Once reports are collected centrally, data pipelines and analytical models could help identify recurring faults, compare patterns across sites or equipment types, and highlight records that warrant further review. Useful results would depend on report consistency, sufficient historical data, and reliable equipment identifiers.

Builds on: submitted reports and the centralized data available to the administration workflow.

What this requires

These extensions would need a separate assessment of report quality, available historical data, source documents, integration requirements, connectivity constraints, and human-review processes. AI features that depend on server-side processing would not automatically be available while a technician is offline. The appropriate architecture should be selected for each use case rather than assuming that every capability belongs on the mobile device.

Planning to extend a field service application with AI? Azati can help assess the existing workflow, data readiness, and integration requirements to identify which use cases are practical to validate first.

Planning an offline-first field service application?

If your technicians need to complete changing service or inspection forms without a reliable internet connection, Azati can help define the application architecture and delivery scope.

Start by mapping the field workflow, form configuration requirements, offline data handling, and synchronization needs. This creates a clearer basis for deciding what the application must support before development begins.

Discuss your field reporting requirements

Frequently asked questions

Elevator maintenance companies can replace paper reports with a mobile application that lets technicians complete structured digital forms on site and submit them electronically. A web administration interface can help authorized staff manage the forms, while offline storage supports reporting in locations without reliable internet access.

The solution Azati built for a client in Germany combined a mobile reporting application, a web administration interface, and a backend. Administrators could configure report forms using fields such as text, numbers, selections, photos, and signatures.

An offline-first mobile app allows users to complete and save information locally when a network connection is unavailable. The application can retain reports on the device and submit them when connectivity becomes available, depending on its implementation.

The elevator maintenance application developed by Azati stored reports awaiting submission on the mobile device. Technicians could complete and save their reports offline, then submit them when a connection was available.

Service teams can use configurable, server-driven forms that separate the form structure from a permanently fixed mobile interface. Authorized administrators manage and publish the form configuration, while the application retrieves available updates when it can connect to the server.

Azati built a web interface where administrators could configure and publish the active report form using predefined field types. The mobile application checked for available form updates when opened and retrieved them when connectivity allowed.

Field service management covers the broader category of tools for scheduling, dispatching, and managing field technicians. The application Azati built addresses one part of that category specifically. Namely, structured, configurable reporting that works without a reliable connection, rather than functioning as a full FSM platform with scheduling and dispatch.

Server-driven UI is an approach in which a server provides configuration that determines parts of an application's user interface. It can be useful when field service teams need to change form fields or reporting requirements without relying exclusively on a permanently fixed mobile form. The extent to which changes can be made without an app update depends on the implementation.

For the elevator maintenance solution, administrators configured report forms centrally through a web interface, and the mobile application used the available configuration to present the relevant fields to technicians. This supported adaptable reporting while keeping form management separate from field data entry.

Azati’s workflow and reporting application development expertise

Construction & Real Estate

AI-Powered Road Defect Detection

85–92% accuracy of pothole and road defect detection on annotated datasets

60–75% reduction in manual inspection time when using the prototype

70–80% success rate of video frame processing without loss of defect detection quality

Python
Caffe
OpenCV

Business challenge

Manual road inspections are time-consuming, inconsistent, and prone to errors. Municipalities and infrastructure operators need more efficient ways to identify potholes and other road surface defects, while automotive manufacturers can benefit from automated road-condition monitoring to inform vehicle maintenance.

Developing a reliable detection model presented an additional challenge: publicly available datasets did not provide sufficient suitable images, and real-world footage varied in lighting, camera angles, weather, and image quality.

Solution at a glance

Azati developed a computer vision proof of concept that detects potholes and other road defects in images and video footage. The team collected and annotated real-world road data, trained a custom object detection model, and built a prototype that highlights detected defects in images and reconstructed videos.

How Azati solved the challenge

Real-world road data collection: Azati collected road footage from vehicles to build a dataset reflecting actual road conditions. This addressed the limitations of publicly available data and provided examples for model training across different environments.
Data preparation and annotation: Video footage was divided into keyframes, which were manually mapped and annotated. The team also filtered out unsuitable, low-quality footage to improve training-data consistency.
Custom computer vision model: Azati trained a custom object detection model on the curated dataset to identify potholes and other road surface defects. The approach was tailored to the collected imagery rather than relying exclusively on generic pretrained models.
Image and video processing: The prototype processes both static images and video clips. Videos are split into individual frames for analysis, and the processed frames are reassembled into annotated footage.
Defect visualization: Detected defects are highlighted with bounding boxes in the output images and videos. This makes potential road damage easier to review and provides a basis for subsequent inspection and maintenance workflows.

Business outcomes

Automated road defect detection demonstrated: The proof of concept demonstrated the feasibility of identifying potholes and other road surface defects using machine learning and computer vision.
A custom dataset for model development: Real-world footage was collected, filtered, and annotated to address the shortage of suitable public training data and establish a foundation for further model refinement.
Visual outputs for inspection workflows: Annotated images and reconstructed videos make detected defects visible for review, supporting the development of AI-assisted road inspection processes.
Potential for more efficient maintenance planning: Automated defect detection could help municipalities identify road damage for further assessment and repair planning, reducing reliance on exclusively manual inspection.
Foundation for future computer vision development: The prototype established a starting point for improving road defect detection models and exploring applications in infrastructure monitoring and automotive road-condition assessment.

Full case study

Professional Services

Automated Steak Marbling Grading Solution

98% grading accuracy

75% reduced inspection time

90% consistent results

Python
OpenCV
React Native
Generative AI
ML

Business challenge

The client needed a more consistent and objective way to assess steak marbling quality across production workflows. Manual grading depended heavily on individual evaluators, leading to inconsistent results, slower inspection cycles, and challenges maintaining quality standards at scale. Environmental factors such as lighting conditions, image variability, and subtle differences in marbling patterns further complicated accurate assessment.

Solution at a glance

Azati developed an AI-powered computer vision solution that automatically evaluates steak marbling from photos using a convolutional neural network (CNN). The solution focused on reducing subjectivity in grading, accelerating inspection workflows, maintaining consistent quality standards, and providing an intuitive mobile experience for operational staff. The system was designed to support continuous model improvement without disrupting production operations.

How Azati solved the challenge

Computer vision model development. Trained a CNN model on client-provided image datasets to identify and classify marbling patterns with high accuracy.
Image preprocessing and quality optimization. Implemented preprocessing techniques to minimize the impact of glare, lighting variability, and image inconsistencies.
Mobile AI deployment. Developed a mobile application that enables users to capture images and receive grading results directly on the production floor.
Iterative model refinement. Improved model performance through testing, validation, and multiple feedback-driven development iterations.
Continuous model update capability. Designed the platform to support AI model updates without requiring full application redeployment.
Human-centered workflow design. Created an intuitive interface suitable for operational personnel without specialized AI or technical expertise.

Business outcomes

Automated quality grading. AI automatically evaluates steak marbling levels from captured images, reducing dependence on subjective human assessments.
Computer vision-based inspection. CNN models analyze visual characteristics and classify marbling patterns consistently across large volumes of products.
Mobile inspection workflow. Production staff can capture photos and receive grading results directly from a mobile device.
Near real-time assessment. The system delivers rapid grading results to support high-throughput production environments.
Adaptable AI models. Supports continuous retraining and deployment of improved models as new datasets become available.
Scalable quality-control platform. The architecture can support additional visual inspection and quality-classification use cases beyond steak grading.

Full case study

Construction & Real Estate Engineering & Manufacturing

Automated Reporting Platform for a Canadian Municipality

50 engineers freed from routine manual reporting

624 reports processed daily

16 weeks from development to delivery

React
React Native
MongoDB
Java 8

Business challenge

A Canadian municipality relied on manual reporting to track equipment depreciation across departments. Dozens of evolving templates created inconsistent data and repetitive work, while engineers in remote locations needed to collect information without reliable internet access. The municipality needed a centralized platform to standardize reporting, support offline fieldwork, and handle high report volumes.

Solution at a glance

Azati developed an integrated reporting platform comprising cross-platform mobile applications for field engineers and a web interface for administrators. Dynamic form templates, offline data collection and synchronization, centralized report management, and automated notifications streamlined the reporting process.

How Azati solved the challenge

Clarifying requirements through iterative discovery: The municipality initially had a high-level vision but lacked detailed business rules, workflows, and field-level specifications. Azati used weekly discovery sessions, rapid prototyping, and continuous stakeholder validation to clarify requirements alongside development.
Building mobile applications for field reporting: Azati developed React Native applications for iOS and Android, enabling municipal engineers to record equipment depreciation data directly in the field. Engineers could complete forms offline, navigate between sections, and preview submissions before sending them.
Standardizing reporting with a dynamic form builder: A configurable form builder enabled administrators to create and update form and report templates without relying on developers for routine changes. Template versioning and centralized rule management helped accommodate evolving requirements across departments and equipment types.
Implementing offline-first data synchronization: The mobile applications stored data locally and synchronized submissions when connectivity returned. Auto-save and incremental synchronization supported fieldwork in locations with unreliable internet access, while helping prevent data loss and conflicting updates.
Centralizing report management and notifications: A web-based administration interface brought user management, template configuration, form submissions, and report review into one system. Submission tracking and automated email notifications gave relevant stakeholders visibility into reporting progress and required actions.

Business outcomes

50 engineers freed from routine manual reporting, allowing staff to focus on priority tasks.
624 reports processed daily through the reporting platform.
16-week delivery for the complete system.
More consistent reporting through standardized templates and centralized form management.
More reliable field data collection through offline access and automatic synchronization.

Full case study

Last updated

2026-11-03

Got a job for Azati? Let’s talk business!

Browse files

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

What's next?

1. Tell Us Your Story

Describe your project. We come back within one business day with team availability and a rough plan. NDA on request before the first call.
2. Get Your Roadmap

Receive a detailed proposal with scope, team composition, timeline, and costs tailored to your goals.
3. Start Building

Azati aligns on details, finalize terms, and launch your project with full transparency.