Digital Parliament & Councils — Sessions, Voting, Minutes and Member Portals

We are Neruos, a  software company building the technology behind modern businesses. From custom software and web platforms to cloud infrastructure and AI solutions, we help organizations innovate, automate operations, and scale with confidence!

   DIGITAL PARLIAMENT & COUNCILS

Digital Systems For
Parliaments And Councils.

NERUOS builds digital parliament and council systems: sessions and agendas, attendance and voting, minutes and decisions, legislation and committee tracking, and a secure portal for members and staff, in one platform. It is built for parliaments, legislative councils, municipal and regional councils, and the boards, committees and secretariats of public institutions in Saudi Arabia and the GCC that still run session work across paper files, email and disconnected tools.

The platform is deployed where your institution requires it, on-premise in your own data centre or on KSA-hosted cloud, so session records, draft legislation and member data stay inside the country. It is built Arabic-first for official documents, minutes and search, with role-based access for members, secretariat and staff, and a full audit trail behind every agenda item, vote and decision. Where AI is used, it drafts and proposes; the secretariat reviews and approves before anything becomes official.

The Systems That Run A Session Cycle.

A session is a chain of work: the agenda is prepared, papers are circulated, members attend, items are debated and voted on, decisions are recorded, and the follow-up is tracked to the next sitting. NERUOS builds that chain as one connected system, configured around your standing orders and internal rules rather than a fixed template.

Session & Agenda Management

Session calendar, agenda preparation and approval, item submission from departments and committees, supporting papers, circulation to members before the sitting, and a versioned record of what was tabled and when.

Voting & Attendance

Member attendance and quorum tracking, motions put to the vote, open or recorded voting captured per member or in aggregate as your rules allow, abstentions and absences, and a permanent voting record tied to its item.

Minutes & Decisions

Minutes drafted, reviewed and approved through a defined workflow, resolutions recorded against their agenda items, assignments and deadlines issued to the responsible party, and a searchable archive of every sitting.

Member & Committee Portal

A secure portal where members open their agendas, papers and voting history, and where committees run their own sittings, documents and recommendations, with access controlled centrally by the secretariat.

Built Around How Councils Actually Work.

Legislative and council work has requirements that general-purpose meeting software does not meet: the official language of the record, the need to prove what was decided and by whom, the separation between members, secretariat and staff, and where the data is allowed to live.

Arabic-First Documents And Search

Arabic is the working language of the record, not a translation layer. Agendas, papers, minutes, resolutions and correspondence are authored, stored and searched in Arabic with right-to-left screens and Arabic document output, with English alongside where your institution needs it.

A Full Audit Trail Of Every Decision

Every agenda change, document version, attendance entry, vote and approval is recorded with the user, the role and the timestamp, so the archive answers what was decided, when, on what basis and who approved it.

Role-Based Access For Members And Staff

Members, committee chairs, the secretariat, legal and technical staff and, where applicable, the public each see a defined view. Confidential items and closed sessions stay restricted while open items proceed normally.

Deployed Inside The Institution

The platform runs on-premise in your own data centre or on KSA-hosted cloud, so session records, draft legislation and member data stay in-country. Backups, logs and any AI models in use are placed under the same rule.

For Legislative And Deliberative Bodies.

The same core system serves any body that meets formally, deliberates, votes and must be able to prove its decisions afterwards, from a national legislature to a standing committee inside a public authority. Scope, roles and workflow are configured per institution.

AI That Drafts, While People Approve.

The capabilities below are delivered by NERUOS’s AI, Data & Intelligent Automation practice as scoped work on top of the platform, built against your own sessions, documents and archive. In every one of them the AI drafts, summarises or proposes: the secretariat reviews and approves every AI output before it is issued, published or recorded as official. Models run on-premise in your data centre or on KSA-hosted cloud, so session material is not sent outside the environments you approve.

Draft Minutes From Session Records

A first draft of the minutes produced from the session's recording, transcript and agenda, with items, interventions, motions and outcomes in order, which the secretariat edits, corrects and approves before it enters the official workflow.

Summaries Of Long Documents And Reports

Plain summaries and key-point extracts from long bills, committee reports, studies and correspondence, with links back to the source paragraphs, so members and staff can see what a document contains before reading it in full.

Arabic Document Search Across The Archive

Search that understands Arabic questions and returns the specific agenda item, minute, resolution or paper that answers them, across scanned and digital records, with Arabic OCR applied to the historical archive where needed.

Classification And Routing Of Correspondence

Incoming letters, petitions, requests and departmental submissions are classified, the key details extracted, and each item proposed to the right committee, department or officer, with a named member of staff confirming the routing.

Legislation Status And Deadline Tracking

Each bill, proposal or resolution is tracked through its stages, with pending readings, committee referrals, assignments and statutory or internal deadlines surfaced in advance, and alerts raised before a date is missed.

Decision Dashboards For Leadership

Attendance, session throughput, item and decision status, committee workload and follow-up completion in one view for the speaker, chair and secretary-general, with drill-down to the underlying session records.

How We Work

From Standing Orders To Live Sessions.

Discovery With The Secretariat

We work through your standing orders, session cycle, committee structure, document flow, roles and archive with the people who run them, and agree exactly what the first release must cover.

Requirements & Documentation

Functional and non-functional requirements, scope, roles, integration list and acceptance criteria written up in the form your procurement, tender and approval process needs.

Architecture & Security Design

Deployment model, network placement, identity and role model, access rules for confidential items, audit-trail design, backup and retention, reviewed with your IT and security teams before any build.

Build & Configure

The platform is built and configured around your rules: session types, agenda and minutes workflows, voting rules, committee structures, document templates, permissions and Arabic document output.

Pilot With One Committee

One committee or one full session cycle runs on the system in parallel with the current process, so the secretariat can compare the record, raise corrections and sign off before anything else moves.

Rollout, Training & Support

Staged rollout to remaining committees and members, role-based training for members, secretariat and technical staff, documentation handed over, then SLA-based support and maintenance.

One Solution, Three NERUOS Practices.

A digital parliament program is built by the same teams that deliver NERUOS services: the AI practice, the digital platform team and the infrastructure and security team, working to one plan. It is part of our wider AI & Digital Government work for ministries, municipalities, parliaments and public authorities.

AI, Data & Intelligent Automation

Draft minutes, document summarisation, Arabic search across the archive, correspondence classification and decision dashboards, built against your own records with the secretariat approving every output.

Digital Platforms & Connected Experiences

The member and committee portal, the secretariat workspace and any public-facing session or decision pages, designed Arabic-first and built for the roles that use them.

Cloud, Infrastructure & Cybersecurity

On-premise and KSA-cloud deployment, identity and access, hardening, audit logging, backup and retention for an environment that holds the institution's official record.

Questions Councils And Secretariats Ask First.

Answers on scope, on-premise deployment, Arabic minutes and search, voting records, access control, AI governance, integration, procurement documentation, pilots, cost and timelines.

What does a digital parliament or council system cover?
It covers the full session cycle in one platform: preparing and approving the agenda, submitting and circulating papers, recording attendance and quorum, putting motions to the vote and capturing the result, drafting and approving the minutes, recording decisions and the assignments that follow, tracking legislation and committee work, and giving members and staff a secure portal into all of it. The scope for your institution is set in discovery against your own standing orders.
The system covers:
sessions, agendas and papers
attendance, voting and minutes
decisions, legislation tracking and member portal
Can it run entirely on-premise?
Yes. The platform can be deployed entirely inside your own data centre, with no dependency on external cloud services, or on KSA-hosted cloud. Databases, document storage, backups, logs and any AI models in use sit under the same deployment decision, so the official record and member data stay in-country. The model is agreed with your IT and security teams during architecture design.
Deployment options:
on-premise in your own data centre
KSA-hosted cloud
same rule for backups, logs and AI models
Does it support Arabic, including Arabic minutes and Arabic search?
Yes, and Arabic is treated as the working language of the record rather than a translated layer. That covers right-to-left screens, Arabic agendas, papers, minutes, resolutions and correspondence, Arabic document output for the official record, and search across current and archived material, including Arabic OCR for scanned historical documents. English is provided alongside where your institution needs it.
Arabic scope:
right-to-left interface and documents
Arabic minutes, resolutions and reports
Arabic search and OCR across the archive
How are voting and attendance recorded and audited?
Attendance and quorum are recorded per sitting, and each motion is tied to the agenda item it belongs to, with the result captured per member or in aggregate according to your standing orders, including abstentions and absences. Every entry is written with the user, the role and the timestamp, and corrections are made as tracked amendments with their own trail.
How it is recorded:
attendance and quorum per sitting
results tied to the agenda item
user, role and timestamp on every entry
Who can see what: members, secretariat, staff and the public?
Access follows the institution own structure. The secretariat administers sessions, agendas and the minutes workflow; members see their agendas, papers, voting history and committee material; committee chairs see their own committee work; legal and technical staff get the access their role requires. Confidential items and closed sessions stay restricted, and any public view is configured separately and explicitly approved.
Access model:
role-based permissions per group
confidential and closed-session restrictions
public view only where explicitly approved
Does AI write the official minutes?
No. AI produces a draft; the secretariat produces the minutes. The system can generate a first draft from the session recording, transcript and agenda, but that draft goes into the normal review workflow where the secretariat edits, corrects and approves it. Nothing is recorded as official, issued to members or published without a named person approving it.
How AI is governed:
AI drafts, the secretariat approves
named approval before anything is official
models run on-premise or on KSA cloud
Can it integrate with our existing archive, identity and document systems?
Yes, as integration work delivered on your project rather than ready-made connectors. In discovery we assess your document management or e-archiving system, correspondence and case systems, the identity provider your members and staff sign in with, email and calendars, and any existing legislative or committee registers, then build and test the connections needed. Migration of historical sessions and documents is scoped the same way.
Integration work:
document management and e-archiving
identity, sign-in and directory services
correspondence systems and archive migration
Do you support the procurement and tender documentation?
Yes. Requirements and procurement documentation is a defined stage in how we deliver. We produce functional and non-functional requirements, scope and role definitions, the integration list, architecture and security design, and acceptance criteria, written in a form your procurement, tender, audit and IT governance processes can use.
Documentation produced:
functional and non-functional requirements
architecture and security design
acceptance criteria and scope definitions
Can we start with a pilot instead of the whole institution?
Yes, and that is the approach we recommend. A pilot runs one committee, or one full session cycle, in parallel with your current process, so the secretariat can compare the two records, raise corrections and sign off before anything wider is committed. What the pilot must prove is agreed in discovery.
Pilot approach:
one committee or one session cycle
runs in parallel with the current process
agreed sign-off criteria before rollout
What does it cost and how long does it take?
We do not publish prices or standard durations, because both are set by scope. Cost and schedule depend on the size of the institution, the number of committees, members and session types, the modules in the first release, integrations and archive migration, the deployment model, the Arabic and AI scope, and the support level after go-live. Approval and procurement cycles also affect the schedule.
Scope drives both:
institution size, committees and modules
integrations, migration and deployment
approval cycles and post-launch support
DIGITAL PARLIAMENT & COUNCILS Sessions, voting, minutes & portals

Start With One Committee.

Tell us which body you represent, how your session cycle runs and what your deployment and data-residency requirements are. We will walk through a first release, answer the Arabic, audit and security questions directly, and prepare the documentation your procurement process needs.

Create your account