Inspection Checklists
Walk a place on a schedule and record what you find. Staff mark each check, and a problem becomes a ticket on your project board. The same checklists work for any company, from a building walk-through to any other round.
Key Features for Inspections
Checklist and Schedule
Set up a named checklist with a description, a ticket project, an optional default assignee, and an active switch. Schedule it as none, daily, weekly, or monthly. The list shows ok, due, overdue, or in progress. The schedule marks the list. It does not send the worker out by itself.
Sections and Checks
Group checks in named sections, such as Entrance or Roof, or leave them on their own. A check is a name. Reorder sections and checks. A round needs at least one check, and an inactive checklist cannot be started.
Outcome Buttons
Each checklist has its own result buttons. The defaults are Normal, which opens no ticket, and Not normal, which opens a ticket. Rename buttons, add more, and pick green, red, orange, blue, or gray. A button can open a ticket, require a note, and require a photo, each on its own. A photo is stored on the ticket, so a required photo only works together with opening a ticket.
One Open Round
Start from the list. If a round is already open, start continues that same round. Only one round of a checklist can be open at a time. Walk every check, grouped by section, with progress as answered count out of total. A result that requires a note or a photo cannot be saved without them. Editing the checklist later does not change a round already in progress.
Tickets from a Check
When the chosen result opens a ticket, the app creates one on the checklist project. The title is the inspection name plus the check name. The description includes the note, the inspection, the section, the round date, and the worker. The ticket starts in that project first status. The default assignee becomes the responsible person. Photos on that check are attached to the ticket. Changing the note later updates the ticket description. The round keeps a link to the ticket.
History and Permissions
Each checklist keeps a history of rounds: when it started, who started it, when it finished, how many checks were answered, and how many tickets were opened. A finished round stays readable. Two rights apply: Inspections, to design checklists, and Inspection rounds, to view and run them. A person can run checklists without being allowed to redesign them.
Teams run their rounds in Lua CRM
Start your journey with Lua CRM today
How It Works
1. Set Up the Checklist
Name it, choose a schedule and a ticket project, and turn it on.
2. Add Checks and Buttons
Add sections and checks, and set what each result button requires.
3. Run the Round
Start the walk-through. If one is already open, you continue that round.
4. Finish and Follow Tickets
Finish only when every check has a result. That time drives due and overdue. Problems are tickets on the project board.
Why Choose Lua CRM for Inspections?
Any Company
The same checklists work for a building walk-through or any other round. Inspections are not limited to one industry.
Due on the List
Daily, weekly, and monthly schedules mark the checklist due, overdue, or in progress. They do not send the worker out by themselves.
Dedicated Support
Our team is here to help you every step of the way.
Ready to Run Inspections in Lua CRM?
14 günlük ücretsiz deneme sürümünüzü bugün başlatın. Kredi kartı gerekmez.