7. Have you checked technical competence beyond the résumé?
Evidence to request: A short technical walkthrough focused on reasoning, testing and limitations. A non-technical parent can ask for an independent reviewer rather than pretending to evaluate code they do not understand.
8. Have you assessed teaching fit with the actual instructor?
Look for: Questions before explanations, space for the child to think and a constructive response to mistakes. Ask the learner privately whether they felt listened to.
9. Is the project small enough for the time and starting skills available?
Evidence to request: One learner-owned core task and optional extensions. For example, test a private hobby FAQ prototype using invented information before considering a public service.
10. Will you know what the child, mentor and AI each contributed?
Evidence to request: A redacted sample progress note. Do not demand percentage-of-authorship estimates; ask for concrete examples of decisions and assistance.
11. Have you agreed how understanding will be checked?
Evidence to request: One age-appropriate “explain, change, check” activity. Accept demonstrations, diagrams or written explanations where those suit the learner better than an oral performance.
Sources and context
This page sets out the desk’s purchasing framework. Sources →