Complete worked example

A sample Career Clarity Portfolio.

This fictional example follows Avery, a Grade 11 student exploring front-end web development. It demonstrates the method; it is not a participant story, impact claim, or recommendation of a career.

How to use this example: Copy the structure, not Avery's conclusions. Requirements, programs, costs, and labour information must be checked against current responsible sources for your own question.
Stage 1

Career Criteria Card

Question: Would front-end web development fit how I like to work?

Why Avery is investigating it: Avery enjoys organizing visual information, improving small details, and making school materials easier for classmates to use. The career is an idea to test, not a decision already made.

Five ranked criteria: visible project output; a mix of independent focus and collaboration; opportunities to improve through feedback; skills that can be practised through small projects; and work that makes information easier to access.

Assumptions to test: most of the day is creative design; every employer expects the same education; and liking a finished website means enjoying the detailed work required to build one.

Research question: How much of entry-level front-end work involves coding, testing, accessibility, revision, and communication?

Stage 2

Career Evidence Brief

Use three sources for different questions.

Avery chooses a Government of Canada Job Bank occupation profile to identify common tasks and labour information; two current Ontario institution pages to understand education options and admissions; and a public professional talk to hear how one worker describes collaboration and revision.

Source notes: Job titles can cover different combinations of development and design. Official program pages show that education routes emphasize different mixes of programming, design, projects, and work-integrated learning. The professional account suggests that testing and explaining decisions are important parts of the work, but one person's workplace does not represent the whole field.

What the evidence supports: Avery should test coding and revision, not only visual design. Education is one part of a pathway; a small project can also reveal whether the recurring tasks fit Avery's criteria.

What remains unanswered: Which beginner skills appear repeatedly in current local postings? How do the two education routes differ in practical project time? Avery records the exact links and access dates in the workbook before relying on them.

Stage 3

Pathway Comparison

Compare a college diploma and a university degree.

Route A: Ontario college diploma

Verify: program length, Grade 12 course requirements, current tuition, project courses, placement options, transfer agreements, and application deadline.

Possible advantage: the sample curriculum may place practical production tasks early in the program.

Possible constraint: Avery needs to check how broadly the credential transfers if interests later change.

Route B: university degree

Verify: program length, Grade 12 course requirements, current tuition, specialization options, co-op rules, and application deadline.

Possible advantage: the sample curriculum may provide a broader computing foundation and room to explore related fields.

Possible constraint: Avery needs to check when hands-on front-end projects begin and how to build practical work alongside study.

Conclusion: Neither route wins on title alone. Avery will compare two named current programs using the same eight fields in worksheet 3 and bring the remaining questions to a guidance conversation.

Stage 4

Experience Test

Build and revise one accessible information page.

Question: Does Avery stay engaged while translating information into code, testing the result, finding errors, and revising after feedback?

Task: In four hours across one week, create a single static page explaining a school club. Include a clear heading structure, keyboard-usable links, readable contrast, and a layout that works on a phone. Ask an educator and a classmate to find the meeting time and contact route.

Evidence: Save the first and final versions, a time log, the two pieces of feedback, and a list of changes. Record which task—planning, coding, debugging, testing, or explaining—felt most and least engaging.

Boundaries: Use only public club information, a private practice file or approved school tool, no student personal information, and no public claim that the page represents the school.

Five questions for a professional: What do beginners underestimate? How often do you revise after feedback? Which accessibility task is routine? How do developers and designers divide decisions? What small project best reveals whether someone likes the work?

Stage 5

30-Day Exploration Plan

Make the next month specific.

Finding that increased interest: Avery enjoyed turning a confusing list into a page that two people could navigate quickly. Tradeoff: debugging a small display problem required more patience than expected. Changed assumption: the work was less about decorating and more about structure, testing, and revision.

  1. By day 7, compare two named Ontario programs using official admission, curriculum, cost, and experiential-learning pages.
  2. By day 14, revise the practice page after a keyboard and mobile check and record the changes.
  3. By day 24, ask a guidance counsellor which Grade 12 choices keep both routes available.
  4. On day 30, review the portfolio and decide whether to complete a second project, compare a related field, or change the career question.

Portfolio decision: continue exploring for 30 days; do not make an education commitment until current program details and the experience test are reviewed.

Your turn

Choose one career question and begin.

A useful portfolio does not need to confirm the first idea. It needs to show what you checked, what changed, and what action will produce better evidence.

Last reviewed August 13, 2026.