Furness io: Case Study

IPAF Case Study - Automated Processing

IPAF relied on a legacy application requiring manual approval. We identified bottlenecks and solutions to automate this process. Upon delivery, 72% of applications are automatically approved.
72%
Automatically Processed
22 hours
Saved a month
125,000

Applications automatically processed 

The Challenge

IPAF promotes and enables the safe use of powered access equipment worldwide, working closely with accredited training centres to deliver globally recognised training courses. As part of this process, training centres submit licence applications through IPAF’s web portal.

Once submitted, each application had to be reviewed and approved manually by IPAF staff using a separate legacy system hosted on an on‑premises server. This split workflow created operational friction, where staff were required to move between two systems, approvals were slow and repetitive, and the ageing infrastructure was increasingly unreliable.

In its existing form, the process was time‑consuming, difficult to scale, and prone to delays - ultimately limiting IPAF’s ability to grow and modernise their operations.

Project Outline
Client: IPAF
Industry: Powered Access/Construction
Services provided: Software development, automation, cloud infrastructure
Date: May 2025 - Jan 2026

"The delivery of this project was a huge milestone in IPAF’s digital transformation journey. Furness did not only make this possible but assured that risk was continually managed, progress was well communicated and solutions were found for any issues identified."


- Anouck Sauer, IPAF Operations Project Lead

Impact on the business

The manual approval process placed a significant administrative burden on IPAF's team, with staff spending valuable time completing repetitive checks instead of focusing on higher-value activities. As application volumes increased, processing times slowed and additional resource was required simply to keep pace.
OPTION 1 / POINT 1
Staff Time

Every licence application needed a manual review, tying up a dedicated member of IPAF’s team. Staff were working through the same routine checks on each submission, leaving less time for the exceptions, training centre support and improvement work that genuinely needed their expertise.

OPTION 1 / POINT 1
Scalability

Because every application was handled by hand, workload rose in step with volume. Busy periods led to backlogs and slower turnaround for training centres, and the only way to keep pace with demand was to add more resource to the approval process. Now the process can scale without increasing workload for staff. 

OPTION 1 / POINT 1
Reliability

Approvals depended on a separate legacy application running on an on-premises server. Staff had to switch between two systems for every application, and the increasingly unreliable infrastructure created a risk of downtime and stood in the way of IPAF’s wider digital transformation.

Our Process

A series of discovery workshops were held with key stakeholders in IPAF’s projects team, allowing us to identify challenges in the existing workflow early in the project, while also understanding the outcomes which IPAF wished to achieve. We were then able to collaborate on a clear and actionable delivery plan which worked for both Furnes.io and IPAF.

Collaborative planning with regular stakeholder engagement.
Delivering value early through incremental releases.
Continuous feedback to refine and improve the solution.
Agile development practices that enabled flexibility as requirements evolved.
Controlled, low-risk deployments using feature flags and phased rollouts.

To support controlled and low-risk deployments, we leveraged feature flags. This allowed IPAF to enable changes selectively, starting with specific clients for pilot rollouts, expanding to country‑level rollout once validated, and eventually activating features globally.

This phased approach ensured smooth adoption, reduced the risk of disruption, and gave IPAF full control over how and when each capability was introduced. 

Our Solution

The initial focus was on upgrading the portal to support automated processing. To achieve this, we introduced new logic which automated the checks staff were having to do on each application. Compliance checks were added directly into both the course‑booking stage and the application‑submission stage, ensuring that course records remain complete and accurate, even when exceptions occur, while also improving traceability.
Introduced automated compliance checks during course booking and application submission, improving accuracy.
Embedded IPAF's approval rules to automatically process standard applications, leaving only exceptions for staff to review.
Migrated the full approval process to the cloud, removing the legacy on-premises system.

“Delivering this project with Furness.io was a true collaboration – we brought the business problem and process knowledge, and Furness brought the technical know-how, problem solving expertise and can-do approach.  The project ran incredibly smoothly from start to finish – achieving all the required deliverables and enabling massive business benefit. It is easily one of the smoothest software development projects I’ve been involved with”

- Matt Hutchinson, Project Manager, IPAF
Ready to start a project?
We’d love to hear more. Tell us a bit about your project and we’ll be in touch with you shortly.

Or Contact Us

servicedesk@furness.io01229 808050

Privacy Policy(Required)

Office Address

84 Dalton Rd, Barrow-in-Furness, Cumbria LA14 1JH

© 2026 Furness.io (a wholly owned subsidiary of Furness Internet). All Rights Reserved. Privacy Policy | Cookies Policy

Registered Office: Furness.io, 84 Dalton Road, Barrow-in-Furness, LA14 1JH, United Kingdom. Registered in England and Wales Company Number 13829169.

phonemenu