# Reviewer booking checklist

During Week 0 Task 06, save the request status and next follow-up in your existing week record.
Keep names, contact details, and calendar arrangements in your private email or calendar, not in Git.

> **What this teaches:** I can set up outside feedback as part of shipping my work. I share only the minimum, cleaned of private details.

## Qualification check

- [ ] Gates 1–3: the reviewer does current Java or full-stack development and code review.
- [ ] Gates 4–5: the reviewer has real CI/CD, container, and cloud-delivery experience.
- [ ] The reviewer is a person who is separate from your daily AI coaching.
- [ ] The reviewer agrees to use the published rubric and a fresh task of the same kind.

## Private booking fields

- Reviewer name/contact:
- Gate:
- Time zone:
- Proposed date/time:
- Confirmed date/time:
- Meeting format:
- Backup window:
- Cost, if any, approved by you:

## Send only what is needed

- [ ] The purpose of the gate and the fixed rubric
- [ ] The planned length, and that you will change code live while they watch
- [ ] How the reviewer will see your repo and proof, cleaned of private details
- [ ] A request for a fresh Issue of the same kind, kept private until the clock starts
- [ ] A request for a written decision based on proof
- [ ] No private records, secrets, test solutions, or earlier AI grades

## Explain it back

Explain why booking a reviewer early is part of the shipping plan. Then explain why the reviewer needs a fixed rubric but not your private learning history.