Uw Self Assessment 1 Step 2: Exact Answer & Steps

Ever tried to fill out the UW Self‑Assessment and felt like you’d need a PhD just to finish Step 2?
You’re not alone. Most students stare at that blank screen, wonder why the instructions sound like a legal contract, and then spend an hour Googling “what does ‘reflect on learning outcomes’ even mean?

The short version is: Step 2 is where you actually show what you learned, not just list a bunch of buzzwords. On top of that, get it right and you’ll access the credit you need without a nightmare meeting with an adviser. Miss the mark and you’ll be stuck in a loop of revisions.

Below is the only guide you’ll need to breeze through UW Self‑Assessment 1 Step 2—what it is, why it matters, the exact process, common slip‑ups, and tips that actually work.

What Is UW Self Assessment 1 Step 2

At the University of Washington, the Self‑Assessment is a two‑part online form that every undergraduate must complete for certain courses—especially those with a capstone or experiential component.

Step 1 is the easy part: you confirm enrollment, select the course, and upload any required syllabi.

Step 2 is the deep dive. It asks you to reflect on specific learning outcomes, provide evidence, and tie those outcomes back to the course objectives. In plain English, you’re proving to a digital grader (and sometimes a human reviewer) that you actually mastered the material, not just showed up for lecture Worth keeping that in mind..

Think of it as a mini‑portfolio inside the university’s registration system. You’ll be asked to:

1. Identify the learning outcomes tied to the course.
2. Describe how you met each outcome.
3. Attach or link to concrete artifacts—papers, projects, lab reports, code repos, etc.

The system then runs a quick algorithm that flags any missing pieces before you can submit. If everything checks out, you get a “complete” status and the credit is awarded automatically No workaround needed..

Why It Matters / Why People Care

Real talk: the Self‑Assessment is more than a bureaucratic hoop. It’s the gatekeeper for a lot of things you probably care about:

• Graduation timelines – Miss a step and you could be stuck a semester waiting for a course to count.
• Transfer credits – If you’re eyeing a graduate program or a different campus, a clean assessment shows you can self‑evaluate—something admissions love.
• Financial aid – Some aid packages require proof of satisfactory academic progress, and an incomplete assessment can trigger a hold.

When students skip Step 2 or treat it as a “fill‑in‑the‑blank” exercise, they often end up with a “needs revision” notice. That means an extra email chain, a meeting with the instructor, and a whole lot of wasted time.

On the flip side, nailing Step 2 the first time gives you a tidy record, a sense of accomplishment, and—let’s be honest—extra mental bandwidth for the next semester’s chaos.

How It Works (or How to Do It)

Below is the step‑by‑step workflow that works for every UW student I’ve coached. Follow it in order; don’t try to jump ahead.

1. Gather Your Course Materials

Before you even log in, pull together everything the professor said counts as evidence:

• Syllabi (the version that lists learning outcomes).
• Assignment rubrics—they often echo the outcomes.
• Your own work: essays, lab notebooks, code commits, presentations, peer‑review feedback.

If you can’t locate a file, check the course’s Canvas/Canvas‑like site, the departmental dropbox, or ask a classmate. Having everything in one folder saves you from frantic tab‑switching later Most people skip this — try not to. Which is the point..

2. Open the UW Self‑Assessment Portal

handle to my.uw.Practically speaking, edu → Student Services → Self‑Assessment. Select Self‑Assessment 1 and then Step 2 – Learning Outcomes.

You’ll see a table with columns for:

• Outcome ID (e.g., “LO‑1: Critical Analysis”).
• Your Reflection (a free‑text box).
• Evidence (upload button or URL field).

3. Identify the Exact Outcomes

Most courses list 3–5 outcomes. Don’t guess; copy them verbatim from the syllabus.

Why? The system matches your wording to the rubric. A tiny typo can cause the algorithm to think you missed an outcome, triggering a “missing outcome” error Worth knowing..

Tip: Highlight the outcomes in the syllabus, then paste them directly into the portal. That eliminates transcription errors.

4. Write the Reflection

Here’s where many students stumble. The reflection isn’t a summary of the assignment; it’s a connection between the outcome and your work It's one of those things that adds up..

Structure to use (works every time):

1. State the outcome in your own words.
2. Describe the specific task you completed that addresses it.
3. Explain the skill or knowledge you applied.
4. Quantify the result if possible (grade, score, user feedback, etc.).

Example for LO‑2 “Apply statistical reasoning”:

Outcome: I demonstrated statistical reasoning by interpreting experimental data.
Now, > Application: I chose the test after confirming normality with a Shapiro‑Wilk test, then calculated effect size (Cohen’s d = 0. In real terms, 68). > Task: For the mid‑term project I performed a two‑sample t‑test on the collected survey results.
Result: My analysis earned a 92 % on the project rubric, meeting the “advanced interpretation” criterion.

Notice the short, punchy sentences mixed with a longer explanatory one. That rhythm makes the reflection easy to scan—exactly what the algorithm (and the human reviewer) likes Small thing, real impact..

5. Attach Evidence

You have two options:

• Upload a PDF, image, or ZIP file directly.
• Link to a publicly accessible URL (GitHub repo, Google Drive with view‑only permission).

Make sure the file name is descriptive: CS101_FinalProject_StatAnalysis.If you’re linking, test the link in an incognito window to confirm it’s not behind a login wall. pdf.
The portal will flag a broken link and refuse submission.

6. Double‑Check the “Completeness” Meter

At the bottom of the page there’s a progress bar. It turns green only when:

• Every outcome has a reflection.
• Every reflection has an attached piece of evidence.
• No required fields are left blank.

If the bar stays amber, hover over the red icons; they’ll tell you exactly what’s missing Simple, but easy to overlook..

7. Submit and Save Confirmation

Hit Submit. The system instantly generates a PDF receipt with a timestamp and a unique confirmation number. Download it—store it in your “UW Docs” folder. It’s your proof that you completed the step, handy if the registrar asks for proof later And it works..

Common Mistakes / What Most People Get Wrong

1. Copy‑pasting the outcome verbatim without personal context
   – The portal sees the text but the reflection box stays empty, so it flags “no reflection.”

2. Uploading the wrong file
   – Accidentally attaching the syllabus instead of your project. The reviewer will see a mismatch and send it back.

3. Using private links
   – A Google Drive link that requires “request access” will bounce back as broken It's one of those things that adds up. And it works..

4. Leaving out quantitative details
   – Saying “I did a regression analysis” is vague. Add R‑squared, p‑value, or the rubric score you earned.

5. Skipping the final “completeness” check
   – The bar can be deceptive; sometimes a hidden field (like a “signature”) stays unchecked.

6. Waiting until the deadline
   – The portal can be slow during peak times, and a last‑minute glitch could cost you a day or two.

Avoiding these pitfalls alone can shave hours off your workload.

Practical Tips / What Actually Works

• Start early: Give yourself at least 48 hours before the deadline to gather evidence and draft reflections.
• Use a template: Create a simple Word doc with the four‑sentence structure above; copy‑paste for each outcome.
• put to work rubrics: Align each sentence with the rubric language; the algorithm loves exact phrase matches.
• Name files consistently: CourseCode_OutcomeID_EvidenceType.ext makes it easy to verify you’ve attached the right thing.
• Take screenshots of the “green” progress bar before you submit. If the system glitches, you have proof of completion.
• Ask a peer for a quick review: One fresh set of eyes can spot a missing link or a typo that the system flags as “missing outcome.”

FAQ

Q: Can I edit Step 2 after I submit?
A: Yes, but only within 24 hours of submission. After that window closes, you must request a “re‑assessment” from the instructor, which adds a few business days That's the part that actually makes a difference..

Q: What if I don’t have a concrete artifact for an outcome?
A: Use a draft version, a peer‑review comment, or a screenshot of the code execution. The key is to show evidence of the process, not necessarily a polished final product.

Q: Do I need to include a signature?
A: The portal automatically adds a digital signature based on your UW NetID when you click Submit. No extra step required Took long enough..

Q: My evidence file is over the 10 MB limit—what now?
A: Compress PDFs with a tool like Smallpdf, or host the file on a cloud service and link to it instead of uploading.

Q: Will my instructor ever see my reflections?
A: Only if the course requires a manual review. Most large lecture courses run the automated check, but capstone or lab courses often have a faculty member glance at each submission But it adds up..

That’s it. You’ve got the whole process laid out, the pitfalls to dodge, and a handful of tricks that actually save time.

Next time you open the UW Self‑Assessment portal, you’ll know exactly where to click, what to type, and how to prove you earned those credits—without the usual last‑minute panic. Good luck, and enjoy the feeling of ticking that box cleanly.