IB DP What–How Series: How to Build a Spike Profile in IB DP in 90 Days (Step-by-Step)
You don’t need years of premeditated achievements to build a compelling spike for your university applications. What you need is deliberate focus, smart evidence, and a clear narrative. Over the next 90 days you can transform one genuine interest into a measurable, demonstrable spike that admissions readers notice—without sacrificing your grades or your sanity.

This guide is written for IB DP students who want a hands-on, week-by-week plan. It ties essays, activities (including CAS), interviews, and a simple timeline into one coherent project. Expect practical checklists, realistic deliverables, and examples you can adapt to your subject area or intended major. Where useful, I’ll point out how targeted 1-on-1 support can speed the process; those mentions will be placed naturally so you can decide whether one-to-one tutoring or mock interviews might help.
What a “spike” really is (and why it matters)
Defining the spike
A spike is a concentrated, sustained achievement or contribution that shows deep intellectual curiosity, leadership, or creative excellence in one area. It’s not about having every extracurricular box ticked. It’s about a clear, memorable thread that runs through your activities, your Extended Essay (EE), your CAS reflections, and your personal statements—then being able to talk about it in an interview with evidence.
Why admissions officers notice spikes
Admissions readers try to predict who will thrive academically and contribute to campus life. A spike signals commitment and potential to continue doing meaningful work. It makes your application coherent: your grades, subject choices, EE topic, and activities all start to tell the same story.
Start with a quick audit: the 48-hour stocktake
The honest inventory
Before you plan, know what you already have. Spend no more than two focused days on this audit. Create a single document that answers these questions succinctly:
- What subject or activity excites me enough to sustain long-term work?
- What measurable outcomes can I plausibly achieve in 90 days? (e.g., a research poster, a public performance, a community pilot, an article)
- Which pieces of evidence already exist? (lab logs, project reports, photos, testimonials, gradeable deliverables)
- Who can write a meaningful recommendation connected to this area?
- What is realistically doable alongside IB deadlines and exams?
Prioritize using impact vs. feasibility
Map potential ideas on a two-by-two grid: impact (low to high) vs feasibility (hard to easy). Your spike should live in the quadrant that offers high impact and reasonable feasibility in a 90-day window. That intersection is where intentional work produces visible results.
The 90-day step-by-step plan: week-by-week
Mindset and approach
Treat the 90 days like a creative sprint. Think in cycles: plan, execute, reflect, polish. Small, visible products build momentum and credibility—collect artifacts and reflections as you go. Aim for visible milestones: a working draft, an external submission, a public sharing moment, or a teacher-signed reflection.
Timeline at a glance
| Days | Focus | Weekly Objective | Key Actions | Deliverable |
|---|---|---|---|---|
| 1–14 | Define & plan | Clear spike statement and roadmap | Pick one focus; set 3 measurable goals; schedule weekly time blocks | One-page plan + accountability partner |
| 15–30 | Build foundations | Create first artifacts and initial draft work | Run experiments, draft EE/portfolio pieces, register for competitions | Rough draft, research log, competition entry started |
| 31–45 | Accelerate | Submit or publicly share an intermediate product | Seek feedback, revise, document impact, collect testimonials | Submission, blog post, recorded performance, or poster |
| 46–65 | Deepen & extend | Increase depth and link to academic interests | Refine methods, start linking EE/CAS reflections to project | Polished draft + reflective commentary |
| 66–80 | Polish narratives | Translate evidence into stories and one-liners for activities list | Write personal statement drafts, craft activity descriptions, prepare evidence bundle | Essay draft, activity bullets, compiled folder |
| 81–90 | Finalize & rehearse | Interview-ready and application-ready packet | Mock interviews, final edits, teacher briefings, final proof of artifacts | Application materials packet + practice interview recordings |
This table is a scaffold. Each week should end with one clear artifact or decision. Treat those endpoints as micro-deadlines so you build momentum.
Daily and weekly micro-schedule
- Daily: 45–90 minutes of focused work on the spike (research, writing, practicing).
- Twice weekly: 30-minute reflection and log update (what went well, what to improve).
- Weekly: 1- to 2-hour chunk for deep work (experiments, performance rehearsal, extended writing).
- Every two weeks: external feedback session (teacher, mentor, or a paid mock-review).
Essays: turning the spike into a readable narrative
Find the kernel of your story
Good essays don’t list achievements—they connect an interior life to outward action. Start with a small scene: the moment you realized the problem was worth solving, the first failed attempt, or the time you taught others. Let evidence (project results, awards, supervisor comments) shadow that scene. The rest of your essay should show development: what you learned, how you grew, and why you’ll continue this work in university.
Structure and finesse
- Hook: the specific scene that makes the reader curious.
- Body: two or three concise episodes showing progression, skills, and impact.
- Reflection: what the experience taught you and how it connects to academic aims.
Draft multiple versions and get feedback from someone who understands your subject. Targeted 1-on-1 essay coaching can speed revision cycles and help you find sharper language; for students who want that kind of support, Sparkl‘s personalized essay feedback and tailored study plans can be a time-saving option.
From evidence to activity bullets
Admissions reviewers often skim activity lists for data: role, hours, and impact. Convert each item into a one-line bullet that follows this formula: Role — Specific action — Quantified impact — What you learned. Keep each line under 140 characters if possible so it reads cleanly on forms.
Activities and CAS: documenting depth
Quality beats quantity
A single, well-documented project that shows growth is far stronger than ten half-hearted ventures. Think of CAS as a laboratory for your spike: use it to record reflections, mentor feedback, and artifacts that feed your EE and essays.
Examples of strong activity entries
| Activity | Role | Evidence | Impact / Outcome |
|---|---|---|---|
| Community STEM club | Founder & lead | Project guide, attendance sheet, photos | Launched mentorship for 30 students; measured improvement in test scores |
| Independent research | Primary researcher | Experiment log, data, supervisor note | Presented at a regional fair; refined hypothesis for EE |
| Creative portfolio | Artist-composer | Recordings, program notes, reviews | Public performance and online viewership |
Always keep a dated folder (cloud + backup) with time-stamped files, short reflective notes, and any metrics you can gather. These artifacts become your proof when drafting essays and answering interview questions.
Interviews: practice until presence becomes natural
Answer using the STAR + reflection method
Structure responses with Situation, Task, Action, Result—and add a short reflection linking the experience to future aims. Short practice drills help you stay concise, which is crucial when an interviewer is scanning for substance and self-awareness.
Mock interviews and feedback loops
Do at least three recorded mock interviews: early (to surface gaps), mid (to fix structure), and late (to polish delivery). Use video so you can analyze posture, tone, and filler words. If you want targeted coaching, mock interviews with focused feedback are effective; some students pair those sessions with personalized study plans and AI-driven insights to track improvement, for example through platforms that offer one-on-one guidance and iterative feedback like Sparkl‘s tools.
Teacher recommendations: give recommenders the material they need
How to brief your teachers
When you request a recommendation, provide a short packet: your one-page spike summary, a timeline of interactions with the teacher, a list of your most relevant artifacts, and a reminder of the skills or growth you’d like them to emphasize. Ask early—teachers who have time to reflect will write more specific, vivid letters.
What to include in the packet
- A one-page summary of your spike and how it connects to your academic interests.
- Two or three bullet points of evidence and anecdotes (dates, outcomes, roles).
- An optional short meeting to refresh the teacher’s memory and answer questions.
Time management and well-being
Practical time-blocking
Block consistent small chunks for spike work on your weekly calendar. Treat these blocks like class time—non-negotiable. Use a 90–120 minute deep-work block once per week for the most demanding tasks and multiple short blocks for drafting, reflection, and admin tasks.
Preventing burnout
Pace intensity: alternate focused sprints with active recovery. Keep sleep, movement, and social time on your calendar. Progress compounds faster when you’re rested and reflective.
Portfolio and folder structure: evidence that tells a story
How to organize
- Root folder: “Spike Project”
- Subfolders: Essays, CAS, EE, Research Data, Media (photos/audio), Recs, Transcripts
- Name files consistently: YYYY-MM-DD_shorttitle_version (for easy sorting)
Packaging evidence for an application or interview
Create a two-page summary that compiles the key artifacts and links to larger files. The summary should include a timeline of milestones, two short quotes from supervisors or participants, and a short reflection connecting the work to academic aims.
Common pitfalls and how to avoid them
Top traps
- Chasing shiny opportunities with no depth—avoid projects that start big but never produce a measurable outcome.
- Listing activities without reflection—your reflections are what turn actions into evidence of growth.
- Waiting until the last minute for recommendations—ask early and provide the packet.
- Over-polishing a single draft—iterate with feedback, but keep moving forward.
- Letting pride prevent revision—productive criticism is the fastest route to strength.
Final checklist before you submit or interview
| Deliverable | Ready? | Evidence to attach | Notes |
|---|---|---|---|
| Personal statement / main essay | Yes / No | Drafts, teacher feedback, word count | 3 polished versions recommended |
| Activities list (spike entries) | Yes / No | One-line bullets, evidence links | Lead with the spike |
| Interview prep | Yes / No | Mock recordings, STAR notes | Practice with timed answers |
| Teacher briefing packet | Yes / No | Summary, anecdotes, deadlines | Give at least two weeks’ lead time |
| Evidence folder | Yes / No | Media, logs, testimonials | Cloud + backup |
Closing notes
Building a spike is less about performing for admissions and more about practicing focus, collecting honest evidence, and learning to tell a clear story about who you are intellectually and personally. A concentrated 90-day plan—rooted in measurable goals, regular reflection, and timely feedback—can turn a promising interest into a distinctive part of your application packet and interview narrative. Commit to small, consistent daily work; collect dated artifacts; and practice telling the story behind the work until the evidence and the narrative align. This alignment is what turns activity into a memorable spike.

No Comments
Leave a comment Cancel