A code on the object, a record in your workspace
Hazard reporting
Let permitted visitors report a problem with its location, description and photo. Managers receive an in-app notice and can follow the issue to closure.
Create this solutionQA-014Starting record fields
These fields come from the working preset. Add your own questions, options and required fields before publishing. The core condition, quantity or reading-confirmation field stays in place where the workflow needs it.
| Field label | Field type | Required |
|---|---|---|
| Problem summary | Short text | Yes |
| Location | Short text | Yes |
| Problem description | Long text | Yes |
| Problem photo | Image attachment | No |
Set up, test, then print
- 01
Configure the object and its access
Create a register with a permanent reference, then add its location and description. Mark each attribute you intend to show publicly. Choose manager-only access, all workspace members or named members for private records.
- 02
Publish and place the code
Save a draft, preview the public information, then publish. Choose the platform or an active custom domain when creating the register. Download the code or open a print template; updates keep the original scan address.
- 03
Record, process and review
Submissions keep their original answers and field snapshot. Processing notes and decisions are separate dated events. Free managers can complete basic processing; paid review features add assignment, deadlines and an independent reviewer.
Private attachments and traceable changes
PNG, JPEG and PDF attachments are limited to 5 MB each and stay bound to their record. Authorized members can read them; a public submitter can read only their own receipt in the same browser. Export CSV for a selected period without exposing the complete register publicly.
Private access
- Owners and administrators
- All workspace members
- Selected workspace members
Public
Published pages show only the attributes you selected. Records and attachments stay private.
Start with Free, expand for a team
| Plan | Object allowance | Records per UTC month | Active schedules | Assignment and review |
|---|---|---|---|---|
| Free | 3 | 100 | 1 | No |
| Pro | 100 | 2,000 | 20 | Yes |
| Business | 1,000 | 20,000 | 100 | Yes |
| Business Plus | 5,000 | 100,000 | 500 | Yes |
Independent review requires at least two active members with suitable access. Pro includes the review feature, while team capacity is determined separately by the plan. A downgrade keeps records and export; available objects and schedules follow the remaining allowance.
Compare plans
Frequently asked questions
Can a scan prove that someone is at the location?
No. A QR link can be copied or shared. Account identity and timestamps provide a useful record, but these workflows do not use GPS, facial recognition, biometric attendance or a legal signature service.
Can visitors browse other submissions?
No. The published page contains only selected object attributes and the entry form. Record lists, processing notes and attachments require permission; visitor receipts are restricted to their original browser.
Are these records certified or legally signed?
The platform keeps account-based audit events and publication history. It does not provide blockchain certification, qualified electronic signatures, inspection accreditation or automated compliance approval.