Feature Requests

Current Situation Some checklists contain a long list of items, which requires users to manually select a response for each item during inspections. Issue This process can be time-consuming, especially when most responses are typically the same (e.g., Pass, OK, or Completed). Proposed Enhancement Allow checklist creators to set a default value for each checklist item. Expected Behavior When a checklist is generated: Each item will be pre-filled with the configured default value. Users can still change the response if needed during the inspection. Benefit Speeds up checklist completion. Reduces repetitive manual input. Improves efficiency for inspections with many checklist items. [ALR]

Currently, checklists must be scheduled through a parent checklist with predefined frequencies, or created as adhoc checklists which are generated immediately with the current date. For clients managing periodic tasks across many locations, this can lead to excessive parent checklist configurations and administrative overhead. Suggestion: It would be useful to allow managers to generate a checklist from an existing template, assign it to a location and responder, and schedule it for a specific future date/time. The checklist would only be created and appear to the responder at the scheduled time, enabling better planning and reducing the need to create multiple parent checklists. It's similar to using Schedules but this is directly within the Checklists module: Example Use Case A manager needs to schedule monthly inspections across 100 locations. Currently they must: Create multiple recurring parent checklists for different locations, or Generate adhoc checklists that appear immediately (with the current date/time). With this enhancement, the manager could: Generate a checklist from a template Assign it to the required location and responder Schedule it for the correct inspection date The checklist will only appear to the technician when the scheduled time arrives. Benefit: This will be especially useful for periodic tasks (e.g., different cleaning methods and frequencies across multiple locations). Managers would only need to create a checklist template for each method, then assign it to locations and schedule it accordingly based on their master schedule. [KWSH, SSH,]

To display Customer's details like address in the checklist details. Currently there's no way for responder to click through the name of the customer to for more details. [Don Jon]

When a completed checklist is reverted back to Pending, the remarks entered during the revert action are currently only visible in the History section and not reflected in the checklist PDF. As a workaround, allow the History table (including status remarks) to be optionally included in the checklist PDF via the PDF layout configuration. [CBRE NEA]

To include asset details in Checklist report - similar to request pdf report. [KWSH]

Currently, each child checklist is linked to a specific asset but shares the same checklist title. This makes it difficult to distinguish between child checklists, as the only identifier is the asset ID. When exporting the checklist as a PDF, there's no way to identify the associated asset. Adding the asset description to the title of each child checklist (using it as a placeholder or parameter) would make it easier to differentiate them. [ALR]

Users require the ability to link a Summary Report (configured as another checklist) that will act as a cover page and be linked to one or more completed child checklists. The Summary Report should be downloaded together with the linked/related checklist(s) as a single PDF report. Proposed Functionality A Summary Report checklist can be generated as an ad-hoc and linked to existing maintenance checklists. This checklist will function as: A summary report, and A cover page for the completed checklists. When the checklist(s) are exported or downloaded, the Summary Report should appear as the first page of the compiled PDF. [Scenarios] Scenario 1 – Single Checklist -> Each time a maintenance checklist is completed: A Summary Report is automatically generated and attached as a cover page. Both documents are exported together as one PDF report. Scenario 2 – Multiple Checklists -> In some cases, there may be multiple maintenance checklists completed for the same job. Users should be able to: Link multiple checklists with one Summary Report. Generate one consolidated PDF report containing: The Summary Report (cover page) All related maintenance checklists. The compiled report will be automatically submitted to the Finance Department or customer. Finance will use this combined report as supporting documentation for customer invoicing. Expected Outcome: The Summary Report and linked checklist(s) can be downloaded/exported as a single PDF document. The Summary Report appears as the first page (cover page), followed by the completed checklist(s). [Don Jon]

Currently, when duplicating rows during an inspection: The duplicated rows are moved to the bottom of the checklist. However, the bottom section typically contains fixed fields (e.g. signature response). Issue: Duplicated rows may appear below important fixed fields, disrupting the intended checklist structure. Proposed Enhancement: Introduce the ability to lock certain rows in the checklist. Expected Behavior: Locked rows remain fixed in their position and are not affected by duplication logic. When a row is duplicated: The duplicated row is added above the locked rows, not below them. Locked rows (e.g. signature section) always stay at the bottom. [Primech]

Currently responders cannot duplicate section titles. [Constellar]

In the Checklists page, please add in labels for the linked request IDs for easier identification and prevent confusion whenever multiple corrective request were generated from completing the checklist. [Constellar]