Retiring Reports in Enterprise Service Management

Summary

This article explains why, when, and how to retire reports in Enterprise Service Management.

Body

Overview

This article explains why, when, and how to retire reports in Enterprise Service Management (ESM) Work Management, and offers recommendations for keeping reports organized so fewer need retiring. It applies to ticket, project, asset, and other reports built in the Report Builder, along with the dashboards (desktops) and email delivery schedules that use them.

Only a report's owner can edit or delete it. Report owners carry out the retirement steps; if the owner has left or changed roles, an Enterprise Administrator or the ticketing application's administrator can help transfer ownership first.

Retire reports in stages: review who relies on the report, tell them before anything changes, restrict the report to its owner, wait through a hold period, and only then delete it. Deletion is permanent, so the staged approach gives anyone who still depends on the report time to speak up while it can still be restored with a single settings change. Each batch of reports being retired should be tracked with a ticket, so the review, notices, responses, wait periods, and outcome are recorded in one place.

In this article:

Why Retire Reports

Reports accumulate quickly. Each one is easy to create and copy, but few are ever cleaned up. Over time, unused and outdated reports cause real problems:

  • Clutter makes the right report hard to find. Long report lists and crowded folders slow everyone down and lead people to run the wrong report.
  • Outdated reports give wrong answers. Reports built on retired forms, attributes, statuses, groups, or services can quietly return incomplete or misleading results that people still act on.
  • Duplicates create conflicting numbers. Several versions of the "same" report, each with slightly different filters, produce different results and erode trust in the data.
  • Unneeded email deliveries create noise. Scheduled reports nobody reads add to inbox overload and train people to ignore report emails, including important ones.
  • Broad sharing exposes data unnecessarily. Reports shared widely and no longer reviewed may show ticket details to people who no longer need them.
  • Orphaned reports have no one to maintain them. Reports owned by people who have left cannot be edited by anyone else until ownership is transferred.

When to Retire a Report

Consider a report for retirement when one or more of these apply:

  • It has not been run in a long time, for example six to twelve months. Check the Last Run date in the report's details (see the caution below about dashboards).
  • It has been replaced by a newer report, an application dashboard, or a standard report that answers the same question.
  • It duplicates another report with the same or nearly the same columns and filters.
  • The thing it reports on is gone, such as a retired service, form, custom attribute, status, group, or ticketing application.
  • Its filters no longer work, returning no results or obviously incomplete results because of changes to forms, attributes, or groups.
  • Its owner has left or changed roles and no one has taken responsibility for it.
  • It was built for a one-time need, such as a project, audit, or data cleanup that is now finished.

When Not to Retire a Report

  • It runs on a dashboard. Dashboard refreshes do not count as runs, so a report that is used every day on a desktop can show an old Last Run date.
  • It has an active email delivery schedule with recipients who rely on it, even if no one runs it by hand.
  • It supports periodic work, such as an annual audit, fiscal year-end, or a semester or seasonal process. A long gap since the last run may be normal.
  • It is needed for compliance or records retention. Check with the data owner before retiring reports used for audits or regulatory reporting.
  • You cannot tell who uses it. Complete the review and communication steps in this article before deciding.

Review Who Uses the Report

Before changing anything, find out who can see the report and how it reaches them. Open the report, then use Actions > Show Details (or Actions > Edit) to review each of the following.

  • Owner. Confirm who owns the report. Reports can be owned by a person or a group. If the owner has left, transfer ownership (Actions > Change Owner) to someone who can carry out the retirement.
  • Visibility. Check the Owner and Visibility section. A report visible only to its owner affects one person; a report shared with people or groups, or with everyone, may be used by many people you do not know about. Note every group and person listed.
  • Folder. Check whether the report's folder is shared. People may find it by browsing a shared folder.
  • Dashboards (desktops). Ask whether the report appears as a widget on any dashboards, including shared or application dashboards. Dashboard use does not update Last Run.
  • Email delivery schedules. Review the delivery schedules at the bottom of the report details: each schedule's interval, whether it is active, and its recipients. Recipients can include groups and people who never open TeamDynamix themselves.
  • Last Run. Note the Last Run date, keeping in mind that dashboard refreshes and scheduled deliveries may not reflect hand-run use.
  • Copies. People who could see the report may have copied it. Copies are independent and are not affected by retiring the original, but their owners may still want to know.
How changing report settings affects people
Change Who is affected What they will notice
Visibility changed to owner only Everyone in the shared people and groups The report disappears from their report list and folders.
Visibility changed to owner only Anyone viewing it on a shared dashboard The dashboard widget stops showing the report's results.
Email delivery set inactive or removed Every delivery recipient, including those outside of TDWorkManagement Their scheduled email simply stops arriving, with no explanation.
Report renamed or moved to another folder Anyone who finds it by name or folder It is no longer where the expect it.
Report deleted Everyone above, plus the owner The report, its dashboard widget, and its deliveries are gone permanently. Copies remain.
Ownership transferred Previous and new owner Only the new owner can edit or delete the report.

Because most of these changes are silent from the user's point of view, tell people before you make them (see the next section).

Track Each Batch with a Ticket

Create one ticket for each batch of reports being retired, whether the batch is a single report or a team's annual cleanup. The ticket is the retirement record: it shows what was reviewed, who was told, how they responded, and when each report was restricted, restored, or deleted. It also keeps the work visible while it waits weeks or months between stages.

Create the ticket

Create the ticket in the ticketing application your organization uses, and include:

  • Title: "Report retirement – [team or area] – [month and year]".
  • Responsible: the report owner carrying out the retirement, or their team.
  • Description: the reason for the batch and the planned dates for each stage.
  • Reports in the batch: for each report, its name, folder, owner, visibility, delivery schedules and recipients, Last Run date, and the reason for retiring it. A short table in the description or an attached spreadsheet both work.
  • Attachments: A PDF copy of the report's details (Actions > Show Details > Print) showing settings, visibility, and delivery schedules before any change, and later its definition before deletion. Each attachment's file name should be in the format of "[App Name]-[Report ID]-[Report Name]-[Audit Date in the form of YYYYMMDD]". For example: "UAA_IT-629-Missing_Service-20261118.pdf"

Add the main stakeholders, such as the data owner or the leads of shared groups, as contacts or notification recipients so they can follow progress.

Keep the ticket updated

Record every step as a ticket update or feed entry: notices sent, responses received, reports kept or removed from the batch, settings changed, restores, and deletions. Attach or paste the text of each notice sent.

Use On Hold for wait periods

Set the ticket to On Hold whenever the batch is waiting on time to pass, and set the Goes Off Hold date to the end of that wait, so the ticket returns to an active status on its own when the next step is due.

Stage Ticket Status Goes Off Hold Date
Stage 1: reviewing reports and preparing the notice In Process Not used
Stage 1: waiting for responses to the notice On Hold The response date in the notice
Stage 2: restricting reports In Process Not used
Stage 3: hold period On Hold The end of the hold period
Stage 4: final notice and deletion In Process Not used
All reports in batch deleted, kept, or restored Resolved Not used

If someone responds while the ticket is on hold, take it off hold, handle the request, and put it back on hold with the same Goes Off Hold date.

Tip
Status names can vary by ticketing application; use the equivalents in yours.

Communicate Before You Change Anything

Tell people before the report changes, not after they notice it is missing. Early notice lets them say they still need it, move to a replacement, or save a copy for themselves.

Who to contact

  • Members of every group and every person the report is shared with. For large groups, or reports shared with a large number of groups, contact the group's manager or lead and ask them to pass it on.
  • Every email delivery recipient, including recipients outside TDWorkManagement.
  • Owners of dashboards that include the report.
  • The Service Owner or data owner for the area the report covers.
  • Anyone who requested the report originally, if known.

When to contact them

  • Before Stage 2 (restrict): send the retirement notice with a clear response date, typically two to four weeks out.
  • When access is restricted: send a short reminder that the report is now hidden and how to ask for it back.
  • Before deletion: send a final notice if anyone responded during the hold period or the report is widely shared.

What to include

  • The report's name and folder, and why it is being retired.
  • The replacement report or dashboard, if there is one, and how to find it.
  • The key dates: when access will be restricted, and when the report may be deleted.
  • How to respond if they still need it, and who to contact.
  • A reminder that they can copy the report now if they want their own version.

Sample notice

Subject: Report retirement notice – [Report name]

The Enterprise Service Management report [Report name] in the [Folder] folderr, of the [Application Name] application is scheduled for retirement because [reason, for example it has not been run since March and is replaced by Report X]. On [date], it will no longer be visible to anyone except its owner, and its scheduled email delivery will stop. If no one needs it, it may be permanently deleted after [date].

If you still use this report, please reply to this notice by [response date]. You can also make your own copy now from the report's Actions menu.

Respond with a response template

Answer every reply to a retirement notice, and record each reply and answer on the tracking ticket. Response templates in the ticketing application keep these answers quick and consistent. Ask your Ticketing Application Administrator to create report retirement response templates such as these, then apply them when updating the tracking ticket:

Template Use when Key points to include
Report Retirement - Report Will Be Kept The person still needs the report Thank them; confirm the report is removed from the batch and stays available; ask whether ownership should be changed.
Report Retirement - Replacement Available The person used the report, but a replacement meets the need Name the replacement report or dashboard, where to find it, and who to contact if it falls short; restate the retirement dates.
Report Retirement - Retirement Proceeding The person has no objection, or asked a general question Confirm the restriction and possible deletion dates; remind them they can make their own copy beforehand.
Report Retirement - Report Restored A report on hold was restored at the person's request. Confirm it is visible again, which deliveries were reactivated, and any change in ownership.

Record the outcome for each report in the ticket, such as kept, retired, or restored, as responses come in.

Staged Retirement Process

Every report identified for retirement moves through four stages. The report is hidden from everyone but its owner well before it is deleted, so anyone who still needs it can ask for it back.

Enterprise Service Management Report Stage Retirement Process

At any point before deletion, a report that turns out to be needed can be restored by putting its sharing and deliveries back as they were.

Stage What happens Typical duration
1. Review and notify Identify who can see and receive the report, and send the retirement notice. Two to four weeks for responses
2. Restrict to owner Visibility set to the owner only; email delivers made inactive; report labeled and moved. One working session
3. Hold period The report stays hidden but intact while you watch for requests. 90 days, or one full business cycle for periodic reports
4. Delete The report is permanently deleted, if no one needs it. One working session

Stage 1: Review and notify

  1. Create the tracking ticket for the batch and set it to In Process.
  2. Confirm the report meets the criteria in When to retire a report, and does not fall under When not to retire a report.
  3. Review the owner, visibility, folder, dashboards, delivery schedules, and Last Run date as described in Review who uses the report.
  4. Record what you found in the ticket, attaching a PDF copy of the report's details (Actions > Show Details > Print) showing settings, visibility, and delivery schedules before any change, so they can be restored exactly.
  5. Send the retirement notice and record it in the ticket.
  6. Set the ticket to On Hold, and the Goes Off Hold date set to the notice's response date.
  7. Answer each reply using the appropriate notice response template, and record the outcome for each report in the ticket.
  8. If anyone still needs the report, remove it from the batch. Keep it, transfer ownership to them, or point them to a replacement.

Stage 2: Restrict to the owner

  1. When the ticket comes off hold, set it to In Process.
  2. Open the report and select Actions > Edit.
  3. In the Owner and Visibility section, set visibility to the owner only, removing all shared people and groups.
  4. Under Email Delivery, clear Active on each delivery schedule instead of deleting it, so it can be turned back on if needed.
  5. Rename the report with a clear prefix, such as "RETIRED 2026-11-09 – " followed by the original name, so its status and date are obvious.
  6. Optionally, move it to a Retired Reports folder visible only to you.
  7. Save, then ask the owners of any dashboards that used the report to remove the widget.
  8. Record the restriction date for each report in the ticket, and send the reminder notice.
  9. Set the ticket On Hold, with the Goes Off Hold date set to the end of the hold period.

Stage 3: Hold period

Leave the report restricted but intact. Use 90 days as a default. For reports that support annual or seasonal work, hold it long enough to cover one full cycle so its next expected use passes without a request.

During the hold, respond promptly to anyone who asks for a report, using the notice response templates. Take the ticket off hold while you handle the request, restore the report if it is still needed (see Restoring a report), record the outcome, and return the ticket to On Hold with the same Goes Off Hold date. Do not add new deliveries or share reports while they are on hold.

Stage 4: Delete

  1. When the ticket comes off hold, set it to In Process and confirm no one has asked for the remaining reports.
  2. Send a final notice if anyone responded earlier or the report was widely shared, and record it in the ticket.
  3. Attach each report's definition to the ticket, such as screenshots of its columns, filters, sort, and chart settings, so it could be rebuilt if ever needed.
  4. Open the report and select Actions > Delete. Only the owner can delete a report, and reports are deleted one at a time.
  5. Record a summary of each report's outcome (i.e. deleted, kept, or restored) in the ticket.
  6. Set the ticket to Resolved.

Treat deletion as permanent. Copies other people made from the report are not affected.

Restoring a Report

If someone needs a report during the hold period:

  1. Take the tracking ticket off hold, and confirm the need with the requester, and consider whether a replacement report would serve them better.
  2. Open the report, select Actions > Edit, and restore its original visibility using the settings recorded in the ticket.
  3. Reactivate the email delivery schedules that are still needed, and confirm the recipient list is current.
  4. Remove the RETIRED prefix from the name and move it back to its original folder.
  5. If the requester will be the main user, consider transferring ownership to them.
  6. Record the restore and the reason on the ticket, reply to the requester with the Report Restored response template, and return the ticket to On Hold if other reports in the batch are still waiting.
Important
Once a report is deleted, it cannot be restored. It can only be rebuilt from the definition attached to the tracking ticket.

Need additional help or have issues

For support, requests may be submitted anytime using the appropriate Enterprise Service Management form. Requests generate a Ticket which will be worked in order received and urgency by IT Employees with the knowledge and permissions to assist with the request.

For immediate assistance please review the Contact Us page for the appropriate support group.

Details

Details

Article ID: 3469
Created
Wed 11/18/26 10:23 AM
Modified
Wed 11/18/26 11:57 AM