Sending applications can feel like progress while leaving you unsure what to improve. A useful job-search log connects each real opportunity to the evidence you submitted, the stage the employer has actually confirmed and your next preparation task. It helps you review your work without turning activity into a promise of an offer.
Start this habit while studying, using a small number of relevant roles. You can then take specific questions to a careers adviser rather than asking only why nothing has happened yet. The log is a planning aid; it does not establish your eligibility to work or the likelihood of employment.
Record a real role before counting an application
Give each opportunity one row. Save the employer's own vacancy link, role title, location, stated deadline and the date you checked it. Distinguish advertised roles from speculative enquiries. If the vacancy changes or disappears, note that rather than treating an old screenshot as a current invitation to apply.
Record any explicit requirements that need checking, including experience, qualifications or work permission. Use the employer's instructions and the relevant current official immigration guidance for your circumstances. A university course, application receipt or interview invitation does not establish permission to work.
If you discover the same vacancy on several websites, keep those links within the same row. Multiple listings of one opportunity are not multiple applications. Separate genuinely different roles even when they are at the same employer.
Link requirements to your own evidence
Oxford's guidance on demonstrating job criteria advises identifying what an employer asks for and choosing specific examples of relevant skills and experience. Examples can come from academic work and other activities; where evidence is weak, the criteria can help identify skills to develop or a closer-fit role. This is application guidance, not an assessment of your eligibility or an offer prediction.
Beside each important requirement, write the example you can honestly explain and the gap you still need to address. A project title alone may not show what you contributed. Keep a short note of your own actions, the evidence available and the result you can substantiate. Do not invent figures to make an example look stronger.
The goal is to make your next preparation task clear: improve an explanation, check a requirement, prepare a portfolio example or reconsider the role. Keep confidential project information out of any public portfolio unless you have permission to share it.
Use stages the employer has confirmed
Oxford's job-search and applications overview separates application writing, interviews, assessments and handling decisions. That distinction is useful for your own record. The stages below are an original tracking suggestion; employers may use a different sequence or skip stages.
Use labels such as researching, preparing, submitted, assessment invited, interview invited, offer received, rejected, withdrawn or closed. Beside the label, save the date and what supports it: an application receipt, employer message or portal update.
Silence is an unknown response, rather than a confirmed rejection. An automated receipt confirms submission, rather than a shortlist decision. A scheduled interview is different from an interview you attended. If you withdraw, record your reason privately so you can learn from it without assigning the employer a decision it did not make.
A simple original log
Use these fields in a notebook or private spreadsheet:
- Opportunity: employer, exact role, vacancy link and location.
- Dates: checked date, actual deadline and submission date when applicable.
- Fit: key requirement, your evidence and unresolved gap.
- Submission: document version and confirmation saved.
- Current stage: employer-confirmed status and evidence date.
- Next action: specific task, planned date and why it matters.
- Outcome: confirmed decision, or still unknown.
Avoid storing passwords, identity scans or sensitive personal details in this log. Application portals and private documents can stay in their appropriate secure locations; a reference to the record is enough for tracking.
A fictional weekly review
Imagine two submitted applications: one has an automated receipt only; the other has an assessment invitation. A third role is still being researched because a stated requirement is unclear. These are invented examples, not a graduate outcome report.
Your summary is two submitted applications, one assessment invitation and one unresolved research task. It is not three completed applications, two rejections or an estimated success rate. Your next actions could be preparing for the assessment and checking the third role's requirement through the employer's stated channel.
For each review, keep the same opportunity set and explain unresolved outcomes. Small early counts are useful for organising work; they are weak grounds for predicting employment. If you want to interpret a university's published outcomes instead, use the separate graduate employment data guide.
Bring one precise question to careers support
Choose the issue your log reveals: how to explain one example, how to prepare for a stated assessment or how to select closer-fit roles. Check the university's actual access and booking rules using the careers-service access guide. Support can help with preparation; its availability is not a placement guarantee.
End each review with one achievable task and a date. A useful log earns its place by changing what you do next, rather than by making the application count look impressive.
Sources checked: 8 October 2026. No salary, placement, visa or employment outcome is promised.
