> For the complete documentation index, see [llms.txt](https://changelog.visilean.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.visilean.com/quality/quality-changelog/release-2.0-2026/quality-on-mobile-checklists-signed-off-on-site.md).

# Quality on Mobile: Checklists Signed Off on Site

Quality inspections happen on site, but an inspection isn't finished until its checklist is filled in and signed off. When completing or approving a checklist means going back to a desk, answers are written up from memory, sign-offs queue until someone is next at a computer, and the people next in line don't know a checklist is waiting for them. Release 2 brings the Quality Module to the VisiLean mobile app, live from 29 January 2026, and adds email notifications so people hear about a checklist when it needs them rather than the next time they log in.

#### Why This Matters

Every step between an inspection and its sign-off is a chance for the record to drift from what was actually seen, or for work to wait on an approval nobody knew was due. Filling in and approving checklists at the point of work keeps the record accurate and the sign-off route moving. Notifications tell each person when it's their turn, and approver history shows exactly who acted on each response, when, and what they decided.

#### What's New?

* **The Quality Module on mobile.** List, search, fill, view and approve checklists from the mobile app, so inspectors and approvers can complete and sign off checklists on site.
* **Automatic email notifications.** Emails go out when a checklist is filled, submitted, approved, rejected or reopened, and when it reaches its due date.
* **Approver history.** Every response records who reviewed it, when they reviewed it and what they decided, giving you an audit trail for every sign-off.
* **Copy a checklist.** Use an existing checklist as the starting point for a new one. Repeat copies are named automatically ("Copy", "Copy 2", "Copy 3") so they don't clash.

#### How It Helps: Three Example Use Case Scenarios

A Site Engineer carries out a pre-handover inspection with the checklist open on their phone, answering each question at the location it refers to and submitting the response before leaving the floor.

The approver receives an email as soon as the response is submitted, opens it on the mobile app between site walks, and approves it on the spot. If they reject it instead, the engineer is emailed straight away and can rework it the same day.

A Quality Manager needs a checklist for a new inspection that closely follows an existing one. They copy the existing checklist, adjust the questions, and later use approver history to confirm who signed off each response and when.

{% hint style="info" %}

#### Key Considerations & Caution Points

**What triggers an email:** a checklist being filled, submitted, approved, rejected or reopened, and a checklist reaching its due date.

**Copy naming:** repeat copies of the same checklist are named "Copy", "Copy 2", "Copy 3" and so on, so they don't clash with each other.

**Approver history:** every review is recorded with the reviewer, the time and the decision, building an audit trail for each response.
{% endhint %}