Building a public record of Canada’s military export industry

Replace this box. Three or four sentences: when you worked, where, what you did, and the one thing you want a reader to take away. The standfirst above already does some of this, so don’t repeat it word for word.

Replace this box. What Project Ploughshares is, who it serves, and why a peace research organization needs software. Verify every factual claim here against their own site rather than writing from memory.

The interesting angle: most co-op reports describe a software company. Yours describes research work where the software is the instrument. Say what kind of computing problem that turns out to be.

Replace this box. This section carries the most marks. Cover, in order:

What you wanted to learn going in, and why those things. Which goals you met. Which you did not meet, and honestly why. What you would carry into the next work term.

The unmet goals are not a weakness in the report. Naming one and explaining what got in the way is what separates reflection from a summary.

Replace this box. The technical core. What the pipeline does, how it is put together, and which decisions were interesting. Keep it readable for a non-specialist: the advisor reads dozens of these.

Say which skills came from coursework and which you picked up on the job. The guidelines ask for that split explicitly.

Stay inside what you and Kelsey agreed is publishable.

Replace this box. If someone read this page and then had to describe it in one sentence, what should they say? Write that sentence first, then write the paragraph around it.

Replace this box. Supervisor, academic supervisor, funding body, anyone who taught you something. Short and specific beats a long list.