Poway Neighborhood Emergency Corps 2026–2027
CSP capstone continuing the PNEC project with proposed household preparedness, volunteer coordination, and community information tools.
CSP 2026–2027 · Samanvi, Joan, and Ainsley. We are continuing the previous PNEC team’s project. Our team proposes the features below to extend the inherited project, with scope and implementation to be reviewed with PNEC.
Poway Neighborhood Emergency Corps 2026–2027
We chose PNEC to help our community prepare for emergencies. Our team identified wildfires, high temperatures, and earthquakes as reasons to make preparedness information and planning easier to access. The project combines community impact with opportunities to build useful technical skills.
Existing Project SiteExtend the existing information platform with personalized household planning, preparedness learning, volunteer coordination, and community feedback. These features are proposed work for our team.
Team Feature PlanThe previous team's handoff describes Risk Watch, the Helper Bot, a neighborhood map, member accounts, and a browser-based site editor. We will review these inherited features before extending them.
Previous Team's HandoffOur proposed direction connects preparedness information with saved plans, learning activities, volunteer tasks, and feedback from residents.
Proposed ImprovementsProposed improvements
Save a personalized checklist to each resident account for a 72-hour kit, evacuation plan, and meeting point. Show household progress and remaining tasks alongside the existing preparedness information.
Proposed acceptance check: Completed tasks remain saved after signing in again, progress updates correctly, and each household sees only its own checklist.
Ask residents 8–10 questions about their emergency kit, evacuation route, and other preparedness steps. Show a preparedness score and the top actions suggested by their answers.
Proposed acceptance check: All questions can be answered with a keyboard, the same answers produce the same score, and recommendations match the gaps identified. The score describes quiz responses, not a guarantee of safety.
Let coordinators post door-to-door check-ins, supply drives, and CERT training sessions. Residents and volunteers can claim available slots.
Proposed acceptance check: A volunteer can sign up or cancel, the remaining capacity stays accurate, and filled slots cannot be overbooked.
Let residents mark themselves as safe or needing help by neighborhood, with their update visible to their coordinator.
Proposed acceptance check: A resident can update their status and timestamp, and only authorized coordinators can view their neighborhood’s reports. The page clearly explains that a check-in does not contact emergency services.
Offer key pages such as Risk Watch, evacuation information, and the Helper Bot in Spanish and additional languages selected with PNEC. Explore translation support with review of critical information.
Proposed acceptance check: A language selector opens the corresponding content, missing translations are clearly identified, and critical preparedness wording is reviewed before publication.
List current needs such as flashlights, water, and first-aid kits, with a running progress tracker so residents and local businesses can see how to contribute.
Proposed acceptance check: Each drive shows its item, goal, and recorded progress. Authorized volunteers can update totals, and pledges are distinguished from supplies received.
Provide a resident form for reporting a downed tree, blocked evacuation route, or broken fire hydrant. Route the report to the relevant coordinator or admin dashboard.
Proposed acceptance check: Required location and description fields are validated, submitted reports appear for the authorized coordinator, and the form distinguishes community reports from urgent emergency requests.
Add a “Was this helpful?” option and a way to submit questions that stump the Helper Bot. Volunteers can review gaps and improve the knowledge base.
Proposed acceptance check: Feedback is saved, unanswered questions appear in a volunteer review queue, and reviewed FAQ changes can be tracked.
Publish weekly preparedness tips and volunteer or learning events. Adapt the topics to current community threats, such as flood preparedness during flooding.
Proposed acceptance check: Each update shows a publication date, relevant sources, and upcoming event details. Authorized volunteers can review and update time-sensitive content.
Team and review process
Scrum Master / Developer
Technologist / Developer 1
Technologist / Developer 2
Iteration process
1 · Investigate and scope
Review the inherited repositories and handoff, reproduce a user problem, and discuss priorities with PNEC. Record the selected scope, owner, and acceptance checks in an issue.
2 · Build and test
Implement one agreed improvement in a small branch. Test the main workflow, failure cases, keyboard navigation, and phone layouts. Keep screenshots and results with the issue.
3 · Review and revise
Open a focused PR with the problem, changes, and actual test results. Have a teammate review it, address feedback, and record the next iteration before the class review.
Evidence for the next iteration
This PR updates the capstone overview only. Feature implementation and stakeholder validation remain future work. The team feature plan is linked above. Subsequent updates should record the selected scope, each teammate’s contributions, test results, and review feedback.
Powered by OCS grids and buttons
| Buttons | Grids |