Concept — Locked Resources (the return-to-platform pull)
The participant-facing half of content visibility states. Post-workshop resources are shown visible but locked before the engagement, then released by the IS after delivery. The mechanism does double duty: correct content timing and a deliberate hook that pulls participants back to the platform.
The experience
| Moment | State | What the participant sees |
|---|---|---|
| Pre-engagement | Locked / greyed [D1] | Resource tiles visible but disabled, labeled “releases after the workshop” |
| Post-delivery | Released [D2] | IS flips the state; resources become accessible; release is logged |
Why “visible but locked” beats “hidden”
Hiding resources gives the participant no reason to anticipate them. Showing them locked creates a small open loop — “there’s more coming” — that:
- gives the Adjust phase a concrete reason to return;
- supports the intervention layer’s repeat-application nudges (the nudge can point at newly-unlocked resources);
- ties the certificate/extension rewards to platform re-entry.
Connected gating in the participant flow
The same “earn-by-behavior” pattern repeats:
- On-time application (≤48h) → extension resources unlocked.
- Survey complete → certificate unlocked + visible (certificate is gated behind the survey).
- IS releases locked resources [D2] in Adjust → repeat-application support material available.
Related
- Content visibility states — the PM-owned state machine behind this
- Intervention layer — nudges that point at unlocked resources
- Source: user stories D1 (Part), D2 (IS); §5a, §6.3 of recommendations doc