“Rejected — Form 6A/challans unavailable” sounds like an answer. It is only a stop sign. It does not say what was checked, who holds the missing record, who must act, when they must act, or what the citizen can do next. The cruelest part of an opaque status is that the person with the least control inherits all the uncertainty.
Decision quality begins before the outcome. A proposed rejection should not move until its evidence, ownership, verification, next action, deadline, source, and accountable human are visible.
The problem is not a missing chatbot
The Build What Moves India brief asks builders to choose one real public-service journey and make it simpler, clearer, and useful from end to end. It also says reviewers will test the citizen experience, not merely an administrative panel. That is exactly the useful constraint here.
NyayaPF does not add an open-ended assistant on top of a rejection. It changes the decision record underneath it. A citizen-facing explanation can only be good if the officer workflow has already recorded what was considered, what remains unresolved, and where responsibility actually sits.
Ownership comes before responsibility
EPFO’s public accounting procedure describes Form 6A as a consolidated annual contribution statement submitted by the employer. That matters because “this evidence is absent” and “the citizen must produce this evidence” are two different statements. NyayaPF represents evidence ownership as citizen, employer, bank, EPFO, or unknown and refuses to silently collapse those categories into a citizen task.
A March 2026 Bombay High Court decision provides one useful illustration. In that matter, the dispute concerned employer-side Form 6A and challan gaps and other recorded evidence. NyayaPF uses the decision as a design prompt: make control, verification, and alternatives visible. It does not use one case to claim the problem is common, decide another person’s rights, or offer legal advice.
Seven boring rules make the dramatic moment possible
Specific reason
A code and plain-language explanation must name what remains unresolved.
Known owner
Unknown ownership means request information or continue review.
Correct burden
Employer- or EPFO-controlled records cannot be assigned to the citizen.
Source
An inspectable policy or source reference must be recorded.
Checks
Non-citizen-held gaps require internal or alternative-evidence checks.
Repair path
Action, responsible party, and deadline must travel together.
Human owner
An accountable officer must confirm the evidence and explanation.
The rules are deterministic because this is the wrong place for vibes. They return a proposal for revision and recommend only five bounded moves: revise the reason, request information, request employer records, perform internal verification, or continue human review. Even a finding-free result means only “ready for a human decision.” It never means approved, rejected, or legally eligible.
The citizen gets an explanation; the system keeps its humility
After the officer records an employer request, checks internal records, evaluates alternatives, structures the next request, and confirms the draft, the citizen sees an English or Hindi notice. The notice names evidence considered, the unresolved issue, the controller, the next actor, the synthetic deadline, and administrative follow-up. If rejection later persists, a local dossier can preserve the evidence ledger, rule receipt, and event trail for a mock EPFiGMS handoff.
“Mock” is doing real safety work in that sentence. Nothing is transmitted. No login is attempted. No government portal is scraped. No real UAN, PAN, Aadhaar, bank detail, OTP, payment, or personal record enters the system. The public lab works from committed synthetic fixtures and deterministic browser replay, with FastAPI as the local reference implementation.
The audit is a test receipt, not an impact dashboard
NyayaPF’s audit screen counts twelve deliberately constructed evaluation cases. They prove that removing a source triggers QG-04, removing a deadline triggers QG-06, and removing human confirmation triggers QG-07. They do not prove anything about actual EPFO rejection rates, processing time, grievances, prevalence, or government adoption.
That distinction is part of the product. Public-service prototypes become less trustworthy when synthetic dashboards borrow the emotional authority of real-world impact. A test fixture is useful proof of software behavior. It is not a citizen outcome.
Do not ask AI to make the high-stakes decision. Make the human decision’s evidence, ownership, and repair path impossible to omit silently.
Try the complete synthetic journey
Start as the fictional citizen, trace the burden shift, then open the officer route and attempt the incomplete rejection. Repair the record, confirm the human boundary, return to the bilingual notice, download the local dossier, and inspect the synthetic audit.
Sources and boundary
- Build What Moves India builder brief
- Build What Moves India FAQ
- EPFO Manual of Accounting Procedure, Part I, Chapter 4
- EPFO Form 6A
- Kiran Rajaram Jadhav v. EPFO — one illustrative decision, not prevalence evidence
Independent prototype. Synthetic data. Not affiliated with or endorsed by EPFO. NyayaPF does not determine legal eligibility, approve or reject claims, or provide legal advice. A human officer remains responsible for every decision.