@@ -10,18 +10,15 @@ export interface AttendeeGroup {
 }
 
 /**
- * Projects first (by attendee count, then title), then "New to Code for
- * Philly", "Looking for a project", "Not sure yet" — each only when
- * non-empty. When nobody has answered, one unlabelled group.
+ * Members who haven't answered first, unlabelled (any label reads as doubt
+ * about attending); then projects (by attendee count, then title), then "New
+ * to Code for Philly", "No project yet" — each only when non-empty.
  */
 export function groupAttendees(rsvps: EventRsvp[]): AttendeeGroup[] {
-  if (rsvps.every((r) => r.plan === null)) {
-    return rsvps.length ? [{ key: 'all', label: null, people: rsvps }] : [];
-  }
   const projects = new Map<string, AttendeeGroup>();
   const newcomers: EventRsvp[] = [];
   const looking: EventRsvp[] = [];
-  const unsure: EventRsvp[] = [];
+  const unanswered: EventRsvp[] = [];
   for (const r of rsvps) {
     if (r.plan === 'project' && r.project) {
       const g = projects.get(r.project.slug) ?? {
@@ -34,13 +31,16 @@ export function groupAttendees(rsvps: EventRsvp[]): AttendeeGroup[] {
       projects.set(r.project.slug, g);
     } else if (r.plan === 'newcomer') newcomers.push(r);
     else if (r.plan === 'no_project') looking.push(r);
-    else unsure.push(r);
+    else unanswered.push(r);
   }
-  const groups = [...projects.values()].sort(
+  const groups: AttendeeGroup[] = unanswered.length
+    ? [{ key: 'unanswered', label: null, people: unanswered }]
+    : [];
+  const byProject = [...projects.values()].sort(
     (a, b) => b.people.length - a.people.length || (a.label ?? '').localeCompare(b.label ?? ''),
   );
+  groups.push(...byProject);
   if (newcomers.length) groups.push({ key: 'newcomer', label: 'New to Code for Philly', people: newcomers });
-  if (looking.length) groups.push({ key: 'no_project', label: 'Looking for a project', people: looking });
-  if (unsure.length) groups.push({ key: 'unsure', label: 'Not sure yet', people: unsure });
+  if (looking.length) groups.push({ key: 'no_project', label: 'No project yet', people: looking });
   return groups;
 }
@@ -462,13 +462,9 @@ export function EventDetail() {
                 <>
                   <p className="flex flex-wrap items-center gap-3">
                     <span className="text-lg font-semibold text-green-700">You&rsquo;re going ✓</span>
-                    <button
-                      type="button"
-                      className="text-sm text-muted-foreground hover:underline"
-                      onClick={() => setWithdrawOpen(true)}
-                    >
-                      Can&rsquo;t make it?
-                    </button>
+                    <Button variant="outline" size="sm" onClick={() => setWithdrawOpen(true)}>
+                      Cancel RSVP
+                    </Button>
                   </p>
                   <FollowUp
                     plan={event.viewerRsvp?.plan ?? null}
@@ -614,15 +610,15 @@ export function EventDetail() {
         <Dialog open={withdrawOpen} onOpenChange={setWithdrawOpen}>
           <DialogContent>
             <DialogHeader>
-              <DialogTitle>Withdraw your RSVP?</DialogTitle>
+              <DialogTitle>Cancel your RSVP?</DialogTitle>
               <DialogDescription>You&rsquo;ll be removed from the attendee list for “{event.title}”.</DialogDescription>
             </DialogHeader>
             <DialogFooter>
               <Button variant="outline" onClick={() => setWithdrawOpen(false)} disabled={rsvpBusy}>
                 Keep my RSVP
               </Button>
               <Button variant="destructive" onClick={() => void doWithdraw()} disabled={rsvpBusy}>
-                {rsvpBusy ? 'Withdrawing…' : "I can't make it"}
+                {rsvpBusy ? 'Cancelling…' : 'Cancel RSVP'}
               </Button>
             </DialogFooter>
           </DialogContent>
 
@@ -123,7 +123,7 @@ describe('EventDetail', () => {
     expect(screen.getByRole('button', { name: 'Change' })).toBeInTheDocument();
   });
 
-  it('going with an answered follow-up shows the selected choice and "Can\'t make it?"', async () => {
+  it('going with an answered follow-up shows the selected choice and "Cancel RSVP"', async () => {
     mockFetch({
       me: USER_ME,
       event: makeEvent({
@@ -133,7 +133,7 @@ describe('EventDetail', () => {
     render();
     expect(await screen.findByText('You’re going ✓')).toBeInTheDocument();
     expect(screen.getByText('I’m coming to work on SquadQuest')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Can’t make it?' })).toBeInTheDocument();
+    expect(screen.getByRole('button', { name: 'Cancel RSVP' })).toBeInTheDocument();
   });
 
   it('project picker: opened empty with nobody named yet shows only the hint; typing searches and Enter saves', async () => {
@@ -208,7 +208,7 @@ describe('EventDetail', () => {
     expect(screen.getByRole('link', { name: '14 going' })).toBeInTheDocument();
   });
 
-  it('groups attendees: projects by count, then newcomers, looking, not sure', async () => {
+  it('groups attendees: unanswered first and unlabelled, then projects by count, newcomers, no project', async () => {
     mockFetch({
       event: makeEvent({ rsvpCount: 6 }),
       rsvps: [
@@ -227,7 +227,10 @@ describe('EventDetail', () => {
     const headings = within(attendees)
       .getAllByRole('heading', { level: 3 })
       .map((h) => h.textContent);
-    expect(headings).toEqual(['Zeta', 'Alpha', 'New to Code for Philly', 'Looking for a project', 'Not sure yet']);
+    expect(headings).toEqual(['Zeta', 'Alpha', 'New to Code for Philly', 'No project yet']);
+    const firstList = within(attendees).getAllByRole('list')[0]!;
+    expect(within(firstList).getByLabelText('Fay')).toBeInTheDocument();
+    expect(within(firstList).queryByLabelText('Ann')).not.toBeInTheDocument();
     expect(within(attendees).getByRole('link', { name: 'Zeta' })).toHaveAttribute('href', '/projects/zeta');
   });
 
 
@@ -0,0 +1,71 @@
+---
+status: done
+pr: 237
+depends: [events-core]
+specs:
+  - specs/behaviors/events.md
+  - specs/screens/event-detail.md
+issues: []
+---
+
+# Plan: Attendee groups and the cancel control, from launch feedback
+
+## Scope
+
+Early feedback in #website-relaunch on the November hack night page:
+
+- A member listed under **Not sure yet** read it as doubt about attending
+  (it meant "hasn't said what they're coming to do"); a second organizer
+  found it unclear too.
+- A member asked for a way to say they're not going: the existing quiet
+  "Can't make it?" link next to "You're going ✓" went unseen.
+- A member asked for "Maybe"; decided against it (an unsure member says
+  yes, adds it to their calendar, and cancels if plans change).
+
+**In:** unanswered attendees listed first, unlabelled, directly under
+"Going (N)"; "Looking for a project" renamed "No project yet" to mirror the
+choice "I don't have a project yet"; "Can't make it?" becomes an outline
+"Cancel RSVP" button with a "Cancel your RSVP?" dialog; the no-maybe
+rationale extended in the spec.
+
+**Out:** "Maybe"; the email copy ("Can't make it? Update your RSVP…"),
+which already points at the page.
+
+## Implements
+
+- [behaviors/events.md](../specs/behaviors/events.md#rsvp) — RSVP and the
+  follow-up groups.
+- [screens/event-detail.md](../specs/screens/event-detail.md) — RSVP block,
+  attendee list, Withdraw action.
+
+## Approach
+
+1. `groupAttendees` puts the unanswered first with `label: null` (the
+   renderer already skips the heading for an unlabelled group); the
+   all-unanswered special case falls out of that.
+2. Swap the text button for a shadcn outline `Button`; reword the dialog.
+
+## Validation
+
+- [x] `npm run type-check && npm run lint && npm test` clean.
+- [x] On an event with mixed answers (component test; devbox has one RSVP), the unanswered avatars sit directly
+  under "Going (N)" and the labelled groups follow.
+- [x] Signed in and going, "Cancel RSVP" shows beside "You're going ✓" and
+  cancels after the dialog.
+
+## Risks / unknowns
+
+- None.
+
+## Notes
+
+- Feedback from Kat Jost and Travis Southard in #website-relaunch after
+  the events launch (2026-10-14). Chris decided: no "Maybe" for now, and
+  the unanswered shouldn't trail the list where they'd look like members
+  of the last labelled group.
+- Checked signed in on the devbox build: "Cancel RSVP" beside "You're
+  going ✓"; the dialog opens with "Keep my RSVP" focused.
+
+## Follow-ups
+
+- **None.**
@@ -76,7 +76,7 @@ An event may carry an **agenda**: an ordered list of time slots within that one
 
 ## RSVP
 
-An RSVP is a public statement by a signed-in member that they're coming. It is **binary**: an `EventRsvp` record exists (going) or it doesn't. There is no "maybe" and no stored "not going" — withdrawing an RSVP deletes the record. Meetup dropped "maybe" years ago for the same reason: it tells organizers nothing.
+An RSVP is a public statement by a signed-in member that they're coming. It is **binary**: an `EventRsvp` record exists (going) or it doesn't. There is no "maybe" and no stored "not going" — withdrawing an RSVP deletes the record. Meetup dropped "maybe" years ago for the same reason: it tells organizers nothing. Someone unsure says yes, adds the event to their calendar, and cancels if plans change; cancelling is one visible button on the event page, and the event description asks people to cancel so the space goes to someone else.
 
 ### Who can RSVP
 
@@ -97,11 +97,11 @@ RSVP records live in the public data repo and the attendee list on the event pag
 | Choice | `EventRsvp.plan` | Attendee list group |
 | ------ | ---------------- | ------------------- |
 | "I'm new to Code for Philly" | `newcomer` | **New to Code for Philly** |
-| "I don't have a project yet" | `no_project` | **Looking for a project** |
+| "I don't have a project yet" | `no_project` | **No project yet** |
 | "I'm coming to work on …" + project picker | `project` + `projectId` | the project |
-| *(unanswered)* | absent | **Not sure yet** |
+| *(unanswered)* | absent | *(no heading — listed first)* |
 
-The answer can be changed any time while the RSVP window is open and never sends mail. The point is organizational, not gatekeeping: the attendee list groups going members by project (ordered by attendee count, then title), then **New to Code for Philly**, then **Looking for a project**, then **Not sure yet**. Organizers see at a glance who to welcome at the door and which tables will be full; newcomers see that they won't be the only new face. This is what laddr's check-in-by-project did well, with the newcomer case made explicit.
+The answer can be changed any time while the RSVP window is open and never sends mail. The point is organizational, not gatekeeping: the attendee list shows going members who haven't answered first, directly under the "Going" heading with no subheading of their own, then groups the rest by project (ordered by attendee count, then title), then **New to Code for Philly**, then **No project yet**. Group names mirror the choice the member clicked; the unanswered get no label because any label ("Not sure yet", "Undecided") reads as doubt about attending, and listing them first keeps them from looking like members of the last labelled group. Organizers see at a glance who to welcome at the door and which tables will be full; newcomers see that they won't be the only new face. This is what laddr's check-in-by-project did well, with the newcomer case made explicit.
 
 ### Side effects of RSVPing
 
 
@@ -44,7 +44,7 @@ Across the top of the content area, before the title:
    | ------------ | -------- |
    | Anonymous, RSVPs open | Button "Sign in to RSVP" → `/login?return=/events/<slug>`; helper "Your name will appear on the attendee list." |
    | Signed in, not going, RSVPs open | Primary button "I'm going"; same helper text |
-   | Signed in, going, RSVPs open | Success state "You're going ✓" with a quiet "Can't make it?" link that withdraws (confirm); below it the **follow-up** per [behaviors/events.md](../behaviors/events.md#the-follow-up-what-are-you-coming-to-do): the prompt "What are you coming to do? (optional)" with three choices — "I'm new to Code for Philly", "I don't have a project yet", "I'm coming to work on [Pick a project ▾]". The picker is a find-as-you-type combobox that never lists the whole catalog: opened with nothing typed, it offers two groups — "Your recent projects", the projects the member named on their own RSVPs to other events (`viewerRecentProjects`, newest first), then "Other active projects", the last ten distinct projects anyone named on any RSVP (`recentProjects`, newest first) — a project appearing once in the first group it belongs to, empty groups omitted, so a newcomer sees the teams that actually meet without searching; only when both are empty, nothing but the input's own hint "Type a project name"; once the member types, it searches projects by title and text (`GET /api/projects?q=`), showing at most eight in relevance order, or "No projects match". Arrow keys, Enter and Escape work as in any combobox. Selecting a choice saves immediately; the chosen one shows as selected with a "Change" affordance. Unanswered shows the three choices; never a blank. |
+   | Signed in, going, RSVPs open | Success state "You're going ✓" with an outline "Cancel RSVP" button beside it that withdraws (confirm dialog "Cancel your RSVP?" with "Keep my RSVP" and "Cancel RSVP"); below it the **follow-up** per [behaviors/events.md](../behaviors/events.md#the-follow-up-what-are-you-coming-to-do): the prompt "What are you coming to do? (optional)" with three choices — "I'm new to Code for Philly", "I don't have a project yet", "I'm coming to work on [Pick a project ▾]". The picker is a find-as-you-type combobox that never lists the whole catalog: opened with nothing typed, it offers two groups — "Your recent projects", the projects the member named on their own RSVPs to other events (`viewerRecentProjects`, newest first), then "Other active projects", the last ten distinct projects anyone named on any RSVP (`recentProjects`, newest first) — a project appearing once in the first group it belongs to, empty groups omitted, so a newcomer sees the teams that actually meet without searching; only when both are empty, nothing but the input's own hint "Type a project name"; once the member types, it searches projects by title and text (`GET /api/projects?q=`), showing at most eight in relevance order, or "No projects match". Arrow keys, Enter and Escape work as in any combobox. Selecting a choice saves immediately; the chosen one shows as selected with a "Change" affordance. Unanswered shows the three choices; never a blank. |
    | RSVPs closed (cancelled, past) | No control; the count line still renders |
 
    Under the control: "14 going" linked to the attendee list anchor. When `meetupUrl` is set, a small muted "Also listed on Meetup ↗" link sits *below* everything in this block, never beside the button.
@@ -63,7 +63,7 @@ Across the top of the content area, before the title:
 
 1. **Attendees** (`id="attendees"`)
    - Heading "Going (14)"
-   - Grouped per [behaviors/events.md](../behaviors/events.md#the-follow-up-what-are-you-coming-to-do): a subheading per project (linked to `/projects/<slug>`) with that group's avatars (48px, name on hover, linked to `/members/<slug>`), then "New to Code for Philly", "Looking for a project", and "Not sure yet", each only when non-empty. When nobody has answered the follow-up, no subheadings — just the avatar grid.
+   - Grouped per [behaviors/events.md](../behaviors/events.md#the-follow-up-what-are-you-coming-to-do): a subheading per project (linked to `/projects/<slug>`) with that group's avatars (48px, name on hover, linked to `/members/<slug>`), The members who haven't answered come first, as an avatar grid with no subheading directly under "Going (N)"; then a subheading per project (linked to `/projects/<slug>`) with that group's avatars (48px, name on hover, linked to `/members/<slug>`), then "New to Code for Philly" and "No project yet", each only when non-empty. When nobody has answered the follow-up, that first grid is the whole list.
    - Empty: "Nobody has RSVP'd yet. Be the first!" (or "Nobody RSVP'd." on past events)
    - For a cancelled event the heading reads "Had planned to go (14)"
 
@@ -80,7 +80,7 @@ Across the top of the content area, before the title:
 | Action | Affects | Caused by |
 | ------ | ------- | --------- |
 | RSVP | `PUT /api/events/:slug/rsvp`; confirmation email | "I'm going" |
-| Withdraw | `DELETE /api/events/:slug/rsvp` | "Can't make it?" + confirm |
+| Withdraw | `DELETE /api/events/:slug/rsvp` | "Cancel RSVP" + confirm |
 | Answer / change the follow-up | `PUT /api/events/:slug/rsvp` with `plan` (+ `projectSlug`) | Follow-up choices |
 | Add to Google Calendar | Opens calendar.google.com template | Link |
 | Download .ics | Downloads the file | Link |