Coding 15 Pages of Interview Data in Three Days

Bottom line: three days, realistic expectations

Three calendar days usually translate to about 24–30 focused hours for a 15‑page thesis chapter that includes coding interview transcripts, running the analysis, and writing a discussion. For most returning adult learners juggling part‑time work, that amount of uninterrupted time simply isn’t available. In practice, you’ll end up stretching the work over a week or more if you want a chapter that meets academic standards and doesn’t leave you exhausted.

If you can carve out a solid 8‑hour block each day, you might finish a rough draft in three days, but the polishing, citation checks, and supervisor feedback loop will add another 2–4 days. So the honest answer is: three days is *barely* enough for a first draft, and far from enough for a polished, submission‑ready chapter.

Breaking the chapter into stages and time estimates

Why the process often drags longer

Underestimating the research phase is the most common pitfall. Even if you’ve already transcribed the interviews, you still need to read them closely enough to notice nuances that affect coding. Skipping that depth means you’ll have to revisit large sections later, which adds at least another half‑day of work.

Rewriting from scratch is another time sink. Many students treat the first draft as a final product, only to discover that the narrative doesn’t flow or that key themes are missing. A genuine revision cycle—reading the draft aloud, restructuring paragraphs, tightening arguments—easily consumes 3–5 extra hours.

Formatting issues can feel trivial until you hit the final submission checklist. McGill’s thesis guidelines demand precise heading levels, consistent citation style, and a specific pagination scheme. Fixing mis‑numbered tables, misplaced footnotes, or inconsistent font sizes often eats into the time you thought you’d reserve for polishing the argument.

Real‑world timeline from a returning student

Consider a 38‑year‑old part‑time student who works 20 hours a week and has a family. When the supervisor moved the deadline up, the student mapped out a concrete schedule:

1. Day 1 (morning, 4 hours): import all 12 interview transcripts into NVivo, create a master codebook based on the research questions.
2. Day 1 (afternoon, 3 hours): conduct an initial read‑through, assign broad codes, flag ambiguous passages.
3. Day 2 (early, 5 hours): refine codes, run a quick inter‑coder reliability check with a peer, adjust the codebook.
4. Day 2 (late, 4 hours): generate theme tables, write the results section, embed illustrative quotes.
5. Day 3 (morning, 3 hours): draft the discussion, linking each theme to two or three scholarly sources.
6. Day 3 (afternoon, 2 hours): apply the thesis template, insert footnotes, run a spell‑check, and send a draft to the supervisor.

Even with this aggressive plan, the student reported feeling mentally drained and had to spend an additional evening after the deadline to address the supervisor’s comments. The experience illustrates why three days feels like a sprint rather than a sustainable pace.

Minimum‑viable plan when time is tight

If you truly have only three days, cut to the essentials without sacrificing academic integrity. Follow this checklist:

• Identify the five most salient themes that directly answer your research question; ignore peripheral findings.
• Code only the excerpts that illustrate those five themes; skip exhaustive line‑by‑line coding.
• Write a results paragraph for each theme, using one strong quote per theme to keep the word count manageable.
• Draft a discussion that focuses on three points: how the themes answer the question, one clear link to existing literature, and one limitation you can acknowledge quickly.
• Apply the thesis template only to headings, page numbers, and reference formatting; postpone fine‑tuning fonts or spacing until after you’ve secured a “good enough” draft.

Anything you cut should be non‑essential to the argument’s core. You cannot cut the coding of the primary themes, the linking of findings to theory, or the citation of at least two relevant sources per theme. Those three elements are the backbone of a defensible chapter.

“I stripped my chapter down to three themes and a single quote each. It felt sparse, but my supervisor said the argument was clearer than my original 12‑theme draft.” – a returning student in their final semester.

Accepting that three days will produce a lean version, not a polished masterpiece, lets you manage expectations and avoid burnout. After the deadline, schedule a short “post‑submission polish” window where you can flesh out any omitted nuance without the pressure of a looming due date.

Protecting your mental stamina while you sprint

Three days of nonstop coding and writing will drain anyone, especially if you’re juggling a part‑time job. The first thing to do is to schedule short, intentional breaks that actually restore focus rather than just shift your attention. A 5‑minute walk outside after each 45‑minute coding block can lower cortisol and keep the next block from feeling like a marathon. Pair that with a single “no‑screen” meal: put your phone on airplane mode, step away from the laptop, and give your brain a chance to process the material you’ve just coded.

Another guard‑rail is to set a hard stop for each day. Even if you haven’t hit the word count, ending at a reasonable hour protects the next day’s productivity. Your supervisor will notice a coherent draft more than a half‑finished, sleep‑deprived mess. If you find yourself still thinking about the chapter at 2 a.m., write a quick “brain dump” of lingering ideas on a sticky note and close the laptop. Those notes become a to‑do list for the post‑submission polish, not a source of anxiety.

Finally, enlist a “micro‑accountability” partner—perhaps a classmate who also has a tight deadline. Agree to send each other a one‑sentence status update at the same time each day. That tiny nudge creates external pressure without feeling like a formal check‑in, and it gives you a moment to verbalize progress, which reinforces motivation.

Step‑by‑step sprint checklist

Having a concrete list keeps you from wandering into non‑essential tasks. Tick each item before you move on; if you’re stuck, note the obstacle and keep the clock running.

1. Gather all interview transcripts and import them into your coding software.
2. Define five core themes based on your research question; write each theme as a one‑sentence label.
3. Code only the excerpts that directly illustrate those five themes; ignore marginal comments.
4. Export coded excerpts into a single document; sort by theme.
5. Draft a 150‑word results paragraph for each theme, inserting one compelling quote.
6. Write a 300‑word discussion that (a) links the theme to your question, (b) cites two relevant sources, and (c) acknowledges one limitation.
7. Apply the thesis template to headings and reference formatting; defer fine‑tuning fonts.
8. Run a quick spell‑check and verify that every citation appears in the bibliography.
9. Save a version named “Chapter‑Draft‑Day3‑Morning” and back it up to cloud storage.
10. Send the draft to your supervisor with a brief note explaining what’s solid and what you plan to polish later.

Following this checklist usually caps the intensive work at around 12 hours of focused effort. Anything beyond that signals diminishing returns and should be shifted to the post‑deadline polish window.

When three days just isn’t enough

If you’ve run the sprint checklist and still see a large gap—perhaps you need six themes to answer the question, or your data are more nuanced than expected—recognize that the deadline may be unrealistic. In that case, communicate early with your supervisor. Explain precisely where the bottleneck lies (e.g., “coding 30 % more excerpts will add roughly four hours of work”) and propose a concrete compromise, such as submitting a shortened chapter with a promise to deliver the full analysis within two weeks.

A realistic student example illustrates this approach. A returning student in their final semester of a sociology program received a three‑day deadline for a 15‑page chapter. After two days of coding, they realized the interview set contained 12 emergent themes, not five. They emailed their supervisor, outlined the extra time needed, and received permission to submit a “core‑findings” version covering the top five themes, with a follow‑up addendum due in ten days. The initial submission met the deadline, and the addendum earned full credit because the supervisor appreciated the transparent timeline.

When you’re forced to admit that three days won’t cover everything, the key is specificity: name the exact task, estimate the additional time, and suggest a concrete plan. Vague pleas (“I need more time”) rarely succeed, but a clear, data‑driven request shows professionalism and respect for the supervisor’s schedule.

“I told my advisor I could finish the coding in 14 hours, but the thematic depth required another 6 hours. We agreed on a two‑stage submission, and I kept my grade.” – a part‑time student in a health sciences program.