FootPrints 2026: Benefits, Features & Pricing

We acquired Footprints at the bank where I worked in 2004, and they still use that system today. It is used for Basically helping in IT Demand Management processes (Incidents, RFCs, RFSs, etc.). And we quickly discovered that the tool would be useful to support other business processes as well. We then use Footprints in IT Project Management (Footprints forms are super customizable and this was very useful for registering and monitoring projects). It was a happy surprise when we were able to implement Footprints in other departments besides IT, we had not planned this, the IT department won many points for that. Because we had a fast implementation solution and we became one of the main suppliers of operational performance reports (from the different sectors of the company). So we start to used Footprints in the area of Internal Controls and Compliance, where we made forms specialized in these activities and methodologies (5W2H for example). Our Legal department has also adopted the tool. Because the alert configuration features (based on elapsed time or status) worked very well to support their activities, in addition to the feature of recording time spent by activity, for billing of lawyers' hours to be separated by cost center, this was very cool.

The best part is the workflow and notifications are sent based on the status selected. Footprints is a great incident management tool. As a queue manager, I would highly recommend this software.

Footprints is reliable and does its job, even if it's a bit old-fashioned and clunky.

We have used this software to track helpdesk tickets, system access requests, and change management for many years now and it's overall worked very well with very little trouble. Support when needed has always been great too.

Footprints was once a great application, but since being rebuilt for version 12, it has lost much of what made it once so successful. While workspaces are fully customizable, they are built in several 'containers' that must match identically across various parts of the application to connect and function. For example, if you connect it to Active Directory for user authentication, you must create each field you want to appear in the ticket type, in that appropriate workspace, and then create a relationship between them. The navigation is not intuitive and requires quite a bit of digging around to find these settings. Footprints is very flexible, however. If you can think of something, you can probably create it and automate it here. My company was able to use it as a ticketing platform across several departments, each with their own custom fields and features. The reporting is very versatile. It allows you to build nearly any type of chart or graph and export it with the ticket data. They can also be scheduled to send to anyone by email address or user name. My biggest issue is the way attachments are handled mostly because if an attachment is added to a ticket, you cannot add it to outbound email by selecting it. It must be downloaded and uploaded to the ticket a second time as Footprints only sends out attachments on the update when they're added.

I've had the displeasure of being the admin for this trashy software for the past two years. I've put in a lot of extra hours just to keep this garbage software running. If you're wanting to give up your life to support garbage then this is the product for you. If you want a reliable software that is easy to maintain, then go find something else.