Back to library
FoundationProduction reviewed

Before you configure TASC

Make the ownership, privacy, structure and rollout decisions that every later setup step depends on.

8 minutes7 stepsStart hereProduction V1 ยท reviewed 6 Sep 2026

Outcome

A one-page launch brief with named owners, a bounded first workflow, approved information rules and a clear go/no-go test.

Find it in TASC

TASC AcademyLaunch planner

Before you begin

  • An operational sponsor and primary administrator
  • A representative from the first pilot site
  • Your privacy, retention and worker-communication requirements

Interface landmarks

Production V1 path and labels.

TASC Academy
Launch planner
1Operating ownerAccountable for the workflow outcome.
2Information rulesVisibility, identity and retention decisions.
3Acceptance testEvidence required before expanding.

Decisions that matter

Ownership

Name a primary administrator, a backup and the operational owner who can accept the pilot result.

Information model

State whether the pilot is anonymous, confidential or identified before configuring visibility.

Pilot boundary

Use one site and one connected workflow. Expansion is a decision after evidence, not a starting condition.

0 of 7 steps complete0%
x

Progress is saved on this device only.

  1. Step 1

    Name the owners

    Assign a primary organization administrator, a backup administrator and an operational owner for the first workflow.

  2. Step 2

    Choose the information model

    Decide which workflows are anonymous, confidential or identified, and who may see individual worker information.

    Treat individual-status visibility as a governance decision, not a convenience setting.

  3. Step 3

    Map your operating structure

    List the first site, departments, crews and shifts before creating scoped users, invitations or QR codes.

  4. Step 4

    Choose one pilot outcome

    Select a small first workflow with a clear owner and measurable success condition.

  5. Step 5

    Plan worker participation

    Prepare notices, training and consultation for workers, contractors and representatives who will interact with TASC.

  6. Step 6

    Set QR governance

    Give each QR code an owner, workflow, location, review date and retirement process.

  7. Step 7

    Confirm retention and evidence needs

    Document the approved retention period, audit expectations and any legal or contractual constraints before changing settings.

Prove it worked

  • Every setup decision has an owner
  • The pilot audience and site are named
  • Retention and individual-status visibility are approved
  • A stop condition and support route are documented

Common problems and safe recovery

The rollout starts with every module.

Choose the one workflow that proves the most useful operating connection and defer the rest.

Nobody owns a failed pilot test.

Assign an operational owner before any invitation or QR code is distributed.

What happens next

Use the completed brief while creating the organization and first site. Do not invite people until the structure and information rules are confirmed.