The records officer placed four versions of the form on the table, each with a date, system identifier and archive hash.
“This is the current version,” he said. “This one was used last month. This was active on the day Ruth Wekesa accepted the terms. And this is the archive from before the major update.”
Amina did not begin by reading dense legal language. She drew four columns on paper: **transport**, **contact**, **media/video**, **behavior management**.
Neema sat beside her with Ruth’s records-request reference and the official safeguarding file. There was no leaked screenshot and no administrator access. The versions were being produced through the formal process.
“Start with the acceptance log,” Neema said.
The officer opened the event history. Ruth’s account had one entry: **ACCEPT ALL — 19:44.** There were no four separate clicks.
“What did Accept All cover on that date?” Amina asked.
“The entire active bundle.”
“And media or progress recording?”
The officer moved the current version next to Ruth’s version. “This is where they differ.”
The current form contained an explicit paragraph about photographs, progress recordings and internal review media. Ruth’s version referred more generally to program documentation, but the specific progress-video clause was absent.
“When was this clause added?” Neema asked.
The changelog showed three weeks after Ruth had accepted the terms.
Amina did not say they had caught anyone. The difference had to be interpreted carefully. Another authorization might have covered some internal documentation. What the company could not casually claim was that Ruth had signed a clause that did not yet exist.
They filled in the matrix.
Transport: Ruth’s version permitted routine transport between approved program facilities. It did not name Kijani.
Contact: it allowed temporary structured-contact limitations “where clinically indicated,” while the Communication Pause Addendum from the first complaint had been sent later as a separate document.
Media/video: general documentation language existed. The explicit progress-recording clause did not.
Behavior management: it sat inside the bundle, while its procedures were referred to in another policy that had not been attached to the acceptance page.
“So the signature is invalid?” Amina asked deliberately.
“We have not reached that conclusion,” Neema said.
“The system shows a valid acceptance,” the records officer added.
“Yes,” Amina said. “The question is scope.”
They separated what had been accepted, what had been added later and what had been sent as an addendum. It was less dramatic than saying every parent had been deceived. It was more accurate.
As the discussion became less accusatory, the records officer relaxed.
“There is something else,” he said. “The bundle changed several times, but the parent portal kept using one button.”
“Accept All?”
“Yes.”
“Could a parent open the individual permissions?”
“They could open the full terms.”
“Could they refuse media but accept transport?”
He hesitated. “Not in those versions. It was a package.”
Neema recorded that as a system-design fact, not an opinion.
Amina thought of Musa admitting in public that he had clicked without reading. That responsibility did not disappear. But one button had combined decisions with very different consequences: a vehicle, a phone restriction, a video and behavioral controls. A meaningful remedy was not pretending that nobody had signed. It was separating the permissions so people could actually choose them.
Neema requested preservation of all four versions, the changelog and the click-event schema. The officer offered certified snapshots and hash references.
“And we do not need other parents’ accounts,” Amina said. “Ruth’s account is the anchor. The system templates are enough.”
Near the end, Neema asked for the oldest archived form. Its final page was short: transport, contact, program rules. There was no media section, no progress recording, no video reflection.
They called Ruth before closing the file.
“So I signed something,” she said after hearing the explanation. “Do not tell me I didn’t.”
“You did,” Amina said. “We’re establishing what was put in front of you that day.”
“And I should have read it.”
“Yes.”
“And they should have separated these things.”
“That is part of the review.”
“Then don’t turn me into a victim who knew nothing.”
“I won’t.”
After the call, Amina added a note: **parental responsibility acknowledged; consent scope remains disputed.**
The officer printed an archive comparison. On one page the video clause was highlighted. On the older version, the section did not exist at all. He also produced an archived image of the screen Ruth had seen: one heading, one button, one small “view full terms” link. No separate toggles for transport, contact or media.
They listed measurable remedies—separate notice for a site transfer, separate consent for progress recording, an independent-contact rule outside behavior terms, and downloadable version history after acceptance.
The officer said the current system could technically support those changes. The remaining question was policy.
Before they left, Amina checked that every certified snapshot carried the active-date range and archive identifier. She did not want a page printed today to be mistaken for the page Ruth saw months ago.
The older version has no video clause.
#