# App-maintenance handoff card

Use this card for one recipient and one task in an existing app. Choose the working surface before sharing a link or asking an authorized administrator to change access. Then let the recipient attempt the agreed task and record what happens.

## Filled preparation example

**Fictional preparation, not a completed handoff.** Service Desk Practice, Harbor Workshop, Mina and all recipients/records below are invented. The content is a setup to adapt, not an Overskill template or an observed app. Every actual result is **Not tested**.

| Shared field | Prepared example |
|---|---|
| App / workspace | Service Desk Practice / Harbor Workshop — fictional |
| Responsible owner | Mina — fictional; actual owner and authority must be confirmed |
| Editor URL | `[confirmed editor URL]` — not supplied or tested |
| Live app URL | `[confirmed live app URL]` — not supplied or tested |
| Preview / presentation | `[checked preview URL or static review file]` — not supplied or tested |
| Account mode and access scope | Unknown; actual authorized administrator must inspect it |
| Test material | Sample heading, DEMO-17 and DEMO-18 below; confirm harmless test setup before any write |
| Current app version / test date | Not recorded; no rehearsal performed |

### H1 — Rae maintains the app

- **Task:** replace “Request a visit” with “Request a service visit” in the builder and show the change in preview. Do not publish.
- **Surface decision:** this task needs builder/editor access. A copied editor URL does not grant it. Before any authorized invitation, the administrator must confirm whether the available scope is the whole workspace or only the intended app, and whether that scope is acceptable. Do not assume app-specific sharing is enabled.
- **Prepared boundaries:** one reversible heading change in the agreed sample setup; no record edits, publication or unrelated app work. These are task instructions, not claimed technical restrictions.
- **Expected evidence:** Rae uses their own authorized account, opens the intended app, shows the exact preview heading and identifies which version is live. Record the preview version and whether any assistance was needed.
- **Observed result:** **Not tested**. No invitation, edit, permission or publication check occurred.
- **Next owner/action:** Mina and the authorized administrator confirm scope; then Rae attempts the agreed task. If the required narrow scope is unavailable, stop and choose another arrangement rather than grant broader access by default.

### H2 — Noor operates a sample request

- **Task:** change fictional request **DEMO-17** from **New** to **In review** through the app, then reload it.
- **Surface decision:** use the generated app's own sign-in and implemented operator permissions. Do not use a builder invitation merely to make a record update possible.
- **Prepared boundaries:** DEMO-17 must be a harmless sample record. The status choices and operator permission are requirements to verify in this app, not automatic Overskill features. No layout/code changes.
- **Expected evidence:** Noor finds DEMO-17, performs the permitted update, reloads and sees In review. Record the actual route, app version and result in the private working card.
- **Observed result:** **Not tested**. No operator screen, permission or saved change has been verified.
- **Next owner/action:** Mina confirms the operator workflow exists and the sample setup is safe; Noor performs the test. If behavior is missing, specify and build it, then test again. Use the existing [private-record access guide](https://www.overskill.com/learn/verify-private-record-access) for enforcement checks.

### H3 — Alex follows the customer journey

- **Task:** open Alex's fictional request **DEMO-18** and find the reply **“Please choose a morning or afternoon visit.”** Explain where a customer would look for a later reply.
- **Surface decision:** use the generated app's customer test account or permitted customer route. No Overskill workspace invitation is needed for the intended task.
- **Prepared boundaries:** DEMO-18 and its reply must be set up as sample content. This task reads the intended own record; it does not establish that other records are inaccessible.
- **Expected evidence:** Alex identifies DEMO-18, reads the exact reply and explains how to return to it without owner guidance. Record assistance separately rather than silently calling a coached attempt successful.
- **Observed result:** **Not tested**. Customer sign-in, ordinary signup and record isolation remain unverified.
- **Next owner/action:** Mina confirms the customer route and sample account; Alex rehearses. Follow the separate private-record test matrix before claiming isolation.

### H4 — Sam reviews the wording

- **Task:** read **“Request a service visit”** and write one sentence describing the kind of visit expected. Identify the exact revision reviewed.
- **Surface decision:** use a deliberately checked harmless preview/demo or a static presentation sufficient to show the wording. A preview link is not inherently read-only or isolated from live data.
- **Prepared boundaries:** no form submissions or record changes. These instructions do not enforce read-only access. If the review requires technically view-only access and that is unverified, stop or use a separately checked static presentation.
- **Expected evidence:** Sam identifies the revision and supplies the requested sentence. A screenshot or static file can be enough for this copy task; it cannot prove app operation.
- **Observed result:** **Not tested**. No preview exposure, recipient behavior or view-only restriction has been verified.
- **Next owner/action:** Mina checks what the proposed presentation exposes before sharing it; Sam reviews only the agreed material.

## Blank card — copy once per recipient/task

Do not put passwords, access tokens or private customer links in a publicly shared copy. Keep any necessary private evidence in the appropriate controlled location.

| Field | Your record |
|---|---|
| App / workspace / responsible owner | ______ |
| Recipient and their own account identity | ______ |
| One task, in the recipient's words | ______ |
| Exact sample record, text or revision | ______ |
| Necessary surface: editor / generated app / review presentation | ______ |
| Editor / live / preview addresses, separately labeled | ______ |
| Authorized administrator or app-permission owner | ______ |
| Observed account mode and scope; evidence/date | ______ / **Not tested** |
| Does available scope fit the task? Stop condition | ______ |
| Harmless sample setup and allowed actions | ______ |
| Expected result; what must survive reload, if applicable | ______ |
| Actual recipient result | **Not tested** |
| Assistance given during attempt | ______ |
| Evidence location, app version and observation time | ______ |
| Unresolved behavior/access question | ______ |
| Next action and responsible person | ______ |
| Rehearsal disposition: demonstrated / blocked / not tested | **Not tested** |

A demonstration supports only the task and scope observed. It does not establish account-wide permissions, data isolation, ownership transfer or every future maintenance job. Keep a blocked result and the next action; do not overwrite it with an expectation.

Start with your existing app. Use [invitation help](https://www.overskill.com/help/articles/inviting-team-members) for current controls and [team roles](https://www.overskill.com/help/articles/team-roles) for the role glossary. If required app-user behavior is missing, describe it in the existing app's chat. The [brief builder](https://www.overskill.com/learn#brief-builder) can also organize a separate build requirement: edit its input fields, review the generated brief, then choose **Start build** when a new build is appropriate. **Copy brief** is secondary. The link imports neither this card nor any sample records and does not update your existing app.