When to Use Field Cards, Solutions, or Tasks

Use these signals to choose between a Task, a Field Card, and a Solution.

Rules of Thumb

Use a Task When

• The job has a set sequence that must be followed step by step.
• Results must be recorded: readings, as-found and as-left values, pass/fail, or photos.
• Someone must sign off, approve, or witness the work.
• A report or record is needed for audit, quality, safety, or the customer.
• The diagnosis branches, and the path taken should be recorded.
• It's a guided choice, such as parts selection or a product release decision.
• It's a repeating route, like rounds, readings, PM, or lubrication.
• It's training that needs completion tracking, quizzes, or a qualification sign-off.
• The procedure is long, high-risk, or done rarely enough that people need guiding.
• A Field Card on the same topic is used often in Ask. Promote it.

Use a Field Card When

• It's reference knowledge that Ask should find, but nothing needs to be recorded.
• Photos or diagrams are needed to explain it.
• It's a simple, single job — swap, clean, refill, reset — done without sign-off.
• It covers one fault with several causes, ordered by how often they were seen.
• It holds values to look up: settings, torques, wiring, alarm codes, or part numbers.
• It shows what something looks like or where it is.
• The content is still Field-derived and needs its values confirmed before it becomes a Task.

Use a Solution When

• It's a single symptom with a single fix.
• The fix can be described in a few lines of text.
• No photos are needed.
• It came from a log entry or ticket, and doesn't justify a card.
• It's a one-off or rare case worth keeping, but not worth a full write-up.
• It should be visible in the app for Technicians to browse.