99 Days to EU AI Act Enforcement. Here's the One Diligence Question Most Indian HR Buyers Aren't Asking Yet.

If your screening vendor doesn’t already log every prompt, every model call, and every candidate-disclosure timestamp, you don’t have a compliance problem. You have a vendor problem.

As of April 25, 2026, there are 99 days until EU AI Act enforcement begins. The two-digit countdown is here. August 2, 2026 is no longer a vague regulatory horizon — it’s a Q3 deadline that sits inside most enterprise procurement cycles.

For Indian HR teams, this is the week the question moves from “should we care?” to “what do we do right now?”

Who This Affects: The MNC + Indian HR Team Scenario

Let’s be precise about scope, because the EU AI Act is widely misunderstood as applying only to European companies.

It applies to any organisation that uses AI in hiring decisions for:

• Roles at EU-based entities — including Indian companies with EU subsidiaries
• Candidates in EU member states — including Indian MNCs with European hiring teams
• Global HR platforms — if the platform processes data for EU entities, the platform (and its clients) are in scope

The specific scenario that most Indian HR teams aren’t thinking about: you’re the India HR team for an Indian company that has a European parent, or that does significant business in Europe. Your global HR platform — Workday, SAP SuccessFactors, Oracle HCM, or their AI add-ons — is almost certainly covered.

Annex III of the EU AI Act explicitly classifies “AI systems used in employment, workers management and access to self-employment” as high-risk. That includes CV screening, interview scheduling, candidate ranking, and first-round AI screening of any kind.

The One Question to Ask Before August 2

Most vendor diligence processes for AI screening tools ask about accuracy, integration, pricing, and support. These are the right questions for a normal procurement decision. But for EU AI Act compliance, there’s a prior question that supersedes all of them:

“Do you maintain complete, timestamped, exportable logs of every AI prompt, model call, and candidate-disclosure event for every interaction — and can you produce those logs for any specific candidate interaction within 48 hours of a request?”

This is the EU AI Act question. Here’s why it’s the one that matters:

Prompts and model calls: The EU AI Act requires that high-risk AI systems maintain records of their operations. “Records” means the inputs the AI received (the prompts), what the AI produced (the model outputs), and when. A vendor that can’t show you a complete log of what their AI said during a specific candidate conversation is not compliant.

Candidate-disclosure timestamp: The EU AI Act requires that candidates are informed they’re interacting with an AI system. “Informed” means at a specific point in the interaction, before the substantive screening begins. That disclosure needs to be logged — with a timestamp — for every interaction. If a vendor can’t show you the disclosure timestamp for each candidate, they can’t prove disclosure happened.

48-hour retrieval: In the event of a complaint, investigation, or regulatory request, you need to be able to produce the full log for a specific interaction quickly. If your vendor’s answer is “we’d have to go to engineering for that,” you’re not ready.

Why This Question Sorts Vendors Immediately

When you ask this question, vendor responses tend to fall into three categories:

Category 1 — “Yes, here’s how.” The vendor shows you a dashboard, an export function, or a documented process for producing logs. They have a data retention policy with specific timeframes. They can demo the retrieval workflow. These vendors are prepared.

Category 2 — “We’re working on it.” The vendor acknowledges the requirement and tells you their compliance roadmap. With 99 days remaining, “working on it” is a yellow flag, not a red one — but you need a committed timeline and a contractual guarantee.

Category 3 — “Our legal team is reviewing.” This vendor is not prepared. At 99 days out, still being in “legal review” mode means they will not be compliant by August 2. If you’re covered by the EU AI Act, this is a disqualifying answer.

The Mobley v. Workday Addendum

The EU AI Act is the regulatory pressure. Mobley v. Workday — the age discrimination class action now proceeding in US federal court, with an amended complaint filed March 28, 2026 — is the litigation pressure.

The Mobley case is directly about what happens when AI screening decisions are made without complete human review and without adequate audit trails. The specific harm alleged: automated rejection with no logged human decision point.

For MNC enterprises that operate across US and EU jurisdictions, these two pressures converge on exactly the same requirement: every AI-assisted hiring decision must have a complete audit trail and a documented human review step.

The vendor question above catches both.

What HireQwik’s Answer Is

HireQwik’s architecture was designed with auditability from day one:

• Every conversation is fully logged — AI prompts, candidate responses, follow-up questions triggered, and scoring decisions — with timestamps
• Candidate disclosure is delivered at the start of every screen and timestamped in the interaction log
• No candidate receives a rejection communication before HR has reviewed the AI’s tier recommendation
• Logs are exportable on demand — HR can pull the full record for any specific interaction

This isn’t a compliance feature we added when the EU AI Act deadline approached. It’s the product design — because building a defensible AI screening tool requires the same architecture that compliance requires.

The 99-Day Action List

If you’re covered by the EU AI Act and you haven’t started, here’s the sequence:

1. Identify scope. Does your company have EU operations, EU parent, or EU data processing? If yes, you’re likely in scope.
2. Audit your current AI screening tools. Run the one question above against every vendor in your stack.
3. Request documentation. Ask for data processing agreements that reference EU AI Act high-risk provisions, sample audit logs, and candidate disclosure language.
4. Resolve gaps before mid-June. At 99 days out, you have time — but not if you wait until July.

The 60-day mark (June 2) is when enterprise procurement panic typically starts. The teams who move now will be ready. The teams who wait for the panic will be scrambling.

See HireQwik’s compliance documentation — audit logs, candidate disclosure workflow, and human review architecture. Built for the August 2 deadline from day one.