Overview
A Continuous Checklist can act as an internal request form: a team member opens it when needed, records the request and raises follow-up work through an Assignment Trigger.
Use this pattern for requests such as restocking an area or reporting a facilities job. Each submission creates a Result, and the Assignment is the work item the receiving team follows.
At a glance |
|
Who can do this | Super Users, or Checklists › Create and Schedules › Create; existing content needs modification access. |
Where | Checklists and Schedules › Create › Continuous Schedule |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: A structured form gives requesters consistent prompts while the receiving team works from assigned tasks.
Define the request journey
Choose one request type, the Locations it applies to and the User Group that will receive the work. Decide which details belong in the Checklist and which must be entered on the Assignment itself.
Use a short form: what is needed, any useful context and a Select Question such as “Is follow-up work required?” Avoid using a request form for a check that must be completed by a fixed deadline.
Build and route the form
1. Create the Checklist
Create the request Checklist and name it for the person submitting it, for example “Request a restock”. Use creating a Checklist for the editor workflow. Use a Requirement Trigger if a particular answer must include a photo or comment.
2. Add the Assignment Trigger
On the follow-up Select Question, open Triggers › Add Trigger › Assignment Trigger. Set the answer that should create work, then set a Prefilled title and Assigned to (Users/User Groups). Confirm that the receiving team can access the relevant Locations.
Keep user confirmation enabled while establishing the workflow so requesters can review the task details. Only use Require no user intervention when creating assignment when its prefilled title and assignees are sufficient. See Assignment Triggers.
⚠️ Heads-up: The trigger’s Description is guidance shown to the User; it is not saved as the Assignment’s description. Do not assume every answer from the request Checklist becomes task text. Check both records in your trial submission.
3. Make the form available
Create a Continuous Schedule, choose the request Checklist, set its Locations or Location Groups and add the requesting team as assignees. Leave kiosk-style Behavior options off unless you need them. See Continuous Schedule setup.
Run and follow up a request
The requester opens the form under Continuous Checklists in the Mobile app. They complete it when a request is needed; the form remains available for later requests.
The receiving team manages the resulting Assignment through its normal statuses. Completing the form records the request; it does not mean the requested job is finished. Agree who checks incoming work and who closes it with resolution details.
Trial the form at a representative Location and inspect the Result and Assignment together. Check the assignee, title, deadline and useful context before assigning the form to the wider team.
Best practices
Keep the request form focused on one recognizable job.
Use a team assignee that will be maintained as staff change.
Review a sample of incoming requests after launch and improve unclear prompts.
Frequently asked questions
Can a Continuous Checklist be used for jobs with no fixed day?
Yes. It is available whenever needed. If you need a deadline or a Missing Result when work is not done, choose a Calendar Schedule or Ad Hoc Slot instead. See Schedule types.
What are Subscribers on an Assignment Trigger?
They are people added to follow the Assignment’s activity. Use assignees to identify the responsible team. See Assignment subscribers, comments and mentions.
Will an unused Continuous request form become a Missing Result?
No. Continuous Schedules have no due slots and produce no Missing Results. See Continuous Schedule behavior.