Module 2 · Hands-on project
Project: Checking technical sheets
Is each sheet correct and complete — checked against its own checklist
A pile of technical sheets in PDF — product specs, equipment datasheets, safety sheets — and you have to tell, for each one, whether it's correct and complete. The trick isn't asking Claude "is this OK?" (it has no way to know what "OK" means for you). The trick is to give it the checklist of what a correct sheet must contain, and let it check every file against it.
This is the closest an office user gets to "evals." An eval is just a structured check of whether output meets a known standard (and an eval harness is the machinery engineers build to run thousands of them automatically). You need none of that here: you hand it the ground truth (the required fields) and have it report gaps. The quality of the check is only as good as the checklist you write, so that's where you spend your effort.
What you need in the folder
- The technical sheets to check (PDF or Word), each named so its type is recognizable (e.g. valve-DN50.pdf, pump-X.pdf).
- A checklist file — required-fields.md — listing the mandatory fields per sheet type. This is the heart of the project.