P3 qualification

From DPWiki
Jump to navigation Jump to search
DP Official Documentation - Proofreading
Languages: English Français Português
If you would like to learn how to receive email alerts when this page is updated, please read this document.

For general information on qualifying to work in different rounds (e.g. P2, P3, F1, F2, etc.), see DP Official Documentation:General/Access Requirements.

Round Access FAQ

For detailed information about qualifying for the various proofreading rounds, please read Access Requirements -- P1, P2 and P3. (Please note that P2 access is automatic once the requirements are met and the request button is pushed). This article does not repeat what is said there, it is a collection of additional information gathered from the forums. (Some of the paragraphs are quotes from forum posts of past evaluators, such as DMkazoo, JulietS and yralih, hence the use of the first person.)

Basic Requirements

  • At least 150 P2 pages across at least three projects, with at least 50 which have been proofread by P3 volunteers. These pages should indicate proofreading proficiency covering a range of matter including footnotes, tables, indexes, illustration captions, poetry and/or sidenotes.
  • At least 50 F1 pages
  • Up-to-date successful completion of the [https://www.pgdp.net/c/quiz/start.php?show_only=PQ Basic, Basic Extra Practice, and Moderate (Parts 1 and 2) Proofreading Quizzes and Tutorial
  • 42 days or more since registration

You can monitor your progress toward the requirements, and apply for access, on the P3 "home" page. After these requirements are met, the volunteer's P2 pages are reviewed before access is granted. See P3 qualification and Am I Ready For P3? for more details.

Please note that an evaluator will check over at least 50 of your recent P2 pages that have been completed in P3. (Except for special circumstances, we do not review pages until they have been through P3!) Due to the extra abilities a project manager has over his or her projects, pages proofread in projects in which the project manager and the applicant are the same will not be eligible for evaluation.

Once you meet these requirements, you can request P3 access via a link on the P3 page, below the list of requirements.

Why F1 pages?

F1 pages are considered a necessary requirement before working in P3 so that the proofreader is aware of the formatting guidelines, what is included in formatting, and consequently what not to do when proofreading. To date no other way of measuring this skill has been formulated. Some have said that working in F1 has helped make them better proofreaders because, for example, they know they

  • can ignore long strings of asterisks in a row by themselves in P3 and don't have to add them to the proofread text in order to "match the scan" because the formatters will add a <tb> tag instead
  • should leave small caps text as it comes to them because the formatters will change it to mixed or upper-case as appropriate
  • should leave only one blank line between paragraphs, headings, subheadings et al. without having to match the extra space as shown in the original image
  • will recognise a series of short lines to be a list and don't need to worry about adding or removing blank lines between items on the list
  • most importantly, don't need to be concerned about diffs that are due to formatting issues

Evaluation of Pages

After you request access via the P3 page, an evaluator will check over at least 50 of your recent P2 pages. If you didn't miss too many errors, then you will be given access to P3. If you missed too many errors, then you will be asked to proof more pages and try again. Either way, you should receive a PM informing you of the status of your request and listing which pages were used for evaluation. If you apply before 50+ pages have gone through P3, the wait for results can be over a month.


Check the list of DP administrators for currently-assigned evaluators. If none are listed or responding to queries, you may contact the General Manager via email (dp-genmgr at pgdp dot net).

Which pages?

We cannot do an evaluation until at least 50 eligible pages across three different projects have been proofread by you in P2 within the last 100 days and have been proofread in P3. To be eligible, a page needs to have valid diffs in either or both P2 and P3. Pages that come perfectly from P1 are not eligible.

Depending on the project, proofreading more than 40 P2 pages in a single project may not always demonstrate various skills; in such a case, evaluators may choose to use a subset of those pages. Also, evaluators may decide whether to review projects in which you have proofread fewer than 15 pages.

Once evaluators have reviewed the most recent pages that you have completed in at least three of your most recently completed projects, if there are sufficient pages, the evaluator will decide whether or not to review older pages. In addition, if, after reviewing several pages, the error count has been too high, the evaluators may not continue to review the rest of your available proofread pages.

Evaluations are undertaken by looking at what the P3er found that the P2er may have overlooked. A check is also made to ensure that the diffs made in P2 are valid. Evaluators work from the most recent of your proofread pages to the oldest because it is expected that your work will have improved over time. If you don't have some fairly recent work available, the evaluation cannot be undertaken and the application will be cancelled.

When projects in more than one language are encountered, the evaluators separate the evaluations and grant access on a language by language basis.

How many errors?

Before we added another proofreading round (then called P2alt), the cutoff for P3 access was one serious error in 5 pages (averaged across 50+ of course). Since virtually all the pages that were considered were from P3 Qual projects, we were able to keep them roughly the same size. We have decided to keep this error rate (1/5) for the time being. This means that we divide the number of evaluated pages by the number of errors found, and will generally approve applications where the resulting number is greater than 5.

For example: MickJagger has proofed 323 P2 pages. Of these, 162 have been proofed by P3. Of those 162 pages, 72 have no changes made by either P2 or P3, leaving 90 eligible pages for evaluation. Unfortunately, MickJagger did not catch 41 errors, giving him an error rate of 2.195 and he does not pass on this try. IggyPop has proofed 157 P2 pages, of which 121 have been through P3. Only 6 had no diffs, leaving 115 for evaluation. IggyPop is a born DPer and has left only 8 errors, giving him a rate of 14.375 and a welcome into P3.

The evaluators do keep in mind the overall difficulty of a page. Some pages might be disregarded for qualification purposes if those pages have a high number of errors to correct and/or contain a large amount of specialist material. We might either ignore very long pages or count them as several pages. The evaluations will always have notes about any of these things. This is yet another reason why we have humans doing the evaluations.


But, knowing that even this might be too much for a small community (such as languages other than English with a very small volunteer base at Distributed Proofreaders), we have left an alternate path for P3 or F2 access in such cases. You may send the General Manager a PM with the DP usernames of people you think should be able to work in either P3 or F2 or both, and, provided the General Manager approves, the appropriate Evaluator Team will do a special review of their access. Please note that this recommendation has to come from someone who already works in those rounds (or has a sound knowledge of the work involved) and that this process applies only to tiny communities which require language knowledge that very few of our volunteers have.

Improving Your Proofing Accuracy

If you're not happy with the quality of your diffs, there's no need to apply just to clear things out. You can just keep working on your proofreading until you think the last 75–100 Qual diff pages look good, then apply. However, if you want an official review of your work complete with proofreading suggestions tailored to your particular potential areas of improvement, by all means go ahead and apply.

Qual projects, while excellent and appropriate for taking your proofing temperature when you're trying to beat a problem (or for accumulating enough pages to get an evaluation), are not the best place to work that problem through. Think of them like water: something necessary and which you're welcome to use. Don't leave it running and walk off, though.

If any P3 candidate has a besetting fault, spend time concentrating on it in the regular projects. Pick a book that will be around for at least a couple of days. Try out your new proofing strategies on it. Go back the next day and look at the pages again with fresh eyes. If you're finding things on the second pass that you missed on the first, try to figure out what and why. Maybe ask for feedback from a P3er.

After you think you've made progress on that front, by all means do 5 or 10 Qual pages to get P2–P3 diffs and see if they're lining up with what you thought they'd say. If all is well, do more Quals with an eye toward accumulating enough to apply. If problems are showing up, go back to practicing on regular projects, and dip back into Quals to check your progress.

You can find other strategies in the Tips'n'Tricks on improving proofing accuracy thread.

Related Wiki Pages

Access requirements

Am I Ready For P3?

To comment or request edits to this page, please contact jjz or John_NZ.

Return to DP Official Documentation Menu