The Week-One Project: Turning an Evening Course Into Something You Can Actually Show

You sign up for a ten-week evening course at the local college, you turn up, you do the exercises, you get the certificate, and then... it goes in a drawer. Six months later you're filling in an application form and there's nothing to put in the box marked 'relevant experience'. Sound familiar?

The awkward truth is that a short course, especially an unaccredited one, doesn't travel very far on its own. What travels is a piece of work with your name on it. So the plan here is simple: don't wait for the certificate to land before you start making evidence. Start in week one, aim the whole course at one small real project, and finish with a single page that says what you did and what changed.

Here's the four-step version.

Step one: choose your project in the first session

Not after the course. In week one, while you're still keen and haven't yet discovered that Tuesday evenings are also the only time you can see your friends.

The project needs to be three things:

• Small enough to finish. One page, one client, one repaired thing, one small dataset. If it could take longer than the course itself, it's too big.
• Real. Not a pretend scenario from the workbook. Something with an actual person, business or situation attached.
• Yours. You need to be the one who did the doing, otherwise it's not really evidence of anything.

Good candidates: redesigning the menu board for a mate's café, building a simple spreadsheet for your aunt's craft business, rewriting the product descriptions for a charity shop's online listings, setting up a basic booking system for a community hall, planting and recording a small raised bed on an allotment. Bookkeeping course? Tidy up three months of your own household finances and log it. Web design? A one-page site for a local Scout group.

If you genuinely can't find a real person to help, use your own life. The project just has to be real to you.

Step two: capture the 'before' properly

This is the step people skip, and it's the one that makes the whole thing credible. Before you learn anything, record the starting state.

Take photographs on your phone. Screenshot the messy spreadsheet. Save the original document. Write a short paragraph describing the problem in plain English — what was annoying, slow, unclear or broken, and what it was costing in time or money.

Keep that 'before' file somewhere you won't lose it. A folder on your phone called 'Course Project' will do. The reason this matters is that a case study is a story about change, and you can't show change if you never captured the starting point. Trying to reconstruct the 'before' in week nine from memory is a waste of an evening.

Step three: ask the tutor for one written paragraph

Most tutors are delighted to be asked and slightly surprised, because almost nobody does.

Wait until you've done something worth commenting on — week four or five is about right — then ask for something specific rather than a vague reference. Not 'would you write me a reference?' but 'could you put two or three sentences in an email about how I handled the [project] and what you noticed about my progress?'

Two things make this land well. First, give them the material: send a short summary of what you did and a couple of photos. Second, be clear you're not asking for a formal reference on headed paper. A plain email reply is fine, and far more likely to arrive.

That paragraph does a lot of heavy lifting. It's independent, it's written by someone with standing, and it says something the certificate can't: how you actually worked.

Step four: publish one page while it's still fresh

Aim to write it within two weeks of the last session. Not because there's a deadline, but because your recall of the detail — the hiccup in week six, the reason you changed approach — fades fast, and that detail is what makes it read as real.

One page. Plain language. No jargon borrowed from the course materials.

The one-page template

Steal this structure wholesale:

• Title: what you made or fixed, in plain words.
• Who it was for: one line. A person, a business, a group.
• The situation before: two or three sentences plus a 'before' image.
• What I did: four or five bullets, in the order you actually did them.
• What the course gave me: one short paragraph naming the specific techniques. This is the bit that connects the work to the training.
• The result: what changed, in numbers where you can manage it. Time saved, errors removed, enquiries received, a thing that now works.
• What I'd do differently: one honest sentence. This is the most persuasive line on the page, because it proves you can evaluate your own work.
• Quote: that paragraph from your tutor, attributed simply.

Put it on a single page of a personal website, as a PDF, or as a post on LinkedIn. A PDF is the most portable — you can attach it to an application form or email it to a prospective client without asking anyone to click a link.

But what if the course isn't accredited?

This is the worry that stops people. Here's the useful reframe: an unaccredited course can't give you a qualification, but it can't stop you producing evidence either. Nobody needs to accredit a page that shows a before photo, a description of what you did, a result and a tutor's comment.

Two practical points. First, be honest about what the course was — 'a ten-week evening class at [college], unaccredited' is perfectly respectable and infinitely better than implying something grander. Second, lean harder on the work itself. Where a formal qualification does the talking, your case study has to. That's the trade, and it's a fair one.

Where it goes afterwards

• The 'relevant experience' box on application forms.
• The projects section of your CV, in two lines with a link.
• Any interview where someone says 'tell me about a time when...'.
• Your first paying clients, if you're heading that way — it's the difference between 'I've trained in this' and 'here's a thing I did'.

Start the project in week one. Everything else follows from that one decision.