When to Say No to a Department's AI Request

A joint secretary asked, in a pleasant voice, whether the model could auto-reject scholarship applications that looked weak so the staff could focus on the deserving. The room waited for the vendor to be helpful. The helpful answer was no.

Indian departments are under real pressure: vacancies, transfer season, monsoon, election duty, a minister who saw a demo. Pressure is not a lawful basis. It is not a safety case. It is not a reason to let a probabilistic system close a citizen's file.

This is an opinionated field list from a vendor that intends to stay in this market. Prcept AI will lose some rooms by using it. We would rather lose the room than sign a statement of work that we cannot defend to a CIC bench, a CVC inquiry, or a plant safety officer.

Refusals that are not rude — they are the product

Saying no is not a brand pose. It is how you avoid becoming the named contractor in a vigilance file. Departments remember the vendor who let them launch. They also remember the vendor who was on the letterhead when the launch went badly.

Write your refusals into the first meeting note, not into a private Slack. If the department still wants the work after the refusal, you have a serious buyer. If they want you to be flexible on the ethics annex, you have a brochure buyer.

The no-list we actually use

• Any workflow that issues or refuses a benefit, licence, admission, transfer, or penalty without a named officer's accept in the system of record.
• Any write path into OT — PLC, DCS, SCADA, historian set-points, relay settings. Draft on an IT copy. Never write back.
• Any request to paste, store, or embed Aadhaar numbers, biometrics, or eKYC XML in the model path.
• Any predictive targeting of citizens for enforcement or welfare that has no statutory scheme and no human order.
• Any demand to train on another department's live corpus because we are all government.
• Any hosted demo on real applications, real patients, real vendors, or real students.
• Any request to keep the human gate on WhatsApp or a personal mail ID.
• Any request to go live before a departmental AI register row exists.
• Any request to mark the vendor as the fiduciary so the department can stay agile.
• Any L1-only buy where isolation, gates and exit were never scored — we will not help you theatre a specification around our brand either.

The slow yes is also a no to the original ask

Many requests can be rewritten. Auto-reject becomes a draft note for the officer. Plant optimisation becomes a shift-handover draft from a one-way copy. Aadhaar login becomes the existing AUA widget plus a file number. A state-wide brain becomes two reconstructable workflows.

If the department refuses the rewrite, you are not in a scoping fight. You are in a values fight. Leave.

Document the rewrite in the minutes. The original dangerous sentence will otherwise reappear in the sanction as if you had agreed to it.

How to say it in the room without a sermon

Name the harm in one sentence. Name the paper that already forbids or warns — DPDP purpose, UIDAI rules, a charter, a plant standing order, CVC's ordinary fairness expectations. Name the rewrite. Then stop talking.

Do not invent a circular. If you have not found a CVC AI circular, do not cite one. Ordinary vigilance and ordinary law are enough.

Do not hide behind our legal will get back. If your legal is not in the room, you are not ready to sell to government.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note.

If we say no they will buy a hosted chatbot

They might. That is not a reason to put your company on the speaking order. Losing a bad deal is cheaper than explaining it to vigilance.

The department signed an indemnity

Indemnities do not bind citizens, CAG, or a court. They also age badly when the signatory transfers. Do not hide a bad workflow behind a clause.

It is only a pilot

Pilots on live rights are productions with a smaller audience. Sandbox or refuse.

Every other vendor said yes

Then you are not in a feature race. You are in a due-diligence race. Let the others be first on the para.

A four-week habit of useful refusal

1. Week 1: write your no-list on one page. Get counsel to strike anything you cannot defend. Share it with every salesperson.
2. Week 2: add a rewrite column. Every no should have a slower yes where one exists. Practise saying both in one breath.
3. Week 3: review the last five government conversations. Mark any sentence you should have refused. Send a clarifying mail now if the file still assumes yes.
4. Week 4: put the no-list in the proposal template as out of scope unless rewritten. If a department deletes the page, walk.

How this shows up in the file

Subject: Use cases this organisation will not implement as requested.

We will not implement agent workflows that decide citizen or employee rights without a competent officer in the system of record; that write to operational-technology networks; that store Aadhaar or biometrics in model logs; or that treat a pilot on live personal data as a sandbox. Where a safer rewrite exists, it is offered in annex.

Absence of a specialised circular does not create permission. This note is a commercial boundary. It is not legal advice to the department.

What founders owe their own staff

A salesperson who is punished for a refused bad deal will stop refusing. Put the no-list in the commission plan. A solutions engineer who is asked to enable Aadhaar logging at 11 p.m. needs a written right to halt the sprint. If only the founder can say no, the founder will be in every room, and will eventually say yes from tiredness.

Ministries are not the only askers. Campuses will want to grade from a hosted model. PSUs will want OT write-back. Districts will want a bot that denies certificates after hours. The no-list is the same list with different nouns. Practise the nouns.

Prcept AI publishes this list because we will be measured against it. If we breach it, you should compete us with the packet, not with a louder brand. The officer who has to sign the speaking order deserves a vendor that has already refused the easy version of the work.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation, engineering or board advice. Confirm against the live Gazette, GFR, GeM term, CVC instruction, CERT-In direction, UIDAI regulation, DPE guideline, DPDP text, departmental charter, plant safety manual and your counsel before you file it.

How to sequence this in a state, not a slide

“When to Say No to a Department's AI Request” is a department problem. A P5 GovTech Founder should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “government AI bad use case”.

The bravest line in a GovTech meeting is no. Not every departmental request is a use case. Some are rights violations with a chatbot skin. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “When to Say No to a Department's AI Request” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P5 GovTech Founder, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “government AI bad use case” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What the next file must contain

“When to Say No to a Department's AI Request” earns a line in the noting only if a P5 GovTech Founder can attach proof of “government AI bad use case.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “government AI bad use case.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.