The motion, the mover, the vote, and who stood down.
A meeting recorded in a public-sector workspace is read as a public record rather than as a team catch-up: the items in the order they were taken, the motion in the words it was moved, who moved and seconded it, how the vote went, and who declared an interest and stood down - each anchored to a sentence somebody actually said. A motion that directs staff to report back becomes a card with an owner; a resolution, an appointment or an adoption becomes a Decision Log entry carrying the verbatim sentence. Beside it, a records-request register with its statutory clock on the card, one-click packaging of a project's whole history as a real PDF and structured JSON with a checksum, a sanitised board on a public URL, and inter-agency guests scoped to one programme. Choose Government & Public Sector at setup and all of it is queued for you.
9 apps queued at setup - untick any of them before you finishDefault project tabs
Goals and RAID are on, Capacity is off - public work is measured against published objectives. The statutory clock on a records request rides on the board card itself rather than costing a twelfth tab.
Projects created on day one
- Programmes
- Public Records
- Procurement
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working - or install any one of them on its own, later, from the marketplace.
FOIA Exporter
A request register plus one-click packaging of a project's full history as a real PDF and structured JSON, carrying a content checksum.
- A register of requests, tracked as work
- One-click packaging of a project's full history
- A real PDF plus structured JSON
- A content checksum on the package
Public Read-Only Boards
A sanitised board on an anonymous public URL, with field-level control of exactly what is exposed and what is not.
- An anonymous public URL per board
- Field-level exposure control
- Internal chat and comments never leak
- Disable it and the public URL stops answering at once
Advanced RBAC
An inter-agency guest register with field-level view and edit rules, enforced on the server rather than by hiding a control.
- A register of inter-agency guests
- Field-level view and edit rules
- Enforced server-side on every request
- Guest scoping is per project
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
09:15
a records request arrives, with its clock
It goes into the FOIA register rather than someone's inbox, and the statutory response deadline rides on the card itself as an SLA countdown, counted on a business-hours clock, with an escalation before it is missed. When it is time to respond, one click packages the project's full history as a real PDF plus structured JSON, with a content checksum so the recipient can prove the package they hold is the package you sent.
14:00
the committee sits, and the reading knows what a minute needs
In a public-sector workspace the summariser is told who it is writing for: the clerk who has to produce the minutes, and every member of the public who can ask for them afterwards. It takes the items in the order they were taken, the motion in the words it was moved rather than paraphrased into what it meant, the mover and the seconder, the method of the vote and the roll where there was one, whether a quorum was present, who declared an interest and stood down and the reason they gave, the ground stated for going into closed session and what was reported back, and one verbatim sentence anchoring each item. What it is unsure of is left null rather than tidied. Then the work routes as it always does: a carried motion that directs staff to report back becomes a card with an owner and a date where one was said; a resolution, an appointment, an award or an adoption becomes a Decision Log entry with the sentence that settled it; the next meeting, a posting date or the day a records request falls due becomes a calendar entry. The clerk completes the minute book from a record that is already in front of them.
16:30
the public sees the programme, and the contractor sees one project
Public Read-Only Boards publishes a sanitised board to an anonymous URL with field-level control over what is exposed; internal chat and comments are never part of it, and turning the extension off stops the URL answering at once. Advanced RBAC keeps the inter-agency guest register with field-level view and edit rules enforced on the server, so a contractor invited to one programme sees that programme and nothing else.
These sit on top of the whole product.
- SLA Timers put the statutory response clock on the request's own card, counted on a business-hours clock, with an escalation before it is missed and a breach recorded rather than dropped
- The Decision Log is the minute book: a meeting's decisions land in it with the words that were said, and a body records the motion, the mover and seconder, the vote, recusals, the quorum and the date its record has to be approved by
- Approvals is how an agenda item gets from a department to the clerk, with who approved what, and when, on the item itself
- The Policy Library holds each policy with its effective date and one authoritative text; the Compliance Audit Logger is append-only and exportable
- Goals, Budget and RAID are tabs on every programme, so progress is reported against the objectives that were published, spend is watched against the grant, and the risk register is where an auditor expects it
- Public meetings, consultations, case reviews and briefings each get a steer on the recorder, and become owned action items automatically
- Forms is a consultation you can put in front of the public: build it from blocks - a written answer, a multiple choice, a date, a note - attach it to the programme it belongs to, and share it as a link anyone can open without an account. Answers can be anonymous, and anonymity is fixed when the form is made rather than switchable afterwards, so what a respondent was told when they answered stays true
- Offered at setup, one tick each: Intake as the front door for requests, the Vendor & Client Register for procurement and contracts, the Risk Register, Announcements, Checklists & SOPs, Codex and Training
- A notice period, a posting requirement, the approval of the previous minutes and a records-request response date are captured in the words they were stated in, with a calendar date attached only where somebody actually said one - because what a minute must contain differs by jurisdiction, and this product holds no rules content and computes no deadline
- Anything a member said is exempt, confidential or not for the public record is flagged for a person to review before anything is published. It is a flag raised for a human, never a determination that the material is exempt
- A workspace, or one programme inside it, can be given a media retention period: after it, the sweep destroys the transcript Noots holds and asks the recording provider to delete its copy. It is off until an administrator sets it, it is a timer you choose rather than a rule tied to your own records schedule, and setting one is an operational choice about what this product stores rather than a compliance claim
- SAML/SCIM single sign-on, two-factor authentication the workspace can require of every member, and an IP allowlist
- Private AI: run every AI feature against a model your own organisation operates
- Ten interface languages and a high-contrast palette
The honest edges.
- A FOIA package inlines meeting summaries and action items. It does not inline full transcripts.
- Advanced RBAC governs this extension's own surfaces and its guest register. It is not a field-level permission layer over every board in the product.
- Guest scoping is per project rather than per task.
- The statutory clock is one you set per severity tier - twenty working days here, ten there. Noots does not know your jurisdiction's statute and will not pick the number for you. A public consultation is published as a board; the responses to it come back through your own channels, because a public board takes no input.
- The public-body reading changes how a meeting is summarised and what reaches the workspace: cards, calendar entries, decisions with their quotes, notes and reminders. It does not produce a minute document, and it does not file one. The minute book's own fields - the motion, the mover and seconder, the vote tally, recusals and the quorum - are ones a clerk enters in the Decision Log.
- An exempt flag is raised for a person to review before anything is published, and is never a determination that material is exempt. Nothing here decides what your statute requires a minute to contain, and at least two states point in opposite directions on whether a summary of the discussion belongs in one at all.
- A retention period destroys the transcript Noots holds and asks the recording provider to delete its copy, on a timer an administrator sets. Nothing ties that timer to your own records schedule or to the moment minutes are approved, and with nothing set a transcript is kept.
- Noots holds no FedRAMP, StateRAMP or SOC 2 authorisation, and does not claim one.
The model can be one you run, and ours never sees the file.
Public bodies are the buyers most often told they may not send a record to a commercial AI service. So on the Business plan the address is yours to choose: give Noots an OpenAI-compatible endpoint your organisation operates and every AI call the product makes goes there - summarising a committee session, triaging correspondence, drafting a response, Autopilot, Hoot. Not a copy, and not a fallback.
What the control actually is
- One resolver decides where every model call goes, so switching the endpoint moves all of them at once - there is no surface that quietly kept using ours.
- A killswitch, on by default. If your server is unreachable the feature fails and names your server; nothing is retried against our provider, not during an outage and not if the plan lapses.
- The endpoint must be https and must resolve publicly. Noots re-checks the address on every call rather than only when it is saved, pins the one address it dials, and refuses redirects.
- The stored key is sealed with AES-256-GCM and never returned to a browser again - not even to the administrator who typed it.
- A five-check test runs before anything routes and again every day, on a fixed prompt that is never your content. One of the checks re-sends the request with no key, which is how a self-hosted model server turns out to be usable by anyone who finds the URL.
- Every call is recorded where your administrators can read it: when, which feature, which host, and whether it worked. Never what was in it.
Where the line actually is.
- It decides which model reads your text. It is not database-level encryption: the transcript and the summary are stored as ordinary text in our database either way, and we will not describe that as encrypted at rest.
- Noots never stores meeting audio, with or without it. There is no file storage in the product - audio is transcribed in flight and the recording is not kept.
- Bring your own transcription and those meetings come back as prose with no speaker labels, because the OpenAI-compatible audio API has no diarization and inventing speakers is something we refuse to do.
- A call captured by a third-party meeting bot arrives as a link rather than a file, so your own transcription endpoint cannot take it. It fails and says so rather than sending the recording elsewhere.
- One exception, and it is one you make: if you separately connect a third-party AI provider with your own key, work you push to it goes to that provider, because that is what you asked for.
- It is a Business-plan feature, configurable by an owner or an administrator only, and it is not an authorisation of any kind. Noots still holds no FedRAMP, StateRAMP or SOC 2.
How Government & Public Sector actually runs.
Each of these is a project in Noots - its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
Built for the way your trade actually runs.
The ones buyers ask first.
What is actually in a FOIA package?
Can the public see internal discussion on a public board?
How far does Advanced RBAC reach?
Can it keep our minutes?
How long is a recording of a public meeting kept?
Do our records have to go to a commercial AI service?
Open a workspace that already knows Government & Public Sector.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required