Context
- Internal mobile app for service partners in the field
- Offline-capable by design so service work, evidence capture, and signatures can continue on-site
- Guides order execution and reliable handover back into connected backend processes
- Built for operational work where reliability matters more than visual novelty
Field-service software earns trust in places where no one has time for software drama: in customer homes, on tight schedules, and often with weak connectivity. The real challenge is not showing a task list on a phone. It is guiding the job from arrival to handover, capturing evidence on site, and making sure nothing gets lost on the way back to the organization.
This is what makes the Marquardt Service-App such a strong reference. This app is built around real service work. It helps service partners move through the job in a clear sequence, document what happened on site, capture the necessary evidence, and hand the result back in a form the organization can actually work with. In other words, it is not a lightweight companion app. It is an operational tool that supports execution from arrival to completion.
Product visuals
Screens, product surfaces, and supporting material
Core differentiator
What stands out most is the offline-first character of the workflow. For a service-partner app, that matters because documentation, image capture, signatures, and handover often happen in customer environments where mobile coverage is unreliable or simply absent.
- Work continues even without stable connectivity
- Inputs are preserved locally until synchronization is possible
- Photos, signatures, and documents can be collected on-site
- Visible network and upload status help users understand what is already transmitted and what is still pending
That combination is important because field-service documentation rarely happens in ideal conditions. The workflow has to survive customer locations, moving schedules, and inconsistent network quality.
We can feel that in the shape of the product itself. Guided execution, image-heavy documentation, signatures, scheduling context, and later transmission back into business processes only work well when the job can be completed first and synchronized afterwards. That is why offline capability is so central to the case.
What the product delivers
- Guides service partners through the active order workflow step by step
- Captures photos, documents, payment information when needed, and signatures on-site
- Keeps inputs safe locally and synchronizes results once connectivity returns
- Feeds structured completion data back into connected backend systems
Guided workflow design
The active order flow is designed as a clear sequence so service work remains consistent and traceable.
- Navigate to customer
- Arrive on-site
- Unload / assemble
- Complete the quality checklist
- Finish the service protocol
- Handle payment when required
- Capture the final signature
Then: transmit the result in the background.
Scheduling, evidence, and handover
What matters here is that the app supports much more than task completion. It sits inside the daily rhythm of service work: planning appointments, keeping track of customer-service positions, handling blocked times, capturing image-based evidence, and making sure order data and documentation reach the right place afterwards.
- It supports scheduling and coordination around active customer-service work
- It gives field teams orientation through dashboards, calendars, and service positions
- It supports evidence-heavy workflows where images and documentation matter
- It helps the handover work continue after the on-site visit instead of ending with a simple status change
This is important because good field-service software has to connect planning, execution, and handover in one reliable flow. That is exactly what this product does.
Contribution note
As BasalBit GmbH, we contributed directly as the delivery company on this project.
- Product strategy and process analysis
- UX/UI for guided workflows
- Agile delivery and QA
- Mobile engineering, offline-first behavior, and backend integration
In this project, we were able to turn operational complexity into a mobile process that stays dependable in the field, supports offline-first capture, and remains understandable under pressure.
This is what gives the reference its strength: guided workflow design, scheduling-aware service operations, image-heavy documentation, and reliable handover back into connected business processes.
Disclaimer & sources
Product names and trademarks belong to their respective owners. We present this as a BasalBit portfolio case study. On this project, BasalBit GmbH contributed directly as a company.