Loading...
Community presentation
# RESQ-AI — Hackathon PPT Prompt (FINAL) ## CONTEXT — READ FIRST This is an **ASYNC PPT SUBMISSION**. There is no presenter, no live pitch, no Q&A. Judges open the file cold and…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
# RESQ-AI — Hackathon PPT Prompt (FINAL) ## CONTEXT — READ FIRST This is an **ASYNC PPT SUBMISSION**. There is no presenter, no live pitch, no Q&A. Judges open the file cold and decide shortlist-or-not in under 3–5 minutes, skimming each slide for roughly 60–90 seconds. Every slide must fully carry its own point — no relying on verbal explanation. One short caption per slide replaces the presenter. Keep captions to one line, ~12 words max. **Current build status: CONCEPT STAGE. Nothing is built yet.** Never use "prototype" for anything functional. Never show a screen as if it's a real working product. Use this language instead: - `CONCEPT` — for the overall idea - `CONCEPT INTERFACE — NOT YET BUILT` — for the GIS command center slide - `PROPOSED ARCHITECTURE` — for the tech stack slide - `ILLUSTRATIVE SCENARIO · EXAMPLE CALCULATION` — for the flood scenario and its risk score (94 / 95 out of 100 are worked examples, not live system output) - Status framing where relevant: "Concept + UX direction validated this round, engineering build is next phase." Any "concept only" tag must be large and visually unmissable, never fine print. --- ## PRODUCT STORY RESQ-AI — AI-Powered Disaster Response & Rescue Coordination. Flow: Disaster → Citizen SOS → Data → Risk Analysis → AI Decision → Priority GIS Zone → Recommended Response → Rescue Team Assignment → Coordinated Response Tagline: FROM SOS TO THE NEXT BEST ACTION. --- ## STYLE CLASSY + PREMIUM + MODERN + MINIMAL + EDITORIAL. Apple keynote × premium editorial magazine × modern AI product × emergency operations center. No neon, no cyberpunk, no gaming UI, no glassmorphism overload, no generic corporate template, no walls of text, no 8+ bullet lists, no screenshots claiming to be a real working product, no animations (deck may be viewed as static PDF — every slide must work as a still image). **Palette:** deep charcoal, warm black, soft ivory, off-white, graphite, stone gray, muted emergency red (sparing use only), subtle burgundy, restrained navy. **Typography:** large confident headlines, small uppercase metadata, big numbers as design elements, generous whitespace, intentional alignment. **Signature overlay — apply identically to every slide, no exceptions:** 1. Faint geographic grid/contour-line texture behind content, ~4–8% opacity, graphite/stone gray 2. Small thin crosshair/reticle mark, same corner, same size, every slide 3. Thin single rule under every slide's headline Nothing else added per-slide beyond these three — restraint is the design choice. **Slide rule:** 1 headline + 1 hero visual + 1 caption sentence + 2–4 supporting labels max. Test: "would a judge understand this in 60 seconds, alone, with no narration?" If not, simplify — don't add more text. --- ## SLIDE-BY-SLIDE CONTENT (11 slides, no repeated ideas) **Slide 1 — Hero** RESQ-AI — From SOS to the Next Best Action Presenter: [name] · Date: [date] Overview: AI-powered disaster response and rescue coordination, connecting citizen SOS to coordinated action. Status: CONCEPT SUBMISSION — HACKATHON PPT ROUND **Slide 2 — Problem** Fragmented signals delay decisive response Fragment 1: Fragmented citizen SOS Fragment 2: Disconnected response data Fragment 3: Delayed risk prioritization Fragment 4: Uncoordinated rescue assignment Caption: Every extra minute of fragmented data costs response time. Impact stat: [STAT TBD — add real sourced number if available, do not fabricate] **Slide 3 — Solution (the ONE full flow diagram — appears in full only here)** One connected path from SOS to action Flow: Disaster → Citizen SOS → Data → Risk Analysis → AI Decision → Priority GIS Zone → Recommended Response → Rescue Team Assignment → Coordinated Response Input: Disaster and citizen signals Intelligence: Risk analysis and AI decision Action: Assignment and coordinated response Caption: Turning fragmented emergency data into coordinated response decisions. **Slide 4 — Differentiation** Most tools stop at alerting Tag: DIFFERENTIATION Fragment 1: Existing tools — Detect → Alert → [stops] Fragment 2: RESQ-AI — Detect → Analyze → Decide → Act Caption: Other tools flag disasters. RESQ-AI recommends the next move. **Slide 5 — Scenario** A flood just hit Tag: ILLUSTRATIVE SCENARIO · EXAMPLE CALCULATION Metadata: Incident #RX-104 Flow: Flood event → Citizen SOS points → Risk analysis → Priority GIS zone → Recommended response Labels: 40 people at risk · Medical emergency · Severe flooding · Rising water Result: 94 Risk Score · P1/Critical Recommended: Rescue + Medical Response Caption: One signal, one score, one recommended action. **Slide 6 — Decision Engine** Why 94? Tag: Sample scoring model — weights are illustrative Fragment 1: Population risk +25 Fragment 2: Disaster severity +25 Fragment 3: Medical emergency +20 Fragment 4: Infrastructure +15 Fragment 5: Weather +10 Result: 95/100 Critical Situation: Severe flooding + high population risk + medical emergency. Next Best Action: Rescue · Medical · Evacuation Caption: Explainable risk, not a black box. **Slide 7 — GIS Command Center** GIS command center for coordinated response Tag: CONCEPT INTERFACE — NOT YET BUILT Proposed UI: GIS map, priority zone, SOS context, response recommendation Labels: Map · Priority · Recommendation · Assignment AI Decision: 94 · P1/Critical · 40 at risk · Medical: 02 Fragment 1: 127 people at risk Fragment 2: 05 incidents Fragment 3: 18 teams Fragment 4: 08m est. response Caption: A shared geographic view connects decisions with rescue coordination. **Slide 8 — Decision to Action** Decision becomes coordinated field action Action chain: AI Decision → Priority GIS Zone → Recommended Response → Rescue Team Assignment → Coordinated Response Decide: Convert analysis into action Locate: Identify the priority zone Assign: Connect response with rescue teams Recommends: Rescue · Medical · Evacuation · Supplies Status: Team Assigned · ETA 08 min Caption: The output is an assigned response, not another alert. **Slide 9 — Technology** PROPOSED ARCHITECTURE | Layer | Role | |---|---| | Frontend | React + TypeScript | | Backend | FastAPI + Python | | Intelligence | RESQ-AI Decision Engine — risk scoring, AI analysis, priority detection | | Data | PostgreSQL + PostGIS | | Operations | GIS Command Center, rescue coordination | Labels: Leaflet GIS · Recharts · AI/LLM Integration · Future External APIs Caption: Engineering build begins next phase. **Slide 10 — Status** Concept to build Current status: Concept + UX direction validated this round Next phase: Engineering build Status line: CONCEPT VALIDATED · BUILD PHASE NEXT Caption: The response model is defined; implementation is the next phase. **Slide 11 — Closing** RESQ-AI — From SOS to the Next Best Action Tagline: FROM SOS TO THE NEXT BEST ACTION. Closing flow: Citizen SOS → Risk Analysis → AI Decision → Coordinated Response Status: CONCEPT VALIDATED · BUILD PHASE NEXT Caption: Disaster response moves from fragmented signals to coordinated action. --- ## OPEN ITEM - [ ] Impact stat (slide 2): real, sourced number on disaster response coordination delays. Leave as [STAT TBD] if not sourced — never fabricate. ## FINAL CHECK Every slide understandable alone in under a minute, no narration. Overlay identical across all 11 slides. No slide repeats another slide's core idea (flow diagram appears in full once — slide 3 — plus one small closing callback on slide 11). Numbers/architecture are specific, not vague.
Presentation overview
This community presentation was shared by Utkarsh Sharma as a complete 11-slide example. # RESQ-AI — Hackathon PPT Prompt (FINAL) ## CONTEXT — READ FIRST This is an **ASYNC PPT SUBMISSION**. There is no presenter, no live pitch, no Q&A. Judges open the file cold and… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
