# Client-app handoff and offer worksheet

An editable worksheet from Overskill. Use one copy per app and version.
These are proposed checks for your own app, not completed chiropractic-demo
tests. Every unfilled result starts at **Not tested**.

## Identify the work

- App and intended user:
- One job this version should complete:
- Responsible builder and reviewer:
- Build identifier / version:
- Preview URL:
- Production URL, if published:
- Test date and browser / device:
- Scope: public fictional-data demo / private pilot / other:
- Where records are stored and what survives a reload:
- Features intentionally excluded:

Keep passwords, tokens, private access links and real client records out of
shared evidence. Use fictional contacts and authorized test accounts.

## Record observed behavior

Replace Not tested only after executing the check. Use Pass, Fail, or
Not applicable with a reason. Name the preview or production environment
and link a useful receipt: a screenshot, downloaded file or concise test log.
Repeat important checks after a repair and on the published version.

| Check | Expected result to agree | Observed | Status | Evidence / environment |
| --- | --- | --- | --- | --- |
| Main calculation | For the Workshop example: $500 fee minus $300 cost gives $200 contribution; 10 inquiries give $30 cost per inquiry; 4 consultations give 40% conversion. Replace with your own independent expected values if adapting. | Not tested | Not tested | |
| Change, save and return | Workshop cost $400 gives $100 contribution and $40 per inquiry after reload; conversion stays 40%. The relevant summaries agree. | Not tested | Not tested | |
| Invalid or missing input | Workshop rejects 26 inquiries for 25 attendees; zero-denominator ratios show n/a. Invalid input does not replace a valid saved record. | Not tested | Not tested | |
| Navigation and mobile | Direct page entry and reload work for intended visitors. Main controls, errors and save actions are usable on the agreed phone size and with a keyboard. | Not tested | Not tested | |
| Actual download | The file arrives, opens and contains the expected records and format. Record TXT, CSV or PDF accurately. | Not tested | Not tested | |
| Private access, if included | Test account A can access its record. Independent account B and signed-out visitors cannot read or change it through lists, direct links or attempted edits. | Not tested | Not tested | |
| Recovery | In an authorized test copy, exercise the agreed failed-save and record-recovery procedures. Verify code recovery and saved-data recovery separately where offered. | Not tested | Not tested | |
| Published result | The production URL serves the intended version; repeat main navigation and calculation checks there. A queued publish response alone is insufficient. | Not tested | Not tested | |

External messages, payment and other connections are disabled in the supplied
Workshop brief. If added, define separate checks and recipients before enabling
them. Use provider-supported test mode where available. If there is no safe test
environment, leave the result Not tested; do not use a real charge as a test.

- Added connection / purpose:
- Authorized test setup and expected result:
- Actual outcome: Not tested
- Failed or unverified check that blocks the intended use:
- Next repair, owner and retest date:

## Proposed services — separate from demonstrated features

No row is included, delivered or purchased until agreed. A proposed fee is
not evidence of a sale or return on investment.

| Proposed service | Exact scope and exclusions | Who supplies inputs? | Acceptance evidence | Fee / timing to agree |
| --- | --- | --- | --- | --- |
| Configuration | Branding, roles, fields and one named workflow | | | |
| Data setup | Allowed records, source, volume and import checks | | | |
| Tailored scenarios or templates | Quantity, examples and reviewer | | | |
| Training and handoff | Sessions, operator instructions and access transfer | | | |
| Rollout review | Pilot participants, review date and corrections included | | | |
| Optional support | Response expectations, included changes and exclusions | | | |

- Proposed implementation fee and currency:
- Payment milestones and acceptance terms to agree:
- Recurring platform / hosting / provider costs and payer:
- Ongoing maintenance owner:
- Separate connections, sending, outreach labor or advertising excluded:
- Client responsibilities and dates:

## Handoff decision

- Demonstrated features and evidence:
- Unverified features and restrictions:
- Agreed next stage: demo review / limited pilot / client rollout:
- Reviewer decision: Not reviewed
- Decision date:
- Operating instructions and support contact:
- Data and code recovery instructions, verified separately:
- Open work, owner and due date:

Guide: https://www.overskill.com/learn/build-an-app-with-mcp
Worked example: https://www.overskill.com/learn/chiropractic-apps-with-mcp
Launch checks: https://www.overskill.com/learn/ai-app-launch-checklist