Single Window Clearance: Agent-Assisted Review

The investor's consultant sat in the facilitation cell with a printed deficiency list eleven pages long. Five items had already been uploaded. Three items cited a circular that had been superseded in 2024. Two items belonged to a department that no longer existed after the last reorganisation. The single-window portal still showed 'under process' in a cheerful blue. Nobody could say which officer owed the next note.

A vendor then offered an agent that would 'approve non-critical clearances automatically'. The room liked the sentence. The law did not. Single-window is a coordination problem dressed as a portal. The statutes still live in labour, pollution, fire, factories, and the municipal building code. An agent that stamps those statutes is not helpful. It is a defendant.

This case study is a field guide for state CIOs and investment-promotion cells. It is written on 17 August 2026. It is not legal advice and it does not invent a model act. If your state has a single-window statute, read that text. If it has only an executive order and a portal, read those. The method below still holds: assemble, flag, draft, and leave the clearance with the officer the instrument names.

What the clock actually starts on

Every single-window brochure talks about a clock. Few files show when the clock started. A complete application is a legal object. A zip of half-scanned PDFs is not. The first job of an agent is to test completeness against the checklist that was in force on the filing date, not against a salesperson's memory of last year's workshop.

Write the completeness object as something you can export. Application identifier. Checklist version. Each annexure: present or missing, hash if present, page count, and whether the extractor could read the critical field. If the pollution consent form is present but the plot coordinates are blank, that is not 'uploaded'. The agent should say so in a sentence a joint secretary can read.

Deemed approval, where a state law provides it, is not a software feature. It is a consequence of a complete file sitting untouched for a notified period. If you let the agent start the clock on an incomplete file, you have manufactured a clearance the statute never granted. If you let the agent stop the clock by inventing a deficiency, you have manufactured a delay. Both errors are visible in court.

Line departments are still the law

Single-window cells fail when they pretend to be a super-department. They succeed when they become a disciplined clerk for many departments. The agent should know, for each clearance type, which instrument governs, which officer is competent, what the published timeline is, and where the latest circular lives. It should not invent a merged permission called 'AI composite NOC'.

• Map each clearance to its parent instrument. If you cannot name the Act, the G.O. or the municipal bye-law, you cannot automate the review.
• Retrieve the circular that is in force, with date and hash. Stale checklists are how investors are asked for abolished forms.
• Keep purpose tags narrow: completeness, circular retrieval, noting draft. Never a purpose tag called 'decide'.
• Do not send application packets to a public model API. They contain personal data, sometimes land records, sometimes process diagrams a factory would not put on the internet.

What an agent-assisted single window can honestly claim.

Claim in the steering note	Honest product	Dishonest product
Faster clearance	Faster complete files and faster deficiency memos	Auto-stamp after N days on any upload
One window	One assembly point with named line-department owners	A portal that hides who must sign
AI approved	Officer approved a draft the agent prepared	The model issued a PDF with a state emblem
Integrated with departments	Connectors plus purpose tags, or retrieved PDFs	Invented APIs and silent screen-scrapes
Investor transparency	A status the investor can read, with the live deficiency	A blue spinner and a ticket number

Two rooms after the same cabinet note

Objections you will hear — and what to do with them

Investors will leave if an officer still signs

Investors leave because clocks start on incomplete files, because deficiency lists cite dead circulars, and because nobody can say who is sitting on the note. Fix those three. A signature that exists in law will still exist after you buy a model. Selling them a forged stamp is how they leave and sue.

Our single-window Act already allows deemed approval

Then implement the Act, not a timer. Show the completeness object. Show when the clock started. Show that no valid deficiency was pending. If the Act excludes certain clearances from deemed approval, exclude them in software. An Act is not a mood.

We need APIs into every department before we start

You need the checklist and the circular. Many line departments will give you a PDF and a competent officer long before they give you a stable API. Describe the integration as a connector and a purpose tag. Do not invent an API in the RFP that the labour department has not published. That is how SI bids become science fiction.

GIGW does not apply to a back-office agent

If the investor or the citizen sees a status page or a chat, GIGW 3.0 is in the conversation — accessibility, quality, and the cybersecurity chapter CERT-In contributed. The companion piece on GIGW for AI-powered interfaces is the longer map. Do not ship an unlabelled bot on a .gov.in domain and call it innovation.

A four-week playbook for one clearance type

1. Week 1: pick one high-volume clearance, not all forty-one. File the parent instrument, the live checklist, and the competent post. If two officers disagree on the checklist, stop and settle that on paper.
2. Week 2: build the completeness object on fifty historical applications. Count how many were treated as complete when they were not. That number is your baseline, not the vendor's demo.
3. Week 3: put draft deficiency memos in front of the real officer. Measure edits. If the officer rewrites every memo, the checklist in the agent is wrong.
4. Week 4: write the standing order — the agent shall not generate a clearance letter, shall not start a deemed-approval clock except on a complete object, and shall not call a public model with the packet. Then, and only then, add a second clearance type.

File note you can paste

Subject: Agent-assisted review on the single-window portal — completeness and drafts only.

The agent authorised under this note shall test applications against the checklist in force on the filing date, retrieve the current circular for the relevant line department, and draft deficiency memos and noting skeletons. It shall not issue, stamp, or deem a clearance. A deemed-approval clock, where the governing instrument provides one, shall start only on a complete application object stored in the department system. Application packets shall not be sent to public model APIs. Connectors to other systems will be described by purpose tag; this note does not invent an API that a line department has not provided.

This note is an internal aid. It is not legal advice.

What we will put on the desk

Prcept AI will run the completeness clerk on your side of the perimeter. We will not print a state emblem on a model output. We will not train on investor packets. If your single-window law is stricter than this note, we will follow the law. If a competitor offers a button that 'clears MSME cases automatically', ask them which section of which Act they propose to repeal by CSS.

Deficiency memos that do not invent law

A bad agent writes a deficiency that sounds official and cites nothing. A worse agent cites a circular that died two years ago. The test is simple. Every bullet on the memo must carry a checklist line number and a live circular hash. If the extractor is unsure, the bullet is a question to the officer, not a demand to the investor. Invented deficiencies are how single-window cells become famous for harassment.

Keep a refused-phrase list. The agent may not say 'as per norms', 'etc.', or 'any other document the department may require'. Those phrases are how completeness becomes infinite and how the clock never starts. If the checklist is genuinely incomplete, fix the checklist in a dated revision. Do not ask the model to paper the hole with atmosphere.

When a line department disputes a checklist item, stop the agent on that clearance type until the paper is settled. Scaling a disputed checklist to thirty files is how you industrialise a feud. The facilitation cell's job is to surface the feud early, not to hide it in a confident paragraph.

This article is informational field guidance for Indian public institutions, not legal, investment-promotion or procurement advice. Confirm against your state's single-window statute or G.O., line-department instruments, DPDP, GIGW 3.0, and counsel before you file it.