Use a Field Survey to Scope Conveyor Guarding Work

A conveyor guarding proposal built only from old drawings looks fast but promises something you cannot actually deliver on the date printed on the page. As a technical sales engineer, you get pulled into this trap whenever a customer has an audit deadline and a set of drawings that predate years of maintenance changes on the plant floor. The fix is not to argue about the deadline. The fix is to explain, in terms tied to the audit itself, why a short field survey protects the schedule instead of threatening it.

Why This Conversation Goes Wrong

When a safety engineer calls with an audit date already on the calendar, pressure builds fast on both sides. The customer wants a number and a plan today. You want the deal to move. Old drawings look like the shortcut that solves both problems at once. But conveyors get modified constantly. An installer adds a takeup section. Maintenance relocates a pull cord station after a near miss. Operations swaps a drive package and never sends the change back to engineering. None of that shows up on a drawing issued years earlier.

If you quote from the drawings anyway, you are guessing at guard dimensions, access point locations, and interlock placement. Any gap between the quote and the real machine turns into a change order, a delay, or a design that fails the audit outright. The conversation goes wrong when either side treats the drawings as current fact rather than a starting point for the real scope.

How to Prepare

Before you get on the call, pull the drawing set and the equipment list side by side. Note the conveyor lines, their ages, and any line where you already know from service history that work has been done. Call your project or applications team and ask what a field survey actually requires, how many hours it takes per line, and who from the customer side needs to be present, usually a maintenance lead and someone from operations who knows the current guard status.

Get clear on the audit itself too. Ask what the auditor flagged, not just that an audit is coming. An observation about a specific access point or missing interlock tells you exactly where to focus the survey first. Write down two or three questions about existing safeguards and pinch points so you are not improvising on the call. If you already know a survey date that works for your team, offer it directly instead of promising to check and circle back later.

What to Say

Here is a short exchange between safety engineer Ella and technical sales engineer Marcus.

Ella says, "Can you quote this from the old drawings? Our audit date cannot move."

Marcus says, "I can use the drawings to build the first draft of the survey plan, but several of these conveyors may not match what is on paper anymore. What did the audit observation point to, and which access points or existing guards did it mention?"

Ella says, "An installer reworked three of the lines a couple of years back, and the auditor flagged a takeup point on line four that has no fixed guard."

Marcus says, "That helps a lot. I will compare the drawings against the equipment list and that audit note, then set up a short survey with your maintenance lead so we measure line four and the other reworked lines directly. Once we have real dimensions, your safety team can run the design through its own review before the audit date."

Ella says, "How long does a survey like this take, and can we still hit the date?"

Marcus says, "A survey like this usually takes a few hours per line with someone from maintenance walking it with us. If we schedule it this week, you still have enough time for your review and for fabrication after that. I will send two possible dates today and coordinate directly with your maintenance lead so you are not stuck waiting on emails back and forth."

Notice what Marcus does not do. He does not promise a number today, and he does not tell Ella that a quote from the drawings will satisfy the auditor. He ties every next step to the audit date instead of avoiding it, which keeps the deadline a planning fact rather than a pressure tactic.

Mistakes to Avoid

Do not quote a firm price or a guard design straight from old drawings just to end the call on a positive note. That number will not survive contact with the actual machine, and walking it back later costs you more credibility than a short delay up front.

Do not hand the audit date back to the customer as their problem alone. If you only say a survey is needed without naming a date, an owner, and a rough timeline, you have added a step without removing any of the anxiety that came with the deadline. Also avoid treating the survey as a formality you rush through. A field survey with no real measurements taken, done just to check a box, gives you the same bad data as the drawings did, and the audit finds the gap anyway.

Watch your tone as well. A safety engineer facing an audit is already under pressure from their own leadership. Explaining why the drawings are not enough should sound like problem solving, not like a lecture on process.

How to Practice and Score This

Roleplay this scenario with a fixed deadline already sitting on the calendar, since that pressure is what pushes people to skip the survey step. The person playing the sales engineer should acknowledge the date directly, ask a specific question about a physical access point or existing safeguard, and describe what evidence the survey will produce before the design goes anywhere.

Score the conversation on three points. First, did the engineer avoid quoting a design or a price from the drawings alone. Second, did the engineer name a specific next step, including who owns the survey and roughly when it happens. Third, did the close name who reviews the resulting design once the survey is done, so the customer knows the design does not move straight from field notes to fabrication without a check.

You can run this same drill through DealSpeak, where the AI counterpart holds the deadline pressure steady across several turns and scores whether your close actually protects the schedule instead of just sounding confident. For more scenarios built around this kind of technical back and forth, look at Manufacturing practice conversationsincluding Gather the Right Inputs for a CNC Coolant Filtration Reviewwhich covers a similar problem of collecting real data before committing to a scope, and Coordinate a Cooling Tower Startup Review Before the Warm Seasonwhich walks through the same kind of scheduling pressure tied to a seasonal deadline instead of an audit date.

Close

An old drawing is a starting point, not a guarantee. Treat the audit deadline as a shared planning fact, run the field survey with a named owner and date, and let the customer's engineering review confirm the design before anyone treats it as final. That sequence protects the project and the relationship more than any quote you could hand over on the first call.