Appendix X · Digital companion · all tools

The Public Accounting Audit Protocol

Appendix X: The Public Accounting Audit Protocol

A public accounting system is only as strong as the trustworthiness of its records. A dashboard can lie. A land inventory can omit the most valuable parcels. A medicine stock report can say "available" while patients are sent outside. A service guarantee can publish timelines that no office follows. A wage compliance certificate can be signed while workers remain unpaid. A public project can be marked complete while the road collapses after the first rain. Records matter, but records must be tested.

This appendix provides an audit protocol for public accounting, for public auditors, universities, citizen groups, journalists, legal aid clinics, professional bodies, reform commissions, local governments, donor-funded programs, and public accounting coalitions. Its purpose is to prevent public accounting from becoming another theatre of paperwork. It asks whether published records match reality, whether citizens can use the systems described, whether missing records are identified, and whether remedies actually reach claimants.

The central standard: do not only publish records. Verify them.

Why Audit Public Accounting?

Every captured system learns to imitate reform. If citizens demand dashboards, the system may create dashboards. If citizens demand receipts, the system may issue receipts but ignore timelines. If citizens demand stock lists, the system may display lists without real stock. If citizens demand project boards, the contractor may put up a board while hiding poor work. If citizens demand complaint numbers, the office may issue numbers without action.

An audit protocol tests whether the new symbols of accountability are functioning as real instruments. It asks: can the citizen use the receipt? Does the tracking number show status? Do written reasons explain actual defects? Is the appeal route real? Does the hospital stock record match pharmacy reality? Does the ward ledger match the street? Does the public land inventory match site conditions? Does the contractor wage certificate match worker payment evidence?

A reform that cannot be audited can be captured again.

Audit Scope

The audit must begin with a clear scope. Do not audit everything at once. Choose a domain, institution, district, service, project, ward, hospital, police station, land office, school cluster, or public contract category. The narrower the scope, the stronger the first audit is likely to be.

• Possible audit scopes include:
• One public service guarantee.
• One hospital medicine stock system.
• One ward ledger.
• One public project list.
• One public land inventory section.
• One police complaint access pilot.
• One wage compliance rule for public contractors.
• One female-heir inheritance safeguard process.
• One court-delay data dashboard.
• One school foundational learning ledger.
• One tax expenditure statement.
• One procurement disclosure portal.

The scope should define what records will be tested, what field reality will be checked, what citizen experiences will be reviewed, and what period the audit covers.

Audit Questions

• Every audit should begin with core questions.
• Does the record exist?
• Is the record public?
• Is the record complete enough to be useful?
• Is the record updated?
• Can citizens access it?
• Does the record match field reality?
• Does the record identify responsible offices or actors?
• Does the record include timelines?
• Does the record include complaint, appeal, or correction routes?
• Did remedies occur where failures were found?
• These questions keep the audit practical. The goal is not to produce academic complexity. The goal is to test answerability.

Evidence Categories

• Auditors should categorize evidence carefully.
• Evidence may include:
• Official records.
• Published dashboards.
• Receipts.
• Tracking numbers.
• Written reasons.
• Complaint logs.
• Appeal logs.
• Field photographs.
• Site inspections.
• Citizen interviews.
• Worker payment proof.
• Patient outside purchase records.
• Hospital pharmacy records.
• Public project boards.
• Land maps.
• Court statistics.
• School assessment records.
• Official responses.
• Missing records.
• Disputed records.

Each evidence item should be dated, sourced, and labeled by reliability. A citizen statement is important, but it should not be confused with an official record. An official record is important, but it should not be assumed true without testing where possible.

Audit Sample

• An audit often cannot test every record. It should choose a sample. The sample must be explained.
• Sampling methods may include:
• Random sample.
• Risk-based sample.
• High-value sample.
• High-complaint sample.
• Geographic sample.
• Time-period sample.
• Vulnerable claimant sample.
• Repeat-failure sample.

For example, a hospital stock audit may sample high-demand essential medicines, medicines with repeated outside purchase complaints, and medicines marked available in the dashboard. A ward audit may sample drains, streetlights, waste routes, project boards, and public spaces. A service guarantee audit may sample applications submitted over a 30-day period and test whether receipts, timelines, written reasons, and appeals were functioning.

The audit should state its limitations. A sample does not prove everything. It indicates patterns and identifies where deeper review is needed.

Service Guarantee Audit

• A service guarantee audit tests whether the citizen-facing promise works.
• Audit items:
• Are requirements publicly displayed?
• Are official fees displayed?
• Are receipts issued at submission?
• Do receipts include tracking numbers?
• Are processing timelines displayed?
• Can status be checked?
• Are written reasons provided for delay or rejection?
• Is an appeal route available?
• Are complaints recorded?
• Is performance data published?
• Do sampled citizen cases match the published standard?

Auditors should conduct citizen test cases where lawful and ethical. They should also review actual cases with consent. If a service says it processes applications in ten days, the audit should check whether applications were actually completed within ten days and whether delays were explained.

Public Land Inventory Audit

A public land inventory audit tests whether listed land exists, whether status is accurate, and whether missing land categories are being hidden.

• Audit items:
• Does the inventory include location, size, legal status, current use, and controlling authority?
• Does it identify original public purpose?
• Does it identify current possession?
• Does it identify leases and allotments?
• Does it identify encroachment?
• Does it identify litigation?
• Does it identify conversion history?
• Do field visits match inventory entries?
• Are public facility sites included?
• Are high-value vacant lands included?
• Is there a correction route?

Auditors should compare maps, official records, field photographs, local testimony, and satellite imagery where available. They should be cautious about declaring ownership disputes without legal verification. The first audit finding may simply be that the public record is incomplete, outdated, or inconsistent with visible use.

Land-Use Conversion Audit

• A land-use conversion audit tests whether land-use changes were disclosed and justified.
• Audit items:
• Was the original use recorded?
• Was the new use recorded?
• Was the approving authority identified?
• Was the legal basis disclosed?
• Was the beneficiary identified?
• Was valuation considered?
• Was public-purpose justification provided?
• Was environmental or infrastructure impact reviewed?
• Were conditions imposed?
• Were conditions complied with?
• Was public consultation held where required?

This audit is especially important where public or ecological land appears to have become private commercial value. The audit should avoid assuming illegality. It should ask whether the record proving legality, public purpose, and compliance exists.

Female-Heir Inheritance Safeguard Audit

• A female-heir safeguard audit tests whether women are actually being identified, informed, and protected in inheritance procedures.
• Audit items:
• Are all heirs listed?
• Are female heirs separately identified?
• Were female heirs notified?
• Were shares explained in plain language?
• Were copies of records provided where required?
• Were relinquishments recorded?
• Was consent verified separately?
• Was legal aid information provided?
• Were coercion complaints recorded?
• Were aggregate female-heir statistics published?

Auditors must protect privacy. Individual inheritance cases should not be publicized without careful consent. The audit should generally report aggregate findings and anonymized case patterns.

Wage Compliance Audit

• A wage compliance audit tests whether workers were paid as recorded, especially in public contracts.
• Audit items:
• Does the employer or contractor maintain wage records?
• Do workers confirm payment?
• Do payment records match worker statements?
• Were deductions lawful and recorded?
• Were subcontractor workers included?
• Were final wages paid?
• Were wage complaints recorded?
• Were retaliation risks assessed?
• For public contracts, was wage compliance certified before final payment?
• Did the public authority review unresolved complaints?

Auditors should speak to workers privately where safe. Group interviews may expose workers to retaliation. Payment proof should be reviewed carefully. A signed receipt may not be reliable if the worker claims it was forced or signed without payment.

Hospital Medicine Stock Audit

• A hospital stock audit tests whether medicine availability records match patient reality.
• Audit items:
• Is the essential medicine list public?
• Is stock status updated?
• Are stockout days recorded?
• Do pharmacy records match public availability boards?
• Do patients report being sent outside for listed medicines?
• Are outside purchase cases recorded?
• Are expiry and near-expiry medicines tracked?
• Is replenishment date provided?
• Are official fees displayed?
• Are patient complaints tracked?

The audit should avoid blaming doctors automatically. Medicine failure may occur in budget, procurement, supplier delivery, storage, pharmacy management, prescribing, or distribution. The audit should identify where the chain appears to fail.

Police Complaint Access Audit

• A police access audit tests whether citizens can approach police and receive a record.
• Audit items:
• Is a complaint reception register maintained?
• Are written acknowledgments issued?
• Are complaint numbers provided?
• Are non-registration reasons written?
• Are referral records issued?
• Is senior review available?
• Are vulnerable complainants handled privately?
• Are domestic violence protocols followed?
• Are land threat or labor intimidation complaints recorded?
• Are aggregate complaint access data published?

Citizen test cases in policing are sensitive and should be conducted only with legal and safety advice. Auditors should not create false complaints. They may review real complaint experiences with consent and compare them to official records.

Court Delay Data Audit

• A court delay audit tests whether delay data is complete and meaningful.
• Audit items:
• Are pending cases counted by category?
• Are cases aged by duration?
• Are adjournment reasons recorded?
• Is government litigation identified?
• Are interim order durations tracked?
• Is execution pendency tracked?
• Are high-volume justice categories separated?
• Are vulnerable claimant categories protected and aggregated?
• Are dashboards updated?
• Do data samples match case records?

This audit should respect judicial independence while still testing whether time is visible. It should focus on data integrity and system performance, not attacking judges personally.

Ward Ledger Audit

• A ward ledger audit tests whether local government records match the street.
• Audit items:
• Does the ward profile exist?
• Is the boundary clear?
• Is the budget published?
• Are local projects listed?
• Do project boards exist at sites?
• Do boards show cost, contractor, scope, and timeline?
• Are complaint numbers issued?
• Do complaint statuses match field conditions?
• Are drain cleaning schedules accurate?
• Are streetlight repair records accurate?
• Are waste collection routes followed?
• Are parks and public spaces accurately recorded?
• This audit is highly practical because citizens can verify many items with photographs, dates, and locations.

Education Capability Audit

• An education audit tests whether learning data is real, not decorative.
• Audit items:
• Are reading assessments conducted?
• Are writing assessments conducted?
• Are numeracy assessments conducted?
• Are results age-appropriate?
• Are results shared with parents?
• Are students below grade level identified?
• Is remedial support actually provided?
• Do attendance records match classroom reality?
• Do teacher support records exist?
• Do school dashboard claims match sampled student capability?
• Auditors should not humiliate children or teachers. Student privacy must be protected. The goal is learning repair, not public shaming.

Procurement Disclosure Audit

• A procurement audit tests whether public contracts are traceable.
• Audit items:
• Is tender notice public?
• Is bidder list public?
• Is winning bidder named?
• Is contract value disclosed?
• Is scope disclosed?
• Are variation orders disclosed?
• Is payment status disclosed?
• Is inspection or completion record available?
• Is beneficial ownership disclosed where required?
• Does field delivery match contract claims?
• Are contractor wage records reviewed?
• The audit should test both paperwork and delivery. A contract can look correct on paper while public value is weak.

Tax Expenditure Audit

• A tax expenditure audit tests whether fiscal privileges are disclosed and reviewed.
• Audit items:
• Are concessions listed?
• Is legal basis identified?
• Is beneficiary category identified?
• Is fiscal cost estimated?
• Is public purpose stated?
• Is performance condition defined?
• Is review or sunset date provided?
• Was last review conducted?
• Are high-capacity beneficiaries separated from vulnerable groups?
• Is public version readable?

This audit may be more technical. It should still produce public-language findings. The public deserves to know which privileges exist and what they cost.

Media Follow-Up Audit

• A media follow-up audit tests whether major public-interest stories were followed until remedy or documented non-compliance.
• Audit items:
• Was the original issue recorded?
• Were authority responses tracked?
• Were records requested?
• Were committees or inquiries tracked?
• Were promises given deadlines?
• Were remedies verified?
• Were corrections published?
• Were conflicts disclosed?
• Did the story receive follow-up after 30, 90, or 180 days?
• Did coverage protect vulnerable claimants?
• Media must also be accountable to public memory.

Claimant Protection Audit

• A claimant protection audit tests whether public accounting work itself is ethical.
• Audit items:
• Were consent records obtained?
• Were privacy levels assigned?
• Were vulnerable claimants anonymized?
• Were retaliation risks assessed?
• Were children protected?
• Were medical details protected?
• Were women's inheritance or violence cases handled safely?
• Were workers protected from employer retaliation?
• Were public reports redacted?
• Were corrections issued when needed?

This audit should be mandatory for citizen groups and media platforms using public accounting methods. Accountability work must not harm claimants.

Audit Fieldwork Rules

• Fieldwork should be disciplined and safe.
• Rules:
• Do not trespass.
• Do not provoke confrontation.
• Do not photograph private persons unnecessarily.
• Do not expose vulnerable claimants.
• Do not enter dangerous sites without support.
• Do not impersonate officials.
• Do not offer bribes or unofficial payments.
• Do not create false complaints.
• Do not pressure citizens to speak.
• Do not publish field notes before review.
• Fieldwork should collect evidence, not drama.

Official Right of Reply

• Before final publication, the audited institution should receive draft findings where safe and appropriate.
• The right of reply should include:
• Findings shared.
• Evidence summary.
• Response deadline.
• Correction invitation.
• Official explanation requested.
• Response included in final report.

If the institution does not respond, the report should say so. If it provides valid correction, the report should correct. If it provides excuses without records, the report should identify that.

Audit Scoring

• An audit can use a simple scoring system.
• Score 0: no record or process exists.
• Score 1: record exists internally but is not usable by citizens.
• Score 2: record is public but incomplete, outdated, or not tied to remedy.
• Score 3: record is public, updated, and citizens can use complaint or correction routes.
• Score 4: record is public, updated, verified, tied to performance, and linked to remedy or consequence.
• Scores should be supported by evidence notes. Do not score by impression. Score by record and reality.

Audit Report Structure

• A public accounting audit report should be clear.
• Recommended structure:
• Audit title.
• Scope.
• Period covered.
• Method.
• Records reviewed.
• Sample selected.
• Fieldwork conducted.
• Citizen cases reviewed.
• Privacy safeguards.
• Key findings.
• Official response.
• Corrections made.
• Unresolved issues.
• Recommendations.
• Remedy tracker.
• Next audit date.
• The report should include enough evidence to be credible but not expose private data.

Audit Recommendations

Recommendations should be specific and time-bound.

Weak recommendation:

"The department should improve transparency."

Stronger recommendation:

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.

Within 30 days, the department should publish the official fee, required documents, processing timeline, receipt process, written-reason format, and appeal route for the pension service.

Weak recommendation:

"The hospital should fix medicine problems."

Stronger recommendation:

Within 14 days, the hospital should publish the essential medicine stock board, record outside purchase cases, and report stockout days for the top 50 essential medicines.

Specific recommendations create follow-up.

Remedy Tracker

• Every audit should include a remedy tracker.
• The tracker should show:
• Finding.
• Recommended remedy.
• Responsible authority.
• Deadline.
• Status.
• Evidence of completion.
• Citizen impact.
• Next follow-up.
• An audit without follow-up becomes another report. A remedy tracker turns findings into pressure.

Audit Ethics

• Auditors must follow the public accounting ethics code.
• They must:
• Tell the truth.
• Protect claimants.
• Distinguish allegation from finding.
• Avoid reckless accusation.
• Seek response where safe.
• Correct errors.
• Disclose conflicts.
• Protect data.
• Avoid political manipulation.
• Use language that reveals duty.
• An audit that violates these standards can damage the movement it claims to serve.

Audit Team Roles

• A good audit team should include defined roles.
• Lead auditor.
• Records reviewer.
• Fieldwork lead.
• Data analyst.
• Legal or rights reviewer.
• Privacy and safety reviewer.
• Official liaison.
• Report writer.
• Correction reviewer.
• In small projects, one person may hold multiple roles, but privacy and evidence review should not be ignored.

Audit Calendar

• Public accounting audits should be repeated. One audit creates a snapshot. Repeated audits create pressure.
• Possible calendar:
• Monthly for medicine stock and ward complaints.
• Quarterly for service guarantees, police access, wage recovery, and local projects.
• Six-monthly for education capability, court-delay data, and public project performance.
• Annually for land inventory, tax expenditures, procurement systems, and public enterprise support.
• The update cycle should match the issue. Fast-changing services need frequent audits. Structural ledgers may need annual review.

Audit of Digital Systems

• Digital systems need special audit.
• Audit questions:
• Can citizens access the system?
• Does the system issue receipts?
• Does status update meaningfully?
• Can citizens correct errors?
• Is there an appeal route?
• Is personal data protected?
• Are records searchable?
• Are dashboards updated?
• Do digital records match physical files?
• Are offline citizens excluded?
• Are system errors recorded?
• A portal is not accountability unless it changes the citizen's power.

Audit of Record Correction

• A record system should allow correction. The audit should test this.
• Questions:
• Can citizens request correction?
• Is there a correction form?
• Is a tracking number issued?
• Is there a timeline?
• Are written reasons provided if correction is denied?
• Can denial be appealed?
• Are corrections reflected across linked records?
• Are vulnerable citizens assisted?
• A wrong public record without correction route can become a weapon.

Audit of Official Communication

• An institution may publish records but communicate poorly. The audit should check whether citizens can understand what is published.
• Questions:
• Is language clear?
• Are technical terms explained?
• Are local languages used where needed?
• Are notices visible?
• Are fees and timelines easy to find?
• Are complaint routes displayed?
• Are disabled citizens accommodated?
• Are non-digital citizens assisted?
• Transparency that citizens cannot understand is incomplete.

Audit of Public Meetings

• If local governments or institutions hold public meetings, the audit should test whether meetings produce records.
• Questions:
• Was notice given?
• Who attended?
• Were minutes prepared?
• Were issues recorded?
• Were commitments assigned deadlines?
• Was follow-up published?
• Were citizens able to speak safely?
• Were vulnerable groups represented?
• A meeting without a record is often performance.

Audit of Committees

• Committees should be audited because they often absorb public anger.
• Questions:
• When was the committee formed?
• What were its terms of reference?
• Who were the members?
• What was the deadline?
• Did it have power to request records?
• Did it receive public submissions?
• Did it submit a report?
• Was the report published?
• Were recommendations implemented?
• If not, why?
• A committee without output should not be treated as action.

Public Participation in Audits

• Citizens can help audit public systems, but participation must be structured.
• Citizens can provide:
• Photographs.
• Complaint numbers.
• Receipts.
• Timeline evidence.
• Service experiences.
• Field observations.
• Public project board checks.
• Stockout reports.
• Ward issue locations.
• Workers' payment evidence.
• Citizens should not be asked to make legal conclusions. They provide evidence and experience. The audit team verifies and frames.

Handling Disputed Findings

• Some findings will be disputed. The audit report should not hide disputes.
• For disputed findings, state:
• Finding.
• Evidence supporting it.
• Institution's response.
• Auditor's assessment.
• Remaining uncertainty.
• Further records needed.
• Next review date.
• This is more credible than pretending every disagreement is settled.

Audit Red Flags

• Certain patterns require deeper investigation.
• Red flags include:
• Records exist but are not updated.
• Receipts issued without status movement.
• High rejection rates without written reasons.
• Repeated stockouts of the same medicines.
• Public projects without boards.
• Large variation orders without explanation.
• High female-heir relinquishment rates.
• Wage compliance certificates contradicted by worker claims.
• Police complaint refusal without written reasons.
• Court cases pending under old interim orders.
• Tax concessions without review dates.
• Ward complaints marked resolved while field conditions remain unchanged.
• Red flags are not final proof. They are signals for further review.

Model Audit Plan

Audit title: [Insert]
Domain: [Insert]
Institution or location: [Insert]
Period covered: [Insert]
Audit questions: [Insert]
Records requested: [Insert]
Records received: [Insert]
Sample method: [Insert]
Fieldwork plan: [Insert]
Citizen cases included: [Insert]
Privacy safeguards: [Insert]
Official response plan: [Insert]
Report deadline: [Insert]
Follow-up date: [Insert]

Model Audit Finding

Finding number: [Insert]
Domain: [Insert]
Issue: [Insert]
Evidence reviewed: [Insert]
What the record says: [Insert]
What fieldwork or citizen evidence shows: [Insert]
Gap identified: [Insert]
Institution response: [Insert]
Audit assessment: [Insert]
Recommended remedy: [Insert]
Deadline: [Insert]
Privacy level: [Insert]
Status: [Open, resolved, disputed, pending]

Model Audit Score Entry

Indicator: [Insert]
Score: [0 to 4]
Reason for score: [Insert]
Evidence: [Insert]
Institution response: [Insert]
Recommended improvement: [Insert]
Next review: [Insert]