Workshop Reports
Workshop reports give maintenance managers visibility into workload, repair history, labour productivity, and service compliance. The data in these reports comes directly from Requests and Work Orders as they move through the workshop workflow. Fields set during daily maintenance activity accumulate into the metrics shown here.
See Reports Overview for how to find these reports. Several also appear directly on the Workshop Dashboard.
Fields That Feed Workshop Reports
How accurately these reports reflect reality depends on workshop staff consistently filling in key fields as they work. The tables below show which fields matter most for reporting.
On each Request:
| Field | Reports that use it |
|---|---|
| Request Type | Request Analysis, Turn Around Time For Repairs, Overdue Requests |
| Workshop | Overdue Requests, Workshop Performance, Scheduled vs Unscheduled |
| Expected Completion | Overdue Requests, Overdue Work Orders |
| Completed Date | Turn Around Time For Repairs, PM Service, Workshop Performance |
| Downtime | Downtime Report |
| Priority | Overdue Requests |
On each Work Order:
| Field | Reports that use it |
|---|---|
| Work Order Type (Scheduled / Unscheduled) | Scheduled vs Unscheduled |
| Repair Type | Work Order Analysis, Repair Cause/Type/Reason, Completed Repair |
| Repair Cause | Repair Cause/Type/Reason |
| Repair Reason | Repair Cause/Type/Reason |
| Work Completed | Repair Cause/Type/Reason |
| Assigned Technician | Completed Repair, Labour Productivity, Time Recorder |
| Estimated Labour Minutes | Work Order Labour Productivity |
| Completed Date | Workshop Performance, Completed Repair |
| Total Labour Cost | Work Order Analysis, Direct vs Indirect Labour |
| Material Total Cost | Work Order Analysis |
Labour time recorded via Time Recorders linked to Work Orders feeds into the Time Recorder reports, the Direct vs Indirect Labour Report, and the Actual Labour Time in the Labour Productivity Report.
Workload and Overdue
Overdue Requests
Lists Requests where the Expected Completion date has passed, status is Open, Pending, Drop Off, or In Progress, and the request is not deferred. Deferred requests are always excluded — there's no filter to show them here. There are no other filters; the report runs automatically.
| Column | Definition |
|---|---|
| Name, RQ Type, Status | The request and its type — includes Repair, Service, and Daily Driver-originated requests. |
| Assigned To | The workshop the request is assigned to. |
| Exp Completion | The expected completion date that has passed. |
| Critical Asset | true if the request is against an asset flagged as critical. |
| High Priority | Shows the request's priority (for example, Urgent - Fleet Out of Service) where one is set. |
Overdue Work Orders
The Work Order equivalent of Overdue Requests, with no filters of its own. A Work Order appears when its status is New, In Progress, or On Hold, and its Expected Completion date has passed.
The first two columns are both headed Name on screen — the first is the Work Order's own name, the second its parent Request's name.
| Column | Definition |
|---|---|
| Name (first) | The Work Order. |
| Name (second) | Its parent Request. |
| Status, Exp Completion | The Work Order's current status and the expected completion date that has passed. |
| Assigned | The assigned technician(s) — can show more than one name where a Work Order has multiple. |
Use this report alongside Overdue Requests to build a complete picture of the workshop backlog. Overdue Requests shows work that has not progressed; Overdue Work Orders shows jobs that are in progress but taking longer than planned.
Completed Work Analysis
Completed Repair Report
The Completed Repair Report lists all completed Work Orders for a chosen period, giving a detailed record of repair activity. A graph at the top of the report summarises Work Orders by Repair Type.
Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Repair Report. Work Orders are included where their Completed Date falls within the selected date range and a Repair Type is set — there's no separate check on the Work Order's status, so a Work Order with a Completed Date but a different current status would still appear here.
| Column | Source |
|---|---|
| Work Order | Work Order name |
| Request | Name of the parent Request |
| Date Initiated | Date the Work Order was created |
| Expected Completion | Expected Completion from the Work Order |
| Completed | Completed Date from the Work Order |
| Assigned | The assigned technician |
Use this report to produce a detailed list of completed repairs for a period, verify that all work in a time window has been closed off, or review individual technician output.
Request Analysis Report
Summarises closed Requests over a chosen period, broken down by Request Type and by Request Reason.
Use Pre-Set Times or enter a Report Start Date and Report End Date, optionally narrow to a specific Asset, choose a Granularity (Days, Weeks, Months), then select Run Report. Requests are included where Status is Closed and the Closed Date falls within the selected period.
Setting Granularity too fine for a long date range can make the report take a very long time to run — for a multi-year range, use Months rather than Days.
The report shows: - Count and percentage breakdown by Request Type (Repair/General, Service, Internal, and others) — every Request Type appears here, including ones with zero Requests in the period, not just types that had activity. - Count and cost breakdown by Request Reason, the reason code selected on each closed Request.
Select a cell in the Request Reasons table to drill into the underlying Requests.
Work Order Analysis Report
The Work Order Analysis Report analyses the cost and volume of completed Work Orders, broken down by Repair Type. For each Repair Type it shows a count of Work Orders and the total cost split across four categories.
Use Pre-Set Times or enter a Report Start Date and Report End Date, choose a Granularity, then select Run Report. There's no Asset filter — this report always covers the whole fleet.
| Column | Source |
|---|---|
| Count | Number of Work Orders for this Repair Type in the period |
| Materials | Store materials costs from Work Orders (materialTotal minus additional materials) |
| Additional Materials | Non-store materials costs from Work Orders |
| Labour | Total labour costs from Work Orders (totalLabourCost) |
| Total | Sum of Materials, Additional Materials, and Labour |
Work Orders without a Repair Type set are excluded. Use the Granularity selector to compare costs across different time periods. Select any chart column or row to drill into the Work Orders that make up that figure.
Use this report to compare the relative cost burden of different repair types and to track whether costs are rising over time in a particular category.
Repair Cause/Type/Reason Report
The Repair Cause / Type / Reason Report breaks down completed Work Orders by four IPWEA maintenance classification codes set on the Work Order. Each code appears in its own chart and table.
Use Pre-Set Times or enter a Report Start Date and Report End Date, choose a Granularity, then select Run Report.
| Section | Work Order field |
|---|---|
| Repair Type | Repair Type selected on the Work Order |
| Repair Cause | Repair Cause selected on the Work Order |
| Repair Reason | Repair Reason selected on the Work Order |
| Work Completed | Work Completed code selected on the Work Order |
Work Orders are included where their Completed Date falls within the selected date range. Work Orders with no value set for a given code appear under "No Data" in that section.
Use the Granularity selector to compare counts across different time periods. Select any chart column to drill into the underlying Work Orders.
This report is most useful for identifying common fault patterns, for example, whether most repairs stem from a particular cause, or whether a specific component is generating repeated work. The quality of the data depends on technicians consistently selecting the correct codes when completing Work Orders.
Scheduled Vs Unscheduled Report
The Scheduled vs Unscheduled Report compares the volume of scheduled versus unscheduled Work Orders across workshops. It draws on the Work Order Type field (set to either Scheduled or Unscheduled on each Work Order) and the Main Defect Type code.
Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Report. There's no Granularity selector on this one.
The report shows: - A raw listing of Work Orders with their Work Order Type and Main Defect Type - A stacked bar graph comparing Scheduled and Unscheduled Work Orders by workshop - A summary table showing Count Scheduled, % Scheduled, Count Unscheduled, % Unscheduled per workshop - A breakdown by Main Defect Type with the same Scheduled / Unscheduled split
Use this report to understand how much of the workshop's workload is reactive versus planned, and to identify whether specific workshops or defect types are the main drivers of unscheduled work.
Turn Around Time For Repairs Report
The Turn Around Time For Repairs Report measures how long Requests take to move from the In Progress date to the Completed date, grouping results into time bands to identify how much of the workshop's repair work is completed quickly versus taking extended periods.
Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Report. Requests are included where the Completed Date falls in range and a Total Repair Time has been calculated; Internal, Infringement, and Registration requests are excluded.
The report is built around these targets: 70% or more of repairs completed within 24 hours, 20% between 24 and 48 hours, and no more than 10% taking longer than 48 hours. Use the results to see how your workshop's actual split compares.
Each Request appears in the detail table with:
| Column | Source |
|---|---|
| Service | Request name (linked) |
| Start Date | In Progress date on the Request |
| Completed Date | Work Completed date on the Request |
| Total Repair Time (hr) | Total time from all linked Time Recorders, converted to hours |
| Category | Time band: for example, < 24 hrs, 24–48 hrs, > 48 hrs |
Requests with a total repair time over 48 hours are highlighted in red.
A Summary Table above the detail shows a count per time band, giving a quick picture of how the workshop's response times are distributed.
Use this report to identify delays in repair completion, benchmark turn around performance against targets, and flag requests that have taken significantly longer than expected.
Note: The Total Repair Time shown here is the labour time recorded against the request's work orders, not downtime. It reflects how long staff spent working on the job, whereas downtime reflects how long the asset was unavailable within its business hours. See the Downtime Report for how downtime is measured.
Labour and Time
Work Order Labour Productivity Report
The Work Order Labour Productivity Report compares estimated versus actual labour time on Work Orders, helping identify where jobs consistently overrun or underrun. There's no Run button — enter a Report Start Date and Report End Date and the results filter directly.
| Column | Source |
|---|---|
| Name | Work Order name |
| Date Created | Date the Work Order was initiated |
| Parent Request Id | Name of the parent Request |
| Request Description | Description field from the parent Request |
| Est. Labour Time (mins) | Estimated Labour Minutes field on the Work Order |
| Actual Labour Time (mins) | Total time from all Time Recorder documents linked to the Work Order |
| Variance | Actual Labour Time minus Estimated Labour Time |
| Technician's Report | The Technicians Report text entered on the Work Order |
| Assigned | The assigned technician |
| Workshop | The workshop assigned to the Work Order |
Work Orders are included where Date Initiated falls within the selected date range.
A large positive variance may indicate a job that was more complex than anticipated; a large negative variance may indicate incomplete time recording. Use this report to refine estimates over time and identify Work Orders that may need follow-up.
Direct Vs Indirect Labour Report
The Direct vs Indirect Labour Report classifies Time Recorder time by whether it relates to productive (direct) or non-productive (indirect) work, based on the type of Work Order the time was recorded against.
Indirect labour is time recorded against exactly four Work Order types: Internal Task, Accident Data Collection, Refuel, and Training Task.
Direct labour is everything else — time recorded against any other Work Order type (Repair, Diagnose, PM Service, Supervisor Review, and so on) counts as direct. This is a closed list for Indirect and an open one for Direct, not two matching lists — if a new Work Order type is added to the application in future, it will count as Direct unless it's added to the Indirect list specifically.
Use Pre-Set Times or enter a Report Start Date and Report End Date, optionally select an Account (Optional) to focus on one technician, use Show to choose what the chart displays, then select Run Report. The report shows direct and indirect labour counts and costs per account.
Use this report to understand how technician time is divided between chargeable workshop work and internal or administrative activity, and to set benchmarks for direct vs indirect labour targets.
Time Recorder Report - Single Selection
The Single Selection Time Recorder Report shows all time recorded against Work Orders by a specific employee within a chosen period. The report period is limited to a maximum of 31 days.
Employee is required — for Technician accounts it's pre-populated with the logged-in user. Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Report.
Results show Time Recorder totals rolled up per Work Order, with drill-down capability to view the individual time recorder entries that make up each total.
Use this report to review an individual technician's recorded time in detail, for payroll verification, timesheet review, or labour cost queries.
Time Recorder Report Multiple Selection
The Multiple Selection Time Recorder Report provides an overview of time recorded across multiple employees within a chosen period. Unlike Single Selection, there's no 31-day limit on the date range here.
Choose how to select employees using Select By (Account, Business Role, Section, Department, or Supervisor), then use Select to pick the specific value for that category — for example, a particular department if you chose Department. Optionally narrow further using Accounts. Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Report. Results are rolled up as a total per user rather than per Work Order.
Use this report for a broader overview of workshop labour activity across a team or department.
Time Recorder Document Listing
The Time Recorder Document Listing shows all individual Time Recorder documents within a selected date range. Unlike the Time Recorder Reports, which roll up totals, this listing shows each time recorder entry as its own row.
Filter by Report Start Date and Report End Date — there's no Run button, results filter directly. Columns include: Name, Work Order, Asset, Employee, Workshop, Role (the role the time was recorded under), Started, Completed, Total Time (min), Rate, and Labour Cost. The listing can be exported to CSV.
Use this report when you need to see individual time recording events, for example, when investigating a specific Work Order's time history or auditing entries for a particular date.
Overtime Report
The Overtime Report shows time recorder entries that have been flagged as overtime, allowing supervisors to review and verify overtime hours claimed by workshop staff. Enter a Start Date and End Date — there's no Pre-Set Times option or Run button here; results filter directly.
| Column | Definition |
|---|---|
| Started / Completed | When the time recording began and ended. |
| Avail Start / Avail End | The employee's rostered availability window for that day. |
| Normal Minutes | Time within the availability window, at the standard rate. |
| OT Minutes Rate 1 / OT Minutes Rate 2 | Overtime minutes at each of the two configured overtime rates — see Rates. |
| Total Time | Normal Minutes plus both overtime totals. |
Results are grouped by employee and show individual time recorder entries alongside totals. Use this report for payroll verification, overtime budget review, or checking whether specific periods generated unusual overtime claims.
Service Reports
Asset Services Due
The Asset Services Due report identifies all upcoming or overdue preventive maintenance services within a specified threshold range. Use it to get ahead of services before they are automatically generated as Service Requests, or to manually generate requests for a batch of assets at once.
Running the Report
Enter values in one or more Within threshold fields:
| Field | What it finds |
|---|---|
| Within Days | Service Details documents with a Generation Date within today + the entered number of days. |
| Within Primary Meter | Service Details documents with a Generate Primary Meter value within the asset's current Primary Meter + the entered value. |
| Within Secondary Meter | Service Details documents with a Generate Secondary Meter value within the asset's current Secondary Meter + the entered value. |
| Within Fuel | Service Details documents with a Generate Fuel value within the asset's current total fuel consumed + the entered value. |
Use Primary Meter Measure to set the unit (for example km or hr) that Within Primary Meter is measured in. Optionally filter by specific Assets or Asset Groups using the Filter Asset Selector (Asset Group, Asset, or All) and the selection dropdown, then select Run Report.
Generating Service Requests
- Select the asset rows (light blue) to include. This also selects all services for that asset. Deselect individual service rows (dark blue) to exclude specific services.
- Select an Auto Set Request Status — Pending or Open.
- Optionally set an Expected Start and Expected Completion for the generated requests.
- Select Create Requests For Selected Assets. A separate Service Request is created for each selected asset, with all its selected services linked.
Recently Created Requests
The Open/Pending Requests Created Last 24hr panel lists Service Requests you've created from this page in the last 24 hours — Name, Status, Created Date, Expected Start Date, Expected Completion Date, and the services included. Select a row and select Open Selected to jump straight to it.
Cancelling Services
Use this to permanently cancel services that will never be carried out (not just deferred).
- Select the asset rows or individual service rows to cancel.
- Select Cancel Selected Service Details.
Asset Services Remaining Report
The Asset Services Remaining Report displays one row per asset summarising its service history and how many services it has left, giving a picture of where each asset sits in its service lifecycle.
Set the Filter Asset Selector to Asset Group, Asset, or All, and choose whether Calculate Weeks Since Last Service By uses Request or Work Order completion dates, then optionally narrow the results with Select Assets / Asset Groups (optional) before selecting Run Report.
For each asset the report shows: - Request Created, Request Completed, Cancelled, No Status — counts of the asset's Service Details records grouped by their current status - Services Remaining — the number of the asset's Service Details records still Active (not yet turned into a request). Values of 3 or fewer are highlighted, but only for assets with at least one Service Configuration - Asset Replacement Date — the asset's replacement due date - Final Scheduled Service Date — the scheduled date of its most recently scheduled service - Weeks Since Last Service — weeks since the last completed Work Order or Service Request (depending on the Calculate Weeks Since Last Service By selection). Highlighted if over 30 weeks - Service Details Configuration Count and Configuration Count — the number of distinct Service Configurations behind the asset's Service Details records, and the number of Service Configurations linked directly to the asset. Either shows Not Configured in red when zero - Configuration — links to the asset's linked Service Configuration document(s)
Tick Exclude Assets Not Configured to hide assets with no linked Service Configuration (a Configuration Count of zero) from the results.
Use this report to assess service compliance across the fleet and identify assets approaching their replacement point or overdue for a service.
Orphan Services Report
The Orphan Services Report displays Service Details records that are still Active but whose parent Service Configuration has been deleted. These are orphaned records — they remain in the system but are no longer linked to an active configuration and will not generate service requests as expected.
The report runs automatically as soon as it opens, with no filters to set. It searches through every deleted Service Configuration on the system, showing a Processing message for each one as it goes, so on a system with a large number of deleted configurations it can take some time to complete. Once finished, it lists each orphaned Service Details record as a link.
Use this report periodically to identify and clean up orphaned service records. Open each result and cancel or delete it as appropriate.
PM Service Overview
The PM Service Overview shows every Active asset's preventive maintenance setup in one place — its Service Configurations, the Service Definitions they use, and any gaps in that setup — so you can audit servicing configuration across the fleet without opening each asset individually.
Rows are grouped by asset, with one row per Config/Service Definition combination beneath each asset's group header. The group header shows Service Details Count, Services Completed, and Services Incomplete for that asset. Use Asset Search and Asset Group Search to filter the assets shown.
Each row includes: - Config Name, Config Status, Secondary Config, Config Type — the Service Configuration behind this row - Service Definition, Service Definition Service Group, Service Inherits — the Service Definition the configuration uses, and any other definitions it inherits from - Service Notes, Est Service Time, Service Intervals — the definition's notes, estimated time, and its configured intervals (date, primary meter, secondary meter, and fuel, wherever each is set) - Service Checks, Materials, Questionnaires — the maintenance checks, materials, and questionnaires attached to the definition (and anything it inherits) - Warnings — data quality issues found for this row, such as No Configuration Found For Asset, Configuration Status Not Set, No Service Definitions Linked To Configuration, or a linked definition/check/material that no longer exists
Two buttons control extra detail on the main table: - Toggle Service Definition Service Details Visibility shows or hides a Services Using Definition column listing the actual Service Details documents generated from each definition. - Toggle Service Checks Visibility shows or hides the Service Checks column.
Within an asset's group header, two more controls drill into that asset's Service Details: - Toggle Service Details — Summary View expands an inline table of that asset's Service Details documents grouped by configuration, with their Name and Status. - Service Details — Detail View loads that asset's full Service Details documents into a second table below the main report, with one column group per meter type (Date, Primary Meter, Secondary Meter, Fuel) showing the Manufacturer Scheduled, Service Interval, Scheduled, and Generate values for each, plus Service Status, Service Checks, Materials, and Questionnaires. Use Clear Table to empty this second table.
Use the Warnings column to find assets with incomplete or broken PM service setup, and the Detail View to check exactly when a specific asset's services are scheduled to generate.
Service Materials Report
The Service Materials Report lists the materials expected to be needed to complete every Pending or Open Service Request, one row per material per service. Use it to plan parts ordering ahead of scheduled services. It loads automatically when opened — there's no Run Report button.
For each material the report shows the request it belongs to (Request, Exp Start Date, Status, Sched. Date), the asset (Class, Workshop, Asset Loc, Asset Id, Chassis No, Make, Model, Manufactured, Fuel Type), and the material itself (Location, Part No, Category, # Available, Reorder #, Exp. Cons, Supplier, Location Desc). Materials come from the service's Service Definition where one is configured; if not, the materials configured directly on the Service Details document are used instead.
Use Exp Start > and Exp End < with Run With Filter to narrow the list to requests with an expected start date in that range, and Clear Filter to remove it.
Select one or more material rows (not the request/service/material hyperlinks) and select Mark Selected As Acknowledged to flag them as actioned — for example, once the part has been ordered. Acknowledged rows stay in the list but are highlighted in green (RQ Updated) on every future load, so you can track what's still outstanding without losing the row.
- Enter an Exp Start date and Exp End date, the Expected Start date range of the Service Requests to include.
- Select Run Report.
Results display Service Requests that fall within the date range, grouped to show the materials and quantities associated with each service. A Legend at the top of the report explains any status indicators shown in the results.
Only Service Requests with materials configured on their linked service definitions will show meaningful results. Services without predefined materials lists will appear but without material detail.
Service Requests - Not Closed
The Service Requests — Not Closed report lists all Service Requests that are not in a Closed or Cancelled status. Use it to monitor the full pipeline of active and pending service work.
Filter results by status using the checkbox list. Select one or more of: Pending, Open, Drop Off, In Progress, Pick Up, Work Complete. The default view shows Pending and Open requests.
Columns include: Name, Asset, Service, Status (shown with an icon per status), Date Created, Expected Start, Expected Completion, Assigned, Deferred, Asset Type, Allocation, and Location. The Service column lists up to three linked services, with ...more shown if a request has more than that. Results sort by Date Created (newest first) by default; columns can be reordered by dragging and resized, and the search box searches across Name, Asset, Assigned, Deferred, Asset Type, Location, Status, Service, and Allocation.
Service Requests Due
The Service Requests Due report shows Open Service Requests that are either coming up within the next two weeks or are already overdue. It is divided into two panels:
Service Requests Due Next 2 Weeks: Open Service Requests with an Expected Start date within the next 14 days.
Service Requests Overdue: Open Service Requests with an Expected Start date that has already passed.
Both panels show an asset image thumbnail, the request name, asset, linked service, and Request Created Date — the date the request was created, not its Expected Start date. The Expected Start date determines which panel a request appears in but is not itself shown as a column; open the request to check it.
Use this report as a daily or weekly check on services that need to be actioned soon or have already slipped past their scheduled date.
Service Performance
Workshop Performance Report
The Workshop Performance Report displays a summary of repairs completed per workshop for a chosen date range. Work Orders are included where the Completed Date falls within the selected dates. Work Order types for Parts Management, Accident Data, Training, and Hire are excluded.
Optionally select a specific Workshop to narrow the results. Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Workshop Report. Results can be exported using the Copy or Excel buttons above the table.
Use this report to compare output across workshops and review repair throughput over time.
PM Service Report
The PM Service Report displays completed Service Requests and categorises each one as completed early, on time, or late, based on a configurable percentage threshold relative to the scheduled service date.
Use Pre-Set Times or enter a Report Start Date and Report End Date, set Percentage Under / Over to the threshold percentage, then select Run Report. Use Print Report to print the results.
| Category | Definition |
|---|---|
| Completed Early | Completed date is earlier than the scheduled date by more than Percentage Under / Over. |
| Completed On Time | Completed date falls within Percentage Under / Over of the scheduled date. |
| Completed Late | Completed date is later than the scheduled date by more than Percentage Under / Over. |
Service Requests are included where the Date Initiated falls within the selected date range, the service has been completed, a scheduled service date exists, and — for group services — no inherited sub-services exist (this avoids double-counting a group service and the individual services generated from it).
Downtime Report
The Downtime Report displays downtime and uptime ratios for assets that have Business Hours and Days configured. Downtime is calculated by totalling the downtime recorded on closed Requests within the selected date range — specifically, Requests with a Closed Date in the selected range and downtime greater than zero.
Use Pre-Set Times or enter a Report Start Date and Report End Date, then select Run Report.
An asset is marked as Passed if its ratio of downtime to uptime is greater than 98%, meaning it was available and operational for at least 98% of its scheduled business hours.
Only assets with Business Hours and Days configured are included; assets without this configuration do not appear.
How Downtime Is Calculated
Downtime measures the time an asset is off the road being worked on, but only the time that falls within the hours the asset is expected to be in use.
- Each time a request moves from In Progress to Work Complete, FLEET records that period as a repair interval on the request. The downtime for a request is the total of its intervals.
- Downtime counts only the portion of each interval that falls within the asset's configured Business Hours on its Business Days. Time outside business hours (overnight, or on days not set as business days, such as weekends) is not counted as downtime, even though the asset was still in the workshop.
- Time a request spends Deferred is excluded. Because deferring splits a job into separate intervals, the gap while the request is paused (for example, waiting on a part or an external specialist) does not count towards downtime. See Deferred Requests.
This means downtime reflects working-hours availability, not the raw elapsed time an asset spent in the workshop. An asset booked in over a weekend, or one waiting several days on a deferred part, accrues downtime only for the business-hours periods when it was actively being repaired.
Note: Business Hours and Days are configured on the asset. An asset without this configuration records no downtime and does not appear in the Downtime Report.
Maintenance Tools
Bulk Close/Cancel Requests
The Bulk Close / Cancel tool finds and processes Requests in Open, Pending, Work Complete, or Pick Up status. Use it in place of navigating to individual Request documents when closing or cancelling a batch of Requests.
- Use the filters to narrow the grid by Created Date and/or Request Status.
- Select rows by selecting them. Rows with Work Orders or Time Recorder documents shown in the Related Items column cannot be automatically updated. Complete those documents first before selecting the row.
- Select Close/Cancel Selected.
- If any selected Request is a Service Request, a dialogue appears with options for how to handle the linked Service Details Documents:
- Keep Service Details — sets all linked Service Details Documents back to Active.
- Cancel Service Details — sets all linked Service Details Documents to Cancelled.
- Ask For Each — prompts you individually for each Service Details Document.
- Cancel Update — aborts the entire operation.
- Review the confirmation dialogue (which shows a count of eligible and ineligible Requests), then select Confirm to proceed.
Updates run in the background and will continue even if you navigate away from the page. Notifications appear for each update, and updated documents are listed in the Updated Documents table. Errors are flagged in the table.
Rows with Work Orders or Time Recorders in the Related Items column must be completed before they can be batch-closed. They are counted as ineligible and skipped.
Updated: August 2026 · Formbird FLEET 4.2.8