Asking a Professor for Feedback on a Draft in English

Two weeks before the deadline, the draft exists. It is not good yet, but it is finished enough to be read, and there is one office-hours slot left this week. This is the moment when most international students write the email they regret: four lines of apology, one vague request, and a silence that lasts until the paper is due. The problem is almost never English. It is that the request has no shape, so the professor cannot tell what they are being asked to do, how long it will take, or how to say no without being unkind. This guide gives the request a shape — four parts, two worked emails you can adapt, and a plan for the comments once they arrive — as one specific answer to the wider question of how to talk to professors in English.

Why "could you take a look" gets a polite no

The request that fails most often is also the shortest one: Could you take a look at my draft? It is polite, it is humble, and it hands the professor a job with no edges. A look can mean two minutes or forty. It can mean grammar, structure, evidence, or all three. The cheapest honest reply is "it looks fine so far", and that reply is technically true.

The Writing Center at the University of North Carolina makes the point directly in its guidance for multilingual writers: general requests such as "Could you give me some comments on my paper?" usually produce vague or poor feedback, while specific questions direct the reader's attention and produce better comments. That is not a difference in kindness between professors. It is a difference in scope. A request that names a place and a decision gives the reader somewhere to put their attention.

Apologising makes it worse. Three sentences of "sorry to bother you", "I know you are very busy" and "any feedback at all would help" add social weight without adding information. The professor still has to work out what to read, by when, and for what purpose, and now the email is also slightly painful to answer. Politeness is not clarity, and in a request the second one is what gets a reply.

There is a second reason the vague version fails: it cannot be refused gracefully. Ask someone to read a whole draft and the honest replies are "yes", which may mean a long unpaid read, or silence, which both of you read as rejection. Ask for one section by Friday and "no, not this week" becomes an ordinary sentence. The smaller the ask, the easier the no, and the more likely you are to get a real answer. You are not asking for a favour; you are proposing a small task with a size, a deadline and an exit.

The four-part request: context, ask, deadline, exit

Four sentences do most of the work, in this order.

Context tells the professor who you are and what they are looking at. Purdue University's advising page suggests giving your preferred name, your year, your major and the course you are enrolled in; the University of Tennessee's office-hours guidance asks for full name, course title and number, and a brief statement of purpose. Both describe the same requirement: nobody should have to open a gradebook to place you. Add the stage of the draft and its length, because that is the number the professor will use to decide.

The ask is one sentence about one bounded object. Not "feedback" but "the introduction and the paragraph on page three", or "section 3, about 900 words". Naming a piece turns an open-ended favour into a task that fits between two meetings.

The deadline is the date you need comments and the reason for it. "The draft is due on the 14th and I want four days to revise" tells the professor how your request interacts with their week, which is information they cannot get anywhere else.

The exit is the sentence that makes a no cheap: what you will do if the answer is no. Without it, the professor has to invent a refusal; with it, they can simply agree that the timing does not work.

The order matters, and the exit goes last on purpose. Read the first three sentences alone and the email is a demand with a date attached. Add the fourth and the same three become an offer: here is a small job, here is when I need it, and here is what happens if you cannot do it. The whole email is five sentences, shorter than most apology chains and faster to answer.

Naming the feedback you want

"Feedback" hides three different jobs, and they cost different amounts of attention. Structural feedback asks whether the argument holds and whether the parts are in a useful order. Evidence feedback asks whether the sources are doing the work the paper claims. Language feedback asks whether the sentences are accurate and clear. A request that names one of the three is answerable in ten minutes; a request that names all three is a request for a marking, which is a different and much more expensive thing.

The same North Carolina guidance lists the questions that actually produce comments, and they share a pattern: each names a place and a judgement. "Are my ideas in a useful order?" "Can you follow the logic of my argument?" "Are my transitions clear?" "Does the third paragraph make sense?" None of them asks whether the paper is good. All of them ask the reader to check something specific and report back.

It also helps to say what you are not asking for. I have already had the grammar checked, so I am not asking for proofreading removes a job from the professor's list and shows that you did your part before spending their time.

The one-decision rule

If you can only ask one question, ask about the decision you are still making. A decision question produces comments you can act on; a quality question produces a grade in disguise.

• Is the counter-argument in section 3 worth keeping, or does it weaken the main claim?
• Is my thesis too broad for a 2,000-word paper?
• Does the evidence in paragraph 4 actually support the point I make in the topic sentence?

Each tells the reader what you will do with the answer. That is the difference between a question that earns a paragraph of comments and one that earns "looks good".

Asks that are too big, and what to say instead

• "Can you tell me if it's good?" becomes Is the argument in section 2 clear enough to follow?
• "Can you check my English?" becomes Are there sentences in the first two pages where the grammar makes the meaning unclear?
• "Any feedback would help" becomes Which of these two structures would you keep?

Every replacement names a place, names a decision, and has a size the reader can picture before saying yes.

Two requests you can adapt

The four parts stay the same at every length. What changes is the guarantee you offer, because a twelve-page draft is a different cost from a two-page one. Both emails below are original examples written for this article; they are not copied from a real student or a real professor, and the names are invented.

Short draft, early stage

1. Subject: HIS 204 — question about my source-analysis draft (2 pages)
2. Dear Professor Nakamura,
3. I am in your Tuesday section of HIS 204. I have a two-page draft of the source-analysis paper and I am still deciding how to order the two sources.
4. Could you read the introduction and tell me whether the order I have chosen makes the comparison clear?
5. The draft is due on the 14th, and I would like to revise over the weekend, so comments by Friday the 8th would help.
6. If this week is impossible, I will bring two questions to your office hours on Thursday instead.
7. Thank you, Ana Ruiz

• The subject line carries the course, the assignment and the length, so the professor can decide when to open it.
• The greeting uses the title and surname from the syllabus; when unsure, "Professor" plus the surname is safe.
• Line three is context plus a stated uncertainty, which is what makes line four a real question rather than a formality.
• Line four asks for two named pieces, small enough to finish in a few minutes.
• Line five gives a date and the reason for it, so the professor can see whether it fits their week.
• Line six is the exit: one sentence, no apology, and "no" becomes a normal answer.
• There is no paragraph about how much the comments would mean. That paragraph is why most requests go unanswered.

Long draft, later stage

1. Subject: POL 310 — feedback on section 3 of my policy memo (draft attached, 12 pages)
2. Dear Dr. Okafor,
3. I am in POL 310 and the policy memo is due on the 21st. The draft is complete at 12 pages, but the part I am least sure about is section 3, where I compare the two funding models.
4. Would you be willing to read section 3 only, about 900 words, and tell me whether the comparison is fair to both models? I have attached the full draft so you can see the context, but I am not asking you to read all of it.
5. If comments could reach me by the 15th, I would have time to rewrite that section before submission.
6. If your week is full, that is completely fine. I will ask the writing centre for a reader's response and bring one question to office hours.
7. Best regards, Daniel Kim

• The subject line states the attachment and its length, so nothing in the email is a surprise.
• Line three names the uncertainty before the request, which makes a specific ask feel natural rather than arbitrary.
• Line four does two jobs: it gives the size of the job in words, and it says explicitly what is not being asked. That second clause is what makes a twelve-page attachment acceptable.
• Line five converts a deadline into a plan: comments by the 15th, rewrite before the 21st.
• Line six offers an alternative reader, which is a real exit and not a rhetorical one.

The second email is longer than the first, but the ask is the same size. That is the whole technique: when the draft grows, shrink the request and say so out loud.

The office-hours follow-up

If the reply is "come to office hours", that is a yes, and often a better one than written comments. Bring three things: the draft with your own notes in the margin, the two questions you already named in the email, and something to write with. A meeting without prepared questions turns into a general conversation about the assignment, which is pleasant and rarely useful two weeks before a deadline.

What to say when you sit down

1. Thanks for making time. I brought the draft and the two questions from my email.
2. Can I read you the sentence I am worried about, and tell me what I think is wrong with it?
3. So the problem is that the evidence is too general, not that there is too little of it?
4. Can I send you a three-line summary of what I changed, so you can see how I used your comments?

The third line is the one students skip. Repeating the advice back in your own words is how you find out whether you understood it, and it takes ten seconds. The University of Tennessee's guidance asks students to take notes and to summarise next steps at the end of the meeting, for exactly this reason: both people should leave with the same version of the plan. The North Carolina guidance makes a related point about clarification, which is that asking what a comment means is treated as evidence of engagement, not as a challenge.

If a comment is still opaque afterwards, one short email is enough: You mentioned that my evidence is too general. Do you mean I need a different source, or the same source used more precisely? That question offers two readings and can be answered in one line.

What to do with the comments afterwards

Comments arrive as a pile, and a pile feels like a verdict. It is not. Sort it into three buckets before you change a single sentence.

The first bucket is mechanical and fast. The second is where most of the work is, because an evidence gap usually means one paragraph is claiming more than its source supports, and the fix is to narrow the claim rather than add another citation. The third is a decision: "interesting" is not an instruction to keep something. If you cannot give it a paragraph of its own, it belongs in your notes for the next paper.

The three-line reply

Send one reply, within a few days, and then stop. It should say what you changed, what you kept, and where you disagreed.

1. Thank you. I rewrote the topic sentence in section 2 and moved the counter-argument after the evidence.
2. I kept the comparison in section 3 but cut the second table, which was repeating the text.
3. I did not change the ending. I think the short version is clearer, but I would like to hear why you would extend it.

Three lines is enough because the professor does not need a report; they need to know the comments were read and used. The third line is worth keeping, because disagreeing with a reason is part of the work and is very different from ignoring a comment. What you should not do is send the revised draft unless it was invited. A revision nobody asked for is a new request wearing a thank-you note.

Frequently asked questions

How do I ask a professor to read a draft without sounding demanding?

Use four sentences in this order: context, a bounded ask, a date, and an exit. The exit is what removes the demand, because it says what happens if the professor says no. Keep the request to a named section rather than the whole draft, and drop the apology sentences, which add length without adding information. A request that can be answered in ten minutes reads as considerate; a request that could take an hour reads as demanding, however politely it is written.

How much of a draft should I send to a professor?

Send the part you want comments on, and name its size. If the paper is long, attach the whole draft for context but say explicitly that you are only asking about one section. Two pages and one question is a reasonable first request; twelve pages and no question is not. The exception is a short paper that is already complete, where the whole document is the natural unit and the ask should name the two or three decisions you are least sure about.

What should I say if the professor says they are too busy?

Thank them in one line and use the exit you already wrote: say what you will do instead, such as asking the writing centre or bringing two questions to office hours. Do not renegotiate the deadline in the same email, and do not ask again that week. A refusal about timing is not a judgement about your work, and treating it as one is what turns a small request into a difficult relationship. If timing was the problem, the next request should come earlier, with a smaller ask.

Where to practise next

The request improves fastest when you say it out loud before you type it. Read the four sentences as a script, time yourself, and cut anything that is not context, ask, deadline or exit. For the wider set of situations this belongs to, the guide to talking to professors and classmates covers class participation and the first email of the semester, the guide to asking for an extension shows the same four-part structure under more pressure, and the guide to requesting a reference letter applies it to a request with a much longer horizon. If you want to rehearse a spoken version before an office-hours visit, HiBay's conversation practice with AI partners gives you a place to say the sentences out loud and hear them back before they matter.