Participant self-assessment

Understand your tools.

Use this optional assessment when your event includes it. It shows what your tools may expose and what support would make your next choice safer.

Before you answer

Use your real situation, but do not enter passwords, payment details, confidential client records, legal or medical records, private information about another person, or anything your organization has not approved for this workshop.

Where this routes

The live workshop version should send raw responses to the governed Sweetgrass Workspace or shared Drive. This staging page generates guidance in your browser and does not save responses.

What gets reused

Aggregate patterns can feed the knowledge base and correlation engine after human review. Raw free text should not go to public AI.

1. Registration context

Start on Register so the workshop record has one shared participant context.

Open Register

This context comes from Register and stays in the governed workspace record. Return to Register to change it; this page is for the audit questions only.

2. What are you using?

3. How are you using it?

4. What information goes in or gets exposed?

5. Which concerns should the system acknowledge?

6. Which AI path are you using or considering?

7. Which cost pressure matters most?

Individual subscription costOrganization-wide subscription costHidden maintenance and supportEnterprise contract costLocal AI hardware/admin costDependency if vendor policy changes

8. Which settings have you already checked?

Browser cookies, ad settings, or cross-site trackingAccount history or chat historyTraining, reuse, or human-review termsData retention or deletion settings

9. What support would help next?

10. What do you assume stays private?

Participant action list

Turn answers into a pathway.

Immediate safety check

Nothing selected creates an immediate stop sign, but reread every upload or prompt before you submit it.

Account and browser settings

Review these first: Browser cookies, ad settings, or cross-site tracking, Account history or chat history, Training, reuse, or human-review terms. Ask for a walkthrough if you are not sure where they live.

What not to upload

Keep passwords, payment details, confidential records, legal or medical records, and private information about another person out of public AI.

What is safer to draft

Draft with generic examples first. Add names, stories, internal context, or strategy only inside approved tools.

Enterprise path

Personal use can stay simple, but know when a task crosses into work, organizing, or other people's data.

Local/private path

Local/private tools may not be necessary for every task, but they matter when the knowledge should stay under coalition control.

Cost and maintenance

Track subscription cost alongside the hidden cost of training people, reviewing output, and maintaining trusted workflows.

Follow-up question

Who in your organization owns the decision about which AI tools are approved for real work?

0 selections active. Submission waits for the approved Google Form, Sheet, Workspace, or site endpoint.

Browser + tracking settings

Start with the route your data already travels.

Browser cookies, tracking pixels, ad settings, location permissions, contact syncing, and cross-site sign-ins shape what platforms can infer before an AI tool ever sees a prompt.

This prototype

No tracking scripts, no cookies, and no saved audit responses are used in this staging version.

Popular platforms

Check whether the browser, app, account, or AI provider keeps history, uses data for training, syncs contacts, or shares activity across services.

Local knowledge rule

Use public tools when helpful, but keep coalition memory, source material, decisions, and sensitive context in the local knowledge store.

Intake capture path

From answer to action to evidence.

1. Intake

Participant answers describe tool use, data exposure, settings, cost pressure, and concerns.

2. Action list

The page returns immediate guidance without judging the participant for using common platforms.

3. Governed record

Approved live capture routes raw responses to the Sweetgrass Workspace or shared Drive.

4. Correlation

Reviewed patterns become facts, experiences, concerns, evidence needs, and recommended actions.

How it ties in

The audit feeds the repository and the six-month decision.

The workshop version should connect this intake to the governed repository. The correlation engine then rolls up patterns without publishing raw free text, helping Future Bound decide what to go forward with, stop, or adjust.