Marking Job Card re-issuance in bulk instead of ten at a time

Some work is difficult. Other work is just long. Marking Job Card re-issuance on the VBG-RAM-G portal is firmly the second kind: tick ten checkboxes, click Update, click OK on the confirmation, wait for the page to come back, and do it again. And again. Across every village, in every panchayat.

Nothing about it requires judgement. It requires a person to sit there for hours doing something a script can do.

Why it takes so long

The portal shows records in pages of ten with a checkbox each. Marking a batch means selecting them, submitting, confirming a dialog, and waiting for a full page reload before the next batch appears. Then you finish a village and start the next one, finish a panchayat and start the next one.

The arithmetic is the whole problem. A block with a few thousand records is hundreds of rounds of the same four actions. It is the kind of task where you lose your place, double-handle a village, or miss one entirely — not through carelessness, but because keeping count across hundreds of identical screens is not something people are good at.

What the script does

It is a browser console script. For each panchayat you choose, it works through the list on its own:

1. Opens each village in turn.
2. Ticks all the checkboxes on the page.
3. Clicks Update and waits for the portal's own confirmation — the "Valid Record(s) updated successfully !!" message.
4. Moves to the next batch of records.
5. Repeats until that village has nothing left, then checks it again to be sure.
6. Moves to the next village, then the next panchayat.

At the end it reports how many records were marked and how long it took.

Two details are worth pulling out, because they are the difference between a script that works and one that quietly loses data.

It waits for the portal, not for a timer. The script watches for the actual success message before continuing. A fixed delay would be either too slow or — much worse — too fast, submitting the next batch before the last one committed and silently skipping records.

It re-checks each village. After a village reports empty, it goes back through once more. On a paginated form where submitting reshuffles what is on screen, "the page is empty" is not quite the same as "there is nothing left", and the second pass catches the difference.

What you need

• Google Chrome on a computer. Not a phone.
• Your portal login. The script drives the session you are already signed into; it never sees or stores credentials.
• To be in India — the portal blocks connections from other countries.
• Thirty to sixty minutes, depending on how many records you have.

There is a step-by-step illustrated guide, written for people who have never opened developer tools. That was deliberate: the users who need this most are block-level operators, not developers, and "paste this into the console" is not self-explanatory if you have never seen a console.

Limitations worth knowing

• It automates clicking, and nothing more. Every action is one you could perform by hand, through the same interface, with the same permissions. It does not touch an API or bypass any check.
• Leave the tab alone while it runs. It drives the live page, so navigating away or closing the tab stops it mid-run.
• No resume yet. If it is interrupted you restart the panchayat. Records already marked stay marked, so a restart is safe — just not fast.
• The portal can change under it. It depends on the page's current structure. A redesign on the portal side will break it, and it will need updating.
• Check the summary. It reports its count for a reason. Confirm the number matches what you expected before signing off.

On automating government portals

Worth stating plainly, because the question is fair: this does nothing you are not authorised to do. It signs in as you, clicks what you would click, and marks what you would mark. The only thing it removes is the requirement that a human be the one moving the mouse several thousand times.

The portal is built as though every record will be handled individually by a person with unlimited patience. Since it offers no bulk action of its own, the automation lives in the browser instead. That is a workaround for a missing feature, not a way around a control.

Job Card Re-issuance Auto Processor on GitHub · Step-by-step guide