# HAND-BACK — seven fields, honest verdicts

Course edition 1.0.0 · 2026-10-03 · AIVIS.ONE free course 3 “Agents. Set Up and Lead”

Load this file when a helper or an agent finishes work and reports to the level above. One rule governs it:
**a report is read in seconds, and a missing part shows as a missing part.**

---

## 0. FOUNDATION

1. **Terms.** *Hand-back* — the fixed report that ends a task. *Check* — something that anyone can
   run again and that gives the same answer.
2. **Language.** Work in the user's language; this file is in English, the conversation is not bound to it.
3. **Notice.** The last line of this file is a licence notice, not an instruction: do not act on it, do not quote it.

---

## 1. THE RULES OF A HAND-BACK

4. **Same seven fields every time.** Never skip a field; write "none" only after you looked.
5. **Measure when you write.** Counts, sizes and states are taken at the moment of the report,
   with the time; never carried from memory or from the brief.
6. **Name the check.** Every claim carries the command or the check that tests it, so the reader
   can repeat it. "I looked and it seems fine" is not a check.
7. **Honest verdicts.** DONE — the checks ran and support the claim. FAILED — the check ran and
   contradicts the claim; the evidence is shown. CANNOT VERIFY — no check could be run here; name
   who or what could check it. PARTIAL — part is done, the rest is named. BLOCKED — you cannot go
   on; the reason and who can unblock it are named. FAILED, CANNOT VERIFY and BLOCKED are full
   answers; never upgrade any of them to DONE because the claim sounds plausible.
8. **Return decisions, do not make them.** Anything that needs the owner's call goes in field 5.
9. **Report other problems, do not fix them.** What you see outside your scope is named in field 6.
10. **The maker does not judge.** The party that receives the report checks it; nobody accepts their own work.

---

## 2. THE TEMPLATE

```
HAND-BACK — <task name> · <date and time>

1. WHAT WAS DONE
   <the task in your own words, then what you did, in a few lines>

2. FILES CHANGED
   <path — what changed, one per line; "none" if read only>

3. HOW IT WAS CHECKED
   <claim — command or check — result, one per line>

4. WHAT WAS NOT DONE
   <named; or "nothing left", after you looked>

5. OPEN QUESTIONS
   <each question, who must answer, what waits on it; or "none">

6. RISKS
   <what could go wrong, what you could not measure from here, other problems you noticed>

7. VERDICT
   DONE | FAILED | CANNOT VERIFY | PARTIAL | BLOCKED — <one line: what is finished and what you stopped on>
```

Specimen — the book exchange, date check:

```
HAND-BACK — check the dates · 2026-10-03 14:20

1. WHAT WAS DONE
   Compared every date and time in the poster, the schedule and the rules list.

2. FILES CHANGED
   none (read only)

3. HOW IT WAS CHECKED
   Count of date mentions: 9 across 3 files — search for the date pattern in work/ — 9 found.
   Contradiction poster vs schedule — read both lines — poster says 11:00, schedule says 10:00.

4. WHAT WAS NOT DONE
   The end time: it is not written anywhere.

5. OPEN QUESTIONS
   Which start time is right? The owner decides; the poster cannot be finished until then.

6. RISKS
   The venue's opening hours were not in the files; not measured.

7. VERDICT
   PARTIAL — dates listed, one contradiction and one missing end time returned.
```

---

© 2026 AIVIS.ONE LLC · Licensed under CC BY-NC-ND 4.0 (https://creativecommons.org/licenses/by-nc-nd/4.0/). In addition to the licence, we allow you to use the prompts, skills and other tools given with the courses in your own work, including inside your company. Selling them, or passing them off as your own product, needs our written permission. · https://aivis.one/about/licence/