Use cases

Built for the paperwork of any operation

The same platform runs each of these. They are configurations, not products — you can have all of them in one workspace.

Field inspections and reports

Someone on site scans a QR code, fills in the report on their phone, and it is filed under the right job as a PDF before they leave.

  • Form → report record with the job linked
  • Word template filled: site, client, date, inspector, result, notes
  • Emailed or WhatsApped automatically
  • A shared page lists every report for the client

Approvals

Invoices, expenses, purchase requests move Draft → Submitted → Approved → Paid. Submitting assigns the approver with a due date; approving sends the PDF.

  • Assignments with reminders and holds
  • Dashboard: unpaid, by client, this month
  • Event log for who approved what and when

Stock and consumables

One QR label per item on the shelf. Scanning shows the quantity and two buttons: Receive and Use. Low stock flags itself and shows on the dashboard.

  • Actions logged with who and how much
  • Flag: Quantity below Minimum quantity
  • Widgets: low stock count, low stock by supplier
  • JSON endpoint for a barcode scanner

Contracts and client documents

Quotes, contracts, permits, certificates and drawings filed by client and job, with versions, check-out and retention. Share one record or a page of them by link.

  • Duplicate detection on upload
  • Office files previewed as PDF
  • Expiry fields and retention rules

Equipment and assets

A record per unit with its history. A QR on the unit opens its page: last service, next due, documents, and a 'Mark serviced' action.

  • Flags for overdue service
  • Links to the job and the client
  • Pages for the owner without a login

People and compliance files

Certifications, training records, onboarding forms and policies per person, visible only to the people who should see them.

  • Named access lists per record
  • Field-level security
  • Expiry flags for certificates

Your case is probably one of these.

And if it isn't, it is a record type, a form and a workflow away.