Appendix N · Digital companion · all tools

The 90-Day Public Accounting Pilot

Appendix N: The 90-Day Public Accounting Pilot

A national reform movement becomes credible when it can prove one small part of the State can be made visible, measured, and improved. A pilot is not a substitute for national transformation but the first test of method. It shows whether citizens can move from complaint to record, whether officials can respond to structured questions, whether data can reveal patterns, whether claimants can be protected, and whether public pressure can produce correction without collapsing into noise.

The purpose of this 90-day pilot is to create a disciplined, limited, repeatable model of public accounting. It should be small enough to execute, serious enough to matter, and clear enough to replicate. The pilot should not try to fix the entire country. It should choose one district, one ward, one hospital, one university office, one labor sector, one land office, or one high-volume public service and build a working ledger around it.

This pilot holds one standard: in 90 days, produce records that did not exist before, identify failures that were hidden before, secure at least some corrective action, and publish a method others can use.

Choosing the Pilot Area

The first decision is scope. A pilot fails when it is too ambitious. The temptation will be to choose every issue at once: land, tax, police, courts, hospitals, schools, wages, local government, and public services. That would recreate national paralysis at a smaller scale. The first pilot must be narrow.

• Good pilot options include:
• One ward's local government services.
• One hospital's medicine stock and patient complaints.
• One university's transcript and document service.
• One labor sector's wage claims.
• One land office's inheritance mutation process.
• One police station's complaint acknowledgment process.
• One district's public project boards.
• One school cluster's foundational learning.
• One pension office's service timeline.
• One local court category's case-delay ledger.

The chosen area should meet five tests. It should affect ordinary citizens. It should produce records. It should be measurable within 90 days. It should have a responsible office or institution. It should be safe enough for claimants and researchers to engage without reckless exposure.

Pilot Governance Team

A pilot needs a small governance team. It should not be controlled by one personality. It should include enough roles to protect quality, safety, and follow-up.

• The team should include:
• Pilot coordinator.
• Records lead.
• Citizen intake lead.
• Legal or rights advisor.
• Data and documentation lead.
• Official liaison.
• Communications lead.
• Safety and privacy reviewer.
• Youth or volunteer coordinator where relevant.

The team does not need to be large. In fact, a small disciplined team may work better. The key is role clarity. Everyone should know who collects records, who verifies evidence, who speaks to officials, who protects claimant privacy, who publishes updates, and who decides what is safe to disclose.

Pilot Charter

Before beginning, write a short pilot charter. This prevents mission drift and helps explain the work to citizens, officials, journalists, and supporters.

• The charter should state:
• Pilot issue.
• Pilot location.
• Public duty being examined.
• Duration.
• Records to be collected.
• Citizens or claimants involved.
• Privacy safeguards.
• Officials or institutions to be contacted.
• Output expected.
• Limits of the pilot.

The charter should be public where possible. It should make clear that the pilot is not a political attack, not a defamation campaign, and not a promise to solve every case, but a public accounting exercise.

Baseline Record

• The pilot must begin with baseline facts. Without a baseline, improvement cannot be measured.
• For a public service pilot, the baseline should include:
• Published requirements.
• Official fee.
• Processing timeline.
• Receipt or tracking process.
• Appeal route.
• Complaint route.
• Actual citizen experience.
• Average delay where measurable.
• Common objections.
• Number of pending cases where available.

For a hospital pilot, the baseline should include medicine availability, stockout days, outside purchase cases, complaint route, official fees, and equipment status.

For a ward pilot, the baseline should include public projects, complaints, waste schedule, drain cleaning status, streetlight condition, public spaces, project boards, and maintenance responsibilities.

For a wage pilot, the baseline should include number of workers affected, amount claimed, employer categories, evidence available, retaliation risks, and complaint routes.

The baseline should be honest about missing data. If the office does not publish timelines, say so. If official fees are not displayed, say so. If complaint routes are unclear, say so. Missing records are part of the baseline.

Evidence Standards

• The pilot must define evidence standards before collecting claims. Otherwise it will become vulnerable to exaggeration, rumor, or selective accusation.
• Evidence categories should include:
• Official record.
• Receipt or tracking number.
• Photograph of public notice or site.
• Written message.
• Payment proof.
• Witness statement.
• Citizen testimony.
• Field observation.
• Official response.
• Missing record.
• Pending verification.

Each entry in the pilot ledger should identify the evidence category. A complaint should not be presented as proven fact. A missing record should be stated as missing, not converted into a broader accusation without proof. Precision protects the pilot.

Citizen Intake

If the pilot involves citizens or claimants, intake must be structured. Citizens should not be asked to tell their entire life story without purpose. The intake process should collect only what is necessary for the pilot issue.

• A basic intake form should include:
• Name or protected reference.
• Contact method.
• Issue category.
• Date issue began.
• Office, employer, hospital, school, police station, ward, or institution involved.
• Documents submitted.
• Receipt or tracking number.
• Response received.
• Delay or denial.
• Evidence available.
• Urgency.
• Retaliation or privacy risk.
• Consent for use of information.
• Preferred remedy.

Consent is essential. Citizens should understand whether their information will be used privately, anonymously, in aggregate, or publicly. Vulnerable claimants should not be exposed for the sake of a report.

Privacy and Safety Review

Every pilot should include a privacy and safety review before publication. Public accounting must not endanger the people it claims to protect.

• Review questions:
• Is a child involved?
• Is a patient involved?
• Is a domestic violence complainant involved?
• Is a woman claiming inheritance at family risk?
• Is a worker at risk of dismissal or retaliation?
• Is a complainant facing local political or police pressure?
• Is the matter legally sensitive?
• Could publication expose private medical, family, or financial details?
• Can the case be anonymized?
• Does the claimant consent?
• Should the case be referred to legal aid instead of being published?
• The safest version of the truth is often aggregate data, anonymized case summaries, and document-based findings rather than personal exposure.

Official Engagement

Officials should be contacted early and respectfully. The goal is not to ambush every office. The goal is to request records, clarify procedures, and provide a chance to respond.

• An official engagement letter should state:
• Who is conducting the pilot.
• What issue is being examined.
• What records are requested.
• Why the issue affects citizens.
• What timeline applies.
• How the office can respond.
• How the information will be used.

The tone should be firm but not insulting. An official may be defensive at first, especially in a system where accountability is often factional. The pilot should make clear that accurate records and genuine constraints will be reported fairly.

The 30-Day Phase

• The first 30 days are for mapping and baseline collection.
• Tasks:
• Finalize pilot charter.
• Identify responsible offices.
• Collect published requirements and public notices.
• Create intake form.
• Begin citizen intake.
• Request official records.
• Conduct field observations.
• Photograph public notices, project boards, fee lists, or service conditions where relevant.
• Build initial ledger.
• Identify missing data.
• Conduct privacy review.

At the end of 30 days, publish a brief baseline note or internal briefing. It should not overclaim. It should say what is known, what is missing, what records were requested, and what the next phase will examine.

The 60-Day Phase

• The second 30 days are for verification, pattern detection, and official response.
• Tasks:
• Verify citizen claims where possible.
• Follow up on official record requests.
• Categorize delays and failures.
• Identify recurring issues.
• Meet or write to responsible offices.
• Seek correction of simple failures.
• Refer urgent cases to legal aid or proper authority.
• Update the ledger.
• Protect sensitive cases.
• Prepare interim findings.

At this stage, the pilot should begin to distinguish isolated failures from patterns. One delayed transcript may be an individual issue. Fifty delayed transcripts without written reasons show a system problem. One medicine stockout may have an explanation. Repeated stockouts of essential medicines require public review.

The 90-Day Phase

• The final 30 days are for public reporting, correction tracking, and replication planning.
• Tasks:
• Finalize verified ledger.
• Publish aggregate findings.
• Include official responses.
• Identify remedies achieved.
• Identify unresolved failures.
• Publish missing records list.
• Publish recommendations.
• Create replication guide.
• Hold public briefing or stakeholder meeting where safe.
• Plan next 90-day cycle.

The report should be direct and evidence-based. It should not sound like a manifesto. The manifesto already exists. The pilot report should show dates, records, numbers, patterns, responses, and next steps.

Pilot Report Structure

• A strong 90-day pilot report should include:
• Pilot title.
• Location and scope.
• Why this issue was chosen.
• Method used.
• Records requested.
• Records received.
• Records missing.
• Citizen cases reviewed.
• Privacy safeguards used.
• Key findings.
• Official responses.
• Corrective actions achieved.
• Unresolved issues.
• Recommendations.
• Replication steps.
• Appendix of non-sensitive records.
• The report should be readable. Do not bury the public in technical detail. Put technical documents in appendices where needed.

Metrics of Success

• A pilot should not measure success only by public attention. Attention can help, but the goal is proof.
• Useful success metrics include:
• Number of records obtained.
• Number of missing records identified.
• Number of citizens assisted.
• Number of cases resolved.
• Amount of wages recovered.
• Number of service timelines clarified.
• Number of official fees displayed.
• Number of complaint routes created or clarified.
• Number of medicine stock items published.
• Number of public project boards installed or corrected.
• Number of female-heir safeguards adopted.
• Number of police complaints acknowledged.
• Number of official responses received.
• Number of replication partners identified.

If the pilot produces no immediate remedy but establishes a credible baseline and exposes missing records, that can still be a success. Visibility is often the first victory.

Example Pilot: University Transcript Service

• Scope: one university or one campus document office.
• Records to collect:
• Published transcript requirements.
• Official fee.
• Processing timeline.
• Urgent processing criteria.
• Receipt process.
• Tracking method.
• Appeal route.
• Number of student requests reviewed.
• Average delay.
• Common reasons for delay.
• Student deadline harm.
• Official response.
• Possible remedies:
• Posted requirements.
• Receipt or tracking number.
• Written reasons for delay.
• Urgent deadline process.
• Complaint route.
• Monthly document performance report.

This pilot is practical because students can document submission dates, deadlines, receipts, and delays. It also shows how a routine administrative service can affect life chances.

Example Pilot: Public Hospital Medicine Availability

• Scope: one public hospital.
• Records to collect:
• Essential medicine list.
• Medicine stock availability.
• Stockout days.
• Outside purchase cases.
• Official fee display.
• Complaint process.
• Equipment status for selected high-use machines.
• Patient complaints, anonymized.
• Official response.
• Possible remedies:
• Medicine availability board.
• Stockout recording.
• Complaint tracking number.
• Outside purchase register.
• Monthly public stock summary.

This pilot is powerful because it connects public money to patient experience. It also avoids blaming doctors for procurement failures unless records show specific conduct.

Example Pilot: Ward Streetlight and Drain Complaint Ledger

• Scope: one ward.
• Records to collect:
• Streetlight locations.
• Non-functional lights.
• Drain blockage points.
• Complaint route.
• Complaints filed.
• Response time.
• Repair status.
• Maintenance schedule.
• Responsible office.
• Project or maintenance contractor.
• Possible remedies:
• Complaint number system.
• Public repair list.
• Monthly ward scorecard.
• Pre-rain drain cleaning record.
• Streetlight repair timeline.
• This pilot is visible because citizens can verify conditions with photographs and dates.

Example Pilot: Wage Recovery in One Sector

• Scope: one sector, such as security guards, private school teachers, construction workers, domestic workers, or clinic staff.
• Records to collect:
• Worker claims.
• Work period.
• Wage due.
• Wage paid.
• Evidence available.
• Employer response.
• Retaliation risk.
• Complaint route.
• Amount recovered.
• Possible remedies:
• Written employment templates.
• Wage claim clinic.
• Settlement process.
• Public contractor wage certification where relevant.
• Aggregate wage theft report.
• This pilot must prioritize claimant safety. Workers may face retaliation. Do not publish personal details without careful consent.

Example Pilot: Female-Heir Inheritance Safeguard

• Scope: one land office or one district inheritance mutation process.
• Records to collect:
• Mutation process.
• Whether female heirs are separately identified.
• Whether notices are issued.
• Whether shares are explained.
• Relinquishment frequency.
• Consent verification method.
• Legal aid information.
• Complaints of coercion.
• Possible remedies:
• Separate notice form.
• Written share explanation.
• Relinquishment safeguard form.
• Legal aid referral.
• Aggregate female-heir reporting.

This pilot is sensitive. Personal inheritance cases should not be exposed. Aggregate data and procedural reform should be the first focus.

Volunteer Training

Volunteers should be trained before collecting data. Untrained volunteers can damage the work by exaggerating, exposing claimants, confronting officials unsafely, or mixing rumor with evidence.

• Training should cover:
• Purpose of public accounting.
• Evidence categories.
• Privacy and consent.
• How to conduct intake.
• How to photograph public evidence safely.
• How to write field notes.
• How to avoid defamation.
• How to handle vulnerable claimants.
• How to escalate urgent cases.
• How to communicate with officials respectfully.
• How to store records securely.
• Volunteers should not act as lawyers unless qualified. They should not promise outcomes they cannot deliver.

Data Storage

• Records must be stored securely. Public accounting work often involves sensitive information.
• Basic storage rules:
• Use structured folders.
• Separate public records from private claimant information.
• Protect personal data.
• Back up files.
• Limit access to sensitive material.
• Name files clearly.
• Record source and date.
• Keep original versions.
• Track edits.
• Do not store sensitive data casually on personal phones where avoidable.
• A public accounting movement that loses or exposes claimant data can harm people and destroy trust.

Communications Discipline

The pilot's public communication should be sober. Avoid exaggerated claims. Avoid insulting language. Avoid declaring guilt without evidence. Avoid turning vulnerable citizens into emotional material.

Good communication says:

"We reviewed 42 cases."

"Thirty-one had no written reasons for delay."

"The office did not publish an official timeline."

"The hospital stock board was not available to patients."

A translated version of any form or letter is a draft for your understanding. Submit in the office’s official language, and have the final text checked by someone you trust.

Workers reported unpaid wages totaling [amount], with evidence reviewed in [number] cases.

The department was contacted on [date] and responded on [date].

"The following records remain unavailable."

This style is harder to dismiss than rhetorical anger.

Dealing With Official Resistance

• Resistance may come in several forms:
• No response.
• Verbal dismissal.
• Demand for unnecessary permission.
• Claim that records are sensitive.
• Accusation of political motive.
• Partial data release.
• Delay.
• Threat.
• Offer of informal settlement.

The response should remain disciplined. Record the resistance. Ask for written reasons. Use lawful information request routes where available. Escalate carefully. Seek legal advice if threatened. Do not turn every resistance into public drama immediately. Some offices may respond after process is clarified. Others may require public pressure.

Dealing With Internal Capture

A pilot can itself be captured. A political group may try to use it against rivals. A donor may want selective focus. A local official may try to control findings. A volunteer may leak private data. A media partner may sensationalize. A lawyer may push cases for personal gain. A claimant may submit false information.

• Safeguards:
• Written pilot charter.
• Evidence standards.
• Privacy rules.
• Conflict-of-interest disclosure.
• Multi-person review before publication.
• Correction process.
• No single person controls all data.
• Public distinction between verified facts and allegations.
• A public accounting pilot must practice the standards it demands from others.

Correction Process

• Errors will happen. The pilot should have a correction process.
• The correction process should state:
• How errors can be reported.
• Who reviews correction requests.
• How corrections are published.
• How affected persons are notified.
• How data is updated.
• How false or misleading entries are removed.
• A willingness to correct increases credibility. A movement that refuses correction becomes another source of noise.

Replication Guide

• At the end of 90 days, the pilot should produce a replication guide for other communities.
• The guide should include:
• Pilot scope.
• Forms used.
• Evidence checklist.
• Privacy rules.
• Official letter template.
• Data fields.
• Lessons learned.
• Risks encountered.
• What worked.
• What failed.
• Recommended next steps.
• This guide allows the pilot to become a method rather than a one-time activity.

The 90-Day Timeline

• Days 1 to 10:
• Choose pilot issue and location.
• Form team.
• Write charter.
• Define evidence standards.
• Prepare intake forms.
• Identify responsible offices.
• Days 11 to 30:
• Collect baseline records.
• Begin citizen intake.
• Request official records.
• Conduct field observation.
• Build initial ledger.
• Review privacy risks.
• Days 31 to 60:
• Verify evidence.
• Categorize patterns.
• Follow up with officials.
• Refer urgent cases.
• Seek simple corrections.
• Prepare interim findings.
• Days 61 to 80:
• Finalize data.
• Collect official responses.
• Draft report.
• Review legal and privacy risks.
• Prepare replication tools.
• Days 81 to 90:
• Publish report.
• Brief stakeholders.
• Track immediate remedies.
• Set next cycle.
• Recruit replication partners.
• This timeline is adjustable, but it should remain disciplined. A pilot without deadlines becomes another discussion.

Model Pilot Charter

Pilot name: [Insert]
Issue: [Insert]
Location: [Insert]
Duration: 90 days
Public duty examined: [Insert]
Records to be collected: [Insert]
Citizen cases to be reviewed: [Insert]
Responsible office or institution: [Insert]
Privacy safeguards: [Insert]
Evidence standards: [Insert]
Expected output: [Report, ledger, recommendations, replication guide]
Limits: [Insert what the pilot will not do]
Coordinator: [Insert]
Review team: [Insert]

Model Official Records Request

To: [Office or authority]

Subject: Request for public records related to [service or issue]

We are conducting a 90-day public accounting pilot on [issue] in [location]. The purpose is to document service standards, citizen experience, and available public records. We request the following records:

[List records]

Please provide the records or written reasons if any record cannot be provided. We would also welcome any clarification of official process, timeline, fee, appeal route, or complaint mechanism related to this service.

We will include official responses in our pilot report and will protect personal information of citizens involved.

Date: [Insert]

Contact: [Insert]

Model Pilot Finding Entry

Finding number: [Insert]
Issue category: [Insert]
Evidence type: [Official record, citizen case, field observation, missing record, official response]
Description: [Insert]
Date observed: [Insert]
Office or institution involved: [Insert]
Citizen impact: [Insert]
Official response: [Insert]
Status: [Open, resolved, partially resolved, disputed, pending]
Recommended remedy: [Insert]
Privacy level: [Public, anonymized, restricted]

Model Remedy Tracker

Issue: [Insert]
Remedy requested: [Insert]
Responsible authority: [Insert]
Date requested: [Insert]
Deadline: [Insert]
Status: [Pending, completed, delayed, rejected]
Evidence of completion: [Insert]
Citizen impact: [Insert]
Next follow-up: [Insert]