Repository navigation
Question SW 06
SW-06 How will a person's request for supplies or assistance reach a responsible relief operator and show what has actually happened?
Start here · Questions · Progress · People decide
Sending a request, a person accepting it and help arriving are distinct steps. Clear progress helps residents and crews decide what to do next.
Draw the request's journey from draft to delivery, acknowledgement, acceptance, handover and closure. Set out privacy, consent, repeated requests, expiry, withdrawal and escalation. Demonstrate a power cut, a duplicate request, an unavailable recipient and an urgent request still awaiting acknowledgement.
- comprehensive rebuild plan — reviewed source; public copy can be added through the evidence process
- site-data.js (supplier-request, risk-incident and run-sheet definitions)
- Aura_Teacher_Training_60_Days.pdf (p.55)
- Professional review and comparison of proposed improvements (When this work overlaps professional or public-authority responsibilities, compare the proposal and Luke's research with applicable industry/global best practice and relevant legal-engine sources. Record differences, reasonable improvements and deficiencies, with the responsible reviewer and response. Routine authorised drafting and wiki work can advance.)
- Council plan crosswalk and proposed Aura integration (Relevant question row identifies the management/recovery source section and printed/PDF page. AI-generated analysis, 21 October 2026; proposed checks and actual review/operating agreements retain separate status.)
For discussion and review · research checked 2026-10-20. These are AI-generated options and transfer assessments. The user's request and research method identify the source of this work. The source catalogue states what the references establish. The decision and approval record retains its own status.
Create a private request with an understandable receipt and separate milestones for saved, sent, received, accepted, handed over and closed. The agreed receiving service would own acceptance and escalation. A waiting request would explain current contact options and its last confirmed status.
AI-generated adaptation of an existing pattern. Trial ODK for a structured, consent-based non-emergency request. Add the operator's acceptance and fulfilment records separately, so a server upload cannot be presented as help being assigned or on its way.
Research basis: ODK Collect: managing draft, ready-to-send and sent forms · RFC 9171: Bundle Protocol Version 7.
AI-generated future concept. Explore a personal Aura tracking an approved request's receipts and preparing a reminder or alternate contact proposal. People would retain the choice to disclose more information or approve a changed recipient.
Research basis: Solid FAQ: personal data sharing, storage and copies · NIST AI Risk Management Framework 1.0: core functions.
- ODK Collect: managing draft, ready-to-send and sent forms: AI transfer assessment: Offline forms distinguish content waiting to send from content transmitted to a server. Local difference to check: Relief operators must separately agree supported needs, staffing, response expectations and what constitutes acceptance or completed assistance.
- Rehearse repeated submissions, a power interruption, withdrawn consent and an unavailable recipient using fictional records.
- Agree urgent-help wording and escalation with the responsible services, then observe whether visitors understand the receipt.
Who reviews: Proposed relief coordination lead and request service owner (unconfirmed)
Connected questions: DAT-01, SW-02, SW-05
Work state: open. Assigned person or AI assistant: Ready to be assigned.
Research and alternatives can move ahead while connected decisions develop. Before acting on a choice, check the people, evidence and approved scope in People decide.
Growing capability together · Planning and design underway · People decide · Repository
Aura Disaster Resilience
- Start here
- The whole system
- About and topic slugs
- First choices
- All-weather design
- Questions
- Progress
- Working together
- People decide
- Professional review
- AI assistant jobs
- Council integration
- Council plan crosswalk
- Guardian IMS and QIT Plus
- Ecosystem
- Agreed direction
- Evidence
- Source library
- AI research and prompt
- Research sources
- Useful words/glossary
- Rights and discovery
Work areas
- Everyday service and disaster work
- Weather-ready kiosks and places
- Energy and backup power
- Connections and messages
- Information people can trust
- Software and device care
- Personal Aura and learning
- Place models and practice exercises
- Community and operating responsibility
- Budget and continuing support
- Tests and field learning
- Project connections
- Working together and human review