Use the first call to determine whether the consultant can define your production problem, explain the proposed scope, and name the decision the work will support.
Ask for the Problem Statement
A useful proposal should state the production condition in observable terms. “Improve efficiency” is too broad; “understand why the first-piece approval repeatedly stops one machine family” gives the work a boundary.
Ask what is included, what is not included, and which information could change the scope. This makes proposals easier to compare without relying on a generic hourly rate.
Ask How the Work Will Be Observed
Some questions can begin with drawings, routings, programs, and production records. Others require live observation because the issue occurs during a setup, handoff, inspection wait, or schedule change.
Ask which conditions must be running during a visit and who should be available to explain the current method.
Ask What You Will Receive
The deliverable might be a decision record, a measured baseline, a prioritized loss list, a test plan, training material, or implementation support. The proposal should name it clearly.
Also ask how assumptions, missing data, and acceptance criteria will be documented so the team can use the result.
A Simple First-Call Scorecard
| Listen for | Why it matters |
|---|---|
| A specific production question | Keeps the work tied to an operating decision. |
| A clear observation plan | Shows how conclusions will be supported. |
| Named client responsibilities | Prevents missing access, records, or people from stalling the work. |
| A defined deliverable | Lets your team compare proposals on substance. |