Websites had their WordPress moment. SaaS is having its BuildWithHQ moment. See the new BuildWithHQ homepage →
Example product you can build today · Work verification

Make every checkoff provable and accountable.

Build a reusable checklist system that attaches to any record, ticket, project, asset, or work order. Require a document or photo for critical steps, then route completed work through real human signoff.

Any recordDocument + photo proofHuman signoffRole + location security
Checkoff & Approval · product previewBuilt with BuildWithHQ
8 / 8Items complete
3Proof files
1Signoff waiting
WO-1042 · READY FOR SIGNOFFRooftop unit commissioning

Electrical isolation, startup readings, and final-site photos are complete. The reviewer sees the work and its evidence together.

Open proofReview itemsApprove
Product blueprint

Add proof-backed completion without inventing a second approval system.

Use Checklists & Signoffs as the work-verification layer. The target stays in its native module, uploaded evidence stays in Files, and the final decision stays in Workflow and Universal Inbox.

01

Reusable templates

Define ordered items, instructions, response types, required steps, and the minimum proof expected.

02

Attach to any record

Place the module on a work page or pass a target record ID for a ticket, project, asset, inspection, or work order.

03

Documents and photos

Require any file, a document, or a photo for each item. Original bytes remain governed File records.

04

Secure by inheritance

The checklist follows the target record's tenant, DataRole, and Location envelope.

05

Universal Inbox review

Requesting signoff creates a normal require_approval Workflow step and Inbox item.

06

Durable accountability

Record who completed each item, uploaded each proof, and approved or rejected the work.

The architectural rule: the checklist coordinates work; it does not replace the work record, file system, security envelope, Inbox, or approval engine.
Implementation path

Build the complete journey, not just a row of checkboxes.

STEP 01Design the templateAdd item text, answer type, required flag, proof type, and minimum count.
STEP 02Attach it to workStart a run against the secured record representing the ticket, project, asset, or job.
STEP 03Complete with proofWorkers save responses and upload documents or photos through Files.
STEP 04Sign off in InboxA permitted reviewer approves or rejects the Workflow item.
Builder configuration

What you decide

  • Which records show the module
  • Template items and ordering
  • Required versus optional completion
  • Document, photo, or any-file proof
  • Who receives approval rights
Platform enforcement

What BuildWithHQ preserves

  • Verified tenant identity
  • DataRole and Location visibility
  • Secured File ownership and download
  • Inbox activity-version protection
  • Workflow approval and audit lineage
Under the hood

Existing platform capabilities working as one feature.

Universal RecordsThe target identity for any first-class or custom module.
FilesPrivate storage, metadata, download authorization, and evidence lineage.
Workflow + InboxThe human-approval engine, reviewer queue, decision fence, and resolution history.
DataRoles + LocationsThe same security envelope used by the work and its evidence.
Ways to package it

Use it wherever completed work must be trusted.

FIELD SERVICE

Commissioning and closeout

Require readings, safety checks, customer acceptance, and before/after photos.

SUPPORT

Incident resolution

Verify reproduction, remediation, communication, and attached logs before resolution.

OPERATIONS

Quality and compliance

Collect inspection evidence, policy acknowledgements, and management signoff.

Build your version