What This Report Is For

By the end of this lesson you will know who this report is for and what it has to achieve.

Two readers

• Your university. They are assessing whether your training met their requirements. They did not see any of it, so the report is the only evidence they have.
• The company. It is the record of what you did here, and it is read by people who will be asked, later, whether you were any good.

And a third, eventually

You.

In two years, when someone asks what you actually did in your co-op training, this document is what you will have. Not your memory — this. Write it for the version of you who has forgotten the details but needs to speak about them confidently in an interview.

Check your university's requirements first

Before you read anything else here. Most universities mandate a format for the training report — required sections, a word count, a cover page, a supervisor signature block, sometimes a specific template.

Their requirements override everything in this course. Get them, read them, and build to them. What follows is how to make the report good; it is not a substitute for what your university demands.

If their format conflicts with something here, follow theirs and tell your mentor.

What makes this report different from the others you have written

You have written three reports in this programme already. This one differs in one way that matters: it is evidence, not explanation.

The ISO report showed you could research. The PM report showed you could understand a field. This one has to show that you did the work — and the burden of proof is on you.

That is why screenshots matter more than prose here, and why a report full of confident description with nothing to show is the weakest thing you can submit.

What it is not

• Not a diary. Nobody wants a day-by-day account of what you did each morning.
• Not a summary of Odoo or ISO 9001. The reader does not need teaching; they need to know what you did.
• Not a list of tasks. Tasks without outcomes prove nothing.