Recently, our ORC team got our heads together to discuss ideas for post-go-live health checks. What do we focus on when an Oracle Recruiting customer asks us to take a look at their setup six months or a year after go-live?
For those who have worked with our band of merry (talkative/excitable/mostly Brummy) ORC consultants, you probably won’t be surprised to hear that ideas came thick and fast. We found ourselves talking about everything from interview management and how candidates move through the process to offer letters, change management, new Oracle functionality and, of course, a sprinkling of AI.
What was interesting was that, based on our real experiences as consultants, recruiters and in-house HRIS people, most of the conversation came back to the niggly things. The things that wind users up and, when stacked up, can damage the reputation of what should be a hugely powerful tool. It was about all the little things that happen after go-live: the spreadsheet that was only supposed to be temporary, the extra CSP state that got added “just for this scenario”, and the process that made perfect sense during design workshops but doesn’t quite reflect how the business works today.
Talent Acquisition teams and hiring managers aren’t sitting there wondering which feature to enable next. They’re trying to recruit efficiently, make life easier, engage the best candidates and get the most value from the system they’ve invested in. And that’s why health checks can be so valuable.
Is Your Process Still the Right Process?
One topic that came up repeatedly was process design. Most of us have seen selection processes that have redundant phases, states and workarounds. Each made sense “at the time”, but a few years later the overall process can feel more complicated than it needs to be, leaving users unsure what to select.
Perhaps one way of looking at the process piece would be to take a step back and ask, “If we were implementing ORC today, would we design it this way?”
Are People Really Using ORC?
Another common theme was adoption. It can be so common to see how many manual processes can creep back in after go-live: interview trackers, spreadsheets, offline approvals, manual offer administration, all the usual suspects. Recruitment teams are resourceful. If they think something helps them get the job done quicker, they’ll find a way. The problem is that over time those workarounds can create inefficiencies and reduce the value of the system.
A health check is a great opportunity to understand what’s really happening on the ground rather than what the process map says should be happening.
Have You Looked at What’s Changed Since Go-Live?
Oracle Recruiting Cloud doesn’t stand still. Far from it, staying on top of releases takes commitment! Several of the team highlighted features that clients are now revisiting because the functionality available today is very different from what existed when they first implemented ORC. From interview management improvements and recruiter tools, through to VBS enhancements and offer automation, there are often opportunities to simplify processes without major change programmes.
Optimisation isn’t always about changing the process; it’s also about taking advantage of capabilities you didn’t have when you first went live. That’s what people buy into when they buy Oracle Cloud, but it can be hard to remember that when you’re back into BAU. Here’s your reminder 😉
Now, Let’s Talk About AI
It wouldn’t be a 2026 blog if we didn’t mention AI. But interestingly, when AI came up in our discussion, the conversation didn’t jump straight to shiny new functionality. It came back to the basics.
That was probably the most useful AI takeaway: before you get too excited about what AI could do, it’s worth checking whether the basic data and processes are in good shape. Are recruiters using the system consistently? Is candidate data being captured properly? Are job profiles being maintained? Are key recruitment activities actually happening in ORC? Because if the answer to those questions is “not always”, then there is probably more immediate value in fixing the basics first. AI can help unlock real value, but only if the underlying processes, data and system usage are reliable enough to support it.
One AI feature that really did get us talking, was the Career Coach. Embedded within Oracle Recruiting, Career Coach uses AI to analyse candidates’ skills, experience and interests to recommend relevant roles and provide conversational support throughout the hiring journey. Candidates can get help discovering suitable opportunities, understanding their fit for a role, navigating the application process and preparing for interviews. For recruiting teams, it can also provide richer candidate information and help streamline early screening and interview scheduling.
But Career Coach also brings us right back to the point about foundations. If you’re considering capabilities like this, a health check is a good opportunity to look at the quality and consistency of the data and processes that sit underneath your recruiting experience. Are your job profiles and skills information in good shape? Is candidate information being captured effectively? Are your recruitment processes working as intended?
The good news is that this doesn’t mean putting AI on hold. It means using a health check to understand how ready you are for it. The same activities that improve reporting, streamline processes and reduce manual effort also put organisations in a much better position to benefit from AI when they’re ready.
Final Thought
By the end of the conversation, we’d decided an ORC health check isn’t about finding problems per se. It’s about understanding what’s working, what’s changed since go-live, where the quick wins are, and where there might be opportunities to get even more value from Oracle Recruiting Cloud.
Sometimes that’ll lead to enabling AI features. Sometimes it might lead to deleting a spreadsheet that’s somehow survived three years of system adoption. And, depending on where you’re at on your ORC journey, both are pretty good outcomes.
