Practical evaluation guide · Updated 7 September 2026
In this guide
Use actual work deadlines
The export contains open work orders with a due date. Completed and cancelled work is excluded. Each entry is an all-day deadline in your workspace timezone, not a technician appointment or an estimate of job duration. Recurring plans appear only after they generate dated work orders.
Download as a workspace manager
Open Maintenance schedules and choose Download open work due dates. The export requires a signed-in workspace manager and remains available after the trial expires. The file includes work titles, linked asset names and links back to the private work orders. Store and share it according to your organization’s access rules.
Import into a compatible calendar
Use your calendar application’s file-import option and select the downloaded .ics file. Import into a separate maintenance calendar so you can manage this snapshot independently of your appointments. Review several entries, especially those near midnight or across timezone changes, before relying on the display.
Refresh deliberately
This is a snapshot, not a live calendar subscription or two-way synchronization. Changes made in the calendar do not update PreventiveHQ. A later import may duplicate entries depending on your calendar application. Replace the old maintenance snapshot where supported and consult the application for current status. Exports above 5,000 open dated jobs are rejected instead of silently truncated; use the work-order CSV for the full list.
Decide what a maintenance calendar should communicate
A maintenance calendar is most useful when everyone understands what its entries mean. A due date tells the team when a work order needs attention or completion under its operating process. It does not necessarily tell a technician when to arrive, how long the task will take or whether production has released the equipment. Treating those different meanings as interchangeable creates avoidable scheduling conflicts.
AI-generated editorial illustration; not a customer photograph or product screenshot.
PreventiveHQ exports open work-order due dates as an iCalendar file. That gives a manager a portable view of dated obligations that can be imported into a compatible calendar application. It is useful for a weekly planning discussion, a deadline review or coordination with people who already organize their day in a calendar. The underlying work order remains the place to check current status, scope and execution details.
Start by deciding who the calendar serves. A maintenance manager may need an overview of approaching deadlines. An operations manager may need to discuss equipment access. A technician may need assigned work instructions. Those audiences overlap, but a deadline snapshot alone cannot satisfy all three needs. Use it as a shared planning reference and agree where the authoritative operational record lives.
Understand exactly which records appear
The export includes open work orders that have a due date. A work order without a due date cannot appear on a date-based calendar, even when its priority is critical. Completed and cancelled work is excluded because this export represents outstanding deadlines rather than historical activity. If a user expects a completed job to remain visible as proof of service, direct them to the work history instead.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Recurring maintenance plans are not themselves calendar events in this download. A plan must generate a dated work order before that obligation is included. This distinction matters when a manager compares the number of plans with the number of exported events. Ten recurring plans do not necessarily mean ten current open work orders, and a single asset can have several distinct dated jobs.
| Record or condition | Included in this export? | Where to review it |
|---|---|---|
| Open work order with a due date | Yes | Calendar deadline and private work order |
| Open work order without a due date | No | Work-order list and planning review |
| Completed work | No | Asset and work-order history |
| Cancelled work | No | The underlying work record |
| Recurring plan without a generated dated job | No | Maintenance schedules |
| Technician appointment created in another calendar | No | That calendar’s appointment workflow |
Before exporting, review undated work separately. An apparently quiet calendar can coexist with a substantial undated backlog. Do not use the number of calendar entries as a measure of the entire maintenance workload. Pair the deadline view with the work-order workflow when assessing what the team actually needs to execute.
Keep deadlines distinct from appointments
An exported event is an all-day deadline in the workspace timezone. It is not a reserved technician time slot. The export marks events as transparent, expressing that they should not represent busy time merely because a work order is due that day. Individual calendar applications may display imported events differently, so inspect a sample in the calendar you actually use.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Consider an illustrative pump inspection due on Friday. The team may perform it on Wednesday during an agreed production stop. The Friday calendar entry communicates the deadline; it does not mean that the inspection occupies all of Friday. If an appointment is needed for Wednesday, create and manage that appointment through your scheduling process with the appropriate participants and duration.
This distinction also avoids a misleading capacity calculation. Six all-day deadlines do not mean six technician-days of labor. One job might take twenty minutes, another might require a contractor and another might wait for a part. Capacity planning needs task duration, skills, availability and dependencies. The calendar snapshot supplies a date reference, not a complete dispatch or resource-planning engine.
Agree on language in the planning meeting. Say “due Friday” when referring to the exported obligation and “booked Wednesday at ten” when referring to an appointment. Clear language prevents someone from assuming that equipment access has been arranged just because an event exists in their calendar.
Prepare the workspace before downloading
Check the organization timezone first. Due dates displayed in the calendar should correspond with the workspace’s interpretation of the work. A manager traveling abroad or using a calendar configured for another region should inspect the result rather than assume every date will look identical across applications.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Review a few representative work orders: one due soon, one overdue and one with an equipment name that helps identify the location. Confirm that titles are understandable without exposing unnecessary detail to the eventual calendar audience. The file contains work titles, associated asset names and links back to the private work orders. Calendar sharing therefore deserves the same thought as sharing a work list.
The download requires a signed-in workspace manager. Open Maintenance schedules and choose Download open work due dates. Save the file somewhere appropriate for operational records. The ability to export remains available after a trial expires, allowing the manager to retain this portable deadline snapshot without implying that all paid operational features remain active.
If the export is rejected because there are more than five thousand open dated jobs, use the work-order CSV for the full list. The calendar endpoint does not silently omit excess records. A large backlog may also justify a separate planning review, but the immediate interpretation is straightforward: a rejected export is not a partial calendar that can safely be treated as complete.
Import into a separate calendar first
Use the file-import function supported by your chosen calendar application and select the downloaded .ics file. Menu names vary by product and version, so consult that application’s current help if the import option is not apparent. This guide describes the meaning of the PreventiveHQ file rather than promising an identical interface in every calendar product.
Create a separate maintenance calendar where your application supports it. Keeping the snapshot separate from personal appointments makes its purpose visible and makes later replacement easier. Give it a recognizable name that includes the fact that it is a snapshot, and retain the download date in your own planning notes or calendar description.
After import, inspect several events. Compare each displayed date with its work order, confirm that the asset is recognizable and test the link back to the application. A person following a private work-order link still needs the appropriate application access. Importing an event does not grant permission to the underlying workspace.
Check the display on the devices people will actually use. A desktop month view, a phone agenda and a shared team calendar may emphasize different fields. Verify that users can distinguish a deadline from an appointment and can find the source work order. If the display is confusing, clarify the calendar naming and team instructions before distributing it widely.
Work through a weekly planning example
Imagine a small facilities team with twelve open dated jobs, four undated requests and three recurring plans that have not yet generated work. The manager downloads the calendar on Monday morning and imports it into a separate maintenance calendar. The twelve dated jobs appear as deadlines. The four undated requests and three ungenerated plans do not appear.
AI-generated editorial illustration; not a customer photograph or product screenshot.
During the planning meeting, the team identifies two jobs that need access to occupied rooms. Their deadlines are visible, but access still needs agreement. Another job needs a replacement filter that has not arrived. The team uses the underlying work records and maintenance inventory process to resolve those dependencies rather than moving calendar entries and assuming the application has been updated.
On Tuesday, a technician completes one job and a manager changes another job’s due date in PreventiveHQ. Monday’s imported calendar does not automatically change. A colleague looking only at that snapshot could see stale information. The team’s operating rule should therefore require a current work-order check before execution and a deliberate refresh of the calendar at the agreed planning interval.
At the next meeting, the manager downloads a new file and replaces the previous snapshot using the calendar application’s supported process. The exact replacement behavior belongs to that application. The manager checks for duplicates and verifies a completed job has disappeared from the new snapshot before using it as the week’s reference.
Refresh without creating a second source of truth
This export is a one-way file snapshot. It is not a subscription URL and does not establish two-way synchronization. Editing, deleting or moving an imported event in a calendar does not update the work order. Equally, changing the work order does not reach a file that has already been downloaded and imported.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Choose a refresh cadence that matches the calendar’s purpose. A weekly management review may tolerate a snapshot prepared immediately before the meeting. A rapidly changing dispatch operation needs a more current operational view and should work from the application rather than treating a weekly file as live scheduling data. The appropriate cadence depends on how quickly deadlines and statuses change.
Repeated imports can create duplicates depending on the receiving application. Do not assume that a familiar-looking event title guarantees the application will update the existing event. Test replacement behavior with a small calendar before adopting a routine. A separate calendar can make cleanup more manageable, but confirm the consequences before deleting events or an entire calendar.
Document the refresh owner and the point at which an old snapshot should stop being used. A simple note such as “prepared for Monday planning; check current work order before action” is more useful than leaving recipients to infer freshness from an attachment name.
Investigate missing or unexpected events
When a job is missing, first check whether it is open and has a due date. Then confirm that you exported from the intended workspace and that the calendar application imported the intended file. A recurring plan that has not generated a dated work order is not a missing event; it is a different record type outside the export’s scope.
When a completed job remains visible, compare the calendar snapshot time with the completion time. If completion happened after download, the old event is expected. Refresh the snapshot through the agreed process and check again. Do not reopen a completed work order merely to make it match a stale calendar display.
When a date appears wrong, compare the work-order deadline, organization timezone and receiving calendar configuration. Inspect the original file and a second representative event if needed. Avoid correcting a source deadline until you know whether the discrepancy comes from the actual record or the calendar’s display behavior.
When duplicate events appear, identify whether multiple snapshots were imported into the same calendar. Use the receiving application’s supported cleanup or replacement process. Changing work-order titles to hide duplication does not address the cause and makes future reconciliation harder.
Share the minimum useful operational context
Calendar files are portable, which is useful for coordination but also means they can be forwarded or retained outside the original application. Review the audience before sharing. Equipment names, work titles and internal links may reveal operational context even if the link itself requires authentication.
For a broad meeting, it may be more appropriate to present the relevant deadlines directly than distribute the entire file. For a maintenance team with an established shared calendar, confirm who can view or export its events. The export does not replace the receiving calendar’s access controls or your organization’s information-handling practices.
Avoid putting credentials, personal contact details or sensitive incident narratives into a work title just to make an exported event more descriptive. Keep the title concise and use the authorized work record for detailed execution information. This improves both readability and the quality of information shared through the snapshot.
If a recipient needs to act on the work, make sure they have the appropriate workspace role and know how to find the current record. A calendar attachment alone is not onboarding, assignment or evidence that a technician accepted a job.
Measure whether the calendar helps planning
Evaluate the workflow through practical outcomes rather than the number of events imported. Ask whether managers can identify approaching deadlines faster, whether operations can arrange equipment access earlier and whether users understand where to check current status. Observe a planning meeting instead of assuming that a successful download proves usefulness.
Track problems such as stale snapshots, duplicate events and undated work that was overlooked. These reveal whether the process needs clearer ownership or a different planning surface. If most discussion concerns rapidly changing assignments, the work-order list may be more useful than a calendar export for that part of the meeting.
Keep outcome claims proportionate. A calendar can improve visibility, but it does not itself prove reduced downtime or higher maintenance compliance. Those outcomes depend on execution, record quality and comparable measurement periods. The maintenance evidence method explains how to separate adoption evidence from operational improvement.
Questions about maintenance calendar exports
Can this reserve technician time automatically?
No. The file communicates all-day work deadlines. It does not calculate job duration, allocate skills or book participants. Arrange appointments and equipment access through your planning process, then keep the current work order as the execution reference.
Can I subscribe to a continuously updating calendar feed?
This workflow provides a downloadable snapshot. It is not a live subscription feed. Plan refreshes explicitly and avoid promising recipients that imported events will update whenever a work order changes.
What should I verify before relying on the first export?
Compare representative dates, confirm the intended workspace, test private work-order links, check that events do not imply booked labor time and establish how the next snapshot will replace the current one. Review undated work separately so the calendar does not hide part of the backlog.
Does exporting replace maintenance reporting?
No. The file is a planning aid for open dated work. It does not contain a complete service history, stock ledger, reliability analysis or capacity forecast. Use the corresponding application records and exports for those questions, and explain the calendar’s narrower purpose to everyone who receives it.