Portfolio Example — Jane Smith

★ Example only — built from one specific case (Jane Smith · Waterfront Toronto) Yours will look different. Be creative.

01 — Who I Am

A short professional bio

Jane Smith is a third-year Political Science student at the University of Toronto, concentrating in urban governance and public policy. She came to Waterfront Toronto's Development team with a background in municipal planning research and a longstanding interest in how public agencies make decisions about land use in contested waterfront spaces.

Your turn — write this in third person, 2–4 sentences Teaser, not a template: a Waterfront intern might open with a sentence about why they care how cities decide who gets to live near the water. Yours will start somewhere else entirely — maybe it's a transit corridor, a refugee settlement process, or a budget hearing you watched fall apart. Write toward what genuinely moved you to take this placement.

02 — Where I Was

Placement context

Waterfront Toronto is a tri-government corporation — funded and accountable to the City of Toronto, the Province of Ontario, and the Government of Canada — responsible for the long-term revitalization of approximately 800 hectares of underutilised land along Toronto's lakefront. The Development division manages the planning approvals, design controls, and delivery partnerships that turn policy ambitions into built form.

As a Development Intern on a team of eight, I supported project managers and planners across several active precincts simultaneously. My work sat at the intersection of policy research, regulatory process, and stakeholder engagement — with a particular emphasis on translating complex approval frameworks for both internal decision-makers and external audiences.

My time was concentrated on two pre-construction blocks in the Quayside precinct, where coordination across municipal review, consultant teams, and development partners was most active. Replace with the specific precinct, neighbourhood, or files you focused on — just enough context for the contributions below.

03 — What I Did

Three contributions

Each card follows the same structure: what the task was, what you actually did, what resulted, and what you learned. Three is the minimum — you may include four if the fourth is substantively different.

Contribution 01

Building a consolidated action-item tracker across three consultant work-streams

Objective Three parallel consultants — urban design, infrastructure, and sustainability — were logging action items in separate formats. Items were being dropped between meetings. My manager asked me to design a single tracker and own it for the summer.

What I did I audited two months of meeting notes, built a shared Airtable base with standardised fields, and introduced a brief weekly sync to maintain it. I also drafted a one-page protocol so the system could survive after I left.

Result By mid-summer, zero items were reported as dropped in bi-weekly leadership check-ins. The tracker was adopted by a second team before my placement ended.

What I learned That a simple, reliable system people actually use beats a sophisticated one they don't. And that taking ownership of a low-status task — coordination hygiene — can create visible impact faster than a research deliverable.

Contribution 02

Comparator scan: how three jurisdictions handle inclusionary housing on phased developments

Objective Leadership needed a quick comparator scan before a regulator briefing — specifically, how peer jurisdictions handle affordability commitments when a development is delivered in phases over several years.

What I did Describe your research method, sources, and the form of the deliverable — a memo, a slide, a table. Be specific about what you produced, not just that you "did research."

Result What happened after you handed it over? Was it used in the briefing? Did it change the framing? Concrete outcomes matter here — even a small one.

What I learned One honest sentence. What's different about how you'd approach this kind of task next time?

Contribution 03

Open house Q&A prep: translating density targets for a contested park edge

Objective The team needed plain-language materials for a public open house where residents had strong views about building heights and shadowing near a park edge. My job was to anticipate the hardest resident questions and draft answers the project manager could use without legal review flagging them.

What I did How did you prepare? Did you review prior consultation records, draft Q&A scripts, attend the event itself? Tell us what the work actually looked like day-to-day.

Result How did the open house go? Did your materials get used? Was there a moment where the prep paid off — or didn't? Either is worth writing about.

What I learned Something about the gap between technical accuracy and public communication — or about whose questions never get answered at open houses. Your call.

04 — What I Can Do Now

Six skills I developed or deepened

Not a job description. Skill names should be specific and evidence-anchored — earned through doing, not declared. Four are filled below as illustration; write your own six.

Skill 01

Regulatory process mapping

I can now read a planning approval timeline and identify where decisions are actually made vs. where they are ratified — and explain the difference to someone who hasn't been in the room.

Skill 02

Plain-language policy translation

I drafted materials for audiences ranging from municipal planners to residents with no planning background. I got faster and sharper at finding the sentence that does the work without losing the nuance.

Skill 03 — your example might be different

Stakeholder documentation & records management

Waterfront interns often develop this — tracking commitments, consultant deliverables, or consultation records across a long approval timeline. Pick the version that fits your actual work.

Skill 04 — your example might be different

Reading spatial data in planning context

Even basic literacy in how parcel data, zoning overlays, or shadow studies inform decisions can be a differentiator. If this applied to your placement, name it precisely.

Skill 05 — your example might be different

Meeting facilitation & agenda management

Did you run any meetings, take structured notes, or manage follow-up? If so, that's a skill — name it as a competency, not a task you completed once.

Skill 06 — your example might be different

Research synthesis under time pressure

The comparator scan in Contribution 2 is an example — a fast turnaround deliverable with a real decision-maker waiting. If you did something similar, this is the skill it demonstrates.

05 — What I Noticed

One field insight

Not a summary of the organisation. Not "I learned a lot." One observation about how power, process, or legitimacy works in your placement context that you couldn't have gotten from a textbook.

"The people who controlled the timeline controlled the outcome — not because they had authority, but because everyone else was too busy to dispute their version of events."

Your insight will be different — here's the direction A Waterfront intern might notice the tension between the speed development partners need and the pace democratic consultation actually requires — and ask whether the process is designed to accommodate both or only appears to. That's the kind of observation this section is asking for: specific, earned, and slightly uncomfortable to say out loud. Yours will come from your own placement context.

06 — What Changed

A reflection on the experience

Written in first person. 200–350 words. This is the section where you say something true, not something impressive. Graders can tell the difference.

I went into this placement expecting to learn how a tri-government corporation navigates competing political priorities. I did learn that. But the more durable lesson was about something smaller: how much institutional knowledge lives in the habits of individual people, and how quickly it disappears when they leave.

Continue from here — or start over entirely Example opener you could borrow or discard: "The summer changed less about what I want to do and more about how I read a room." — or — "I came in thinking the obstacle was political will. I left thinking the obstacle was meeting hygiene." Neither is right for everyone. Find the sentence that's honest for you, then build the paragraph around it.

07 — Where This Goes Next

The resume line this earns you

Translating portfolio work into professional language

Your portfolio and your CV are telling the same story in different registers. The portfolio is the evidence; the resume is the claim. Here's how Contribution 01 above reads as a bullet:

Example resume bullet — Contribution 01 "Built and maintained a cross-consultant action-item tracker (Airtable) consolidating three parallel work-streams; reduced dropped commitments to zero over 10 weeks and secured adoption by a second project team before term end."

Your bullets will be different — but they should follow the same logic: what you built or did, the scale or scope, and the outcome. Avoid verbs like "assisted" or "supported" unless you have no choice. You almost always have a choice.

Your turn — write bullets for your three contributions For a Waterfront Development role, a bullet might reference a regulatory scan, a public consultation input, or a coordination process you improved. Write toward action and outcome — not process and presence.

This is one example, built from one specific case. Jane Smith's portfolio reflects the Waterfront Toronto Development internship — its precincts, timelines, approval processes, and stakeholder landscape. Yours will look nothing like this, and that's the point.

The structure is a scaffold, not a script. Change the section names if they don't fit your placement. Write in the voice you actually think in. Show the grader something they couldn't have invented — because only you were there.

Politics & the Public Sphere · Practicum 2026 · Course portfolio — unlisted, not for distribution