Run a Bootcamp on upcoach

What is a Bootcamp?

A bootcamp is a high-intensity, time-compressed program where participants learn by producing something every single day. It runs for 3 weeks — 15 weekdays — and every day has a deliverable. Not a reading. Not a reflection. A tangible output.

The defining pattern is Module = Day. Each section in the curriculum is a week, and each module within it is a single day. Pre-Work sets the foundation before Day 1. Week 1 teaches the core concepts. Week 2 shifts from learning to building. Week 3 polishes and ships. Demo Day on Day 15 is the finish line — everyone presents what they built.

This format works for any domain where skill acquisition happens through doing: a product design sprint, a sales methodology intensive, a fitness certification crash course, a coding accelerator, a leadership development immersion. The pace is the product. Bootcamps compress months of gradual learning into three weeks of focused output, and that compression is what drives transformation.

If you run programs where participants need to emerge with a real skill and a real artifact — not just knowledge — this is your format.

What upcoach creates for you

When you select Bootcamp as your program type, upcoach generates a fully scaffolded 3-week intensive with Pre-Work and daily structure across every weekday:

Pre-Work — Get Ready: A Day 0 module with a welcome guide, an Essential Background lesson, a Baseline Skills Check worksheet (skill self-rating, experience inventory, challenge prediction, time commitment), and a Define Your Project worksheet where participants scope what they will build.

Week 1 — Learn the Foundations (Days 1–5): Five daily modules, each containing a content lesson, a task list, and a deliverable worksheet. Day 1 opens with a kickoff guide. Day 5 closes with a Week 1 Checkpoint Review — a visible worksheet where participants rate their confidence and assess whether their project scope is realistic.

Week 2 — Build Your Project (Days 6–10): Five daily modules focused on production. Day 6 opens with a “From Learning to Making” guide that signals the shift. Day 10 is the Mid-Bootcamp Reset — a visible Mid-Bootcamp Pulse survey (value rating, on-track check, pace assessment, open feedback) plus a halfway check guide. Week 2 requires completion of Week 1’s final module before unlocking.

Week 3 — Ship It (Days 11–15): Five daily modules for polishing and presenting. Day 14 includes a Demo Day Prep guide and a Demo Day Prep Sheet. Day 15 is Demo Day itself — a guide, the Final Reflection & Sprint Review (mirroring the Baseline Skills Check), and a What’s Next Checklist. Week 3 requires completion of Week 2’s final module.

Beyond the curriculum, the template also creates:

  • 15 daily standup events — 15-minute morning check-ins, one per weekday, each linked to its corresponding day’s module
  • Demo Day event — a 120-minute session on Day 15 for presentations and celebration
  • Build Log — a feed where participants post daily progress updates, screenshots, and learnings (participants can post)
  • 2 channels — Announcements for daily coordination, Questions for help and support
  • Cohort directory — visible to all participants for peer connection

Set up your Bootcamp

Step 1: Create your program

Open your organization dashboard and create a new program. Select Bootcamp from the program type picker — you will see the “Sprint” label and a summary of what gets generated.

The intake form asks you to set:

  • Program name — defaults to “Bootcamp,” rename it to match yours (e.g., “Product Design Sprint,” “Sales Mastery Bootcamp,” “Full-Stack Foundations”)
  • Bootcamp duration — fixed at 3 weeks (15 weekdays) + Pre-Work. This is displayed but not editable — the intensity is intentional
  • First day — must be a weekday. Everything cascades from here: daily module release dates, standup schedule, Demo Day date
  • Daily standup time — defaults to 9:00 AM with 15-minute increments. Demo Day is automatically scheduled one hour after your standup time

Review the summary panel, then create. Your program generates in seconds — Pre-Work, 15 daily modules, 15 standup events, Demo Day, channels, Build Log, and cohort directory all ready.

Step 2: Customize the structure

The 3-week, daily-module arc is a starting point. You can:

  • Rename sections and modules to match your domain — “Day 1 — Kickoff” becomes “Day 1 — Environment Setup” or “Day 1 — Define Your Niche”
  • Rename day subtitles — each day has a descriptive subtitle (Kickoff, Core Concepts, Deep Dive, Apply, etc.) that you should replace with your actual topic for that day
  • Adjust the weekly themes — the default progression is Foundations, Build, Ship. If your bootcamp follows a different arc (e.g., Diagnose, Design, Deliver), rename the section titles
  • Remove activities you don’t need — not every day needs all three activities. Some days might only need a task list and deliverable

The template includes an admin-only Bootcamp Guide with detailed instructions on running standups, managing the midpoint reset, and structuring Demo Day. Read it, use the advice, then remove it before you publish — participants should not see it.

For more on structuring your curriculum, see Build your curriculum.

Step 3: Add your content

Each day has a placeholder lesson marked with instructions to replace it. Bootcamp lessons should be short and actionable — 10 to 15 minutes maximum. The lesson sets up the day’s work; the task list and deliverable worksheet are where the real learning happens.

The content layers work like this:

  1. Pre-built assessments (Pre-Work, Day 10, Day 15) — these have real questions designed to measure transformation. The Baseline Skills Check asks participants to rate their skill level, describe their experience, and predict challenges. The Final Reflection mirrors these questions so you can compare before and after. The Mid-Bootcamp Pulse collects pace feedback and on-track status. Edit the questions to match your domain, but keep the structure.

  2. Daily deliverable worksheets (Days 1–13) — each day has a deliverable worksheet with prompts like “What did you produce today?” and a day-specific reflection question. Replace these with deliverable prompts specific to your content. A UX bootcamp might ask for a wireframe screenshot on Day 3. A writing bootcamp might ask for a 500-word draft on Day 7.

  3. Daily task lists (every day) — specific assignments for the day. Replace the generic items with your actual tasks. These make between-session work visible — you can see who completed what and who is falling behind.

A technical trainer might use “Deploy your first API endpoint” as Day 4’s deliverable. A business strategist might use “Complete your competitive landscape matrix” on Day 6. A fitness certification program might ask for “Record and upload your coaching demo” on Day 12. The structure adapts to any domain where daily output matters.

Step 4: Configure events

Your standup events are already created — 15 of them, one per weekday, each 15 minutes long and linked to its corresponding day’s module. When a participant opens Day 3, they see the Day 3 standup right there in the curriculum view.

Each standup has a built-in agenda:

  • What did you work on yesterday?
  • What are you working on today?
  • Any blockers?

Demo Day is a separate 120-minute event on Day 15, scheduled one hour after your standup time. Its agenda includes a 3-to-5-minute presentation per participant, structured as: What I built / How it works / What I learned.

Before Day 1, add your video call link to every standup event and to Demo Day. This is the one setup step you cannot skip.

To adjust event times or modify the standup format, see Create and manage events.

Step 5: Set up payments

Create an offer for your bootcamp with pricing that fits your market. Bootcamp programs typically range from $500 to $20,000 depending on the domain, cohort size, and level of individual attention. Technical bootcamps with mentor access command higher prices. Short skill-building sprints sit at the lower end.

A one-time payment with a registration deadline works well for bootcamps since they have a fixed start date and compressed timeline. Payment plans are less common for 3-week programs but can work if your price point is above $2,000.

See Create an offer for the full walkthrough.

Step 6: Invite participants

Once your content is in place and your offer is live, bring participants in. You can:

  • Share your registration page — participants sign up and pay through your checkout flow
  • Invite directly — add people manually from your organization’s user list
  • Use groups — if you want to create smaller pods within a larger cohort

Bootcamp cohort size depends on your format. If your standups include individual check-ins, cap at 12 to 15 participants — a 15-minute standup with 20 people becomes a 30-minute standup, and the format breaks. If your standups are more announcement-style with async check-ins through the Build Log, you can go larger. Either way, everyone should know everyone’s name by Day 3.

See Invite participants for all enrollment options.

Deliver your Bootcamp

The daily rhythm

Each day follows the same pattern for participants:

  1. Morning standup — 15 minutes. What you did, what you are doing, any blockers
  2. Lesson — short content that sets up the day’s work (10–15 minutes)
  3. Task list — specific assignments to complete
  4. Deliverable worksheet — the tangible output submitted by end of day
  5. Build Log post — share what you produced with the cohort

This rhythm is non-negotiable. The consistency is what makes bootcamps work. Participants know exactly what to expect every morning, and that predictability frees their energy for the actual work.

Pre-Work

Pre-Work happens before Day 1 and sets the foundation for everything that follows. Participants complete the Essential Background lesson, fill out the Baseline Skills Check, and — critically — define their project. The project definition is their north star for the next three weeks.

Make sure every participant completes Pre-Work before the first standup. If someone shows up on Day 1 without a defined project, they will spend the entire first week figuring out what to build instead of building it.

Week 1: Foundations (Days 1–5)

Your role this week is teacher. Deliver content, explain concepts, answer questions. Lessons are longer this week — participants need the conceptual foundation before they can produce meaningful work.

Day 1 sets the tone. The kickoff standup is different from every other standup: instead of “what did you work on yesterday,” ask participants to share their goals and their project scope. Day 5 closes with the Week 1 Checkpoint Review — a visible worksheet where participants rate their confidence and assess whether their project scope is realistic. Use the checkpoint data to identify anyone who needs to adjust scope before Build week begins.

Week 2: Build (Days 6–10)

Your role shifts to mentor. Lessons get shorter — just enough to set up the day’s work. The value is in the building, not the teaching. Review work, unblock problems, push quality.

Day 6 requires completion of Day 5 before unlocking. This is intentional — participants who skipped the foundations checkpoint should not start building.

Day 10 is the Mid-Bootcamp Reset. The Mid-Bootcamp Pulse survey collects honest feedback: Is the pace right? Are you on track for Demo Day? What would help most? Use these responses to identify who is falling behind (pair them with someone ahead), adjust remaining content to address gaps, and calibrate the pace for the final week. Make Day 10’s standup a reset session rather than the usual format.

Week 3: Ship (Days 11–15)

Your role shifts again to coach. Help participants polish their work, manage Demo Day anxiety, and prepare their presentations. Your energy sets the tone for this final push.

Day 14 is dedicated to Demo Day prep — no new content, just finalization and practice. The Demo Day Prep Sheet helps participants structure their presentation: What I built, How it works, What I learned. Consider using Day 14’s standup as a dress rehearsal where each person gives a 1-minute elevator pitch.

Day 15 is Demo Day. The 120-minute session gives each participant 3 to 5 minutes to present, plus 2 minutes for peer feedback. End with a celebration round — biggest shift, commitment forward. After presentations, participants complete the Final Reflection & Sprint Review and the What’s Next Checklist.

Track outcomes

Bootcamps generate dense data over a short period. The three assessment checkpoints — Baseline Skills Check, Mid-Bootcamp Pulse, and Final Reflection — give you a transformation arc compressed into three weeks. Use Space Reports to track:

  • Day-level progress — who is keeping up with the daily cadence, who is falling behind. In a bootcamp, falling one day behind quickly becomes falling three days behind
  • Deliverable completion — which daily worksheets are getting submitted, which are being skipped. A participant who stops submitting deliverables on Day 7 needs immediate attention
  • Standup attendance — who is showing up to morning check-ins. Standup attendance is the single best leading indicator of bootcamp completion
  • Build Log activity — who is posting daily updates and who has gone quiet

The Baseline Skills Check vs. Final Reflection comparison is your proof of results. A participant who rated their skill level at 3/10 on Day 0 and 8/10 on Day 15 — with a shipped project to show for it — has a story worth telling. And so do you.

For the full reporting walkthrough, see Track participant progress with reports.

Best practices

Intensity is the product. Bootcamps work because they are intense. Every day has a deliverable, every week has a checkpoint, and the pace creates urgency that drives action. Do not water down the daily cadence to make it “easier.” If participants wanted easy, they would take a self-paced course.

Your role shifts week to week. Week 1: you are the teacher — deliver content, explain concepts. Week 2: you are the mentor — review work, unblock problems, push quality. Week 3: you are the coach — help participants polish and present. Each phase demands a different energy. Recognize the shift and adjust.

Do not skip standups. The 15-minute morning standup is the heartbeat of the bootcamp. It creates accountability and surfaces problems early. Even when things are going well, show up. A missed standup signals that intensity is optional — and once that message lands, the bootcamp loses its edge.

Build content just-in-time. Start with Pre-Work and Week 1 content fully built. You can create Week 2 and Week 3 content while Week 1 runs. Trying to finish everything before Day 1 delays your launch and produces worse content — because you will not know what participants actually need in Week 2 until you see how Week 1 goes.

Use the Build Log for peer accountability. The Build Log is not a nice-to-have. It is where participants see what everyone else is producing, which creates healthy pressure and momentum. Seed it with the first post yourself, and call out good updates during standups. Once three or four people are posting daily, the rest follow.

Design Demo Day as a celebration, not a test. Every participant presents, regardless of how “finished” their project is. The point is not perfection — it is showing what you built and what you learned. Frame it that way from Day 1, and Demo Day anxiety drops significantly.

What to do next