01
For citizens
Find published steps, required documents, opening hours and contacts faster, then follow the institution's official channels.
ROCSI AI Assistant / public institutions and services
Inviting public institutions to explore a pilot
Public information, easier to find. Institutional authority stays clear.
People want to know how a procedure works, the conditions of a service or which documents are required. A website AI assistant could guide visitors through information approved and published by the institution, without inventing requirements or issuing official interpretations.
The public demo uses ROCSI content, not official institutional information or individual case records.
The working ROCSI public beta answers from approved ROCSI information, not from institutional records. A public-sector pilot requires its own corpus, access policies, clearly assigned responsibilities and evaluation. No existing operational integration is implied.
ROCSI / AI
A citizen asks
Which documents do I need for this request, and where can I check submission hours?
Expected responsible behavior
The assistant summarizes only the documents and opening hours present in the institution's approved instructions and points to the relevant official page or office. If the procedure is not sufficiently documented, it says it cannot confirm. It cannot establish eligibility or submit requests on the institution's behalf.
Fictional example; not official guidance, confirmation of required documents or the submission of a request.
01 / Public value
From scattered pages to verifiable guidance.
Opening hours, procedures, forms and requirements may be distributed across many pages. A conversational tool can improve access while respecting the authority and limits of each source.
02
For institutional staff
A pilot can reveal repetitive questions and unclear pages without replacing public-facing employees or official interactions.
03
For decision-makers
Assess information control, answer quality and costs before scaling, without promising automatic savings or outcomes.
02 / Authority and trust
Information guidance, not an administrative decision.
The assistant should use approved material, acknowledge missing evidence and avoid inventing deadlines, fees, eligibility conditions or exceptions. Hallucination risk reduction requires ongoing validation and is not an absolute guarantee.
- Answers are informational and cannot constitute official acts, legal interpretations, approvals, certificates or administrative decisions.
- The assistant cannot submit applications, issue filing numbers or confirm individual cases without a separate authorized official workflow.
- Deadlines, fees, forms and procedures change; corpus freshness must be checked after updates.
- Internal documents approved for processing are not automatically public; user isolation and role-based disclosure require separate validation.
- Personal data, case files, identity and citizen entitlements are not collected or accessed implicitly in a public chat.
03 / How a pilot could work
Approved information, explicit boundaries, institutional escalation.
Start with selected public pages and documents, not access to internal registries, case files or official submission workflows.
- 01 / 04
Map the questions
Select procedures and services that commonly generate requests for clarification.
- 02 / 04
Approve the sources
The institution validates pages, document versions and permitted disclosure.
- 03 / 04
Guide the visitor
The assistant explains published steps and points to the relevant official pages and contacts.
- 04 / 04
Acknowledge limits
Individual or unsupported questions go back to official channels.
04 / Available vs. under development
An information assistant, not a digital public-service desk.
What the ROCSI beta demonstrates
- Romanian and English website chat using approved public ROCSI information.
- Scope-bound responses and acknowledgement of unsupported requests.
- A website-integrated experience under continued evaluation.
What an information-only pilot does not include
- It does not automatically submit applications to institutions or replace official forms or procedures.
- It does not inspect files, verify identity, eligibility, payments or statuses in internal registries.
- It does not issue legally binding decisions, permits or confirmations.
- It does not give public access to internal documents or citizen records.
- It does not promise administrative-system integrations without separate design and authorization.
05 / Pilot journey
A measurable framework with clear responsibilities.
Together we decide which sources can be used and how answers are evaluated. No fixed cost, instant delivery or automated decisions are promised.
- 01 / 05
Institutional discussion
Define services, citizen questions, responsibilities and constraints.
- 02 / 05
Corpus approval
Inventory and explicitly approve pages, forms and access boundaries.
- 03 / 05
Configuration
Set scope, interface and escalation to official contact channels.
- 04 / 05
Validation
Test correctness, changed information, unsupported requests and mobile UX.
- 05 / 05
Evaluation
Assess usefulness, risk and cost before any wider adoption.
06 / Frequently asked questions
What can a public-sector pilot do?
- Can it explain which documents a procedure requires?
- That is a possible pilot use case using approved pages and forms. If the evidence is insufficient, the assistant should say so and refer the user to the institution.
- Can it submit requests or confirm eligibility?
- No. The beta does not submit forms, issue filing receipts or decisions, or establish individual legal eligibility. These remain the responsibility of the institution and its official channels.
- Can it use internal documents or citizen data?
- Not by default. Approved-for-processing information is not automatically public. Restricted material would require separate authorization, authentication and access controls, developed and validated independently.
- What happens when a procedure changes?
- The institution validates the new source, and the approved corpus must be checked for freshness and reindexed as necessary. We do not promise automatic sync with every registry or website.
- How is this different from the municipality pilot?
- This page addresses public institutions and services broadly; the municipality page presents a specific municipal pilot scenario.
- What is the timeline or cost?
- No standard duration or fee is promised. Scope, security, corpus and evaluation criteria must be agreed before estimation.
Invitation / public institutions and services
More accessible information without blurring institutional responsibility.
We invite interested public bodies to explore an information-guidance pilot built around approved sources and explicit disclosure boundaries.
In the message, mention 'ROCSI AI Assistant public institutions pilot' and your institution's website.
Exploratory invitation only, not a binding offer or an official citizen-service channel.