Source-grounded framing
Startup Haryana sits within the Industries & Commerce portfolio and already exposes a public registration workflow with defined eligibility, document uploads, fees, and service timing.
Standalone workflow site
A source-grounded officer workflow built directly on the public Startup Haryana registration service. This site remains the operational reference build inside the Haryana Department Workflow AI Copilot suite.
Public portfolio context
Amit Kumar Agrawal, IAS
This workflow sits inside the Industries & Commerce portfolio and stays within one published departmental application flow.
₹0
Registration fee on Startup Haryana
30 days
Published registration timeline
10 days
Published deficiency-removal window
Why this site
The workflow begins with public requirements, not with AI. That keeps the review path legible to both officers and governance reviewers.
Startup Haryana sits within the Industries & Commerce portfolio and already exposes a public registration workflow with defined eligibility, document uploads, fees, and service timing.
The stronger scale-up story is not a new platform. It is a workflow review layer that can later align with the Invest Haryana / HEPC single-window programme.
Recommended path
This standalone site remains the reference build because it follows the public Startup Haryana application structure exactly, including the upload groups and public document list.
The Invest Haryana / HEPC bridge remains a later service-template expansion, not a shared-data architecture claim.
Separate peer sites
Where the AI sits
This makes the explanation simple: public requirements first, packet mapping second, AI draft third, human approval last.
The workflow begins with the exact public Startup Haryana rule set: eligibility conditions, service timing, and the published document list.
The application packet is mapped against those public document groups: entity records, authorized representative records, director / partner records, Annexure-linked documents, and the DPR.
The AI sits after intake and before any officer action. Its role is limited to classifying documents, drafting deficiency notes, and preparing an editable officer summary for the current workflow only.
No AI output is final. The officer reviews the checklist state, edits the note if needed, and then decides whether to return, hold, or move the case forward.
Across the suite
These remain separate sites so the data boundary stays departmental and the operating context stays clear.
Standalone peer site
A public-release-pack briefing workflow built from PRMS listing pages and public release detail pages.
This is a separate deployable site, not a hidden second module inside Startup Haryana.
Standalone peer site
A PMU review workflow derived from the public Tourism TOR for PMIS, dashboards, digital roadmap, and reporting.
This is a separate deployable site with its own simulated review pack and governance page.
Next route
Open the guided Startup Haryana workflow