The blocker was the statute, so the statute changed first
Everyone saw this as an IT upgrade. The real blocker was the law: the Act did not recognise electronic notices or digital signatures. So we got the Act amended first, then built the platform on top of it.
- Client
- Ministry of CooperationCentral Registrar of Cooperative Societies
- Role
- Senior ConsultantEY India
- Team
- Ministry team and a selected software vendor
- Timeline
- 2022 to 2024Rolled out module by module
The challenge
The Central Registrar of Cooperative Societies, under the Ministry of Cooperation, keeps the country's record of multi-state cooperative societies: about 1,800 societies and some 40 million members. Almost everything ran on paper, in a physical office.
It looked like an IT upgrade. It was not. The Multi-State Cooperative Societies Act recognised neither electronic notices nor signatures that were not physical, so a digital process had no legal standing, however well it was built.
What was done
1. Change the law before building the software.
Discovery found that the blocker was the Act, not the technology. Amendments were proposed so that electronic notices and digital signatures were valid, and they were tabled and passed in about six months. That put the project's critical path through a process nobody on the team controlled. Building something narrower inside the old Act would have been faster, but it would not have been the process the ministry needed.
2. Build accountability into the new process.
A digitised paper process can stall as quietly as the paper one. The new process gave each officer a role and escalated automatically at 5, 7 and 15 days, so delays became visible without anyone chasing.
3. Write the specification, then hold the vendor to it.
The DPR and the RFP were written first. Then delivery was overseen from the ministry's side: keeping the vendor to scope, handling deviations and escalating. The person judging a deviation was the person who had written what was asked for.
My role
What I owned
Discovery and process re-engineering, the case for amending the Act, and authorship of the DPR and RFP, then ministry-side oversight of delivery.
What the team delivered
The selected vendor's design, build and rollout, module by module.
What the client decided
The Ministry decided to pursue the amendments, and they were enacted through the legislative process. It approved each rollout stage.
The result
The paper office became a live platform, rolled out module by module. It now holds the national record of multi-state cooperative societies, with about 40 million members, and application processing is more than 70% faster. It also holds the Sahara credit cooperative society data used for refund validation.
The lesson
The most useful result of discovery is an honest answer to what cannot move. Here it was a law. Treating it as something to change, not something to work around, made the project possible.
View the numbers as a table
| Process | Time |
|---|---|
| Paper | 15 to 20 days |
| Digital platform | about 4 days (under 100 hours) |
Read the detailsThe legal blocker, decisions with their costs, delivery and the numbers
A national registry, on paper
The Central Registrar of Cooperative Societies, under the Ministry of Cooperation, holds the country's record of multi-state cooperative societies: around 1,800 societies and some 40 million members. The process was largely paper-based.
The blocker was the statute, not the software
The easy reading was a technology-modernisation problem. It was not. The MSCS Act recognised neither electronic notice nor a signature that was not physical, so the intended digital workflow had no legal standing however well it was built.
A platform delivered on that foundation would have been a platform nobody could lawfully use. Discovering this during delivery rather than during discovery would have cost the programme.
From discovery to ministry-side oversight
I supported the transformation from process discovery and DPR and RFP authorship through to ministry-side delivery oversight, including vendor scope discipline, deviation management and escalation. My role was Senior Consultant.
Two calls, each with its cost
Decision 1. Change the constraint, not just the software.
WhyIf the statute does not recognise electronic notice, no amount of product work substitutes. I proposed amendments to the MSCS Act so the intended digital workflow could operate inside a proper legal framework. They were tabled and enacted in about six months.
Trade-off acceptedIt put the programme's critical path through a legislative process nobody on the delivery team controlled. Building something narrower inside the old Act would have shipped sooner, but it was not the workflow that was needed.
- Discovery finds the blockera statute, not a system
- Propose amendmentselectronic notice, non-physical signature
- Tabled and enactedin about six months
- Platform builton a lawful footing
Decision 2. Build accountability into the new workflow instead of copying the paper one.
WhyA digitised paper process inherits the paper process's ability to stall silently. The redesigned process introduced role-based access for each officer and automatic escalation at five, seven and fifteen days, so delay became visible by default rather than on request.
Trade-off acceptedAutomatic escalation puts pressure on officers who may be waiting on something outside their control, so it had to be tuned rather than simply switched on. It replaced chasing with a system.
Writing the specification, then holding delivery to it
I wrote the DPR and the RFP, then worked on the ministry side of my own specification: vendor scope discipline, deviation management and escalation. That is an unusual and useful position. The person judging whether a deviation is acceptable is the person who wrote what was asked for.
A paper office became a live platform
The platform now holds the country's multi-state society record, including the Sahara credit cooperative society data used for refund validation.
Ask what cannot move
The most valuable thing discovery produces is an honest answer to what actually cannot move. Here it was a statute, and treating it as a requirement rather than a constraint is what made the programme possible.
Writing the specification and then governing against it is worth seeking out. It removes the gap between what was meant and what was asked for.