Inspection software for thorough and documented checks

Yes. In Lumiform, you create entities to represent assets, locations, vehicles, or equipment. Once set up, you can view all inspections and actions linked to that specific entity. This is the starting point customers in facility management and manufacturing use to track inspection history per machine or site. If your current mental model is object-first, this is how Lumiform structures it: start from the asset, see what was done, what was flagged, and what still needs resolving.

Lumiform supports QR code scanning natively. RFID tag support is not a current feature. If your inspection points require physical presence verification at specific equipment locations, QR codes placed at each point serve the same function: the inspector scans on-site, which ties the submission to that exact location. For teams concerned about inspectors completing checks remotely from a control room, QR codes at each machine or checkpoint enforce physical presence at the point of inspection.

The Lumiform mobile app works offline on iOS and Android. Inspectors complete forms, capture photos, and record findings without a connection. When connectivity is restored, the app syncs automatically. This is a hard requirement for teams working in basements, underground environments, or remote sites. Data entered offline is not lost. Customers who previously dealt with apps that crashed or delayed uploads by a week specifically cite offline reliability as a reason they moved to Lumiform.

Photos are included in the generated PDF report. File size can become significant when many high-resolution photos are attached, which some customers have flagged as a practical issue when emailing reports to clients with inbox size limits. If report file size is a concern for your workflow, this is worth testing during your trial with a realistic number of photos attached, so you can confirm the output meets your delivery requirements before committing.

Lumiform’s report builder lets you add your company logo, configure the header, and customize the footer. The output is a branded PDF that looks like a formal inspection document rather than a generic checklist result. Customers who hand reports directly to clients on-site, or who need a document that looks professional when printed, use this to ensure the report carries their company identity and meets the presentation standard their clients expect.

You can assign an action to an external person via email. They receive a notification with the relevant details and can respond without holding a full Lumiform license. This covers scenarios where corrective actions need to go to maintenance technicians, external contractors, or building managers who are not part of your Lumiform organization. The action status and any response remain visible to the manager inside Lumiform, so follow-up does not require chasing by phone or email.

Lumiform captures e-signatures within completed inspection forms, and the signed report is stored with a timestamp and audit trail. Whether a digital signature meets the legal standard in your specific jurisdiction or industry depends on local regulations and the nature of the document. For most operational use cases, such as shift handovers, safety checks, and inspection sign-offs, the combination of a named user login, timestamp, and captured signature provides sufficient documented accountability. For legally binding documents with specific certification requirements, confirm with your legal team.

Lumiform captures GPS location data when inspections are completed on mobile. You can also place QR codes at specific equipment points or locations and require inspectors to scan them as part of the form. This confirms the inspector was physically at that point, not completing the checklist from an office or control room. For teams running shift-based operations where the temptation exists to complete checks remotely, combining GPS capture with QR code scanning at each checkpoint closes that gap.

Lumiform’s form builder includes conditional logic. You set rules so that a specific answer, such as “no” or “fail,” triggers follow-up questions, mandatory photo fields, or corrective action prompts. This means inspectors cannot skip past a problem without providing context. For quality and safety workflows where a negative finding needs a description, a photo, and an assigned action, you build that sequence directly into the form so the process enforces itself rather than relying on the inspector to remember.

You can set individual questions to require a photo before the form can be submitted. The inspector cannot complete and send the form without attaching the image. This is used in vehicle handover inspections, damage reporting, cleaning verification, and safety checks where photo evidence is the proof of condition. Customers who previously dealt with forms submitted without photos, or drivers who skipped damage documentation, use mandatory photo fields to enforce the standard at the point of capture.

Lumiform generates individual PDF reports per inspection and provides analytics data you can export. A single bulk export that pulls 40 reports into one consolidated Excel table with one row per submission is not a native one-click feature in the standard interface. Customers with high-volume field operations who need consolidated data for BI tools typically use the API or database integrations to extract structured data into external systems like Airtable, Snowflake, or Power BI. This is worth confirming with the sales team for your specific volume and format requirements.

Yes, via the API. When an inspector flags an issue during an inspection, you can configure the API to trigger an automated action in your ERP system, such as creating a work order for the engineering or maintenance team. This removes the manual step of re-entering the finding into a second system. API access is available on the Enterprise plan and as an add-on on the Professional plan. The specific integration requires development work on your side to connect Lumiform’s API to your ERP’s endpoints.