An association with statutory delegated functions and around a hundred and forty active members. Its staff process court decisions daily and prepare documents on strictly defined templates under statutory deadlines, and part of the information the organisation is obliged to publish.
- Problem
- The work rested on a rented system from an outside vendor: the data and more than a hundred and thirty thousand files lived on the vendor's servers, and the platform underneath had long been out of support. Around a hundred and forty external users signed in through their personal accounts there every day. The website ran on a content management system more than a decade old — slow, with addresses that gave the CMS away, and with every edit going through a developer. Court decisions were read by hand, documents were assembled from the previous file, and deadlines were tracked by eye. The job started as a site migration and grew into leaving the rented system altogether.
- Solution
- A reporting platform with personal accounts of its own: each member sees their own documents from the archive, their applications and their correspondence, while staff see a shared queue with statuses. Court decisions are parsed automatically from PDF, documents are generated on the approved templates, the workflow has stages, roles and access rights, and the system itself warns about an approaching deadline and a newly arrived case. Separately from it — a public portal built around the organisation's four audiences: members, candidates, courts and creditors. Courts file their decisions electronically, the register of members is published from the platform's own database with a card for each member and a download as a table, and the figures on the front page are computed from the sources instead of being typed in by hand. All mandatory disclosures, news and documents were migrated off the old site with redirects from every old address, and an archive of more than a hundred and sixteen thousand files was moved into object storage.
- Outcome
- Preparing a set of documents went from hours to minutes, new cases are recognised and summarised on their own, and deadlines are tracked by the system rather than by someone's memory. The organisation is stepping out of renting someone else's system — the data and the archive return to its own perimeter. The public side lives separately from the application: mandatory disclosure stays available even when the application is down, and the register on the site cannot drift away from the reporting, because both read the same database. The portal is deployed and the switchover of the main address is being prepared.