The walkthrough is a 40-minute, facilitator-led FDW workshop. Faculty bring one of their assessments; the workshop traces it through Daley's four-form cycle, ICCB Program Review, and HLC accreditation. The session is split into four artifacts — a dashboard the committee runs from, primer slides projected at the opening, the faculty activity faculty work on their laptops, and discussion slides projected at the close. This page shows the three concerns that matter for planning — what faculty see, what we do at each phase, and what happens to the work they put in.
Phase →
PHASE 3
Discussion
~8 min
Look up at the projector. Five orientation slides the facilitator clicks through: What Hi-C is, what it isn't, the four-form cycle, the alignment repository, the reporting overview. Laptops stay closed.
Walk one of their own assessments through five steps: department/course, CSLO + instrument, benchmark, outcome, intervention. Final screen shows the chain.
Six prompts to reflect on what surfaced. Pair-share if the room allows. Cross-disciplinary listening is the close-the-loop mechanism.
Print PDF for their records. Optional — bring it to their next coordinator conversation.
Set the frame. Hi-C is Daley's framework, anchored to one body of assessment work. Workshop is starting material, not a finished product.
Hold the room. Faculty work on their own laptops. Float for stuck faculty; surface what's working aloud. Don't grade outputs — invite faculty to read their own.
Invite reflection. Use the six prompts. Notice across-disciplines patterns. The discussion is the close-the-loop, not a separate task.
Hand the next step back. No assignments, no follow-up obligations. Faculty carry away what they want to use.
Nothing yet. Static slides; no inputs to capture.
Faculty input lives only in the browser. Refresh the page and it's gone. Nothing leaves the device unless faculty explicitly choose to send it.
Still browser-only. Reflection happens in the room — discussion isn't recorded, transcribed, or saved anywhere.
Faculty print PDF locally — file lives on their device. Optional consent gate appears here. (See callout below.)
Design Decision · Endorsed with conditions
The optional HLC evidence consent gate
At the very end of the activity, faculty see a checkbox: "Yes — save my walkthrough as institutional assessment evidence." If they tick it, a small subset of the chain (department, course, CSLO, instrument, benchmark, outcome category, intervention status, forms drafted) is captured for the assessment committee's records. Default is unchecked. Name field is optional. Nothing is captured without an explicit click.
The committee endorsed this gate at the planning meeting with conditions — specifically, that submissions live in CCC institutional infrastructure (a Microsoft Form owned by a Daley Assessment Committee Microsoft 365 Group), not in any individual's account. That direction is being implemented; for now, the consent gate is wired to a development backend until the institutional Form is provisioned by IT. See the architecture section below.
Under the hood
Three-tier architecture
Frontend
Static site on Netlify
Four artifacts: dashboard, primer slides, faculty activity, discussion slides — plus reference materials (facilitator guide, digital booklet, this overview). Faculty's browser does all the rendering. Loads fast on any device.
Free hosting; no login; no tracking.
Backend
Microsoft Form (transitioning)
Receives the optional consent-gated payload. The institutional target is a Microsoft Form owned by a Daley Assessment Committee Microsoft 365 Group; faculty are redirected there with their walkthrough pre-populated. They review and click submit on Microsoft's UI — a real consent moment signed by their CCC identity. A development backend (Google Apps Script) is wired up while IT provisions the Group.
No additional cost; uses existing CCC Microsoft 365 tenant.
Storage
SharePoint List (institutional)
Form submissions land in a SharePoint list inside the Microsoft 365 Group's shared workspace. The Group survives any individual leaving — addresses the chair-turnover vulnerability the committee flagged at the planning meeting. Excel export, Power BI-compatible, sortable by any column.
No third-party tools; lives entirely in CCC's institutional infrastructure.