Learning path · Level 10 · Tutorial 4

Demonstrating and Handing Over an AI Solution

Present the solution through a short demonstration or narrated text walkthrough, then prepare a handover brief another person could use. Explain its value, design choices, acceptance evidence, limitations, operating instructions, and remaining risks without submitting files.

  • Level: Advanced
  • Duration: 20 min
  • 8 steps
Start tutorial Back to the path
Demonstrating and Handing Over an AI Solution

What you will go through

  1. Build the Demonstration Around a User Task Plan a concise demonstration around one stakeholder task, a visible bounded outcome, and the decision the demonstration is meant to inform. 2 min
  2. Make Claims the Evidence Can Support Turn an attractive demonstration into an evidence-calibrated explanation of benefit, tradeoff, and acceptance status. 3 min
  3. Deliver a Transparent Walkthrough Rehearse a concise demonstration or text walkthrough that accurately labels execution mode and exposes important boundaries. 3 min
  4. Organize a Version-Linked Handover Brief Structure a recipient-facing handover brief that keeps candidate identity, evidence, dependencies, and authority boundaries explicitly connected. 2 min
  5. Write Instructions Another Person Can Follow Create a self-contained Operate section that lets a recipient run one permitted Harbor Helpdesk task and stop at the correct authority boundary. 3 min
  6. Make Risks, Ownership, and Authority Explicit Turn known limitations into clear operating boundaries, assign ownership, and separate a review-ready handover from permission to launch. 2 min
  7. Replay the Handover as the Recipient Replay a routine task and an exception using only the recipient’s brief, then distinguish an instruction clarification from a behavior-changing repair. 3 min
  8. Present and Close the Handover Deliver the final demonstration and handover summary, clearly stating what the recipient can do next and what remains unauthorized or unresolved. 3 min

What you will learn

  • Deliver a concise demonstration in your own tools or a text walkthrough that clearly labels simulated actions.
  • Explain the user benefit, a significant design tradeoff, and the acceptance decision using specific evidence rather than unsupported claims.
  • Create a version-linked handover brief covering permitted use, required inputs, operating instructions, human checkpoints, ownership, limitations, and escalation.
  • Replay a task from the recipient's perspective using only the handover brief, then revise missing or ambiguous instructions.
  • State remaining risks and distinguish readiness for handover from authorization to launch.

Before you start

  • Specifying an End-to-End AI-Assisted Solution
  • Assembling a Small AI Solution Prototype
  • Making an Evidence-Based Acceptance Decision
  • Planning AI Adoption and Ongoing Ownership

Step 1 of 8

Build the Demonstration Around a User Task

Plan a concise demonstration around one stakeholder task, a visible bounded outcome, and the decision the demonstration is meant to inform.

Lead with the stakeholder task

Start with a task and a decision

A useful demonstration is not a feature tour. It follows one stakeholder-relevant task from a real difficulty to a visible, bounded outcome.

For Harbor Helpdesk, focus on this question: can an Operator turn a permitted internal support request and an approved FAQ source into a draft that an Output reviewer can check?

That focus helps the audience decide whether the candidate supports this narrow task. It does not claim that every request, exception, or operating condition has been shown.

Task-led demonstration route

A support request and approved FAQ lead to a draft reply and then a human review checkpoint, while generic features are faded in the background.

Show the path the stakeholder cares about: permitted input, visible behavior, human review, and a usable draft.

Connect the task to a visible outcome

Use five connected beats

Use a compact five-part narrative:

  1. User difficulty — what the person needs to accomplish.
  2. Permitted input — the request and approved source the solution may use.
  3. Visible behavior — what the audience can observe the solution produce.
  4. Human checkpoint — who checks the output and what they check.
  5. Usable output — the bounded result available after that checkpoint.

Keep the narrative tied to one task. Name the boundary as part of the story: Harbor Helpdesk drafts replies; it does not send messages or change accounts.

Example

Example: a short task narrative

User difficulty: An Operator needs to answer an internal request about access after a team transfer without inventing a policy.

Permitted input: The Operator provides the request and the relevant passage from approved source collection FAQ r3.

Visible behavior: Harbor Helpdesk v1.2 produces a concise draft that directs the requester to the documented next step.

Human checkpoint: An Output reviewer compares the draft with the FAQ passage and checks that it does not promise an account change.

Usable output: A reviewable internal support-reply draft is ready for the team's separate process.

Separate the screen story from the spoken story

Choose one informative task

Choose a task that is representative in a limited sense: it should contain a real permitted input, make the intended benefit visible, and include the required review checkpoint.

Do not treat one clean routine task as proof that every condition works. Its job is to make the proposed workflow understandable. Cases with missing sources, unusual requests, or service interruptions may need separate attention.

Map what is seen and what is explained

A two-lane storyboard separates visible task artifacts from the purpose, boundaries, and decision explained by the presenter.

The audience sees the request, source, draft, and review. You explain why the task matters, why the input is permitted, and which decision the demonstration is intended to inform.

Tip

Use a visual demonstration map

Before presenting, make a two-column map:

  • Audience sees: the request, the approved source excerpt, the draft, and the reviewer checkpoint.
  • Presenter explains: the user difficulty, the task boundary, the intended benefit, and the stakeholder decision.

This prevents a common gap: expecting viewers to infer the purpose from screens alone.

Build your own task-led outline

Practice: outline the demonstration

Create a task-led outline for this fictional case. Write five numbered lines in the most useful demonstration order, then add one sentence beginning Stakeholder decision:.

Harbor Helpdesk candidate: v1.2
Approved source: FAQ r3

Request: “I moved to a new team and cannot open the Procurement portal. What should I do?”

Approved FAQ excerpt: “After a team transfer, the employee’s manager submits Access Form P-17 for Procurement portal access. Support does not alter permissions.”

Draft response: “Please ask your manager to submit Access Form P-17 for Procurement portal access. Support cannot change permissions directly.”

Acceptance summary — Illustrative data: 10 of 12 scenarios pass; 1 of 12 fails for missing-source escalation; 1 of 12 is marked Untested for outage handling. Acceptance decision: Revise.

Arrange these elements: the Operator’s difficulty; permitted request and FAQ r3 excerpt; the draft behavior; the Output reviewer’s check; the usable bounded output. State the stakeholder decision that this demonstration is meant to inform, rather than repeating the acceptance decision.

Write at least 300 characters (0/300).

Step 2 of 8

Make Claims the Evidence Can Support

Turn an attractive demonstration into an evidence-calibrated explanation of benefit, tradeoff, and acceptance status.

Separate a demonstration from a claim

One visible draft is not the whole evidence base

A polished draft from one routine task is an illustrative run: it shows what happened once under those conditions. It does not, by itself, prove speed, coverage, or safe handling across other requests.

For a broader claim, name the evidence set, the comparison condition, and what it does not cover. This keeps a demonstration useful without turning it into an unsupported promise.

Illustrative run versus acceptance evidence

A comparison between one reviewed support-reply draft and a twelve-scenario acceptance record with ten passes, one failure, and one Untested case.

Use a single run to make behavior visible; use the acceptance record to bound wider claims.

What each record can support

Illustrative data for Harbor Helpdesk

Evidence supports only claims at its own scope.
EvidenceA supportable statementNot established
Six paired routine tasks: median 6.0 min/task baseline; 4.0 min/task including human reviewA faster median under these six paired routine tasksPerformance for every request type
10 of 12 scenarios passedTen tested scenarios met their recorded criteriaAll scenarios passed
Outage handling: UntestedNo execution evidence for outage handlingSafe outage handling

State tradeoffs and the decision honestly

Write the value at the evidence's scale

A concise value statement has three parts:

  1. Benefit and measure: what improved, using the actual unit.
  2. Comparison and conditions: what it was compared with, and what review or setup was included.
  3. Boundary: why the result is limited rather than universal.

For Harbor Helpdesk, the timing comparison covers six paired routine tasks only, and the 4.0 min/task result includes human review. Say exactly that.

Explain the tradeoff for the audience

Chosen approach: draft internal replies only from approved FAQ r3, then require an Output reviewer.

Rejected alternative: automatically send replies to requesters.

Practical consequence: review takes time, but a person can reject a draft before any message is sent.

Remaining limitation: human review does not turn a missing source into a resolved answer. The missing-source escalation case still failed.

Example

Example: benefit plus tradeoff

A calibrated statement could be:

“Across six paired routine tasks, Harbor Helpdesk reduced the median handling time from 6.0 min/task at baseline to 4.0 min/task including human review. It favors FAQ-grounded drafts and an Output reviewer over automatic sending, which preserves a review checkpoint but retains review effort. This limited timing sample does not show the same result for every request.”

Show the decision with the inconvenient evidence

Illustrative data: acceptance record for candidate v1.2 using FAQ r3

A credible demonstration states failures and unknowns alongside successes.
StatusRecorded resultWhat to say
Pass10 of 12 scenariosTen scenarios passed their criteria
Fail1 of 12: missing-source escalationThis exception needs revision
Untested1 of 12: outage handlingNo execution evidence yet
Acceptance decisionReviseDo not present the candidate as accepted

Check claim-to-evidence alignment

Classify the claims

Match each claim to its evidence status.

Tap an item and then its matching pair.

Apply the evidence without overclaiming

Draft the evidence-calibrated message

Write a short, audience-ready statement of 2–4 sentences about Harbor Helpdesk.

Include all of the following:

  • the measured benefit, comparison, and limited six-task timing sample;
  • the tradeoff between FAQ-grounded drafts with an Output reviewer and automatic sending;
  • the failed missing-source escalation and Untested outage handling; and
  • the exact acceptance field: Acceptance decision: Revise.

Use counts and units accurately. Do not claim that every request is faster or that outages were tested.

Write at least 300 characters (0/300).

Step 3 of 8

Deliver a Transparent Walkthrough

Rehearse a concise demonstration or text walkthrough that accurately labels execution mode and exposes important boundaries.

Frame one bounded task

A 90-second task story

A transparent walkthrough is a short, task-led story—not a feature tour. In roughly 90 seconds, show:

  1. The task and its boundary: Harbor Helpdesk drafts an internal support reply from approved FAQ r3. It does not send messages or change accounts.
  2. The visible behavior: a permitted request becomes a draft.
  3. The human checkpoint: an Output reviewer checks the draft before any use.
  4. The evidence and boundary: what was tested, what failed, and what remains Untested.

Name the execution status at the moment you show each segment. A useful audience should never have to guess whether it is watching a live run, a person standing in for a step, or a saved result.

The walkthrough arc

A four-stage visual flow from support request and approved FAQ, to drafted reply, human review, and evidence with a warning.

Narrate the task, visible draft, review checkpoint, and evidence boundary in that order.

Label modes and boundaries

Make the mode visible

Use execution labels as factual statements, not quality ratings.

  • Live execution: you are performing the action now in the actual tool.
  • Manual simulation: a person performs a step that stands in for the intended solution behavior.
  • Recorded result: you show saved output from an identifiable earlier run.
  • Untested: no execution evidence exists for that capability.

A walkthrough can be mixed-mode. For example, you may show a Recorded result for draft generation and a Manual simulation for the reviewer’s decision. Say the label aloud and place it beside the segment when possible.

Execution-status language

Choose the label that matches what occurred, then state the consequence honestly.

These labels describe evidence status, not whether the result is good or bad.
LabelWhat actually happenedSafe narration
Live executionThe tool is run now“Live execution: I submit this request now.”
Manual simulationA person stands in for a step“Manual simulation: the reviewer checks this draft.”
Recorded resultA saved, identified run is shown“Recorded result: this draft came from candidate v1.2.”
UntestedNo run supports the capability“Untested: outage handling has no execution evidence.”

Warning

Expose the stop point

Do not turn an unresolved exception into a success story. For Harbor Helpdesk, say: “Recorded result: the missing-source escalation scenario failed. Stop and route it for human handling; no repair is being demonstrated.”

If live access is unavailable, switch explicitly to a Recorded result or a text walkthrough. Never describe that fallback as a successful live run.

Check a claim before you say it

Spot the unsupported claim

A presenter cannot access Harbor Helpdesk live. They show a saved draft and role-play the Output reviewer’s check. Which narration is misleading?

Text-only walkthrough materials

Routine task material

Use the following self-contained material for a text-only rehearsal. No account, recording, upload, or paid feature is required.

Task: An employee writes, “I reset my password, but VPN still rejects it. What should I do?” Harbor Helpdesk may draft an internal reply for human review only.

Example

Approved source: FAQ r3

FAQ r3 — VPN access after a password reset

  • Use the Password Reset Portal to reset a password. Wait five minutes, then sign in again.
  • If VPN still rejects the sign-in after that wait, contact the IT Service Desk. Include the employee ID and the time of the error.
  • Harbor Helpdesk drafts support replies only. It does not access accounts, reset passwords, or send messages.

Example

Reusable prompt

Using only FAQ r3 below, draft an internal support reply to the employee. Do not invent steps. If the source does not answer the request, begin the draft with: “Source unavailable—escalate for human handling.” State that the assistant drafts only and does not send messages or change accounts.

[Paste FAQ r3 here]

Example

Recorded result: candidate v1.2

Hello,

Please wait five minutes after using the Password Reset Portal, then try signing in to VPN again. If VPN still rejects the sign-in, contact the IT Service Desk and include your employee ID and the time of the error.

This is a draft for human review. Harbor Helpdesk does not access accounts, reset passwords, or send messages.

Write your transparent rehearsal

Rehearse the labeled walkthrough

Write a concise narrated walkthrough of about 110–170 words using the material on the previous screen. It must:

  • identify the bounded task and FAQ r3;
  • label the draft segment “Recorded result” and the review segment “Manual simulation”;
  • state that the output is only a draft and name the human review checkpoint;
  • expose the missing-source escalation failure as a stop point, not a working repair;
  • close with: “Illustrative data: 10 of 12 scenarios passed, 1 failed, and 1 was Untested for outage handling.” Also state the six paired routine-task timing comparison, Acceptance decision: Revise, and that live execution was unavailable.

Write as if you are speaking to a stakeholder. Do not claim that the candidate sends messages, changes accounts, handles outages, or successfully repaired the failed escalation.

Write at least 550 characters (0/550).

Step 4 of 8

Organize a Version-Linked Handover Brief

Structure a recipient-facing handover brief that keeps candidate identity, evidence, dependencies, and authority boundaries explicitly connected.

Start with a recipient-facing structure

The brief is the recipient’s map

A handover brief is the recipient’s entry point—not a presentation script or a folder of disconnected notes. It lets the recipient identify what they received, what it can be used for, and what evidence applies.

Use these headings consistently:

  • Scope and version
  • Operate
  • Exceptions and escalation
  • Ownership
  • Design rationale
  • Evidence and limitations
  • Handover status

Keep the purposes separate. Operate is for the material needed to use the solution. Design rationale explains significant choices. Evidence and limitations records what was evaluated and what remains uncertain. Handover status states the decision and authority boundaries.

Separate information by purpose

A central handover brief connected to seven visually distinct sections for identity, operation, exceptions, ownership, rationale, evidence, and status.

A usable brief separates instructions, rationale, evidence, ownership, and status instead of blending them into one narrative.

Link evidence to an identifiable candidate

Build an alignment map

Every important statement needs an explicit link to the same candidate. Do not infer that a result, source collection, or instruction applies merely because the names look similar.

For Harbor Helpdesk, the identity chain is: candidate v1.2, source collection FAQ r3, acceptance evidence for v1.2, and handover document Brief r1. The recipient should be able to trace this chain without asking the presenter.

Harbor Helpdesk alignment map

This map makes version links visible before the recipient relies on the brief.

Illustrative data and identifiers linked to the same demonstrated candidate.
RecordExplicit referenceWhat it establishes
Demonstrated candidateHarbor Helpdesk v1.2The solution being handed over
Approved sourceFAQ r3The source collection for v1.2
Acceptance evidenceIllustrative data for v1.2: 10 of 12 scenarios pass; 1 of 12 fails for missing-source escalation; 1 of 12 is Untested for outage handlingThe observed boundaries of this candidate
Timing evidenceIllustrative data: six paired routine tasks; median baseline 6.0 min/task versus 4.0 min/task including human reviewA limited comparison, not a universal claim
Handover documentBrief r1The recipient-facing record linked to v1.2

Tip

Keep document edits distinct from candidate changes

An instructions-only update may create Brief r2 while candidate v1.2 and its evidence remain unchanged. A change to the candidate’s behavior requires a different candidate version; earlier acceptance evidence must not be silently reused as proof for that changed candidate.

Make the transfer usable without private context

Transfer is not launch approval

A complete transfer can be review-only. For the reference case, state these fields separately:

  • Acceptance decision: Revise
  • Handover readiness: Ready for review-only handover
  • Launch authorization: Not granted

This lets a recipient inspect the candidate and its records without mistaking the transfer for permission to launch it. The failed missing-source escalation and Untested outage handling remain visible limitations, not issues hidden by the demonstration.

Check dependencies from the recipient’s position

Before handover, check that the recipient can obtain every dependency through the brief itself or through a genuinely accessible resource. A presenter’s private workspace is not an accessible resource.

A dependency is usable only when its content or access route is explicit.
Needed itemAcceptable in the briefNot sufficient
Candidate identityHarbor Helpdesk v1.2 named explicitly“The current assistant”
Source basisFAQ r3 text or a recipient-accessible location identified clearly“Use my source folder”
Operating materialRequired text included in the brief or an explicit accessible route“Use the prompt I showed”
Evaluation recordCandidate-specific results and limitations summarized in the brief“It passed testing”
People and boundariesNamed role and review-only status“Ask the team if needed”

Check placement and alignment

Place records—and expose the mismatch

Match each record to the section or handling it requires. One record intentionally contains a candidate–evidence version mismatch; do not silently treat it as valid evidence.

Tap an item and then its matching pair.

Step 5 of 8

Write Instructions Another Person Can Follow

Create a self-contained Operate section that lets a recipient run one permitted Harbor Helpdesk task and stop at the correct authority boundary.

Define the route and its boundary

Make the operating route self-contained

In the brief’s Operate section, write a route that an Operator can perform without your memory, private workspace, or hidden setup. It must identify the applicable candidate and source, then make the permitted task and its boundary unmistakable.

For Harbor Helpdesk, this route applies to candidate v1.2 using FAQ r3. It permits one task: drafting an internal support reply from an approved FAQ for human review. It excludes sending messages, changing accounts, inventing instructions, and treating a draft as an approved or sent response.

State the access need, required input, and starting state. For the text-only route, the Operator needs a chat assistant, a blank chat, and the complete reusable prompt plus FAQ r3 text included in the brief. The required input is an internal support question that FAQ r3 answers.

What the Operator needs to see

A visual route from the identified candidate and approved FAQ through a blank chat and visible draft to a reviewer checkpoint, with sending and account changes beyond a stop barrier.

An operating route supplies the materials and visible checkpoints needed to reach a reviewed draft; it does not silently extend the solution’s authority.

Tip

Write checkpoints as decisions

Replace “review carefully” with observable checks and a decision. For example: “The Output reviewer compares every instruction in the draft with FAQ r3, confirms that the draft does not claim Harbor Helpdesk can access accounts, reset passwords, or send messages, then either approves it as a draft or rejects it for correction.”

Name the endpoint precisely. A generated draft is not yet an approved output. An approved output is still an unsent draft: sending it or changing an account remains outside Harbor Helpdesk’s authority.

Show the complete text-only route

Provide the materials, not just a reference

A source name alone is not an operating route. Put the full reusable prompt and the source text needed for the route in Operate so the recipient does not need to find an unpublished file or ask what to paste. This routine task uses the same v1.2 text walkthrough material shown earlier.

Reusable prompt and source material

Copy this entire block into a blank chat for the routine text-only route.

markdown
Using only FAQ r3 below, draft an internal support reply to the employee. Do not invent steps. If the source does not answer the request, begin the draft with: “Source unavailable—escalate for human handling.” State that the assistant drafts only and does not send messages or change accounts.

FAQ r3 — VPN access after a password reset
• Use the Password Reset Portal to reset a password. Wait five minutes, then sign in again.
• If VPN still rejects the sign-in after that wait, contact the IT Service Desk. Include the employee ID and the time of the error.
• Harbor Helpdesk drafts support replies only. It does not access accounts, reset passwords, or send messages.

Internal support question:
“I reset my password, but VPN still rejects it. What should I do?”
Expected output
Hello,

Please wait five minutes after using the Password Reset Portal, then try signing in to VPN again. If VPN still rejects the sign-in, contact the IT Service Desk and include your employee ID and the time of the error.

This is a draft for human review. Harbor Helpdesk does not access accounts, reset passwords, or send messages.

This is the expected routine-task draft for the supplied VPN question. It does not establish that missing-source escalation works: Illustrative data for v1.2 records 1 of 12 scenarios as a failure for missing-source escalation.

Operate

Run this routine route in order. The Output reviewer makes the approval decision; Harbor Helpdesk does not make it.

Each usable action names a visible result and the required human decision.
ActionExpected visible resultRequired decision
Confirm candidate v1.2 and FAQ r3Both identifiers match the briefContinue only when they match
Open a blank chat and paste the complete supplied blockThe prompt, FAQ r3, and internal question are visibleSubmit the prompt
Read the returned resultA source-grounded draft is visibleDo not treat the draft as approved
Output reviewer checks the draft against FAQ r3Instructions are sourced and authority limits are statedApprove as a draft or reject it
Keep an approved item as an unsent draftA human-reviewed internal reply is availableDo not send it or change an account

Warning

Do not convert a prompt instruction into evidence

Keep the missing-source boundary honest. The prompt instructs v1.2 how to begin a draft when the source does not answer, but that does not prove the exception was handled successfully. Illustrative data records 1 of 12 scenarios failed for missing-source escalation. If the Operator lacks source support, they must stop rather than invent a reply or claim that the candidate repaired the failure.

Check the action order

Sequence the operating route

Put the Harbor Helpdesk routine operating actions in the only workable order.

  1. Keep any approved item as an unsent draft; do not send it or change an account.
  2. Have the Output reviewer compare the draft with FAQ r3 and decide whether to approve it as a draft.
  3. Confirm that candidate v1.2 and FAQ r3 match the brief.
  4. Submit the permitted internal question and read the visible draft.
  5. Open a blank chat and paste the complete reusable prompt and source text.

Apply the operating template

Draft the operating section

Complete this compact operating section for the reference case. Use only the routine route established in this step.

Scope and version
Candidate: …
Source: …

Operate

  • Permitted task and exclusions: …
  • Access, starting state, and accessible materials: state that the brief contains the complete reusable prompt and full FAQ r3 text, then include both texts.
  • Required input: …
  • Ordered actions and expected visible output: …
  • Output reviewer’s specific checks and permitted next action: …
  • End state and the point beyond which the Operator is not authorized to proceed: …

Preserve the recorded missing-source limitation: do not claim that missing-source escalation passed.

Write at least 700 characters (0/700).

Step 6 of 8

Make Risks, Ownership, and Authority Explicit

Turn known limitations into clear operating boundaries, assign ownership, and separate a review-ready handover from permission to launch.

Separate limitations from stop conditions

Evidence and limitations

A limitation tells the recipient what remains uncertain or constrained. A stop condition tells the operator when they must not continue.

For Harbor Helpdesk, outage handling is Untested: the recipient must not describe recovery behavior as proven. By contrast, a needed fact missing from the approved source collection is an observable condition that prevents a supported draft. The operator stops, does not fill the gap from memory, and follows escalation.

Make this distinction visible under Evidence and limitations and Exceptions and escalation. Clear boundaries are more useful than vague cautions such as “review carefully.”

When to proceed, stop, or qualify evidence

A process diagram showing a supported request proceeding to human review, a missing source causing a stop, and an outage marked as untested.

A source gap is a stop-and-escalate trigger. An untested condition is a limitation that must remain visible, not a claimed capability.

Exceptions and escalation

Exceptions and escalation

An exception entry should let an unfamiliar operator act without guessing. Write four operational parts:

  1. Observable trigger — what the operator can see.
  2. Stop or fallback action — what to do and what not to do.
  3. Support contact — the accountable route, not a credential.
  4. Minimum diagnostic information — enough context to investigate, with no unnecessary personal data.

The entry describes a response to a condition. It does not quietly repair the candidate or convert a failed scenario into a pass.

Reference exception entry

Use this structure in the Exceptions and escalation section of Brief r1.

An actionable entry for the known missing-source problem.
Entry fieldBrief r1 content
Observable triggerA needed claim is not supported by FAQ r3 and no approved source is available.
Stop actionStop drafting that reply. Do not invent, infer, or add an unsupported claim.
FallbackRequest an approved source or route the request for manual handling.
Support contactSupport lead
Minimum diagnostic informationCandidate v1.2; FAQ r3; missing topic; timestamp; request reference without unnecessary personal data; exact stop message.

Ownership and handover status

Ownership

Name responsibilities by role so the recipient knows who acts, but never put passwords, tokens, or private access routes in the brief. The role assignment is an operating boundary: it does not grant the Operator authority to update sources, approve a launch, or bypass review.

Role-specific references

Record the responsible role and its decision boundary.

Ownership references for Harbor Helpdesk.
RoleResponsibility
OperatorRuns only permitted drafting tasks and stops on documented exceptions.
Output reviewerChecks the draft against FAQ r3 and decides whether it is suitable for onward use.
Source maintainerMaintains approved source content and confirms source updates.
Support contactSupport lead; receives exception reports and coordinates support.
Launch approverService owner; alone decides whether launch authorization is granted.

Handover status

A handover can be complete for review even when the candidate is not ready to launch. Keep these fields separate in Handover status:

  • Acceptance decision records what the evaluation supports.
  • Handover readiness records whether the recipient has a usable review-only brief.
  • Launch authorization records permission to operate beyond that review purpose.

An instructions-only revision may become Brief r2 while still applying to candidate v1.2 and FAQ r3. It clarifies documentation; it does not change behavior, erase a failure, or create outage evidence. A behavior change needs a different candidate version and relevant new acceptance evidence.

Example

Status block for Brief r1

Evidence and limitations

Illustrative data: 10 of 12 scenarios passed. 1 of 12 scenarios failed because missing-source escalation did not meet the acceptance expectation. 1 of 12 scenarios was untested for outage handling.

Handover status

Acceptance decision: Revise
Handover readiness: Ready for review-only handover
Launch authorization: Not granted

The brief communicates the unresolved result honestly; it is not permission to launch Harbor Helpdesk.

Apply the operating boundary

Write the escalation and status record

Using the Harbor Helpdesk reference case, write the Exceptions and escalation entry for missing-source evidence. Include the observable trigger, stop or fallback action, support contact, and minimum diagnostic information.

Then write the three labeled Handover status fields for Brief r1. Preserve the documented failed missing-source outcome and the untested outage outcome; do not treat the brief as a behavioral repair.

Write at least 300 characters (0/300).

Step 7 of 8

Replay the Handover as the Recipient

Replay a routine task and an exception using only the recipient’s brief, then distinguish an instruction clarification from a behavior-changing repair.

Use only what the recipient receives

Replay from the recipient’s starting point

A recipient-perspective replay asks: “Could I complete this task using only what the brief explicitly makes available?” Start as if you have not seen the build, test workspace, or presenter notes.

Use the named brief and only materials it tells you how to access. A source named without an access route is unavailable for the replay. Run two short paths:

  1. One routine permitted task.
  2. One documented exception or stop condition.

Record where you cannot proceed, where a decision is vague, and what consequence follows. A self-replay is a handover check; it is not independent user validation.

The brief is the starting point

A handover brief routes a routine task through a human review checkpoint and routes an exception to a stop and support path.

Replay both the normal route and the exception route using the brief alone.

Tip

Replay rule

Do not fill a gap with knowledge from the person who wrote the brief. If you know where a source lives but the brief does not say, record that as a documentation gap.

Turn a breakdown into a usable revision

Supplied flawed excerpt

Use this intentionally flawed excerpt if you are not replaying your own brief.

Scope and version
Candidate: Harbor Helpdesk v1.2
Source collection: FAQ r3
Document: Brief r1

Operate
“Operator: paste a permitted internal support request into Harbor Helpdesk. Use the approved FAQ and review the draft carefully.”

Exceptions and escalation
“If a needed source is missing, handle it appropriately.”

Ownership
Output reviewer: check the draft.
Source maintainer: FAQ r3.
Support contact: Support lead.

Handover status
Acceptance decision: Revise
Handover readiness: Review-only
Launch authorization: Not granted

A compact replay record

Illustrative data — use these four fields for each replayed path. The record makes a vague instruction observable and gives the writer a focused revision target.

Record the routine task and the exception separately.
Record fieldWhat to capture
Attempted actionThe exact action the recipient tried to take
Missing or ambiguous instructionWhat the brief did not make usable or clear
ConsequenceWhat could not be done, checked, or decided
Proposed clarificationA precise instruction, expected result, or stop route
Replay resultWhether the affected action now works using the revised brief

Example

Clarify documentation; do not silently change behavior

An instruction-only clarification can identify the approved source and version, state a check the Output reviewer must perform, and tell the Operator when to stop and contact the Support lead. These additions create Brief r2 while the candidate remains Harbor Helpdesk v1.2; its v1.2 evidence still identifies the same behavior.

A change that makes the assistant retrieve another collection, route a request automatically, or send a message changes behavior. It needs a new candidate version and affected acceptance evidence must be reconsidered. Do not describe that as a mere Brief r2 clarification.

Practice the recipient replay

Replay, revise, and repeat

Using the supplied excerpt or your own brief, write a recipient-perspective replay log.

Include:

  • one routine attempted action, its missing or ambiguous instruction, and its consequence;
  • one missing-source exception attempted action, its missing or ambiguous instruction, and its consequence;
  • at least one precise replacement instruction for an instructions-only Brief r2 revision;
  • the result of repeating the affected action using that revision;
  • whether one change you considered is documentation-only or behavior-changing, including the candidate-version and evidence implication if behavior changes;
  • the statement that this was a self-replay handover check, not independent user validation.

Do not assume access to an unstated folder, tool setting, or presenter knowledge.

Write at least 350 characters (0/350).

Step 8 of 8

Present and Close the Handover

Deliver the final demonstration and handover summary, clearly stating what the recipient can do next and what remains unauthorized or unresolved.

Link the demonstration to the recipient's next step

Make the delivery one connected argument

A strong close is not a feature recap. It gives the recipient one connected, honest route from a real task to a controlled next step.

Use this sequence:

  1. Name the permitted task and input.
  2. Show the visible draft behavior and the required human review checkpoint, labeling each segment by what actually occurred: Live execution, Manual simulation, or Recorded result.
  3. State the measured user benefit with its comparison conditions and sample limit.
  4. Explain one meaningful tradeoff and its remaining consequence.
  5. State the acceptance evidence, including failures and untested cases, then point the recipient to the operating route in the brief.

Do not let an attractive routine-task demonstration imply that every exception works. The close must make both the useful next action and the boundary of authorization unmistakable.

From demonstrated task to controlled handover

A flow from an approved source through an AI-generated draft and human review to a recipient, with evidence, an unresolved warning, and a closed launch gate.

Use the flow to connect behavior, review, evidence, operating instructions, and the separate decision about launch.

Align the brief, evidence, and authority

Run a final consistency check

Before you close, trace every reference in your spoken walkthrough and brief. A revision to instructions can create a new brief revision without changing the candidate. A behavior, prompt, source, or configuration change creates a different candidate version and requires the relevant evidence to be reconsidered.

Harbor Helpdesk final alignment

Use these sections as the compact spine of the final handover summary.

Reference case: a review-only transfer, not authorization to launch.
Brief sectionReference to stateFinal check
Scope and versionCandidate v1.2; source collection FAQ r3; Brief r2Brief r2 is an instructions-only revision for v1.2.
OperateInternal FAQ-based reply drafting only; draft then human reviewIt does not send messages or change accounts.
Exceptions and escalationMissing-source stop and escalation; outage handling is UntestedOperator records minimal diagnostics; Support contact is Support lead.
OwnershipOperator runs; Output reviewer approves drafts; Source maintainer maintains FAQ r3Service owner is the Launch approver.
Design rationaleApproved-FAQ grounding limits unsupported contentTradeoff: narrower coverage; source gaps remain a limitation.
Evidence and limitationsIllustrative data: six paired routine tasks, 6.0 min/task baseline and 4.0 min/task including human review10 of 12 scenarios pass; 1 of 12 fails missing-source escalation; 1 of 12 is Untested for outage handling.
Handover statusAcceptance decision: Revise; Handover readiness: Ready for review-only transfer; Launch authorization: Not grantedA usable review handover is not permission to launch.

Final application: deliver and hand over

Draft the final delivery

Write your final delivery for Harbor Helpdesk in two compact parts, using only your completed brief.

Part A: write a short walkthrough that identifies the permitted task, visible draft behavior, required human checkpoint, and the accurate execution or evidence label for each segment. Include an evidence-calibrated benefit statement, one significant tradeoff, and the acceptance decision with its failed and untested boundaries.

Part B: write the handover close. Identify the aligned candidate, source, and brief versions; tell the recipient where to start, how to operate, and when and how to escalate. Mention the replay-driven instruction revision, remaining risks and unresolved work, the responsible roles, and separate labeled statements for acceptance decision, handover readiness, and launch authorization.

Keep it concise enough to present aloud. Do not claim production readiness or a successful repair that the evidence does not support.

Write at least 750 characters (0/750).

Close with an honest transfer

Summary

Self-check the close

Use this last review after drafting your delivery.

  • Each demonstration segment is labeled truthfully as Live execution, Manual simulation, Recorded result, or Untested where there is no execution evidence.
  • The version chain is explicit: candidate v1.2, FAQ r3, and Brief r2. Brief r2 is an instructions-only revision; a candidate change needs a different candidate version.
  • The benefit is bounded: Illustrative data from six paired routine tasks shows a median of 6.0 min/task at baseline and 4.0 min/task including human review.
  • The acceptance record remains visible: 10 of 12 scenarios pass, 1 of 12 fails missing-source escalation, and 1 of 12 is Untested for outage handling.
  • The recipient can follow Scope and version, Operate, Exceptions and escalation, Ownership, Design rationale, Evidence and limitations, and Handover status without relying on a private workspace.
  • Your close separates Acceptance decision: Revise, Handover readiness: Ready for review-only transfer, and Launch authorization: Not granted.

Tutorial complete

Congratulations! You completed: Demonstrating and Handing Over an AI Solution

You can now demonstrate and hand over a bounded AI solution without overstating what it is ready to do.

20 XP

You completed the path

Congratulations! You went through every tutorial in this path.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate