Is it common to supervisors to email their students papers to review (which were apparently assigned to the supervisor, and not to the student). The field is Computer Science, but I would also like to hear from the other fields.

  • 7
    I would just take it as a compliment, and a worthwhile experience. Commented Dec 11, 2012 at 9:38
  • 10
    Note that at some conferences, the PC members are not expected to review the papers themselves: one of their roles is to select appropriate reviewers. In this case, it seems perfectly reasonable for a supervisor to request a review from their student. It also seems normal for a reviewer to ask one of their students for comments on a paper (though in some cases there may be confidentiality rules which prevent this).
    – Max
    Commented Dec 12, 2012 at 14:36
  • 5
  • 2
    If "review" means "referee": doesn't it violate confidentiality to show papers to someone else, in the first place? Commented Apr 21, 2016 at 19:35
  • 3
    @paulgarrett In the computer science situation described by Max, it is understood that the program committee members need not referee all their assigned papers themselves. Their use of sub-reviewers is analogous to the way editors send papers to referees. Like referees, sub-reviewers are expected to maintain confidentiality. (In other situations, though, I've heard of cases where a professor, who is supposed to referee a paper, simply signs a report written by a postdoc. I heartily disapprove, but apparently some cultures disagree with mine about this.) Commented May 9, 2016 at 23:25

10 Answers 10


It is not uncommon for the advisor to ask a student to review a paper. Let's face it — reviewing is a chore, takes a huge chunk of your time and most people do it not out of interest for the paper, but rather a necessity (it factors in promotions within the organization and recognition within the society) and probably some feigned interest in the "role of an academic" and "giving back to the society".

Usually, the papers that an advisor passes on to their students are

  • tangentially related to their interests
  • only mildly interesting or borderline stuff
  • are not from top-tier journals

As a student, you should never pass up on these opportunities. It can be a very rewarding experience to review a paper and discuss with your advisor. Some of the things you'll learn are:

  • that you didn't catch on to some inconsistency/mistake after a month of review, but your advisor did it in 15 mins of casual reading.
  • to write an effective critique while at the same time not putting the authors down. Contrary to what many may think, a review is not all about "your math sucks!". While yes, it should be pointed out if it indeed sucks, there are ways of saying that. If you spend a lot of the review finding faults, then it is also "fair" to throw in a couple of nice things about the paper and balance it.
  • you'll also learn to not nit pick on minor quibbles and focus on the technical content (I hate it when a reviewer makes a huge deal of 'data are' vs 'data is').
  • You'll learn to do this while juggling other activities, so it's also an early lesson in time management.

In the end, the quality of the review is partly your advisor's responsibility and he's not going to allow it if it is completely shabby. So, take this as an opportunity to learn about how to write a review.

Speaking for myself, I reviewed a couple of papers for my advisor in my early years and now, after I have a few publications to my name, I get invited to review papers on my own (i.e., not via my advisor). Recently, there were a couple of opportunities that my advisor passed on to me, but the difference this time, is that he trusts me to do a decent review and so requested the editor to officially ask me to review, so that I'll get credit for it.

  • 16
    Reviewing is not a chore, at least not for everybody :-). For me, as well as many colleagues around me, it is also a vehicle to learn about new things in areas I would otherwise hardly explore due to my own initiative.
    – walkmanyi
    Commented Dec 10, 2012 at 20:15
  • 19
    In the end, the review will go out only under your advisors name — This is simply false. First, most CS conference review processes ask for the names of subreviewers, and those subreviewers are credited in the proceedings. Second, when the review goes back to the authors, nobody's name is on it.
    – JeffE
    Commented Dec 11, 2012 at 0:30
  • 17
    The editor knows who the reviewers are — Apparently not! In my research community, outsourcing a review without telling the editor would be considered seriously unethical. (For journal papers, make that "without asking the editor's permission".) Also, I've never heard of "letters of acknowledgment" for reviewing, even for greed card applicants. Different fields are different, I guess.
    – JeffE
    Commented Dec 11, 2012 at 4:26
  • 10
    Claiming credit for (refereeing) work done by your students is wrong. I know that it is accepted practice in some disciplines, but I don't see how it is anything other than dishonest. Commented Dec 11, 2012 at 15:33
  • 3
    In the past I have occasionally given a paper to my student to review in parallel to my review of the same paper. It is important that students understand the purpose and process of reviewing (both so that they can review competently and so that they can write papers that pass review). There is no better way of learning this than by reviewing papers and comparing reviews with someone who already knows what they are doing. Commented Dec 12, 2012 at 11:24

This is partly a response to john k's answer.

In the end, the review will go out only under your advisors [sic] name

Farming out a review to someone else -- especially someone who is subordinate to you -- and then putting only your own name on it is a practice that the vast majority of academics would view as unequivocally unethical. In fact it is essentially plagiarism.

I wish answerers here would not endorse this practice. As Jeff E points out in a comment, if this is done only between the student and the adviser then the editor will not even know about it so certainly cannot be viewed as allowing or participating in this.

So, take this as an opportunity to learn and do not worry that you won't get credit for it.

I certainly do worry about the practice of advisers passing off their students' work as their own.

and he's [the advisor] not going to allow it if it is completely shabby.

If the advisor is going to be involved in the refereeing process anyway, then passing it off to the student is not a clear time savings. However it sounds like a recipe for a bad refereeing job: one very junior, possibly not fully qualified person actually reads the paper, and then the more senior, qualified person mostly looks at the report that the junior person has written. There's a lot of room for something to fall through the cracks.

Here is what I would suggest instead:

1) If as an adviser you actually feel that your student is fully qualified to referee a paper that you have been sent, and if you feel that it will in some way be more useful for your student to do it than you yourself (e.g. you view it as a learning experience for the student), then contact the editor and suggest your student as an alternate referee, while identifying them as your student. Most editors will be happy with this because:

(i) Graduate students can make unusually conscientious and quick referees. I refereed one paper as a graduate student. I was very flattered to be asked to do so, so I carefully read every line and even spent a substantial amount of time gaining background knowledge [for the mathematicians: I had to read part of SGAVII in order to do what I felt was a thorough job]. I also did this over a period of slightly less than a month.

(ii) It's better than asking a very junior person to do the refereeing job out of the blue [as in fact was the case with me in the above situation] because the student can consult with her adviser if necessary, either to ask a key technical question or just to ask for advice about writing the report and dealing with the editor.

I (formally) passed off a referee job to a PhD student of mine about a year or so ago. I think it worked out well: he did a good, fast job, and he did consult me a bit for help. As I recall, most (or all) of the questions he asked me were not about the content of the paper -- on the contrary, after he read it I asked him some stuff out of my own interest and curiosity -- but rather about the mechanics of the referee report: what standards to impose, how to reply to the editor, whether it was okay to request that the authors make a revision doing X and Y, and so forth. I think this latter part was at least as valuable an experience for him as simply vetting the paper for correctness.

2) If you can identify a part of a paper that is sufficiently independent of the rest so as to make it possible to read and judge only that part, then it seems reasonable to contract a "subreviewer" for that part. Maybe this subreviewer is your student and asking her to do it is saving you some tedium. Maybe this subreviewer has expertise that you lack and it is because of them that you feel capable of writing a report at all. With respect to this, I would say:

(i) Of course you need to identify by name all subreviewers that you use.

(ii) If you take on a subreviewer, it should be very clear exactly what the subreviewer is vouching for. You are still the one who is vouching for a paper as a whole. You need to be extra careful that you are not leaving any gaps. For instance, if a paper concerns arithmetic geometry and spectral graph theory, then there will probably be a part in which problems in arithmetic geometry are translated to problems in spectral graph theory, or vice versa. There needs to be at least one referee who understands both of these topics sufficiently well in order to do a credible job.

(iii) If the issues in (ii) are at all complicated -- e.g. if you find yourself wanting to enlist more than one subreviewer -- then it may be better to have this subcontracting process done by the editor. S/he can then, if desired, solicit multiple reports, add/change/remove subreviewers, and so forth.

I have never enlisted subreviewers, and I have refereed more than 30 papers. But I could imagine for instance being given a paper which had a substantial computational component, and then I might ask to see the code itself and give it to a student of mine who has substantial programming expertise. The difference here is that doing so would improve the referee process (it is very unlikely that I would look at the code myself in any detail, and even less likely that any good would come of my doing so). Passing something off to graduate student when you think or know you would do a materially better job already seems slightly ethically suspect.


For a conference, PC members are responsible for reviewing papers. However, it's very common that they can use sub-reviewers, that is, delegating their review to another person. They nonetheless remain responsible for the final review. Some reviewing system, such as Easychair, have an integrated mechanism for asking a sub-reviewer, so there is an official "proof" of the review delegation, and some conferences include in their proceedings the additional reviewers (without saying for which paper, of course).

As for the frequency of such practice, it's hard to tell. Some supervisors might easily use that as an easy way to not do the reviews, others can use them because they believe the student might be more qualified (and more interested) in the particular topic of the paper, others can do it because reviewing is an important task of an academic, and one has to learn at some point. However, if the student does not feel qualified enough to review the paper, he/she should mention it and refuse the review.


It's common in neuroscience. In my limited experience (consisting of two such reviews), the idea was that it's a learning experience for me. My supervisor did his own review independently, then we compared notes, and he put together the final version. In both cases, he mentioned me by name to the journal editors. In one of the two cases I also saw that it's part of the journal's policy that any such PhD students should be mentioned. This, I would say, is a strong indicator that it's common practice.

  • 2
    +1: in my area of the life sciences this is also totally unexceptional behavior. In fact, many editors now explicitly suggest that the faculty member involve a postdoc, student, or other "junior colleague" when they are sending out the request for reviews. This is yet another example of how widely field-specific ethical norms vary.
    – Patrick B.
    Commented Aug 2, 2017 at 20:20

I would never ask someone else to write a review and then put my own name on it, and I don't know of instances of that happening in my field (applied mathematics). If I am unable to referee a paper, I usually suggest alternative referees to the editor. Those suggestions might include one of my students, but it would be up to the editor whether to ask the student to referee.

  • I think the distinctions in field are very important here--applied mathematics is an area where deep knowledge is very important. In fields which are broader and more shallow, a student can quickly make up for lack of breadth by reading another paper or asking a few questions of an advisor. In applied math, if you're out of you're depth, you're stuck for a long, long time.
    – Rex Kerr
    Commented Dec 13, 2012 at 16:51

It is also common for mentors to hand off reviewing tasks to specific group members that work in a field related to the manuscript.

That way, a win-win situation is created, since the group member gets to stay on top of current research in their field of interest.


It is definitely common in our group, but it is more seen as an exercise for the PhD student, as we generally discuss the review with our supervisors and they make sure it's suitable. That way, the PhD student gets practice in paper reviewing and the supervisor has less work (hopefully).

I absolutely agree with some of the other answers that sticking your name on an unread review by someone else or having your supervisor send off your review without discussing it first would be negligent.

(Edit: computer science.)


In my experience from applied computer science, this is very common. Typically, the situation seems to be that professors receive a batch of ten or more manuscripts for an upcoming conference, to be reviewed within a few weeks.

From that point, there are two reasons that make it a logical choice to redistribute at least some of the reviews within the lab:

  • Conferences normally deal with somewhat narrow subfields, yet submissions are normally still diverse enough so different people in the lab are best suited for reviewing some of the manuscripts.
  • Professors are usually swept with all kinds of different tasks, so expecting a single person to thoroughly referee ten or more papers (when each review takes, say, at least a day) within a few weeks is not realistic, anyway.

Concerning the issue of getting credit addressed in some of the other posts, at least my personal perception is that it is a non-issue. Again, I can see three (possibly field-specific) reasons for this:

  • In the fields I am most acquainted with, blind reviews are the norm. Consequently, reviewing is perceived as an activity that is performed anonymously (contrary to, e.g., publishing papers that visibly show the authors' names along with the result of the work). The rare occasion where a conference publishes the list of reviewers may be a nice touch, but I have never seen this done in a prominent way. Hence, the general assumption is that no-one (outside one's lab/group and the small circle of conference organizers) will ever learn that researcher X reviewed papers for conference Y. With this in mind, either conferences would provide an obvious way to indicate subreviewers to the editors - which supervisors will then gladly do -, or they wouldn't, in which case the expected gain is simply not sufficient for anyone involved to go through the hassle of even writing an e-mail to inform the editors about the subreviewers.
  • Connected to the above point, it seems that not only does the fact that X reviewed for conference Y usually remain unknown to the public, no-one is really interested in that piece of information. My impression is that it is simply taken for granted that each doctoral candidate has their share of reviewing experience, as it is expected they get some manuscripts forwarded by their supervisor for reviewing every now and then.
  • Lastly, mirroring the above points, my impression is that reviewing papers is not one of the activities typically associated with getting credit in the first place. It is rather somewhere between the "chores" that someone has to do (and thus, it is understood that it is both fairer and more comfortable for everyone in the group to spread the workload somewhat evenly across the entire group) on the one hand and a good opportunity for expanding one's experience and thus training to improve one's reviewer skills on the other hand - come to think of it, in both aspects, quite similarly to fulfilling one's teaching duties.

Again, the above reflects my personal impression and is probably quite field-dependent (and maybe even a bit culture-dependent, as internal organisation of groups of researchers differs wildly around the globe).

  • It is possible to get credit from reviewing. See for example publons.com.
    – user77791
    Commented Nov 30, 2018 at 10:40
  • @user77791: I do not doubt it is possible to somehow measure the amount of reviewing done by a given researcher. But at least in my field and in my impression, it is not (yet?) a "valuable" kind of credit, simply because the assumption is that anyone is doing a fair amount of reviewing, anyway, with or without a reviewer profile on a site like publons. Commented Nov 30, 2018 at 10:51

There is whole lot of benefits if you are reviewing the manuscript. Your supervisor is a well-known person and active in the field. So he got a paper to review. When you are reviewing the paper you will get the benefits like the following:

  1. Writing style (claims, what to include, what to avoid while writing paper)
  2. How to give negative comments in positive way (although you have to spend some time on this stage)
  3. New methodologies
  4. If you have any confusion or doubts, you can always reach your supervisor for that purpose and learn many things.

Remember, its not always about getting credits. Its about learning something new everytime you do something. Else the whole research world will not grow, given the fact that the PEER-REVIEWERS spend a lot of time for reviewing someone (unseen/unknown) author's works. However, view points might differ. But this is the positive things for me.

  1. You will not get any credit for doing someone else's work.
  2. You might get some knowledge and a little experience working on the project, which some how is good for self satisfaction as you are not getting any thing else
  3. You can ask for some courtesy to the one whom you are shadowing, for bit of your publicity, mentioning your name at end of the day, but again it all depends on him/her.
  4. You can work yourself, put your own name, and at the end of the day you might loose a friendly relationship with a guy.

Ultimately I will conclude : Never get involved in a work that you don't want to do, or the one for which you deserve some credit and you are not getting it. And if somehow if you get indulged in such an activity then forget the credit or forget the relationship, sacrifice needs to be done at that end.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .