Skip to content
Sunbeam
Open menu

Technology for Government and public sector

A public team should be able to say what happened to a request, and show its work.

Direct answer

Public-sector software is ordinary workflow software with stricter rules around who may see a record, where it is hosted, and how a citizen or applicant is answered. Sunbeam builds focused request tracking, document intake and information sites when a department or public body is allowed to commission that work. We do not claim empanelment, a GeM listing, or a government award.

Where the work breaks

The problems we expect to hear.

Requests are tracked in a register and an inbox

A citizen, a vendor or an internal colleague submits something, and the status lives in a physical register, a spreadsheet, or the mailbox of the person who happened to receive it. Asking 'what happened to my application' requires a search.

Public information is hard to correct

Scheme details, eligibility and office hours change, and the website waits on a vendor for every sentence. People then call the office to check a page the office does not control. The call volume is a content problem.

Approvals stall because the file has no visible state

Work moves between desks, and the only status is whoever last held the paper or the email. A due date exists in a circular and not on the item. Reporting upward becomes a monthly exercise in reconstruction.

Applicants resubmit because nothing acknowledged them

Vendors, consultants and citizens send documents and hear nothing, so they send them again. Staff then have two versions and no checklist of what was complete. The delay is partly courtesy and partly the absence of a reference number.

What we would build

A first system sized to the actual work.

  1. 01

    A request with a reference and a status

    Intake gives a reference number, an owner, and a status the desk can update. What the applicant is allowed to see is decided explicitly. This is a focused tracker, not a claim to replace a state's existing e-office suite.

  2. 02

    Public pages a team can update

    Eligibility, documents required, office information and announcements in the languages the audience needs, often English and Hindi. Corrections should not wait on a developer. Accessibility is part of the page, because the audience is the public.

  3. 03

    Document intake with a checklist

    An applicant submits against a list, sees what is still missing, and receives an acknowledgement. Reviewers see the same checklist. Versions are kept so a resubmission does not erase the previous file.

  4. 04

    A reporting view that comes from the work

    Open, overdue, closed, by office or category. The monthly report is a view of the tracker, not a fresh spreadsheet. Hosting, access and audit expectations are settled in discovery, including any requirement to keep data in India.

How the system has to behave

Practical constraints, decided before the build.

  • Hosting and access decisions made before build, including any data-residency rule
  • Pages that work without a mouse and without assuming a fast connection
  • Language and document needs treated as requirements, not as a later translation pass

Answers that sit behind this work

FAQ

Questions from Government and public sector teams.

Do you build software for government departments?

We build focused public and internal systems — request tracking, document intake, information sites — where the organisation is able to commission that work. Procurement route, hosting and security expectations are part of the first conversation.

Are you empaneled, or listed on GeM?

We do not claim empanelment, a GeM listing, or a government contract we have not signed. If a procurement path requires a specific registration, that has to be true before anyone relies on it.

Can citizens track a request?

When the organisation wants them to. A reference number and a short status are usually enough. Internal notes stay internal.

Where would the system be hosted?

Wherever the organisation's rules require, agreed before development. If data must stay in India, or on a specified government cloud, that constraint shapes the design. We do not pick a convenient foreign default and relocate it later.

Not every operational issue needs custom software. See when Sunbeam is not the right fit, compare practical options in our decision guides, or .