Product Requirement Document

1. Product overview

PakoReady: Offline Emergency Decision and Response Guide is an Android educational preparedness application for students, households and communities in the Philippines. It combines offline reference guides for earthquakes, fires, floods, typhoons and landslides with a question-based decision guide, emergency kit checklist, preparedness assessment, emergency contacts and a local evacuation directory. The companion webpage introduces the application, provides the APK and installation instructions, and exposes these requirements through Help dialogs.

2. Problem and intended users

Preparedness information and household planning details can be scattered or unavailable when connectivity is limited. PakoReady places reference information and personal planning tools on one device. Primary users are Filipino students and household members. The developer maintains the content and release files; there is no separate administrator account or remote management console.

3. Goals and scope

Enable users to read five hazard guides offline, organize 21 listed kit supplies, assess five preparedness questions, retain three local contacts, and maintain local facility records. Provide clear navigation and explain the limits of educational guidance. Live alerts, live hazard assessment, responder dispatch, automatic calling, location transmission, verified facility availability, iOS delivery and cloud synchronization are outside this release.

4. Functional requirements

PR-01 — Home shall provide access to Safety guides, Decision guide, Emergency kit, Contacts, Preparedness, Evacuation, and About & safety information. Each module shall provide Back / Home navigation.

PR-02 — Safety guides shall cover all five hazards and organize content into before, during, after, actions to avoid, seeking help and sources. Bundled guide text shall remain available without internet.

PR-03 — Decision guide shall accept a hazard selection and Yes/No answers, display the corresponding educational guidance, and allow restarting. It shall tell users to act on immediate danger and follow current official instructions.

PR-04 — Emergency kit shall show 21 selectable supplies, progress, remaining needs, a mark-all action and a confirmed reset. Individual checklist states shall survive closing and reopening the application.

PR-05 — Preparedness shall require answers to all five questions before scoring, display the score and recommendations, retain the latest result, and allow a retake. Scores shall be described as self-reported education, not certification.

PR-06 — Contacts shall provide a user-initiated dialer action for the displayed emergency number and three editable local contacts. Names and numbers (3–15 digits, optional leading plus and ordinary formatting) shall be validated before saving; clearing saved contacts shall require confirmation. Opening a dialer shall not place a call automatically.

PR-07 — Evacuation shall distinguish sample templates from user-entered records, support searching and selecting entries, and permit adding and removing local records. Map search shall be a user action using the selected public address. No record shall be represented as proof of current operating or safety status.

PR-08 — About shall explain purpose, offline limitations, local data and reference links. The website Help menu shall open PRD and TRD in labeled, scrollable popup dialogs and provide standalone document links.

5. User journeys

A new user visits the landing page, reads the installation instructions, downloads the APK and opens Home. The user reviews a hazard guide, marks available kit supplies, saves a household contact and takes the assessment. Later the user reopens the app to review retained planning data. External calls, maps and reference pages require the appropriate device applications and connectivity.

6. Quality and acceptance criteria

Acceptance requires all five guide topics to open with connectivity disabled; kit ticks, contacts, directory records and the latest assessment to persist after restart; incomplete assessment answers and invalid contacts to be rejected; and sample records to remain visibly identified. Website acceptance requires both Help documents to open, scroll, close with the close button or Escape, restore focus, and remain usable on narrow screens. These are acceptance requirements; the verification record identifies which checks have actually been performed.

7. Content, privacy and release criteria

Guide changes require review against the cited authoritative source material and a new APK build. Personal planning entries remain in device-local TinyDB storage; clearing application data or uninstalling can remove them. A submission release needs the proposal PDF, source AIA, APK, listing assets, full webpage screenshot, public landing-page URL and public shared asset-folder URL. A signed release AAB and genuine screen captures are release evidence, not features that can be assumed from a draft document.

8. Success measures and dependencies

Release targets are five accessible guide topics, seven reachable Home destinations, successful restart persistence for all four stored data groups, and two working Help dialogs. No adoption statistics or field effectiveness measurements have been collected. Dependencies include a compatible Android device, App Inventor tooling for rebuilds, and external browser, dialer or maps applications for optional actions.