# Build Your Own Scorecard

The prompts from the guide, ready to paste. Fill in anything in [square brackets] first.

From Kristen Parise BSc MSc BHScPT · kristen@blueberrytherapy.ca

## Prompt 1 · Install the kit, ten minutes

```
You are helping me set up the Clinic Scorecard kit I just downloaded and unzipped into this folder. Read CLAUDE.md first, then follow it.

STEP 1. Check where we are. If this folder's path contains "OneDrive", "Google Drive", "GoogleDrive", "My Drive", "Dropbox" or "iCloud", stop and tell me: raw client files must not sync to any cloud, and help me move the folder to a plain local spot first.

STEP 2. Ask me these questions, one at a time, and update the config section of scorecard_data.json with my answers (keep everything else in the file exactly as it is):
1. My business's name.
2. Whose hours should this track as the owner (my name, as it appears in my client software).
3. Anything that shows up in my exports that is not an individual client: classes, group programs, meetings, admin blocks.
4. Anyone who appears under more than one spelling.
5. Do I sell online, and where, or "none."
6. My currency and my timezone.

Then the "what matters to you" questions, same rhythm: what I am trying to make happen in my business over the next year (northStar), which three things matter most right now from more new clients, clients rebooking, filling providers' schedules, growing revenue, growing product sales, fewer no-shows, or protecting my own time (focusAreas), whether I want more, fewer, or steady hours seeing clients myself (ownerHoursDirection), and whether it is just me or a team (soloPractice).

STEP 3. Check Python is installed: on Windows run "py --version" (fall back to "python --version"), on Mac run "python3 --version". If missing, walk me through installing it from python.org/downloads. On a Mac, also run chmod +x on "Redact This Week.command" so double-click works.

STEP 4. Run the self-test, fake data only: create two invented sample rows in 1_Raw as a CSV (an obviously fake name, email and phone number, nothing real), run the redaction script, and confirm it prints CLEAN and that the fake identifying details do not appear anywhere in 2_Redacted. Then delete the fake files from 1_Raw and their outputs from 2_Redacted and keys.

STEP 5. Report back: the full path of this folder, what you filled in, anything you could not answer, and the line "Your scorecard is installed. Next: your first real week whenever you have this week's exports ready." Then stop.

Rules: never invent a value, write [to be filled] if I skip a question. Ask me question 1 now.
```

## Prompt 2 · Confirm what your export means, first real week only

```
Look at every file in 2_Redacted. For each one, tell me what you believe it is (a visit or appointment list, a revenue report, a schedule report, a client retention summary, a list of clients with no future booking, or something else), which column you will use for each metric it can supply, and anything you are not sure about. Do not calculate anything yet. Wait for me to say yes, then save the confirmed mapping into scorecard_data.json under config.columnMap so you do not have to ask me again next week unless a new file shape shows up.
```

## Prompt 3 · Run the weekly scorecard

```
Run this week's scorecard from the files now in 2_Redacted, following the column mapping you already confirmed. Update scorecard_data.json, scorecard_data.js and the weekly report in 3_Output, then give me the one-line headline.
```

## Prompt 4 · Build your own recovery-call habit

```
From this week's cancelled-not-rebooked list in the scorecard (client codes, last-visit dates and providers, no names), write me a short phone script for calling these clients once I have looked each one up in my own client software, anchored to their last visit rather than asking an open-ended "when would you like to book." Then build me a small private page (one HTML file, no client names, just a tally) where whoever makes these calls can log how many they called, how many rebooked, and the reason given when someone says no. Do not include any client-identifying detail on the page itself.
```