The current wave: 26C at a glance
26C is 2026's biggest release so far — Oracle's release intelligence trackers count ~634 feature changes across 86 modules, continuing three arcs that started in 26A/26B:
- Agentic applications keep expanding. 26B formally introduced Fusion Agentic Applications; 26C widens the embedded-agent footprint across finance, HCM and SCM. If you haven't formed a view on agents yet, start here — interview panels already have.
- Redwood keeps absorbing screens. Every quarter more classic pages get Redwood equivalents — and each wave moves some from "optional" toward "default." The migration is a conveyor belt, not an event.
- Audit and compliance hardening — continued tightening relevant to SOX/GDPR-minded clients.
Primary source, always: Oracle's official readiness / What's New documents. Read those for the what; read on for the how to survive it.
How the quarterly rhythm actually works
| Beat | What happens | What Oracle doesn't emphasize |
|---|---|---|
| Preview / test window | Your non-prod pods get the update ~2 weeks before production | Two weeks disappears fast — if your regression scope isn't ready before the window opens, you're not testing, you're touring |
| Production weekend | Update applied in your scheduled maintenance window | The rollout is staggered across customers over weeks — "26C is out" and "26C is on your pod" can differ by a month |
| Opt-in features | New features arrive disabled; you enable when ready | Opt-ins expire. Features move from optional to mandatory on a schedule listed in the docs — the trap is treating "opt-in" as "optional forever." Track expiry dates like project deadlines |
What Oracle doesn't clarify (the field notes)
- "Opt-in" is a countdown, not a choice. Every opt-in has an expiry release. The clients who get ambushed by a UI change "nobody approved" are the ones nobody assigned to read the opt-in expiry table quarterly. That's a 30-minute job that prevents a war room.
- Test what moves money, not what's new. The instinct is to test the new features; the damage happens in the old ones. A sane minimum regression: one invoice-to-payment cycle, one order/receipt-to-invoice match, one journal-to-close cycle, your top 5 integrations, your top 10 reports. Boring, and it catches most of what matters.
- Redwood changes behavior, not just looks. Field defaults, search behavior, keyboard flows — retrain the power users before the switch, or your ticket queue does it for you.
- Personalizations and extensions are your risk surface. Standard functionality rarely breaks; the client's customizations are where update weekends go wrong. Inventory them; test them first.
- The interview angle: "How do you handle a quarterly update?" is now a standard scenario question. A senior answer names the preview window, the opt-in review, and a regression scope — in that order. The Panel will happily drill you on it.
The 30-minute quarterly ritual (steal this)
- Open the What's New for your pillars; filter to your modules.
- Read the opt-in expiry table first — anything expiring this release goes on the risk list.
- Skim new features tagged to your modules; flag the 3 most client-relevant for a demo note.
- Confirm your regression pack still matches your top transactions.
- Write the 5-line client note: what's coming, what we'll test, what needs a decision. You are now the consultant who "stays current" — a reputation built in 30 minutes a quarter.
Get drilled on the update question.
"Walk me through how you'd handle 26C for your client" — practice it against The Panel before a real interviewer asks. First drill free.
Face the Panel — free →Updated July 2026 for the 26C wave · Next update: 26D (Q4 2026). Sources: Oracle readiness documents and public release-intelligence trackers; field commentary from working-consultant experience. Verify release-specific behavior against your pod.