Taskhull for QA & compliance

Every inspection done the same way — with proof.

Turn your procedure into a versioned checklist. Every audit, batch or inspection is a project that stays pinned to the version it ran on, with photos, comments and a full history.

Template
v3 · Published
Incoming goods inspection
  1. 1Check delivery note
  2. 2Visual inspection
  3. 3Measure samples
  4. 4Record deviations
  5. 5Release batch
Projects
from v3
  • AUD-0412 · Batch 39-A
    Completed
    100%
  • AUD-0413 · Batch 39-B
    Blocked
    40%
  • AUD-0414 · Batch 40-A
    Active
    12%
My tasks
3 ready
  • Measure samples
    AUD-0414 · Batch 40-A
    2/5Photo required
  • Record deviations
    AUD-0413 · Batch 39-B
    1/3Photo required
  • Visual inspection
    AUD-0414 · Batch 40-A
    0/4Photo required
Sound familiar?

Where it goes wrong today

01

Evidence is spread across inboxes and phones

Photos sit in a chat, sign-offs in email. Pulling it together for an auditor takes days.

02

“Which version of the procedure did we use?”

The procedure changed in March. Nobody can say for sure which runs followed the old one.

03

Steps get skipped when it's busy

Paper checklists get ticked afterwards, or not at all, and deviations go unrecorded.

How it fits

Your words, our model.

Taskhull has only a few ideas, so it fits the way your team already talks about the work. Here's how they map.

Template
Your audit or inspection procedure
Project
Each audit, batch or inspection
Reference
AUD-0412
My tasks
Inspectors, with photo and comment evidence
Taskhull for QA & compliance

What changes with Taskhull

Versioned procedures

Publish a procedure as a numbered version with a change note. Every run records exactly which version it followed.

Required photos and comments

Mark the steps that need evidence. A task can't be marked done until the photo or comment is attached.

A full activity history

Who started, ticked, commented, blocked and finished each step, and when — on every audit, batch and inspection.

Blocked with a reason

Define your own block reasons, such as awaiting sample or deviation found, so holds are visible and consistent.

Questions, answered

Make the next audit the easy one.

Turn a procedure into a template and collect the proof as the work gets done.