Field notes / TORCH JOURNAL
Before the next handoff, capture the reason why
Five questions that help preserve the experience behind a repair, change, or recurring field problem.
Start with work someone will have to repeat
Pick a recent repair, tricky setup, or recurring question. A focused conversation about a real job is easier to reuse than a broad request to explain everything an experienced person knows.
Ask five useful questions
What was the problem, and what conditions mattered? Record enough detail to distinguish this job from one that only looks similar.
What did you try, and why did you choose that approach? Keep the reasoning, including approaches that did not work.
What source or approved procedure governed the work? Link the explanation to the applicable material.
What would make the answer different next time? Capture the limits and exceptions as carefully as the successful result.
Who should review this before another crew relies on it? Identify the person responsible for checking the explanation and keeping it current.
Keep the source with the summary
A short summary is useful, but the original explanation can carry details that a summary leaves out. Preserve the contributor, date, site context, and supporting records with the captured knowledge. Get permission before recording or sharing someone’s contribution.
Make the next question easier to answer
File the result under the question another crew would ask. Test it with someone who was not there: can they find it, understand its limits, and see where the information came from?
That is a practical starting point for getting Jack up to speed during a scoped deployment.
Put your crew’s knowledge to work.
Talk to Torch Labs about a paid 30-day deployment scoped to your team.