How to Build a PhD Application Document Checklist From Official Instructions

A PhD application checklist is only useful when it belongs to one real application. A list copied from a forum, a friend, or another university can remind you of common tasks, but it cannot tell you what your programme requires this year. It may cause a worse problem: you spend time preparing documents that are not requested, while overlooking a condition that is.

The practical goal is not to collect every document that might exist. It is to turn the current instructions for one programme, vacancy, or funding route into a short record that you can follow and check. That record should show what the university calls each item, whether it is required, where it is uploaded or submitted, who owns it, what it depends on, and what page says so.

This guide is deliberately narrow. It helps you build the document checklist for one application. It does not replace a full application plan, decide whether you are eligible, or tell you what every university will ask for. Those answers belong to the official pages for the opportunity in front of you.

Begin with the page that controls the application

Start with the course, programme, vacancy, or doctoral-school page that tells applicants how to apply. Do not start with a general admissions article unless the programme page points to it. The programme page usually tells you which route applies, which deadline matters, and whether it has its own instructions in addition to central graduate-admissions guidance.

There may be more than one official page, and that is normal. A programme page may name the documents. A central application guide may explain file formats and the portal. A funding page may add a separate statement or referee. A vacancy page may request a cover letter and CV before the graduate school asks for its materials. Put all of the relevant pages in the same application record, but do not merge their requirements until you know which one covers which stage.

Oxford makes this distinction clearly in its graduate supporting-document requirements: the required documents depend on the course page, while central guidance explains how supporting documents must be prepared and uploaded. That is a useful pattern to look for at any university. The course page tells you what is needed for that application; the central page may explain how the system handles it.

Before extracting anything, write these details at the top of your checklist:

If you cannot find the official application page, do not build a detailed checklist from a copied advert. Keep the lead in your search notes and find the university, employer, or funder page first.

Read the instructions once without making a list

It is tempting to open the portal and begin uploading immediately. Read the instructions from beginning to end first. Universities often place a condition below the document list: a separate funding deadline, a course-specific prompt, a referee route, or a note that a particular item is needed only after an offer.

On the first reading, mark every instruction that uses words such as “must”, “required”, “if applicable”, “where relevant”, “before submitting”, “after an offer”, or “do not upload”. These phrases tell you whether an item belongs in the current checklist and at which point.

The Cambridge supporting-documents guidance is a good example of why this matters. It directs applicants to their course page to see which documents they need, then separates references, transcripts, CVs, language evidence, personal statements, test scores, and financial documents. It also distinguishes what is uploaded through the Applicant Portal from references submitted by referees through a different route. The lesson is not that every university uses these categories. The lesson is that each category must be taken from the current instructions, not from memory.

Keep a separate note for questions. If a page is unclear, write the exact sentence or heading that caused the question. Do not silently turn an unclear sentence into a requirement. A good checklist can contain “confirm this” when the instructions do not answer it.

Turn every stated item into a traceable row

Now create one row for each item named in the instructions. The document name should match the university's wording. If the page asks for a “statement of purpose”, record that label. Do not rename it “research proposal” because you have used one before. Similar documents can have different prompts, lengths, and assessment purposes.

Use a table that makes missing details visible:

The examples above are row shapes, not a list to copy. Your own table may have fewer items or different ones. A project-funded vacancy may ask for a CV and motivation letter. A doctoral programme may ask for academic transcripts and a statement. A fellowship may have a host statement and proposal. Add only what the relevant instructions say.

The “exact page” column matters because it lets you return to the sentence that created the row. A short note such as “supporting documents page, section on transcripts” is better than a vague note such as “university website”. When you check the page again before submitting, you can see whether the wording has changed.

Capture the prompt, length, and format separately

A completed-looking checklist can still fail if it records only the document name. Each item needs its own specification. For applicant-written material, copy the prompt in plain language and record the limit exactly as stated. For uploaded records, write down the accepted file types, size limits, and any rule about combining pages.

Do not assume that one format applies to every upload. Oxford's central guidance, for example, describes accepted file types and size limits, but it also directs applicants back to the course page for document-specific requirements. The course may specify a different document slot, a word limit, or a particular form of written work. The course instruction and the portal instruction must agree before you treat the item as ready.

Add these columns to your table when they are stated:

If the portal field looks broader than the published instruction, follow the published instruction and ask the admissions contact if the mismatch prevents submission. Do not use an open upload field as permission to add unrelated documents. Oxford explicitly tells applicants not to upload material that is not required to support the application. That is a sensible rule beyond Oxford too: extra documents are not a substitute for the right documents.

Treat translations and official records as a separate task

Translations, interim records, degree certificates, and transcripts are easy to leave until the end because they are not written by you. They deserve an early place on the checklist because they may depend on a registrar, university, or authorised translator.

Record the original record and its translation as separate rows when the instructions require both. The checklist should say who will provide each one, what form is accepted, and whether the original-language version must also be uploaded. Do not assume that translating a document yourself is acceptable. Cambridge's guidance says that documents not in English need a full translation prepared by a registered translator. Oxford's transcript guidance says that applicants with a non-English transcript must provide the original and a translation that meets its published requirements. These are examples of institution-specific rules, not a worldwide standard.

The stage of the application also matters. ETH Zurich's doctoral registration document guidance applies to its doctorate registration route, not to every PhD application. It shows why a checklist should name the stage: its instructions cover original-language records, translations, PDF uploads, file-size limits, and documents from applicants who have not yet received a Master's diploma. Do not transfer those rules to another institution. Instead, use them as a reminder to look for an equivalent page in your own route.

For each academic record, add a dependency note. It might say “request from registrar”, “translation must accompany original”, “awaiting final grades”, or “ask admissions whether an interim transcript is accepted”. A dependency note is not a prediction. It tells you what must be resolved before the item can move to ready.

Give references their own part of the checklist

References often fail because an applicant's checklist says only “ask referees”. That is not enough. A referee needs the right request, route, deadline, and context. The application may also have rules about the number or type of referees, confidentiality, institutional email addresses, or whether the referee uploads the letter directly.

Create one row for each required reference and record:

• the number of references required;
• whether the programme specifies academic, professional, or another type of referee;
• the route by which the reference is submitted;
• whether the reference is due on the same date as the application;
• the exact course or vacancy link you will send to the referee; and
• whether a separate funding application adds another referee or form.

Cambridge's reference instructions state that referees submit references through its Referee Portal and that applicants should make sure a referee knows the course and deadline. Oxford's referee-registration guidance provides a different example: it sets its own reference route and submission rules. Neither example tells you what your programme requires. They show why the submission route belongs in the checklist rather than in a general note to yourself.

The owner column should say “referee”, not “me”. Then add a small completion record: invited, accepted, submitted, or not yet confirmed. Do not ask a referee to share confidential material unless the institution permits it. Your task is to make sure the request and route are clear, not to collect the letter yourself.

Map dependencies before you decide a document is ready

Some checklist items are independent. You can prepare a CV when you have the current requirements. Others depend on another person, an earlier decision, or a portal action. The dependency map is what keeps a checklist from becoming a pile of finished files that cannot yet be submitted.

For every row, add one of these labels where it applies:

This is also where you separate an application requirement from later evidence. A university may request a transcript with the initial application but ask for final originals only after an offer. A language test may be needed by the application deadline, at a later stated point, or only for some applicants. Record the stage exactly as the official pages describe it. Do not bring a later condition forward without evidence, and do not assume a later deadline means the item can be ignored.

Run a final portal check using the same table

When the documents are ready, open the application portal and compare every field with your table. This is a comparison, not a second attempt to remember what you read. Check the title, programme, deadline, requested uploads, and whether each reference has been received. Confirm that each uploaded file is the final version for that programme and that it opens correctly.

Use four simple marks in the final column:

• Not started: the item has not been requested, written, or obtained.
• In progress: work has started, but a dependency or final check remains.
• Ready to upload: the item matches the published requirement, but has not yet been added to the correct field.
• Submitted or confirmed: the portal, referee system, or stated route shows that the item has been received.

Do not treat a green tick in a portal as proof that the content meets the programme prompt. It may only show that a file was attached. Your checklist should confirm both sides: the file was submitted, and it was prepared for the requirement that the programme actually published.

Before pressing submit, reopen the main application page and each supporting page in your table. If wording has changed, update the relevant row and decide whether it affects your material. If a condition remains unclear, send a concise factual question to the contact named in the instructions rather than guessing.

For the wider work of sequencing your application, see the international PhD application workflow. For the question of whether you meet the stated route, see the guide to PhD entry requirements and eligibility. This checklist is the smaller working record that helps you carry one application through those broader decisions.

Browse practical guides

Official sources

• University of Oxford: Graduate supporting-document requirements
• University of Cambridge: Supporting documents
• ETH Zurich: Doctoral registration documents
• University of Cambridge: References
• University of Oxford: Registering referees