Oracle ULA Certification 90 Day Checklist. The buyer side exit.

The cards above are the task list. This companion is the running order: what happens in each of the thirteen weeks, who owns it, the artifact every week must produce, and the four gates that tell you whether the count is ready to submit. Print the checklist, then run the calendar below against it.

Two neighbors carry the material this companion deliberately leaves out. The ULA certification guide owns what certification is, what the evidence pack contains, and how the countersign works, while the Oracle ULA guide owns the agreement lifecycle around it.

If part of the estate runs on AWS, read the ULA on AWS guide alongside this calendar, because cloud counting has its own clause driven rules that change what weeks five to eight must collect.

What has to happen in each of the thirteen weeks?

One focus per week, one artifact per week, and a gate roughly every month. The table below is the whole plan on one screen; the rest of this page explains how to run it and what to do when it bends.

Why the count date is fixed in week seven, not week thirteen

Because the count is taken at the contract end date, and every deployment decision after week seven needs to know which side of that date it lands on. Fixing the date early, in a written memo, turns a future argument into a settled fact.

The partitioning evidence files in the same week for the same reason. Positions documented against the Oracle partitioning policy before the draft count exist as evidence. Positions assembled after a challenge exist as excuses.

What each gate must show before you pass it

• Gate 1, week four. Every host running Oracle is listed, the script and tool outputs match or the deltas are explained, and every VMware cluster boundary is documented. An unexplained delta here compounds through every later week.
• Gate 2, week eight. The draft count exists per product and metric, it has survived an internal challenge session, and nobody on the team is still discovering servers.
• Gate 3, week ten. Every geography maps inside the territory clause, and every option and pack finding has a remediation owner and a date.
• Gate 4, week twelve. Legal has approved the letter wording, the sponsor has signed the number, and the evidence pack is sealed and versioned.

How do you run the heavy weeks without losing them?

Three stretches decide the whole calendar: the week one kickoff, the inventory push in weeks two to four, and the challenge session in week eight. Run these three well and the other ten weeks follow the table.

Week one: the kickoff that saves week thirteen

The kickoff is ninety minutes, and it produces the charter, not enthusiasm. Its agenda has five fixed items.

• Read the certification clause aloud. The actual wording, not a summary. Half the room usually hears it for the first time.
• Confirm the contract end date and the thirteen week calendar. Gate dates go into calendars before the meeting ends.
• Assign the five owners by name. Roles without names are how gate one slips.
• Book legal's return slot. Weeks eleven and twelve, reserved now.
• Agree the escalation rule. Who decides when a recovery rule fires, so slips get managed instead of debated.

Week one's second artifact: the contract file

Certification runs on paper you already have, gathered in one place. The file that must exist by the end of week one contains six things.

• The ULA ordering document and every amendment, including any acquired entity additions.
• The certification clause, the territory clause, and the included products list, extracted and highlighted.
• The count of options and packs named inside the ULA, against the ones the estate is suspected of using.
• Prior correspondence with Oracle about the ULA, especially anything touching scope or entities.
• The support renewal history, because the certified count sets the future support base.
• A blank decision log, opened and dated.

Weeks two to four: the inventory push

The inventory is two parallel streams that must converge by gate one. The discovery tooling stream produces the estate wide baseline, and the Oracle script stream produces the vendor format measurement, and week four exists to reconcile them line by line.

The reconciliation memo is the artifact reviewers respect most. For every delta between the two streams it records the host, the cause, and the resolution, signed by the database owner. Deltas explained in week four are housekeeping. The same deltas found by Oracle later are findings.

Week eight: the internal challenge session

Before the count freezes, someone plays Oracle. The certification lead appoints a challenger, ideally an advisor or a licensing literate manager outside the count team, and the draft has to survive five questions.

1. Which hosts appear in discovery but not in the count, and why is each one excluded?
2. Where are the VMware boundaries, and what happens to the number if a cluster is read at its widest?
3. Which deployments landed within ninety days of the end date, and can each one's date be evidenced?
4. Do the Named User Plus figures respect the per product minimums, and where did the user list come from?
5. If the territory clause is read narrowly, which entries fall out, and what is the exposure worth?

A draft that survives the session freezes at gate two. A draft that does not was going to fail anyway, and it is far cheaper to fail in week eight than in Oracle's review.

How does the plan change for virtual, cloud, or acquired estates?

The thirteen week spine stays fixed. What changes is where the slack goes, and three estate shapes claim it predictably.

Mostly virtualized estates

Give the inventory push an extra week by starting discovery in week one, because cluster boundary documentation is the slowest artifact in the whole plan. The challenge session's cluster question then decides gate two, so the infrastructure owner attends it in person.

Cloud heavy estates

Read the certification clause for cloud treatment in week one, not week nine, because it determines whether cloud deployments belong in the count at all. Evidence for cloud runs on its own rules and its own calendar, covered in the ULA on AWS guide, and the certification lead merges that stream at week eight.

Recently acquired entities

Acquired estates carry two risks into the count: deployments outside the territory clause and entities outside the customer definition. Week one flags them, week three inventories them separately, and week nine resolves them against the clause with legal in the room.

The one variation that never works

Skipping weeks. Every compressed certification we reviewed skipped the reconciliation memo or the challenge session, and both omissions surfaced later as counter findings. The plan flexes by adding parallel owners, never by deleting artifacts.

Who runs the count, and how much of their time does it take?

Five named people run a certification, and only one of them is close to full time. Staffing the count as a side project for everyone is how week four slips into week six.

The roster and the load

• Certification lead. Owns the calendar, the artifacts, and the gate reviews. Two to three days a week for the full thirteen weeks.
• Database owner. Runs the scripts, answers for deployments, and carries the heaviest load in weeks two through eight.
• Infrastructure owner. Owns the cluster map and the partitioning evidence, concentrated in weeks three through seven.
• Procurement lead. Holds the contract file, the count date memo, and the renewal offer, active throughout but heaviest in weeks nine through thirteen.
• Legal counsel. Reads the clause set in week one, then returns for weeks eleven and twelve. Booking that return slot in week one is the single best scheduling decision in the plan.

The meeting cadence that keeps thirteen weeks honest

One weekly forty five minute review against the artifact list, plus a gate review with the sponsor at weeks four, eight, ten, and twelve. Every decision lands in a single log with a date and an owner.

No other meetings are needed, and adding them is a warning sign. A certification that needs daily calls is a certification whose inventory was not finished at gate one.

The weekly review has a fixed shape: last week's artifact shown, this week's artifact named, blockers assigned, and the decision log updated on screen. Twenty minutes of status, twenty five of decisions, and nothing carried verbally between meetings.

What do you do when a week slips?

Protect the gates, not the weeks. The plan has slack inside each month, and the recovery rules below spend that slack deliberately instead of letting it evaporate quietly.

The recovery rules

• Slip inside a month, rebalance inside the month. A week three overrun comes out of week five's slack, decided at the gate review, not discovered later.
• Gate 1 slipping more than two weeks means asking for time early. A written extension request in week six is a routine administrative matter. The same request in week twelve is a confession.
• Parallelize the counting weeks if needed. Processor and user counts can run concurrently with two owners, at the cost of a heavier challenge session at gate two.
• Never compress week twelve. Legal review and sign off take the time they take. Compress week eleven's remediation instead and document what remains open.

Asking Oracle for time, correctly

Extensions exist, but only in writing and only from the right counterparty. The request goes to the contract notice address, states a specific new date, and never explains more than it must.

What you do not do is discuss the state of your count with the account team while asking. The extension conversation and the sales conversation are separate tracks, and Oracle merges them the moment you let it.

If a formal review follows, it arrives through Oracle License Management Services channels, and the delivery record from week thirteen anchors the timeline.

The week ten renewal call

A renewal offer in weeks ten and eleven is not a coincidence. It is priced against your unfinished count, because an uncertain buyer values the safety of another term more than a buyer holding a frozen number.

The decision rule is mechanical: no renewal conversation until gate two has passed and the count is frozen. Park the offer, acknowledge receipt politely, and let your own number, not Oracle's timing, decide whether renewal or exit wins. The exit economics live in the ULA exit strategy guide.

Pricing what remediation cannot fix

Week eleven sometimes leaves exposure standing: an option in use with no license, a geography outside the territory. Price each open item at the Oracle technology price list before submission, so the sponsor signs the letter knowing the worst case number, not hoping there is none.

The same week settles the post exit support posture, because the certified count sets the support base going forward. The reference framework is Oracle's own Software Technical Support Policies, and the third party route for stable estates is covered in the third party support analysis.

15

ULA certifications advised, 2024 to 2025

30 to 40%

More entitlement locked by structured counts

20 to 30%

Of submissions countered by Oracle's reviewers

Source: Redress Compliance advisory engagement file, ULA certifications 2024 to 2025.

The certification letter is one page. The thirteen weeks exist so that every number on that page has a file behind it.

Where the common advice on the 90 day certification plan is wrong

The common advice treats the 90 days as the whole job: start the clock, run the scripts, file the letter. We disagree. The 90 day window is an execution artifact, and it only works when the strategic decisions arrive at day one already made: exit or renew modeled both ways, the post exit support posture chosen, and the deployment footprint pushed while the term still allowed it. Teams that open those questions inside the window spend their counting weeks debating strategy, miss gate one, and land exactly where Oracle's timing wants them, uncertain in week ten with a renewal offer on the table. Do the deciding before day one. Spend the 90 days counting.

What should a buyer do next?

1. Confirm the contract end date and count back thirteen weeks to find your true start date.
2. Name the five owners and book legal's week eleven and twelve slots now.
3. Write the certification charter and put the four gate reviews in the sponsor's calendar.
4. Start week one this week if the start date has already passed, and apply the recovery rules to what remains.
5. Fix the count date memo no later than week seven, whatever else has slipped.
6. Park any renewal offer unanswered until the count is frozen at gate two.
7. If more than one gate has already been missed, bring in help: talk to Redress before submitting anything.

Frequently asked questions

How long does Oracle ULA certification take?

Ninety days from the start of the inventory to the submission of the certification letter, run as thirteen weeks with four gates. Compressed timelines lock less entitlement because the count misses virtual deployments and option usage, which is exactly what the week four gate exists to prevent.

What is the territory clause?

The territory clause inside the ULA limits the certification count to declared geographies. Deployments in countries not named in the clause do not count toward certification and create separate exposure outside the ULA, which is why week nine maps every geography before the letter is drafted.

Do Oracle options count under a ULA?

Only options explicitly included in the ULA. Diagnostic Pack, Tuning Pack, Advanced Security, and similar options are often excluded and create separate exposure, so the week ten audit checks usage before Oracle's reviewers do and gives every finding a remediation owner.

Should I let LMS run the certification count?

No. Customer initiated counts hold in the large majority of submissions, while reviewer led counts move against the customer far more often. Control the inventory, the count date, and the territory map yourself, and submit a number your own evidence supports.

Can I avoid a ULA renewal at certification?

Often. Around seventy percent of the customers Redress advised in 2024 and 2025 exited at certification rather than renewing. The decision depends on the certified entitlement size, the support position, and the strategic direction on Oracle, all of which should be modeled before week one.

What happens if I miss the certification deadline?

The agreement's default consequences apply, which in most ULAs means Oracle treats the estate as uncertified and pushes toward renewal. A written extension request sent early, to the contract notice address with a specific new date, is routine. The same request sent in the final week has no leverage.

Who should own the ULA certification internally?

A named certification lead, usually from IT asset management or procurement, at two to three days a week for the full thirteen weeks. The lead owns the calendar and artifacts, with database, infrastructure, procurement, and legal owners carrying their weeks, and a sponsor who attends only the four gates.

Related advisory: the ULA certification guide for the declaration and evidence pack, the Oracle ULA guide for the full lifecycle, and the ULA on AWS guide for cloud counting rules.