The part of a consultation that decides a court case is usually written last and kept worst: the record of what the public body did with each view. Hearings produce memoranda, forum notes, emails and petitions, and somebody has to read them, decide what to do with each and say why. Courts read that record. The Supreme Court described a record that passed this test in its Finance Act judgment of 29 October 2024. It set out each proposal and whether it was accepted or rejected, grouped similar views by theme, and was published. The High Court in June 2025 described one that failed, finding "no evidence of consideration of public inputs or feedback mechanisms explaining acceptance or rejection of views". This piece explains how to keep the first kind.
What the Supreme Court accepted
The case concerned the National Assembly, and the court's reasoning applies to any body bound by Article 10 of the Constitution, county assemblies and county executives included. It held that there is "no express obligation on Parliament to provide reasons for accepting and/or rejecting proposals", but that a body must "put in place reasonable measures to guide how" it "considers and treats the proposals, views, suggestions, and comments received" (paragraph 148). The test for those measures is in paragraph 150. The record "must be clear enough to enable those who submitted their views to understand that their input was considered and given due attention". A body "is not required to respond individually to every public comment or submission", and it may "group similar views into thematic areas and address them collectively".
The report the court examined shows what that looks like in practice. The Finance Committee received 1,080 memoranda (paragraph 152). Its report runs to 260 pages, and 235 of them respond to the views of 161 persons and organisations: "Under each of the 161 persons and organizations, the Report outlines the proposal made and the Committee's observation on whether to accept or reject the proposal" (paragraph 153). Where one firm made more than thirty proposals, each got an observation. Emails were grouped into clusters, such as 87 objecting to the housing levy, 9 opposing VAT on fuel and 137 calling for the Bill's rejection in its entirety, and the committee made an observation on each cluster except the last (paragraph 155). On the housing levy cluster, for instance, it recorded that it had considered reducing the levy from 3% to 1.5% (paragraph 156). The court found that "to a large extent the Report strives to explain the reasons for accepting or rejecting various proposals", and noted it was a public document (paragraph 157).
The Court of Appeal had gone further three months earlier, holding that reasons are obligatory and that rejecting views without them renders participation "illusory, cosmetic and a mere formality" (paragraph 189). The Supreme Court reversed that holding. The two judgments agree on the substance of good practice, though. A record that sets out each view and what was done with it satisfies both.
Building the record
The record starts the moment a view arrives. Each submission is logged with who made it where that is known, the date, the channel it came on and the decision it is about, and its text is kept as it arrived. A memorandum handed in at a forum, an SMS and an email are logged the same way. The Treasury's budget manual expects both public hearings and "submission of memoranda from stakeholders" (paragraph 16), so both have to land in one list.
Each view, or each group of identical views, then gets an outcome. Four outcomes cover almost everything: accepted, partly accepted, rejected, or out of scope, which is for a view about something other than the decision on the table, such as a complaint about a road in a consultation on fees. Beside each outcome goes a reason a submitter could read and argue with. "Noted" is no reason. "Rejected: the proposed exemption would remove the main revenue line for markets; the fee is instead held at last year's rate for traders under the threshold" is one. The name of the officer or committee that decided goes beside the reason, because a court, an auditor or a resident may later ask who made the call.
The record also needs to keep its history. If a decision changes, after a committee meeting say, the change is added as a new entry with its own reason and author, and the earlier one stays visible. A record that can be quietly edited after a petition is filed proves very little, and an opposing advocate will ask what the first answer was.
Four hundred identical memoranda
Organised campaigns produce many copies of the same submission, and they create two opposite risks. Treating four hundred identical memoranda as one view understates how many people took the trouble to write. Treating them as four hundred separate arguments, each answered "noted", produces exactly the record the Court of Appeal criticised. The Supreme Court's answer was grouping (paragraph 150), and grouping works when it keeps both numbers. The group carries one reasoned response, and each of the four hundred submissions stays in the record with its own entry pointing at that response. The report can then say that one argument was made by four hundred people and what was done with it, and any one of them can find their own submission and the answer to it.
Take an illustration. A county's finance bill raises market stall fees, and 412 traders submit the same printed objection while 37 others write their own. The committee groups the 412, records that the objection was partly accepted with the fee increase phased over two years, and gives the reason. It answers the 37 individually or in themes. Its report states that 449 traders objected, that 412 submitted the same text, and what was decided. Nothing in that record is lost, and none of it needs four hundred copies of one sentence.
Timing
Decisions on views must be recorded before the decision they are about is taken, or they are a justification written afterwards. Order matters here. For a county budget that means the committee's record of views should be complete before it reports to the assembly, which under section 131(2) of the PFM Act must take the public's views into account before considering the estimates. For a finance bill it means before the bill's third reading. A record kept as the views arrive makes that easy, because the committee works from it. One assembled at the end is often an honest summary that has lost the link to each person's submission, and that link is what the courts look for. What the courts have said sets the judgments out in full, and reporting back covers telling people the outcome.
Where Takwimu fits
On Takwimu each view on a decision is marked accepted, partly accepted, rejected or out of scope, with a written reason and the name of who decided; a view cannot be marked rejected without a reason. Identical submissions are counted after a stated normalisation and answered with one reasoned response, and each person's view keeps its own entry. A change is added as a new entry under its author's name. Nothing is overwritten.
The steps are set out in filing a public participation record. To see a record of decisions kept this way, book a walk-through.