# Companion-video guide — A project handoff that can be followed and checked

Course: [Give every new project an owner, a kickoff stage and a visible finish](../appmint-automate-a-business-handoff.md).

The course contains real stills and saved execution evidence, not a finished video. Record the actual application and follow the Markdown. The 21 September local recheck supersedes older empty-picker, 404 and stale-counter footage.

## Story and pacing

Open on the outcome: saving a project puts a task in the owner's queue. Then reveal how the collection, responsibility rule and three-stage definition produce it. Follow the task until it is completed and archived. The second chapter introduces a different tool, Smart Automation, which creates the project rather than tracking the handoff.

Let viewers read each setting before proceeding. Use a close-up of Who decides, the two-day tier and the final model state/status. Keep an establishing shot before each close-up so viewers know which application and panel they are using. Explain each click's consequence; do not read the entire interface aloud.

Suggested edit targets: definition 6–8 minutes; task lifecycle 5–7 minutes; manual automation and result reconciliation 8–12 minutes; duplicate behavior and next steps 3–4 minutes. These are targets, not existing footage lengths.

## Prepare the recording

Use your own training organization and Owner account. Create Design Projects/cf_project using the dashboard course's schema, with workflow enabled. Use a unique definition name if the original already exists. The fixture uses Owner responsibility and fallback, a two-day middle-stage SLA, no notification templates, and an End stage with completed/done values.

Do not recreate the review fixtures for a retake. Every saved project starts a task; every explicit automation execution creates another project. The existing review automation is inactive and its two sample projects remain for comparison.

## Verified shot list

The paths below resolve from this production guide. Each still documents the behavior that a presenter should reproduce with their own records.

| Beat | Evidence | Narration and focus |
| --- | --- | --- |
| Hook | [Automatic task](../../application-fixes/assets/handoff-project-auto-task.png) | “Saving the project puts the kickoff in the owner's queue.” |
| Responsibility | [Stage controls](../../application-fixes/assets/handoff-stage-responsibility.png) | Show Owner, first-to-decide and fallback. Distinguish role resolution from a fixed person. |
| Deadline | [Two-day tier](../../application-fixes/assets/handoff-two-day-sla.png) | Entry into Kickoff scheduled starts the deadline. |
| Completion mapping | [End stage](../../application-fixes/assets/handoff-terminal-status.png) | Show End, completed and done together. |
| Persistence | [Definition readback](../../application-fixes/assets/handoff-definition-readback.png) | Save and reopen; show the attached collection and enabled/start switches. |
| Start the handoff | [Project before save](../../application-fixes/assets/handoff-project-before-save.png) | Save the project through Data Explorer, then reveal its automatically created task. |
| Enter SLA stage | [Middle stage](../../application-fixes/assets/handoff-middle-stage.png) | Advance once and hold on 48h left. |
| Finish | [Done](../../application-fixes/assets/handoff-task-done.png) | The actual recheck showed zero in flight and 100% complete before later tests added new tasks. |
| Retain evidence | [History](../../application-fixes/assets/handoff-task-history.png), [archived task](../../application-fixes/assets/handoff-task-archived.png) | Archive removes the card but All tasks retains the outcome. |
| Scope a trigger draft | [Collection lookup](../../application-fixes/assets/handoff-trigger-picker-fixed.png), [readback](../../application-fixes/assets/handoff-trigger-readback.png) | Select Design Projects and watch stage. Explain that watching a field is not testing its value. Do not start this draft. |
| Manual laboratory | [Raw editor](../../application-fixes/assets/handoff-manual-raw.png) | Preserve record identity and replace data with the supplied triggerless definition. No customer message action is present. |
| Save failure recovery | [Invalid JSON retained](../../application-fixes/assets/handoff-invalid-json-retained.png) | Optional troubleshooting insert: invalid JSON leaves the editor open. Restore valid content before continuing. |
| Controlled execution | [Stopped automation](../../application-fixes/assets/handoff-manual-stopped.png) | Start, Execute once, Stop. Distinguish enabling the automation from executing its action. |
| Result | [Run details](../../application-fixes/assets/handoff-run-details-fixed.png) | Expand Action result; point to created, datatype and recordId. The configuration alone is not proof of creation. |
| Deliberate repeat | [Two projects](../../application-fixes/assets/handoff-two-projects.png), [two tasks](../../application-fixes/assets/handoff-two-tasks.png) | Two executions produced two different records with the same title. Compare IDs. |
| Where work waits | [Approvals](../../application-fixes/assets/handoff-approvals.png) | Show the waiting tasks and inspect controls without making a new decision. Reassign is disabled while its recipient email is empty. |
| Scheduled work | [Schedule](../../application-fixes/assets/handoff-schedule.png) | Introduce Overview, Upcoming, Runs and Logs. No schedule is created in this lesson. |

## Graphics

Use two lanes: Smart Automation creates a record; Workflow Center moves its task through stages. Show the record's design phase separately from the task's handoff stage. For the duplicate example, draw two execution IDs leading to two project IDs with the same title. Do not depict automatic merging.

## Evidence and limits

[Execution responses and saved runs](../../application-fixes/assets/handoff-execution-proof.json) and [project ID readback](../../application-fixes/assets/handoff-project-readback.json) establish the actual results. Credentials must never appear in footage. The first local run exposed missing result persistence; the repaired second run has recorded results. Use the current result still for the successful path. Older defect captures may appear only in a clearly labelled historical troubleshooting segment.

This lesson does not demonstrate a live signature provider, signer/customer mapping, external notification, concurrent deduplication, Import round-trip, elapsed two-day escalation, recurring execution or a second person's approval. Do not imply those happened. The course directs those extensions to their appropriate setup and testing.

Before publishing, confirm every demonstrated control and outcome on the release being filmed. No unrelated clips, fabricated picker options or placeholder success screens belong in the recording.