# App demo shot list and verification worksheet

Plan one useful action. This worksheet contains proposed shots and expected arithmetic, not recorded footage, a transcript or completed test results.

## Define the demonstration

- App / public demo URL:
- Date and version, if known:
- Intended viewer:
- Question the video answers:
- Fictional data / authorized test context:
- What this video will not prove:
- Capture region:
- Microphone / narration choice:
- Intended viewing size:

## Worked plan: Scenario Lab

Example URL: https://chirogrowth-command.overskill.app/demo/scenarios

Hold these relevant inputs constant: 80 additional monthly visits, $75 collected per visit, $8 variable cost per visit and a $0 visit-price change. Independently expected contribution before added fixed cost is 80 × (75 − 8) = $5,360.

| Planned moment | Input / expected result | Actual result and evidence | Status |
| --- | --- | --- | --- |
| Starting state | $1,500 added monthly fixed cost; expected additional profit $3,860 | | Not tested |
| Changed state | $10,000 added monthly fixed cost; expected additional profit −$4,640 | | Not tested |
| Restored state | Restore $1,500; expected additional profit returns to $3,860 | | Not tested |

These are fictional calculations. Record actual starting values before use. Keep additional profit separate from proposed total profit. This exercise is a client-side comparison, not a saved-record, reload, medical or real business-results test.

## Plan the explanation

| Moment | Viewer must see | Planned explanation | Actual spoken words / text equivalent | Final timecode |
| --- | --- | --- | --- | --- |
| Start | Relevant assumptions and displayed result | Explain the question and fictional inputs | | |
| Change | Exact field change and resulting value | Explain what changed and compare with expected arithmetic | | |
| Restore | Original input restored and result checked | Explain that the original assumption and calculated additional profit are back | | |

Leave final timecodes empty until the actual edit is played back. Do not publish planned text as an observed transcript.

## Before capture

- [ ] Confirm permission to record this app and visible data.
- [ ] Hide unrelated windows, account details and notifications.
- [ ] Verify the selected recording region and microphone setting.
- [ ] Check that input labels and results will be readable at the intended size.
- [ ] Make and play back a short test.

## After capture

- [ ] Open the actual saved file and watch beginning to end.
- [ ] Confirm the expected region and complete action were captured.
- [ ] Compare observed values with the independent arithmetic.
- [ ] Verify the changed input was restored; record failures explicitly.
- [ ] Explain meaningful cuts, setup or removed waits.
- [ ] Write captions/transcript from the actual footage, then check timecodes.
- [ ] Check captions do not cover important fields or results.
- [ ] Test the final embedded player and text equivalent on desktop and phone.
- [ ] State untested permissions, storage, integration or rollout behavior.

## Keep the evidence

- Original recording path:
- Final media path:
- Final duration (measured during playback):
- Captions / transcript path:
- Public page and player check, if published:
- Failures or remaining limits:
- Reviewer and actual review date, if reviewed:

Read the guide: https://www.overskill.com/learn/record-an-app-demo
Existing worked case: https://www.overskill.com/learn/chiropractic-apps-with-mcp
MCP workflow: https://www.overskill.com/learn/build-an-app-with-mcp