Found a weak card, missing answer, or site issue?
TinnerFlow™ gets better when field people point out what did not help. Use this page for missing Field Rescue cards, wrong wording, weak safety notes, beta questions, and site bugs.
Not for emergency job approval
If the work is unsafe, unclear, structural, life-safety related, energized, rigging-related, tied to fire/smoke/grease systems, or outside your training, stop and ask your foreman, safety lead, superintendent, manufacturer, or the approved project authority. TinnerFlow is a field education and communication aid, not jobsite permission.
No / missing button
Inside Field Rescue, use No / missing when a result does not answer the problem. That click helps identify weak cards faster than a long message.
Best when the card exists but missed the mark.
Email a correction
Send correction notes to feedback@tinnerflow.com. Include the search term, result title, what was wrong, and what an apprentice should verify first.
Best when safety wording, trade language, or search aliases need cleanup.
Submit a field problem
Use the field problem page when the site does not cover the situation at all. Raw submissions are reviewed before anything becomes a public route.
What to include when reporting a correction
- The page URL or search phrase you used.
- The Field Rescue card title, if you know it.
- What felt missing, wrong, too vague, or unsafe.
- The jobsite condition: deck, ceiling grid, roof, shaft, lift, curb, corridor, mechanical room, etc.
- The first thing a foreman would make an apprentice verify.
- Any slang or typo someone might search.
- Approved source language if you have it.
- No customer names, private drawings, exact jobsite addresses, coworker names, or sensitive info.
Current email routes
Use feedback@tinnerflow.com for wrong or missing Field Rescue cards, contact@tinnerflow.com for general site questions, and beta@tinnerflow.com for beta/access notes. All three are routed and active.
Good reports turn into cleaner cards
The goal is not to let random internet comments publish automatically. The goal is to collect real field gaps, strip out noise/private details, and turn useful patterns into safer Field Rescue cards, cleaner search aliases, and better foreman questions.
TinnerFlow™