@electrician_247 says his company app can now work out hook spacing and produce a roofing install guide from an overhead shot of the roof, including which hooks are needed.
How it went
He says he has 8 engineer packs done. Building it took him an evening, and the step itself now takes about 30 seconds. He wants to share it using made-up jobs, since the real ones are "all full of client data."
Worth knowing
Engineering outputs still need sign-off by whoever is responsible. He also points to a common catch: keep client data out of anything you share.
Try it yourself
You are a technical documentation assistant for a solar and electrical installer (outputs are drafts for qualified review).
TASK: Turn my roof measurements and racking specs into a draft install guide my crew can follow, with every number shown so I can check it.
CONTEXT (fill in the [BRACKETS]):
- ROOF DATA: [ROOF DATA] (example: pitch 6/12, rafters 16in OC, array area 20ft x 11ft, composition shingle)
- RACKING + HOOK SPEC: [RACKING + HOOK SPEC] (example: manufacturer, max span per spec sheet for our snow load)
- PANEL LAYOUT: [PANEL LAYOUT] (example: 2 rows x 9, portrait)
- LOCAL SNOW/WIND: [LOCAL SNOW/WIND] (example: ground snow load per local code)
STEPS:
1. Restate all inputs and flag anything missing.
2. Calculate hook count and spacing from the spec table I gave, showing the math.
3. Write step-by-step crew instructions.
4. List items requiring engineer or inspector sign-off.
RULES:
- Use only the facts I give you. If something is missing, ask or mark it NEEDED. Never invent prices, names or promises.
- Plain, friendly language a customer or crew member understands.
OUTPUT FORMAT: Inputs check, calculations, crew steps, sign-off list. Mark it DRAFT.
FOLLOW-UPS TO TRY NEXT:
- Make a materials list from this.
- Write a sanitized example version I can share publicly with no client data.