- 34
- sources read
- 3
- support
- 6
- dispute
For analysts and policy teams
The analyst's real job.
You are handed a district plan, a funding request or a program review and asked whether the claims stand. The evidence is real but scattered across report cards, budget filings, enrollment counts and prior plans. Reading all of it by hand is the job that never fits in the day. Lens reads it for you and marks each claim supported or disputed against the source.
- A literacy gain the state report card does not show.
- A funding figure that does not match the budget filing.
- An enrollment trend quoted from a year that was later revised.
- A vendor outcome with no study behind it.
THE CLAIM
One claim, checked.
- 1
Load the record
Upload the plan and the sources it rests on as an Index, or point Lens at the open index.
- 2
Ask the question
Smart Search ranks the report cards, filings and plans and invents no answer on top. Chat writes a grounded answer over them, marks each claim supported or disputed and lets you pick the model.
- 3
Read the split
See what supports the claim and what disputes it, with the passage behind each one.
- 4
Send it up with the evidence
Hand the board a memo where every number opens to its source, not a summary you defend from memory.
In your workflow.
The same four steps, whether it is a strategic plan, a grant application or a vendor review.
You already know how to read the evidence. Lens is how you read all of it in time.
Student and district records you upload stay in a private Index your team controls. Lens does not train on your documents, and the same inputs return the same verdicts.