Create a manual PC inspection checklist PDF
- Enter shop, technician, date and device identity. Choose Unknown explicitly when appropriate.
- Record only checks you performed; leave the rest Not tested.
- Add observations, battery information with its source, and recommendations.
- Generate and review the report, then download the PDF or explicitly save a draft file.
Formats, output and limits
Input: manually entered details and an optional JPG/PNG logo. Output: branded PDF, with optional explicit JSON draft. No hardware scan, diagnostic agent or device-health certification is provided.
Spreadsheet-safe CSV: risky text gets the visible prefix text: . Preview: =1+1 becomes text: =1+1; full-width formula starters and leading control characters are handled too. Validated numeric amounts keep their signs. Use JSON, where available, for original text and XLSX for typed exchange.
File tools accept up to 50 files and 100 MiB total, with a maximum of 500 source PDF pages. Mapping imports allow 10,000 rows. These are resource caps, not guarantees for every device. See all limits and troubleshooting.
A worked example
A fictional laptop has a failed USB check and an untested battery. Its report says Issues found, lists the failed check and preserves the untested result instead of inventing a pass.
Common questions
Is this an automatic hardware scan?
No. Specifications and outcomes are recorded by the technician. The browser does not measure SMART data, battery wear or hardware health.
Can I export an incomplete inspection?
Yes, once required technician, date, manufacturer and model details are supplied. Untested checks are allowed. Any Fail gives Issues found; otherwise any Not tested gives Inspection incomplete.
What information is saved?
Only explicitly saved shop/technician preferences persist in browser storage. Serial numbers and notes are not saved automatically. An explicitly downloaded JSON draft includes entered device details and should be stored privately.