The rule we use
There is one rule for deciding where a person belongs in the process. If a decision could change whether a specific student gets a specific seat, a person reviews it before it becomes final. The review happens first, and only then does the decision count. If a decision only removes repeated manual work, no person is needed. Checking that a document is in the right format is one example. Syncing a deadline across two dashboards is another. Nobody’s outcome changes in those cases, and no judgment is being made that affects a student’s seat. A checkpoint there would slow things down and protect no one, so we leave it out on purpose.Where a person steps in
Document verification
A document clears without a person only if it scores high on the automated check. If the system is less sure, the document goes to a reviewer, who makes the call instead of the system guessing. The scoring behind this is explained in the earlier sections on PraveshAI.
Publishing an allotment
A finished match never reaches a student automatically. It goes to the counselling authority first, and nothing is published until they give their explicit sign-off. The student only sees a result after a person has looked at it and approved it. How a Counselling Authority Actually Runs a Round covers this in full.
Grievances
A person resolves every dispute. Each one is sorted into a category and sent to whoever is actually in a position to decide it, so it does not sit with someone who cannot act on it. Nothing is ever closed automatically. How a Dispute Actually Gets Resolved walks through the whole path.
Pausing, extending, or rolling back a round
These are the most disruptive actions the system allows, so each one needs explicit authorisation. A rollback goes one step further and needs more than one person to approve it. No single person can undo a round alone. The Safety Levers Behind Every Round explains how this works.