Chapter 28 - The Public Record
The advisory board decided to publish a full year of maintenance and safety records.
The proposal came from Sofia Reyes, who had joined the board after enrolling her son in the percussion class. She said families should not have to ask for information every time a rumor appeared online.
“If the records are already public, people can read them,” she said. “They can see what was inspected, what was repaired, and what remains open.”
One trustee worried that publishing the documents would expose the building to criticism.
Sofia replied, “The building has already been criticized. Hiding the records won't make it safer.”
The motion passed.
The records were organized into a plain-language portal. It included inspection dates, maintenance requests, repair status, emergency procedures, and contact details for the independent reporting channel. Personal information was removed. Contractor names were included only where disclosure was appropriate under the trust's rules.
Lucas reviewed the portal with Nina.
“It's more detailed than the old reports,” he said.
“It's also more useful,” she replied. “People can see what's unfinished.”
The portal showed two minor repairs still open: a window latch in the art room and a section of exterior paving near the service entrance. Both had scheduled completion dates. The board asked the manager to update the records once the work was complete.
A reporter requested an interview with Lucas about the new transparency policy.
He declined again.
Instead, Sofia and Tessa gave the interview. They explained that the system had been designed by the people who used the building, not by the family.
The article was fair, but the comments were not all positive. Some readers said the family was trying to repair its reputation. Others argued that the building should be sold and the money given directly to residents.
Lucas read the comments once and closed the page.
Isabella noticed.
“Are you upset?”
“Some of it is unfair.”
“Some of it may be worth thinking about.”
He looked at her.
“Do you think we should sell?”
“I think the board should review the building's purpose and costs regularly. If the program stops serving the community, they should have the authority to change it. That's what independence means.”
He nodded. He had wanted to hear that the work would continue forever. But a promise that could not be questioned was another form of control.
At the next board meeting, the trustees reviewed the building's annual budget. The east wing required significant maintenance, and the temporary classroom cost more than expected. The finance committee presented three options: reduce programming, seek additional grants, or transfer some classes to partner organizations.
The youth panel asked that music lessons remain free.
Sofia proposed a community fundraising campaign with no family name attached. Tessa supported it, provided the campaign did not become a condition of participation.
The board approved a mixed plan. It would apply for local arts grants, continue the temporary classroom, and create a volunteer maintenance day for non-specialist tasks. Electrical, structural, and fire-safety work would remain with licensed professionals.
Lucas offered to contribute to the general fund. The board chair reminded him that any donation would be accepted under the same rules as other contributions, with no special voting rights.
“That's what I want,” Lucas said.
He made the donation through the independent trust and did not announce it.
A week later, the portal received its first public complaint. A parent said the accessible entrance had been blocked by a delivery van during a Saturday class. The manager reviewed security footage, confirmed the obstruction, and contacted the delivery company. The van had been moved within eleven minutes, but the complaint identified a weakness in the delivery schedule.
The board changed the delivery window and added a painted access zone.
Sofia sent the parent a response.
Thank you for fixing it. I didn't expect anyone to answer.
Tessa printed the exchange and placed it on the noticeboard, with the parent's permission and without a name.
Lucas read it and felt more satisfaction than he had from any press article.
That evening, he and Isabella walked through the east wing. The window latch had been repaired. The exterior paving was scheduled for the following week. The public portal showed both items as complete once the manager uploaded the inspection photographs.
“Do you think people will trust us now?” he asked.
“Some will. Some won't.”
“That's not very comforting.”
“Trust isn't a prize the family receives. It's a decision people make based on what happens next.”
They stopped outside the old archive room. The door was locked, and a notice explained that access was restricted because the room contained building records and preserved materials connected to the investigation.
Lucas did not want the room to become a shrine to the fire. He also did not want the past erased.
The board decided to keep the archive closed to visitors but make approved public records available through the portal. A small exhibit in the lobby would explain the building's safety reforms without displaying sensitive evidence.
Lily helped design the exhibit's title card.
A SAFE PLACE IS BUILT TOGETHER.
She drew a house with four open windows.
At the opening of the portal, Sofia spoke first. She thanked the volunteers, engineers, parents, and youth panel. She did not mention the Moretti name.
Lucas stood at the back with Isabella.
“Are you disappointed?” she whispered.
“No.”
“Really?”
He looked at the people asking questions about the portal.
“No. This is what I wanted, even if I didn't know how to say it.”
He understood that the public record was not a document meant to prove the family had changed. It was a tool that allowed people to check whether the building was being cared for.
That was better than a speech.
A month after the portal launched, a resident submitted a complaint about a contractor who had spoken dismissively to a parent using a wheelchair. The complaint did not involve a safety violation, but the board treated it seriously.
The manager interviewed the parent, the contractor, and two witnesses. The contractor acknowledged that he had been impatient and apologized. The trust added an accessibility and conduct clause to future service agreements.
Sofia asked the parent whether she wanted the complaint included in the public summary. The parent agreed, provided her name was not used.
The summary stated that the complaint had been reviewed, the contractor had apologized, and the contract terms had been updated.
Lucas read it and felt that the response was more meaningful than a public statement about values. The organization had been asked to change something, and it had changed it.
At the next meeting, the board reviewed whether the portal was too complicated. Several residents said the information was useful but difficult to find on a phone. Daniel suggested a simpler mobile layout with three main categories: safety, schedules, and complaints.
The board approved a redesign.
Lily asked if she could draw icons for the three categories. Tessa agreed, and Lily created a door, a calendar, and a speech bubble.
The drawings were simple, but they made the portal friendlier. When the updated page went live, the youth panel tested it before the public announcement.
For the first time, Lucas saw the building's records being shaped by people who had never known the house before the fire. That was exactly how it should be.
Sofia later told him that the portal had made it easier for parents to raise concerns without feeling that they were criticizing a person who had helped them. The system gave them a place to describe a problem and receive an answer.
Lucas asked whether people were using it.
“More than we expected,” she said. “Some questions are small. Some are difficult. But people are asking.”
“That's good.”
“It's only good if the answers keep coming.”
He nodded. The portal was not a trophy. It was another responsibility that would need attention long after the opening announcement was forgotten.
The new portal soon became a useful part of daily operations. A parent used it to ask why the accessible entrance was sometimes locked during deliveries. The manager reviewed the schedule and discovered that a delivery driver had been given an outdated instruction.
The instruction was corrected. The parent received a reply, and the delivery company was sent the updated access plan.
Another user asked whether the art room could remain open fifteen minutes later on Thursdays. The request was not approved because staff coverage ended at the published time, but the board explained the reason and invited the parent to suggest another schedule.
The parent replied that the explanation was enough.
Sofia told Lucas that the portal was changing the tone of conversations. People were still disappointed when a request was refused, but they were less likely to assume that nobody had read it.
“An answer doesn't have to be yes to be respectful,” she said.
Lucas thought of the old days, when a form could disappear into an office and a person could be told that the matter was closed. The new system could not guarantee perfect decisions. It could make silence harder to hide.
May you like
The board decided to publish a monthly summary of questions received and actions taken. The summary would protect personal details but show whether the trust was responding.
It was another ordinary safeguard. Lucas had come to value those more than grand promises.
