Skip to content
Explain-your-work meeting

How to explain your writing process to a professor

How to walk a professor through how you wrote a paper: your notes, drafts, sources and choices, using your own version history and your own words.

5 min read · Updated · By Academic Wizard

If you've searched "how to explain my writing process", you're probably getting ready to talk with a professor about a paper. The goal is simple: walk them through how the paper actually came together (your topic, research, planning, drafts and revisions) in your own words, using your notes and version history to jog your memory. This guide shows you how to rebuild that story, what questions to expect and how to practice telling it out loud.

What "explain your writing process" usually means

When a professor asks how you wrote something, they generally want to hear the path from the assignment to the finished paper. That can include where your idea came from, how you found sources, how you organized your argument, what changed between drafts and what you cut. Sometimes it's simple curiosity or part of a conversation about feedback. Sometimes it's part of a review of how a paper was produced. Either way, the best preparation is the same: know your own process well enough to describe it clearly.

For help with the meeting itself, see your professor wants to meet about your paper: how to prepare.

Rebuild your timeline first

Most people don't remember exactly how they wrote a paper, especially a few weeks later. That's normal. Start by collecting what you have.

  1. Open your version history. In Google Docs, look under File, then Version history. Microsoft Word keeps version history for files saved to OneDrive or SharePoint. Pages on a Mac lets you browse earlier versions from the File menu. Menu names change over time, so if you can't find it, search the app's help for "version history".
  2. Find your notes. Notebooks, notes apps, sticky notes, voice memos, photos of a whiteboard. Many note apps show when each note was created or edited.
  3. Check where you found sources. Library database accounts sometimes save search history. Your browser history and downloads folder can also show when you found articles.
  4. Look for conversations. Emails with the professor, a writing center appointment, comments from a classmate or a study group chat about the topic.
  5. Write a simple timeline. For each step, note the rough date, what you did and what you can point to that reminds you.

You don't need a perfect record. You need enough to tell the story accurately.

The parts of the process to be ready to explain

Choosing the topic

How did you land on this topic? Did you start with something broader and narrow it down? Was there a reading, lecture or personal interest that sparked it?

Researching

Where did you look first? How did you decide which sources to keep and which to drop? Did any source change your thinking? See how to explain your sources for this part in detail.

Planning the structure

Did you outline, make a mind map or just start writing? Why does your argument move in the sequence it does? If you moved sections around, why?

Drafting

Which part did you write first? Where did you get stuck, and how did you get unstuck? Did you write it in one long session or over many days?

Revising

What changed between your first draft and the final one? Did you rewrite your thesis, cut a section, add a counterargument or change your conclusion? What feedback, if any, led to those changes?

Tools you used

Be ready to say plainly what tools played a part: a citation manager like Zotero, spelling and grammar suggestions in your word processor, a reference librarian, a writing center visit or any AI tool. Courses set different rules about what's allowed, so check your syllabus. Being clear and accurate about what you used is always the right approach.

Questions you might be asked

  • How did you choose this topic?
  • What did your first draft look like?
  • Which part of the paper took you the longest?
  • What's something you cut, and why?
  • How did you organize your argument before you started writing?
  • Why did you put this section before that one?
  • When did you write the conclusion?
  • What would you change if you had another week?
  • Did you get feedback from anyone? What did you do with it?
  • Did you use any tools while writing? What for?

How to talk about your process

  • Tell it in sequence. Start with the assignment and walk forward. A clear sequence is easier to follow than jumping around.
  • Use specific moments. "I cut the section on funding after I realized it didn't support my main claim" is more useful than "I revised a lot."
  • Messy is fine. Real writing processes are rarely neat. If you wrote the middle first or rewrote your intro five times, say so.
  • Say when you don't remember. "I don't remember exactly, but my version history shows I added that section on the 12th" is honest and helpful.
  • Don't invent anything. Describe the process you actually had. Never create or backdate drafts after the fact. Doing that is deceptive and can make a simple conversation much more serious.

If you don't have drafts

Many students write in a single file and overwrite as they go, or work in an app without version history. That's common, and it doesn't mean you can't explain your work. In that case, your notes, your sources and your ability to explain your choices in detail matter even more. Be ready to talk about why you wrote specific sentences and paragraphs the way you did.

For future papers, turn on version history or save dated copies as you go. It takes seconds and gives you a record of your own work.

Practice telling the story out loud

Knowing your process and explaining it clearly under questions are two different things. Practice the second one.

  1. Use the Professor Meeting Prep Sheet to list what to bring and the questions you're likely to hear.
  2. Walk through your timeline out loud in three to five minutes.
  3. Have a friend or classmate ask the questions above and follow up on your answers.
  4. Record yourself and listen for vague spots like "I just kind of wrote it." Replace those with specifics.

You can also practice with Academic Wizard's AI practice coach, which asks spoken questions about your own paper and reports back what you said, where you were clear and where you were vague. For explaining the content of the paper itself, see how to explain your paper out loud, and for more on this kind of conversation, the explain your work page.

A quick checklist

  • You've opened your version history and know what it shows.
  • You have your notes, sources and assignment prompt in one place.
  • You've written a simple timeline of how the paper came together.
  • You can name one thing you cut and one thing you changed during revision.
  • You're ready to say clearly what tools you used, if any.
  • You've practiced walking through your process out loud at least twice.

Practice it out loud

Reading a guide is the easy part. The skill is saying your answer clearly, in your own words, when someone asks. Pick two questions from this guide and answer them out loud, timed, before the meeting.

Questions students ask

How do I explain my writing process to a professor?

Walk through how the paper actually came together, in sequence: choosing the topic, researching, planning, drafting and revising. Use your notes and version history to remember specific moments, such as a section you cut or a source that changed your thinking, and say plainly what tools you used.

How do I find the version history of my paper?

In Google Docs, look under File, then Version history. Microsoft Word keeps version history for files saved to OneDrive or SharePoint, and Pages on a Mac lets you browse earlier versions from the File menu. Menu names change, so search the app's help for "version history" if needed.

What if I don't have drafts of my paper?

That's common, especially if you write in one file and overwrite as you go. Your notes, sources and ability to explain your choices in detail matter more then. Never create or backdate drafts after the fact. For future papers, turn on version history or save dated copies.