Rahul Mehta Gandhinagar LsCandidate

A key difference between clause like (a) 'Patwari will enter approvals of voters on PM's website, which all will be able to see' and a clause like (b) 'DEO shall make a good website with all details' ---- the 2% HONEST officers can easily punish Patwari etc who are not enforcing clause-a, but they cant punish officer who isnt enforcing clause-b !!
.
Thats why , clause-b is SPURIOUS.
.
---
.
When RTR/Jury law-drafts get printed, for a long time, some 95% to 98% officers/judges etc will be hostile to the law and its spirit and will think of all possible ways to sideline the clauses. But some 1% to 2% to may be 5% officers will try to enforce them.
.
But here, they can enforce ONLY those clauses which are very objective, very narrow, which can be executed within minutes or few hours, within fixed funds and man count. IOW, the clause should be so that if that clause is not executed then specific officer can be punished. That is the ONLY way a small % of honest officers can get the clauses executed in 95% hostile environment
.
So clause like "(a) 'Patwari will enter approvals of voters on PM's website, which all will be able to see' is a good clause because a 2-3 specific officers can be blamed when the clause isnt executed, and so even if just 2% to 3% officers are honest, they can get the clause executed
.
But consider clause "(b) DEO shall make a good website with all details". This task involves 10s of staff --- from website coders, data gatherer, data entry people, website admin and clerks of DEO and DEO. Most of them will be hostile to whole RTR/Jury system. Lets say DEO is good. But if some information doesnt come on website, it will NOT be possible to determine who is guilty without a detailed investigation and trial. So good apex officers have to no easy way to know who did mischief and he will need to spend a lot of time to decide who played mischief for every mischief done. And junior and middle level officers know that they can do mischief and get away. So there will be no end to their mischief.
.
Thats why almost all procedures I have proposed in round are "simple" in nature i.e. violation or refusal to execute will be immediately visible to all, and so voters or honest officers can immediately intervene and fix things.
.
One can analyse the clauses which guarantee great things like "officer shall ensure that all get employment" or "officer shall make good website" or "officer shall free food to all". Such clause needs a lot of resources and huge staff , and so when they are NOT properly executed voters or apex honest officers have no easy way to decide who made mischief and who should be expelled/punished. So staff will have ample room to make mischief
.
So thats why SIMPLE clauses like "Talati will enter approvals or voter on PM's website in a way all can see" are useful. And complex / composite instructions like "officer must keep a good website will all details and all expense reports" are useless for several MONTHS even after RTR/Jury come, because when such instructions are not fulfilled neighter voter nor small number of honest officers can decide which mischief playing officer to punish.
.
So my request to activists is --- focus on SIMPLE instructions and all complex tasks you need should be built using drafts containing sequence/set of simple instructions. Avoid great sounding declarations like "officer must ensure all have food", "officers must ensure good education for all" or 'officer must keep a good website" etc etc