Most EPQ students meet the production log as a form to be filled in, and fill it in accordingly: briefly, vaguely, and — in the worst cases — all in one sitting the week before submission. That is an expensive misunderstanding. The log is not paperwork that accompanies your project; for the assessor, it is half the project — the main evidence for AO1 (Manage) and much of AO4 (Review), and the place where your research decisions support AO2 (Use Resources). This guide walks through the document section by section, for both the AQA staged form and the Edexcel activity log. It sits alongside our complete EPQ guide, which covers formats, grading and timelines for the qualification as a whole.
One point of honesty first, because the log is where it matters most. Your EPQ must be your own work, supervised and authenticated by your centre, and the log is part of that authentication: it has to be a truthful record of a project you genuinely did, written as you did it. Nobody can legitimately write your log for you, and a polished log describing a project that never happened will unravel the moment your supervisor compares it with what they saw. What help can do — and what this guide does — is show you what each section is really for, so the real work you are doing gets recorded in a way assessors can reward.
What the log is, and why its format differs by board
AQA builds the log into a single staged document — the Production Log within the Candidate Record Form — with named sections you complete at set points: a record of initial ideas, a proposal in parts, a planning review, a mid-project review, a project product review, a presentation record, and a closing summary and reflection. Other pages in the same document (the declaration, checklist, taught-skills record and record of marks) are completed by you at signing stage or by your supervisor and centre coordinator, not narrated by you. Edexcel (Pearson) splits the evidence differently: a project proposal form, signed off before substantive work begins, and then an activity log — an ongoing, dated record of activities, progress and decisions kept continuously rather than at fixed review points. Centres deliver either board’s paperwork through online platforms or their own templates, so treat the section names below as the substance to cover and check your centre’s exact version.
Record of initial ideas: proving the title was chosen, not landed on
The opening section asks what you considered before you settled. Weak entries name one topic and one title, which tells the assessor the choice was never really made. Strong entries show a small field of genuine candidates — typically two or three areas or draft titles — with the reason each attracted you, the problem each carried, and why the survivor won. Perhaps one title was fascinating but source-poor, another overlapped too closely with your A level syllabus (a real disqualifier: the project must extend your studies, not repeat them), and the third could be argued from evidence you could actually reach. Record your supervisor’s comments too, including advice you did not take, with your reason — assessors check that a discussion happened and that you decided inside it, not that you obeyed. Write this section at the start, while the rejected ideas are still real to you.
Proposal and planning review: the plan you will later be judged against
On the AQA route, your Proposal Part A states the working title and aims, the form the product will take, and the research and resources you intend to use — specifically, not “books and the internet” but named databases, texts, collections or people. Parts B and C are your supervisor’s and centre coordinator’s responses, and on both boards substantive research waits for approval: Edexcel’s proposal form likewise needs sign-off before further work. Do not treat approval as a hoop; it is the moment your scope gets stress-tested while changing it is still free.
The AQA Planning Review, written once the proposal is approved, converts intention into management: your next steps and self-set deadlines, the resources each step needs, a summary of your supervisor’s advice, and the modifications you made because of it. That last element — advice in, change out — is the pattern the whole log rewards. A workable entry names stages with dates you chose (research complete by a stated week, first draft by another), flags the predictable pinch points such as mock exams, and notes a contingency, however simple. Your later reviews will be marked against this plan, which is why a realistic one beats an heroic one: a plan you visibly adapted scores better than a plan you silently abandoned.
The research record: selection, not accumulation
Whether your board gives research its own pages or expects it inside the ongoing log, keep a running research record from the first search onwards. For each significant session, note where you searched, the terms you used, what the search returned, and — the part students omit — what you rejected and why. A source discarded as outdated, partisan without disclosure, or answering a slightly different question is excellent AO2 evidence, because it proves discrimination rather than collection.
Short example of the register that works: “Searched JSTOR and Google Scholar for ‘school starting age outcomes UK’. Kept two cohort studies; set aside a campaign page (no methods given) and a 1998 paper superseded by the later cohort data. Search terms too broad at first — added ‘reception year’ to cut US pre-school results.” Three sentences like that, kept across the project, do more for your grade than a final bibliography ever will, because they show the bibliography being built by judgement. Log method decisions here too: materials tested, data-collection choices, design routes tried and dropped.
Mid-project and product reviews: the hinge of the whole document
The mid-project review is the log’s most consequential page. On the AQA form it asks directly whether the project is still following the original plan, how the plan has developed, what your supervisor advised, what you modified as a result — and it fixes your final title and the agreed form of your product. Write it at the true midpoint, when research is substantially done and production is beginning. The strongest entries report drift honestly: the question narrowed because one strand had far richer evidence; the artefact’s material changed after a failed prototype; the field study’s sample shrank and the write-up plan absorbed that. Then they restate the remaining steps against the remaining time.
The later product review works the same way at smaller scale: supervisor advice on the near-finished outcome, and the minor changes you made in response. On the Edexcel route these review moments live inside the activity log rather than on separate pages, so mark them clearly — date them, head them as reviews, state the decision each produced. On either board, a review that changes nothing and notices nothing is a missed page: if genuinely nothing needed changing, say what you checked to conclude that.
Supervisor meetings, problems and decisions: the entries students skip
Between the formal reviews, keep brief dated entries for supervisor meetings and problems as they occur. Each needs the same four beats: what happened or was advised, the options you weighed, what you decided, and what you did next. A lost fortnight to illness, a key source withdrawn, a chapter whose argument collapsed under its own evidence — each is normal project life, and each converts into AO1 evidence when logged at the time with its response attached. Assessors reward the chain from event to decision to consequence: “research went well this week” breaks it at every link, while “the archive visit returned nothing usable, so I replaced the case study with the published dataset and moved drafting back four days” completes it.
Presentation record and final evaluation: closing the project honestly
The log’s presentation record (Part A on the AQA form is yours; your supervisor completes the record of the event and questioning) asks you to plan the presentation before you give it: what you will cover, in what form, for a non-specialist audience, and what changed after rehearsal or discussion. Treat that planning entry as part of the assessment, because it is — a presentation visibly thought about evidences review skills before you have said a word.
The closing summary and reflection is where AO4 is won or lost. Answer it against your original aims, not against a glow. What did the product achieve relative to the proposal? Which decision, reversed, would most improve it? What did you learn about the subject, and separately, about managing long work — and where in your own log is the evidence? Quote your earlier entries back to yourself: evaluation anchored in dated evidence beats superlatives (“I really enjoyed it and learned so much”), which are the commonest way students undersell a good project.
Contemporaneous or written at the end? A section-by-section rule
Use this rule: anything recording a decision must be written when the decision is live; only the signing and the final reflection belong at the end. Initial ideas, proposal, planning review and research entries are worthless reconstructed, because their value is precisely that they predate the outcome. The mid-project and product reviews must sit at their real points in the timeline. The declaration is signed last, and the final evaluation is written last but built from the dated entries beneath it. If you are reading this with a thin log and a nearly finished project, the honest repair is to write up, now, a frank account of the stages as you remember them, dated as a retrospective account and saying so — then keep the remaining entries live. An openly retrospective section is a weakness; a backdated fabrication is an authentication problem, and supervisors who watched your project develop can tell the difference.
The failures assessors see every year
Four patterns recur. First, the immaculate project: no setbacks, no changes, nothing rejected — implausible for two terms of independent work, and starved of decision evidence. Second, the diary of attendance: dates and activities with no reasoning, documenting presence rather than management. Third, advice recorded but never answered: your supervisor’s comments appear, then nothing changes and you never say why you disagreed. Fourth, the log written in a different voice from the project itself — suddenly fluent, suddenly generic — which invites exactly the authentication questions the document exists to close down. One habit avoids all four: short, dated, specific entries written while the work is warm.
Get coaching on your production log
If your entries are drifting into diary mode, or a review point is approaching and you do not know what an assessor needs to see in it, that is precisely where coaching helps without ever crossing the line into writing the record for you. We review the log you have kept, show you where decision chains are broken, teach you how to frame the remaining reviews and research entries, and give feedback on drafts you have written — the record stays yours, as it must. Our wider guide to how to write an EPQ dissertation shows how the log and the product support each other. Support is priced from £20 per 1,000 words of material reviewed or prepared. Send your brief — board, format, deadline and the sections worrying you — place an order through the site, email team@unitedacademichelp.uk, or reach us on WhatsApp via the contact page.
Frequently asked questions
How much should I write in the production log? There is no word count for the log on either board. Write enough for each decision to be visible: most strong entries run from a short paragraph to a page per section or review point. Thin entries lose marks not by length but by missing reasoning.
What is the difference between the AQA log and the Edexcel activity log? AQA gathers the record into one staged document with named review points — initial ideas, proposal, planning review, mid-project review, product review, presentation record and final reflection. Edexcel separates a signed-off project proposal form from a continuous, dated activity log. Centres vary in how they present both, so confirm your centre’s version.
Can I write my production log at the end? Only the declaration and final evaluation belong at the end, and the evaluation should draw on entries made at the time. Decision-recording sections written retrospectively lose their evidential value, and presenting reconstructed entries as contemporaneous risks an authentication problem.
What if nothing went wrong in my project? Something changed, even if nothing failed: a title narrowed, a source disappointed, a deadline moved, a method was adjusted. Record those. If a stage genuinely ran exactly to plan, write what you checked to confirm it was on track — monitoring is itself management evidence.
Should I record supervisor advice I disagreed with? Yes, always — and your reason for departing from it. Assessors reward evidenced decision-making, not compliance. Advice that vanishes from the record, or appears with no response, weakens both the manage and review evidence.
Does the log really affect my grade that much? Yes. It is the main evidence for AO1 (Manage) and much of AO4 (Review), and it supports AO2 through your research record. A strong product with a thin log will be graded as a project whose management and reflection cannot be evidenced — because, to the assessor, it cannot.