Raise, gas-test, approve, extend and close permits on mobile.

The permit stops being a piece of paper that happens to be in the right pocket and becomes a time-bound, signed, queryable control with a named owner at every step.
The attendance log is contemporaneous, the re-test readings are validated at the point of entry, and the permit cannot be closed against a log that was never filed.
A permit can be raised, filled and submitted with no coverage at all, the form, its reference lists and its compiled rule logic are on the device before the crew leaves, and the submission including photographs queues locally until the device reconnects. Approval is different by design: an approval decision is recorded on the server so that it cannot be forged or replayed, so the approver needs connectivity at the moment they sign. In practice that means the performing authority works offline at the job and the issuing authority signs from the control room, the site cabin or their phone once in coverage.
The workflow reads the expiry datetime out of the permit itself and parks the run until that moment arrives, then takes a dedicated expiry branch. That branch can notify the permit holder, the control room and the area authority, change the permit status, and dispatch an extension request as its own form requiring a fresh approval. Nothing depends on a person watching a clock, and an extension becomes an approved decision with a timestamp rather than an annotation on the original sheet.
No, and keeping them separate is usually the mistake. One published permit form can carry every hazard variant, with rules revealing only the sections that apply to the work type selected. Rules can additionally be tagged into groups, and the dispatch chooses which groups are active, so the same form behaves as a different permit depending on the job. That keeps a change to the common sections, a new authority signature line, a new hazard prompt, as a single edit rather than six.
An approval step can be configured to require an e-signature, using either a password step-up or a drawn signature. The verification is done on the server, not in the app: the signing token is checked against the acting user, it is single-use, and it is claimed in a per-customer ledger inside the same transaction as the decision, so a replayed or reused signature is rejected. The signature, the method, the user and the time are stored against the approval task. We make no claim about the legal status of an electronic signature in your jurisdiction; what the platform provides is a tamper-evident, attributable, non-replayable record of who approved what and when.
Contractors can be users in your account with roles that limit them to raising and completing permits without seeing anything else. Access is component-level role-based, so a contractor supervisor can be given the permit forms and their own submission history and nothing more. Sign-in can go through your own identity provider over SAML or OIDC where you want contractor accounts governed centrally, and permits raised by a contractor still route to your issuing authority for approval.
Yes. A workflow node can email a rendered permit, POST it to an API or webhook with a signed payload, drop a file over SFTP, or map named permit fields onto target fields in SAP S/4HANA or Dynamics 365 through a structured connector. A permit form can also call outward while it is being filled: an API question can query your maintenance system for the equipment record or open work orders and drop the answer into the form while the requester is still standing at the job. Destination credentials are encrypted at rest and outbound calls pass a server-side egress allowlist.
Yes. IndeForms deploys on-premise, including fully air-gapped installations for sites that cannot allow outbound connectivity. In that mode no vendor code runs inside your install and configuration updates are applied through signed offline bundles. Where you enable AI-assisted features, the platform never sends real answer values to a model, form structure and aggregate statistics only, and features that inherently need answer content run only against a self-hosted model in your own environment.
A submission that has not synced does not exist on the server yet, that is a real limit of offline capture, and we would rather say so than imply otherwise. Two things reduce the exposure. First, data at rest on the device is encrypted, so a lost handset is not a readable permit register. Second, the sync is opportunistic rather than manual: the app uploads whenever it regains coverage, so the window is usually the length of one job rather than one shift. For work in permanently dark areas, teams commonly place a sync point at the access control gate so records land as the crew leaves the area.