The new retrieval index creates capacity while uncertain permission evidence blocks the cutover.
Delaying protects against access mistakes while proceeding protects contract ingestion and search continuity.
Who you’d be doing this for
“If a restricted agreement shows up for the wrong person, I’m the one answering that call.”
Jawad Younis · Director of Legal Operations
Administers repository access and must explain why sensitive contract terms appear in search results.
What is at stake
The current index reaches capacity in 21 days, while automated and legal review disagree on 14% of access-sensitive queries. You must weigh a one-way capacity cutover against the proof needed to protect contract confidentiality.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- index capacity vs permission certainty
- automated judgments vs legal verification
- migration progress vs reversible operations
- feature continuity vs tenant isolation
Why Ironclad
Agent Assistant and Conversational Search rely on tenant-scoped contract evidence, making retrieval permissions part of product trust.
Written with these in mind
Not your kind of problem? 9 more at Ironclad, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.