ORX

The challenge: 6,000 documents, and members struggling to navigate them

ORX is owned and driven by its members, so the quality of service it provides is the whole basis of its reputation. It had built that reputation as a leading source of risk loss data. The difficulty was volume: more than 6,000 documents across dozens of topics, growing daily, with members struggling to locate and apply the insight most relevant to them.

In a field where a missed update can mean real regulatory exposure, that was a problem worth solving properly.

Our approach: learn the domain, then build

Financial risk analysis, increasingly called RegTech, is a specialised field where oversights carry real consequences. So we started by learning the domain, not writing code.

Our consultants and developers ran an in-depth discovery phase with the ORX team and their dedicated product owner: collaborative workshops, user profile analysis, and reviews of existing documentation, design assets and infrastructure. That work produced over 200 user stories and acceptance criteria, and a shared product vision. We entered development knowing exactly what we were building and who we were building it for.

What we built on Drupal

We built the application on Drupal. For a project that was equal parts editorial workflow, search and integration, Drupal gave us an enterprise content platform to build on and the freedom to develop bespoke functionality on top of it, rather than starting from scratch.

That combination shaped everything we built:

• A tailored editorial workflow lets the ORX team publish daily news snapshots, analysis and deep dives quickly, while making sure sensitive information is properly validated first.
• Bespoke advanced search lets members filter more than 6,000 documents by content type, currency referenced, loss amount range and more, alongside standard keyword and reference ID searches, and save the searches they run most often.
• A near real-time news map sizes and colours each story by focus and importance, giving members an at-a-glance read on the wider risk landscape. It can be searched and filtered like the rest of the content, with direct access to individual stories.
• A custom Single Sign-On links the news application to the main ORX membership site, checking each member’s permissions and routing them only to the content their subscription covers.

Building all of that on Drupal meant ORX got a platform its own team could run and extend, not a black box.

Delivery: getting the workflow right, and keeping it reliable

Because the information ORX publishes is sensitive and time-critical, getting the workflow right mattered as much as getting it built. We defined a publication process comprehensive enough to validate every document, yet efficient enough not to slow the editorial team down, and flexible enough to adapt as needs change.

Software testing ran alongside development throughout, so the workflow, search and integrations held up under the demands of a live, daily-updated service.

The outcome

Members can now find, filter and act on the content they need in a fraction of the time, with the news map giving them a view of the risk landscape they never had before.

Global member engagement rose by 40%. For an organisation whose value to members is the quality of its insight, that is the metric that matters: the data was always strong, and now it is genuinely usable.

What this means for your organisation

If your organisation sits on a large, growing body of specialist content that members or customers struggle to navigate, the answer is rarely more content. It is making what you have findable, trustworthy and quick to act on.

That is what we did for ORX, building on Drupal so their team could keep evolving the platform themselves. If you are weighing up Drupal for a content-heavy application, or trying to get more value from one you already run, our Drupal development team would be glad to talk it through.