All lessons
LaunchVideo + step screenshots

Run your first TASC pilot

Test one workflow across administration, supervision, worker participation and public QR entry.

20 minutes6 stepsAdvanced

Watch first

Captioned walkthrough using the real TASC screen

24 sec · no sign-in required

Do the task

Follow these steps in order

0 of 60%
x
  1. Define the pilot boundary

    Choose one site, one workflow, named owners, a start date and an explicit go/no-go condition.

    Run your first TASC pilot step 1: Define the pilot boundary.Step 1: Define the pilot boundary
  2. Prepare synthetic acceptance cases

    Test success, validation, denied access, expired invitation and inactive QR scenarios before real participation.

    Run your first TASC pilot step 2: Prepare synthetic acceptance cases.Step 2: Prepare synthetic acceptance cases
  3. Test every role

    Complete the journey as administrator, supervisor, connected worker and unconnected participant.

    Run your first TASC pilot step 3: Test every role.Step 3: Test every role
  4. Verify downstream behavior

    Confirm records, notifications, dashboards, actions and audit events appear only where expected.

    Run your first TASC pilot step 4: Verify downstream behavior.Step 4: Verify downstream behavior
  5. Review privacy and communications

    Confirm notices, worker questions, escalation routes and representative participation are ready.

    Run your first TASC pilot step 5: Review privacy and communications.Step 5: Review privacy and communications
  6. Decide and document

    Record issues, owners and fixes, then approve expansion or repeat the pilot.

    Run your first TASC pilot step 6: Decide and document.Step 6: Decide and document

Check that it worked

  • Every role completed its scripted test
  • Restricted information remained restricted
  • Failed conditions reached the right follow-up path
  • The operational owner approved expansion

If something goes wrong

The happy path passes but errors were not tested.

Add expired invitation, inactive QR, denied access, missing evidence and failed-condition cases.

Issues are known but have no owner.

Keep the pilot contained until each issue has an owner, priority and retest condition.

Before you begin and supporting details

Before you begin

  • A bounded site and workflow
  • Named admin, supervisor and worker testers
  • A public/unconnected participant test where QR is used
  • Synthetic records and explicit acceptance criteria

Find it in TASC

Academy launch planTASC pilot environmentGo/no-go review