How a public utility's website differs from a company site
A company website sells; a public utility's website informs and serves. Citizens come to find a price list, opening hours, an outage notice, a form or an account number, and expect it to work on an old phone, a weak connection, without cookies or registration. So such a site is built by different rules: obligations first, looks second.
We have done it twice for the same company. The site of JKP Bukulja from Aranđelovac (Next.js and Payload CMS) is edited by the company's own team, without a developer. It was followed by the CemetOS cemetery administration and the public “Moje groblje” portal for the Risovača cemetery, where citizens find a grave, funerals and obituaries and pay the lease. This checklist comes from those two projects.
Mandatory content: information booklet, decisions, price lists
Public companies in Serbia fall under the Law on Free Access to Information of Public Importance, so the site must have an information booklet and keep it current. Alongside it go the founding act and statute, decisions and service price lists, procurement and annual plans, competitions and business reports, a complaints contact and a data protection officer.
Practical advice: those documents should not be PDFs buried under “Documents”, but pages with a title, date and version, so both Google and the citizen can find them. A price list as a table on the page, with the PDF as an attachment, not the other way round.
| Item | Why | How we do it |
|---|---|---|
| Information booklet and documents | legal obligation, citizens look for them | pages with date and version, PDF as attachment |
| Cyrillic and Latin | official script and citizens' habit | one content, script switch, English where needed |
| Accessibility (WCAG 2.1 AA) | screen readers, low vision, keyboard | contrast, alt text, forms, works without JavaScript |
| Publishing without a developer | otherwise the site goes stale in a year | editorial system with preview before publishing |
| Citizen portal | fewer counters, payment from home | data from administration, publicly only what is allowed, IPS QR |
| Maintenance and backup | public data, availability | monitoring, daily backup, updates |
Case study: Moje groblje and CemetOS
Cyrillic, Latin and English
Cyrillic is the official script and a public company's site should exist in Cyrillic; in practice citizens also want Latin, and tourist towns want English. The answer is not three sites but one content with a script switch, where Cyrillic and Latin are generated from the same text and English translates only what a foreigner needs.
On the “Moje groblje” portal the search works in both Cyrillic and Latin, with or without diacritics, because the old register was entered half in one script and half in the other. That is not a detail: half the citizens would not find their relatives' grave if the search worked in one script only.
Accessibility and working without JavaScript
Accessibility means the site works for people with weaker eyesight, on a screen reader and with a keyboard alone. The standard is WCAG 2.1 at level AA: contrast, font size, image descriptions, labelled forms, headings in order. For the public sector it is also an obligation under European rules Serbia is adopting, but above all it is about whom the site serves.
We go one step further: public pages work without JavaScript. Search, obituaries, directions to the grave and the lessee profile on the “Moje groblje” portal work on the oldest phone and the weakest connection, and what needs scripts, such as maps or payment by IPS QR code, comes as an extra, not a condition.
Publishing without a developer and a citizen portal
The most common reason public utility sites go stale: every post needs “the person who knows”. That is why the JKP Bukulja site has an editorial system where the team itself publishes news, outages, price lists and documents, with a preview before publishing; one hundred percent of the content since launch has been published by the company alone.
A citizen portal is the next step: instead of a counter, the citizen finds their case on the site and pays. On the “Moje groblje” portal a lessee sees the balance and pays by IPS QR code from a banking app, and personal data is never shown publicly. The same principle applies to water bills, leases or parking: data from the administration, publicly only what is allowed.
Procurement: how it is ordered and how long it takes
Procurement follows the Public Procurement Law. Smaller purchases, roughly under one million dinars for services, a company may contract without a procedure on the Public Procurement Portal by collecting offers; larger ones go through the portal, usually as an open procedure with CPV code 72413000 (website development services). The specification should ask for concrete things: an editorial system, Cyrillic and Latin, accessibility, migration of old content, training and maintenance.
A realistic timeline for a public utility's site with an editorial system is six to ten weeks from signing, including content migration and team training. A citizen portal with data from the administration is a separate project that depends on the state of the records: at the Risovača cemetery, rebuilding the old register from the ledger, cards and the old system was a bigger job than the portal itself.