How to Use a Decision Log During a PhD Search

A PhD search can become confusing long before you have too many opportunities. A few browser tabs, messages, programme pages, and funding pages can be enough. You remember that one lead looked promising, but not which page said what, when you read it, or what still needed checking.

A decision log gives one lead a short, usable record. It separates what the official page says from what you think, what is still unknown, and what you will do next. Use it when you need to decide whether to keep researching a lead, ask one focused question, or put it aside for now.

This is not a full search system and it is not a way to rank universities. It is a trace for one decision at a time. A good entry should let you return a week later and understand why you acted without relying on memory.

Begin with one decision, not a page full of notes

Before you write anything down, name the decision. Keep it small enough to answer from the source material you can actually see.

For example, you may need to decide whether a lead has a clear application route, whether it is worth reading the admission instructions, or whether one missing point needs a direct question. You are not deciding whether a university is "the right one". You are deciding what the evidence supports today.

That distinction matters. Broad notes often mix several questions together: research fit, funding, eligibility, supervisor contact, and personal preference. A decision log works best when it has one purpose. If a second question appears, give it its own entry or make it the next step. This keeps the record honest and makes it easier to update when a source changes.

The title of the lead should come from the official page whenever possible. If you first found it in a directory, save that link too, but do not treat the directory entry as the final source for an application rule, deadline, funding term, or eligibility requirement.

Use six fields for every lead

You do not need a complicated spreadsheet. A notes app, document, or table is enough if it keeps the evidence next to the decision. The six fields below are the core of the log.

The fact field should be plain and narrow. If an official page names an application portal, write that it names an application portal. If it describes a funding route but does not say what an individual applicant will receive, write that the individual terms are not yet confirmed. The log is stronger when it says less but can point to the exact page.

The source field is just as important as the fact. Pages that look similar may have different roles. One page may describe a doctoral programme. Another may explain admissions. A third may state the terms of a funding award. Each belongs in the log if it is part of the decision, but each should be labelled by its role. This lets you see when a general overview is being asked to answer a question that only a direct application or funding page can answer.

Keep evidence and personal preference in separate columns

Personal preference belongs in a PhD search. It is reasonable to care about a research direction, location, work style, training environment, or the type of methods you want to learn. The problem starts when a preference is written as if it were a verified fact.

Keep one short preference note beside the evidence, but label it clearly. This makes the decision more useful, not less. You can see both the external evidence and your own priorities without mixing them.

The first column should always be traceable to a source. The second column is your judgement. Neither should pretend to be the other. A sentence such as "this probably covers everything" is neither a fact nor a useful preference. Replace it with the missing question and keep the lead in the right place until you have an answer.

Find the page that controls the question

Many useful places help you discover opportunities. They are not all the page that controls your next decision. The distinction is practical, not academic.

For example, the German Academic Exchange Service explains that its PhD databases help people find offers, then says applicants apply online at the offering university. That makes the university's page the place to record for the application route. The DAAD page can remain in your log as the discovery source, but it should not be used to settle a university-specific requirement.

The same pattern appears with funding. UK Research and Innovation explains that applicants for UKRI-funded studentships apply through the research organisation, and that research organisations have their own eligibility criteria. The UKRI page helps you understand the wider route. A particular institution's current studentship and admissions pages are still the source for an individual decision.

When a log entry depends on more than one page, note the chain rather than forcing one page to carry everything. A simple chain might look like this:

Discovery page → official opportunity or programme page → admissions or funding page

You may not need every link for every lead. Save the ones that answer the question you are deciding now. If a source is missing, that is information too. Record the gap instead of filling it with an assumption.

Record the date you saw the information

The date in a decision log is not a decoration. It tells you when the fact was true on the page you opened. This is especially useful when you return to a lead after a few weeks, receive a message, or see that a page has been replaced.

If a source changes, do not silently rewrite the old entry. Add a new date and a short note about what is different. You may find that a link now points to a new application round, an old page is archived, or a requirement has been clarified. The earlier note is still useful because it explains the decision you made at that time.

Do not guess from a page's design that it is current. Look for a date, cycle, status, or clear application instruction. When those signals are absent, write the uncertainty exactly as it is: "No current status is stated on the page I found." That is more useful than calling it open or closed without evidence.

Make uncertainty specific enough to act on

An uncertainty field prevents your log from becoming a collection of optimistic guesses. It should state one missing fact and, if there is a permitted route, the next way to check it.

Weak uncertainty notes are hard to use later: "Need more information" or "Maybe eligible." Better notes say what is missing: "The admission page does not state how this degree is assessed," or "The funding page does not explain whether this route applies to my fee status." These notes create a real next step. You can read another official page, check the programme instructions, or ask a focused question through the contact route the institution provides.

Sometimes two official pages appear to conflict. Do not average them or choose the answer you prefer. Record both links, their dates, and the exact point of disagreement. Then identify which organisation owns the decision. A funder usually controls the award terms. An admissions office controls entry requirements. An employer or university vacancy page controls the advertised role. If the source hierarchy is still unclear, the uncertainty remains open.

Let the decision stay modest

The decision field should describe what happens next with the lead, not your final view of the university or your chances of admission. Good decisions are temporary when the evidence is temporary.

You might decide to keep researching because the official route is clear but the funding source still needs reading. You might pause because one eligibility question has a named contact and you need an answer before investing more time. You might move a lead out of the active list because the controlling page no longer supports the reason you saved it. Each decision is valid when the evidence is recorded beside it.

Avoid turning the log into a scoring system. A separate comparison process is more suitable when you have two or more verified opportunities and need to weigh research fit, conditions, and personal priorities. This guide is earlier and smaller. It protects the connection between one source and one decision.

Use a short template you can return to

The following template is deliberately plain. Keep the wording close to the pages you read. Replace the brackets with your own evidence rather than copying the example into a live record.

Lead: [official title]
Decision I need to make: [one narrow question]

Fact: [what the official page says]
Official source: [direct URL, page title, organisation]
Date: [day opened or rechecked]
Uncertainty: [one missing fact or point of conflict]
Decision: [keep researching, pause for confirmation, or move out of the active list]
Next step: [one action that could resolve the uncertainty]

Preference note: [your own priority, clearly marked as personal]

Here is what a useful entry looks like in practice without relying on a made-up opportunity. The fact may say that the official programme page links to a separate admissions page. The source field holds both links. The uncertainty may say that neither page explains a point that matters to you. The decision is not "apply" or "do not apply" yet. It is "read the relevant funding terms before deciding whether this belongs in the active list." The next step has a clear limit and a clear reason.

That is enough. A decision log does not need to capture every thought you have while searching. It needs to preserve the path from evidence to action.

Revisit the log when something changes

Return to an entry when a source changes, you receive an official response, or you are about to spend serious time on the next step. Read the source again before relying on your earlier summary. If you learn something new, add it as a new dated note and revise the decision only when the evidence supports that change.

Keep private messages and personal information with care. A log can say that an official response clarified a requirement without copying private details into a shared file. Store only what you need to understand your own decision and follow the institution's stated process.

Over time, the log becomes useful in a quiet way. It shows which questions keep delaying your search, which sources answer those questions well, and where you may be relying on assumptions. That gives you a more reliable next step than trying to remember every tab.

Sources

• UKRI-funded studentships explains that applicants apply through the research organisation and that organisations set their own eligibility criteria. It is a useful example of why a general funding page and an institution's page can have different roles.
• DAAD: How to Find Your PhD Position in Germany shows a discovery route and directs applicants to the offering university for the application. It illustrates why a discovery page should not replace the page that owns an individual application.

Create your search profile