Practical software guides
An internal site-readiness view should separate official permission, field observations and the decision to open. Software does not issue a permit or override an inspector.
| Stage | Evidence |
|---|---|
| Request | Event scope and official permit reference |
| Inspection | Authorised inspector’s finding, date and version |
| Maintenance | Assigned corrective work and verified closeout |
| Vendor readiness | Stall allocation, utilities and outstanding conditions |
| Go/no-go | Responsible authority confirms the reviewed conditions |
A field worker records a broken light while offline. The photo remains pending until upload; a server timestamp is not the inspection time. If another worker closes the fault before synchronization, present the conflict for review instead of overwriting one observation.
Reopening variation
A fictional market stall has water available but its electrical inspection is still unresolved. Show each dependency and its evidence separately. “Construction complete” must not become “vendor ready.” A public page can show access and opening information without exposing inspection photos, vendor identity documents or staff comments.
Use the relevant local authority’s current permit process. Have qualified officials review the real conditions, safety and opening authority. This is a software coordination specimen, not a permit checklist certified for any event.