Timeline

Move-In 2027 Launch Timeline Nov 12, 2026 · @Stephen Groundwater Overview Full launch is Move-In, late August 2027. Working back from today, that leaves about 9 months and four gates: Proof of Concept by Winter Break, Soft Launch on May 15 (tentative, as the Houses close for summer), Summer Training, then Move-In. Principles (from the board): Done right. We own it. The loop: Move-In is not the end. What we learn at launch feeds the next cycle (the arrow from Summer back to Move-In). Dates are approximate and should be confirmed against the 2026–27 academic calendar. Timeline at a glance [embedded content: Move-In 2027 roadmap · 5 phases, 1 loop] Each break is a gate: POC must work by January, soft launch goes live May 15 when the Houses close, and summer is for training, not building. Phases 0. Now → Winter Break (mid-Nov to mid-Dec 2026, ~5 weeks) Goal: lock scope and build the thinnest working version. [ ] Define what “Move-In ready” means in one paragraph [ ] List MVP features vs. later features [ ] Name the owner for each workstream [ ] Stand up dev environment and repo [ ] Build the core flow end to end, rough is fine

1. Winter Break — Proof of Concept (late Dec 2026 to mid-Jan 2027) Goal: prove the core idea works with real data, in a quiet window. [ ] Core flow works end to end [ ] Demo to stakeholders [ ] Go / adjust / stop decision [ ] Capture gaps into a punch list for spring Spring semester build (mid-Jan to early Mar 2027) [ ] Close the POC punch list [ ] Pick the soft-launch audience (a small group) [ ] Basic support and feedback channel in place Spring Break — Internal Test (early Mar 2027) Goal: run the full flow end to end with staff before real users. [ ] Run the full flow with staff test accounts [ ] Log issues and gaps [ ] Fix list to close before soft launch Fix and prep (Mar to mid-May 2027) [ ] Ship fixes from the internal test [ ] Feature freeze before May 15
2. Soft Launch — May 15, 2027 (tentative) Goal: go live as the Houses close for summer, a low-traffic window to learn before Move-In. [ ] Launch to the pilot group [ ] Collect feedback and usage through June [ ] Fix-forward list for summer
3. Summer Training (Jun to Aug 2027) Goal: people and content ready, system hardened. [ ] Training materials and short how-tos [ ] Train staff / admins [ ] Load real Move-In content and schedules [ ] Load and failure testing; rollback plan [ ] Dress rehearsal two weeks before Move-In
4. Move-In — Full Launch (late Aug 2027) Goal: done right, we own it. [ ] Go live [ ] On-call coverage through Move-In week [ ] Retro within two weeks; feed lessons into the next cycle Open questions What exactly launches at Move-In? (The board shows a page with a hero and three cards; is that a site, a portal, or a reservation flow?) Exact dates for Winter Break, Spring Break and Move-In 2027 Is May 15 firm, and who is the soft-launch audience? Who gets trained in summer, and who owns support at launch? Next 2 weeks (before Thanksgiving) [ ] Answer the four questions above [ ] Write the one-paragraph “Move-In ready” definition [ ] Cut the MVP list for the Winter Break POC [ ] Block calendar time for the Dec–Jan build window