What this is

If you are a member of the public: you can find out what your representative has sponsored and how they voted, follow a bill that affects you from the day it is introduced to the day it becomes law, and see what the House is doing today.

If you work in the House: it answers the question the Clerk’s office and members’ offices field constantly — what stage is that bill at? — without a manual search, and it gives every committee one place to show its work.

If you are a journalist or researcher: every screen here is backed by a public JSON endpoint, so the same information can be queried directly rather than copied by hand.

The House sits Tuesday to Thursday. Each sitting has an Order Paper — the printed list of business the House will take that day, in order. Afterwards, the Votes and Proceedings record what actually happened.

A bill passes through twelve stages, from being gazetted to receiving the President’s assent. Most of the work happens in committee, between the second and third readings. HIVE shows a bill’s journey as a dated history rather than a single status word, because the journey is what people actually want to know.

The Constitution requires the National Assembly to sit for not fewer than 181 days a year.

The next sitting recorded here is Tuesday, 17 November 2026.

Everything shown here is demonstration data. The bills, members, votes, motions and submissions are synthetic — generated to show how the platform works. Nothing here is the record of the House of Representatives, and no item is attributed to a real sitting legislator.

What is real is the shape: the 360 seats and their allocation across the states, the geopolitical zones, the twelve legislative stages, the sitting days, and the names and mandates of the standing committees. So the scale and structure match production even though the contents do not.

In production the record would come from the House’s own systems — the Order Paper and Votes and Proceedings series, and the bills register — with a named office holding authority to publish. Replacing the demonstration data and removing the notice at the top of every screen are the same piece of work.

Partly, and it is worth being precise. The status shown on the home page is worked out from the time of day in Lagos against the sitting calendar. It is not a feed from the Chamber, and it does not claim to know which item the House is debating right now.

Making it genuinely live does not require anyone to type updates. Parliaments that do this well already run an annunciator — the system driving the screens around the parliamentary estate — and simply republish that same feed to the public. The work is to expose something the institution already operates for itself.

Every screen is backed by a public endpoint, so the press, civic groups and other arms of government can use the same information directly.

/api/bills?category=Health
/api/search?q=education
/api/sittings
/api/live

The full surface is documented and browsable. Open the API console to read every endpoint and call it from the page, or take the OpenAPI 3.1 description straight into your own tooling.