Apprenticeship applications — the school files you'll wish you kept

University applications get most of the airtime when people talk about "what comes after school". For an apprenticeship application, the work you produced at school is often more directly relevant than for an academic application — and the assessment process leans harder on evidence.

Here's what to save from your school M365 account specifically if you're applying for an apprenticeship.

How apprenticeship applications differ

Most apprenticeship applications combine some or all of:

• A formal application form — like UCAS but employer-specific.
• An assessment day — practical tasks, problem-solving exercises, group work.
• An interview — sometimes panel, sometimes one-to-one.
• A portfolio review — particularly for higher / degree apprenticeships in technical or creative fields.

The portfolio review is the bit where your school work matters. Employers want to see evidence of independent thinking, project follow-through, technical capability, and how you handle being given a problem and time to work on it.

What to save, by apprenticeship type

Engineering / advanced manufacturing:

• Any independent project (EPQ, F1 in Schools, Arkwright, robotics club, design technology coursework).
• Technical drawings, CAD files, photographs of physical builds.
• Lab reports demonstrating method, results and analysis.
• Maths coursework if it shows applied problem-solving.

Software / digital:

• Code listings — GitHub commits if you had a repository, OneDrive code projects if not.
• Any technical writing — README files, project documentation.
• Computer Science coursework, particularly the practical project.
• Anything from extra-curricular technical activity (Bebras, Cyber Centurion, programming competitions).

Construction / civil engineering:

• Design technology and architecture coursework.
• Drawings, models, technical specifications.
• Geography fieldwork if it shows surveying or measurement skills.

Finance / professional services:

• Maths and Further Maths coursework.
• Business Studies, Economics or Accounting work.
• Anything quantitative — spreadsheets you built, data you analysed.
• Letters to / from employers from work experience.

Healthcare:

• Biology coursework, particularly lab reports.
• Volunteering records, work experience reflections.
• Any project work that involved interacting with the public (NCS, Duke of Edinburgh, mentoring).

Creative / media:

• Same as for creative university applications — finished pieces, development work, the trajectory over time.

OneDrive vs OneNote for evidence

The two workloads carry different kinds of evidence:

• OneDrive holds finished outputs — completed essays, final reports, finished CAD drawings, the polished version of work.
• OneNote holds the development process — your thinking through a problem, drafts, iterations, the steps that led to the finished output.

For apprenticeship interviews, the OneNote development pages often impress more than the OneDrive finished work. Interviewers are looking for evidence that you can work independently on something you weren't told exactly how to do. The page where you wrote "this didn't work because X, so I'm going to try Y" is the page that demonstrates that.

Class notebooks are particularly rich for this. Your section group inside a class notebook is where you typed your in-class working, where the teacher annotated your homework, and where the back-and-forth of "this is what I tried, this is what was wrong" lives. That's evidence.

How to present it at interview

Don't show up to an interview with a 5 GB folder. Curate.

A practical pattern:

1. One or two finished pieces — your strongest work, presented in their final form.
2. A development thread — one project, with the OneNote pages showing how you went from initial idea to finished piece.
3. A reflection — a short written piece on what you learned doing the work, what you'd do differently, what surprised you.

That's three documents, a few pages each. Print them as PDFs to take with you, plus have the originals on a laptop or tablet in case the interviewer asks to see more.

Timestamps and provenance matter

Apprenticeship interviewers are sometimes more suspicious than university tutors about whether you actually did the work. The original Microsoft 365 files have author metadata and creation dates that prove provenance. Don't strip the metadata accidentally by, say, copying everything into a new folder system and letting your OS reset the dates.

Keep the original files with original metadata. The PDF versions for presentation are convenience copies; the originals are the evidence backstop if you ever need to demonstrate that the work is genuinely yours.

When to save

Same as for university applications — the last fortnight of formal teaching is the cheapest moment. Apprenticeship application cycles can run from January through to autumn of the year you start, so you may need this evidence months or years after your school account closes.

If your apprenticeship cycle is in autumn after your A-levels:

• May: download from school M365 while account is active.
• June–August: exam period and results; archive sits ready.
• September onwards: interviews and assessment days; you have the material to draw on.

If your cycle runs differently (some apprenticeships interview in spring of Year 13 for starts after the summer):

• Before the interview window: download from your school account.
• Don't wait until after results day — your account may be deactivating around the same time you most need the evidence.

On work experience records

Apprenticeship applications often weight work experience heavily. If you have any of the following on your school account, they're worth preserving:

• Emails between you and a work experience placement (offer letters, instructions, follow-up).
• Reflective writing you did about the placement (often part of PSHE or careers programmes).
• Project work the placement gave you that you completed.
• Photographs from the placement (with permission).
• Any presentations you gave to the class about the placement.

These are the kind of secondary evidence that gives interviewers something specific to ask you about.

On references

Many apprenticeship applications use references from teachers in addition to academic transcripts. Your school's MIS holds the formal record, but emails between you and teachers about specific projects can be useful supporting context — both for the reference writer and, in some cases, for you to share directly.

Export your sent and received items folder before your account closes. Most of the email is throwaway; the threads with specific teachers about specific projects are sometimes worth keeping.

After you've started the apprenticeship

Even once you've secured the place, the evidence still matters:

• End-point assessment for apprenticeship standards often requires a portfolio of evidence demonstrating competence. Your school work isn't directly part of this, but the style of organising evidence is the same skill.
• Promotion / progression within the apprenticeship sometimes refers back to entry-point capability.
• Career changes later in life can ask about your earliest formal work.

The school M365 archive ages well. Twenty minutes now produces something that's still useful in five years.