A short reflection to close your Compass Cases experience: what worked, what you're now curious about, and the people you'd want to talk to next. It takes about five minutes.
This reflection is voluntary and anonymous. You don't need to enter your name, and taking part (or not) changes nothing about using Compass Cases.
We are not asking for any medical or health information. Please don't include a real patient's name or any private medical details in your answers — keep your questions about people, roles, and careers. Your responses are used only to understand what worked and to make Compass Cases better.
When you're done you can print or save your own copy, and you only share it if you choose to.
This page is designed so the evaluation is woven into the experience but safe by default. It collects no name and no health information, it works fully offline (print or save a local copy), and it only transmits anything if a learner opts in and you have configured a destination. The notes below explain the choices and how to run it cleanly.
HIPAA governs protected health information held by covered entities (providers, health plans) and their business associates. A career-exploration reflection completed by learners is not health care and does not create patient records, so HIPAA is not triggered. To keep it that way, the form never asks about a learner's own health, and it explicitly asks learners to keep real patients' names and private medical details out of their free-text — the same guardrail as the ethnography consent form. If you adapt this for the "Create your own" ethnography, keep that boundary: map roles and careers, not diagnoses or test results.
If Compass Cases runs inside a school, any learner response that can be tied to a student is an education record under FERPA. The default design avoids that by staying anonymous: no name, no student ID, no email. If you keep it anonymous and aggregate, you sidestep most FERPA obligations entirely. If you do collect identifiable responses, treat them as education records — store them in your approved school system, restrict access to those with a legitimate educational interest, and follow your district/institution's disclosure and retention policy.
GFORM block near the top of the script with your Google Form's /formResponse URL and its field IDs (step-by-step in SET-UP-DASHBOARD.md). Responses collect in a Google Sheet you can chart in Looker Studio. Until you set it, the "share" checkbox does nothing and no network request is made.The form asks only for what the evaluation needs: four ratings, three short reflections, the next-steps questions, and a few optional non-identifying context items. The optional anonymous check-in code lets you match a before/after pair without a name — it's a learner-generated string, not an identifier you assign. Define a retention window, then delete or fully de-identify afterward.
Used for program improvement, this is typically quality improvement and often IRB-exempt — but that determination rests with your IRB, not the team. If you intend to generalize or publish findings, consult your IRB early. This mirrors the guidance already in your Program Evaluation Plan.
As learners explore each case, the question they write for each person is saved by the case page in the browser's sessionStorage (key compass-notes:<case>), along with that person's name, role, tier, and case label. When a learner reaches this reflection page in the same browser tab, Part 4 reads that store and pre-fills their questions automatically, tagged by case — no retyping. This page only reads that data; it never writes to storage. Because the cases use sessionStorage, the questions live only for that tab session and clear when the tab closes (or when a learner uses "finish/clear"), which is deliberate for shared devices. Two implications: link to this page from within the same session (e.g., from the closing "find your direction" step) rather than sending it as a fresh link later, and if you want a durable record, have learners Save or Print before closing the tab.
Part 1 covers Kirkpatrick Level 1 (reaction), including the usability and engagement items. Parts 2–3 feed the qualitative "curiosity" and "what worked" strands. Part 4 is the "Next steps on your journey" artifact — the free-text questions you already flagged as the richest data; code them with your logistical / conceptual / systems-level rubric to gauge depth of interest.