How do you prepare an industrial quarterly business review?

This method is for supplier technical or account staff reviewing a quarter of technical support with a manufacturing customer: visits, trials, complaints and changes. It does not cover software usage reviews, price or contract negotiation, or a formal customer satisfaction survey run under ISO 10004:2018, which are separate processes.

What do you need before preparing a quarterly business review for an industrial customer?

Before preparing a quarterly business review for an industrial customer, you need five things fixed in writing: the customer and sites, the quarter's start and end dates, the scope of support covered, the named readers, and the line between what stays internal and what the customer sees. Fixing these first decides which records you read and which you skip.

• Customer and sites: name each plant or line in scope. A review that mixes two plants hides which one improved.

• Period: the exact dates, for example 2026-07-01 to 2026-09-30 (illustrative). Records outside the dates stay out, even when they help the story.

• Scope: which product lines, applications or open cases the review covers.

• Readers: the customer's plant manager, maintenance lead or purchasing contact read for different decisions. Write down who receives the review and what each one decides.

• Disclosure boundary: list the internal items that will not appear, such as opportunity notes, pricing and margin.

Ask also for the customer's own supplier scorecard. Automotive customers score suppliers on their own terms: General Motors requires a Sourceability Level of 3, 4 or 5 (GM Customer Specific Requirements, October 2025). A review that ignores the customer's measure argues on ground the customer does not use.

How do you prepare an industrial quarterly business review step by step?

You prepare an industrial quarterly business review in five steps, each producing one part of the document, and you finish each step before starting the next.

1. Fix scope and readers. Record customer, sites, period, scope, readers and the disclosure boundary from the previous section in the first lines of the working file.

2. Gather records. Pull visit reports, trial results, complaint files, customer emails and lab results dated inside the period. Note any area where no record exists, rather than filling it from memory.

3. Separate proven results. For each activity, decide whether a before and after measurement on the customer's line exists. Put measured effects in a results list and the rest in an activity list marked unproven.

4. List open risks. Write each unresolved issue as a separate item: what could go wrong, where, and what evidence shows it is still open. Keep this list apart from results.

5. Assign follow-ups. Give every action one owner, one due date and the side, customer or supplier, that carries it out.

A published customer success guide also advises that follow-ups "Clearly define who is responsible for each follow-up action and set realistic deadlines" (Velaris, 2024). Its guide is built on software metrics such as product usage and health scores (Velaris, 2024); on an industrial line, the matching evidence is a measured process value, a complaint count or a test result.

How do you separate proven results from activity in an industrial quarterly business review?

You separate proven results from activity in an industrial quarterly business review by asking one question of each item: is there a measurement on the customer's line, under comparable conditions, before and after the change? An item with that pair is a result. An item without it is activity, however much work it took.

A visit, a trial or a training session is activity. A result names the measure, the unit, the two values and their source, for example: tool changes on line 2 fell from 14 to 9 per week after the coolant concentration was reset (illustrative). Each result should say who measured it and where the record sits, so the customer can check it.

Two readings do not prove much on their own. The NIST/SEMATECH e-Handbook treats "Do two processes have the same mean?" as a test on random samples of measurements from two processes (NIST/SEMATECH e-Handbook). One reading before and one after cannot carry that test, so write the effect with its limits: one shift, one line, one week.

Mark activity honestly instead of dropping it. A list titled "Activities, effect not yet measured" tells the customer what was done and what proof is still missing, and it becomes next quarter's measurement plan.

How do you show remaining risks and follow-up actions in a quarterly business review?

You show remaining risks and follow-up actions in a quarterly business review as two separate lists after the results, so the customer does not read an open problem as solved. Each risk names the issue, the place, the evidence that it is still open, and the action that addresses it.

Risk management guidance treats risk as something to identify, analyze, evaluate, treat, monitor and communicate (ISO 31000:2018). A quarterly business review covers the last two of those for the customer: what is being monitored and what is being told. A risk written as "foaming on line 3 recurred twice in September, root cause not confirmed" is open; putting it under results because a defoamer trial started would mislead.

Follow-up actions then take the form of a short table or list with four fields:

• Action, written as one verb and one object.

• Owner, one named person, not a department.

• Due date in YYYY-MM-DD.

• Side: customer or supplier. A sampling task on the customer's line belongs to whoever takes the sample, which is often the customer even when the supplier asked for it; write that side down.

Link each follow-up to the risk or unproven activity it closes. An action with no link is a wish, and an open risk with no action is a decision the customer has to see and accept.

How do you keep internal sales notes out of a customer quarterly business review?

You keep internal sales notes out of a customer quarterly business review by writing the internal and customer versions from the same records, with the disclosure boundary fixed before drafting, then checking the customer version line by line before sending. Internal notes include opportunity size, win probability, pricing strategy, margin, competitor remarks and judgments about the customer's people.

The risk comes from reuse. The account team often prepares an internal review first, with opportunity notes beside each activity, and then cuts it down for the customer. Comments in slides, hidden rows in spreadsheets and speaker notes survive that cut more often than body text.

Three habits reduce the risk:

• Keep internal notes in a separate file or section that never enters the customer draft.

• Export the customer version to PDF and read the export, not the editing file, before sending.

• Ask a second person who knows the boundary to check the export against the boundary list.

In Lubinpla, the account technical support status task fixes the customer, period, scope, recipients and the internal versus customer disclosure boundary before it reads any records, then bundles activities, effects, remaining risks and follow-ups into one report, leaving internal opportunity judgments out of the customer version.

How do you check a quarterly business review before it goes to the customer?

You check a quarterly business review before it goes to the customer by running seven checks on the customer version: scope, results, activity, risks, follow-ups, internal notes and numbers. A review that fails any check goes back to the step that produced the failing part.

The table below decides whether the quarterly business review is ready to send to the industrial customer.

The results row decides most reviews: a result without a before value is activity, and moving it to the activity list keeps the review defensible when the customer's engineer checks it.

Run the checks on the exported file, the one that will be sent, rather than on the editing file. Comments, hidden rows and speaker notes can disappear from view in the editor and still travel with the file. Ask a second reader who did not write the review to run them as well, since the author tends to read what was meant rather than what is on the page. Record who ran the checks and the date in the internal file, so the next quarter's review starts from the same standard and the same boundary list.

Quarterly business review mistakes with industrial customers

Quarterly business review mistakes with industrial customers come from writing for the supplier's story instead of the customer's decisions. Five recur:

• Activity as results. A list of 12 visits reads as effort; the customer's engineer asks what changed on the line (illustrative count).

• Scope drift. Records from outside the quarter, or from another plant, make the trend look better and cannot be checked against the customer's own data.

• Risks buried in results. A problem described as "under trial" in the results list is read as fixed, and the customer is surprised when it returns.

• Department owners. "Supplier quality" as an owner means no one owns it; the action rolls into the next review.

• Leaked internal notes. A margin figure in a speaker note or a hidden spreadsheet row damages the relationship more than any result helps it.

Customer satisfaction is a measured input under quality management standards: ISO 9001:2026 keeps clause 9.1.2 Customer satisfaction (ISO, 2026), and automotive suppliers carry the supplemental clause 9.1.2.1 (IATF 16949:2016). A quarterly business review that the customer can check line by line feeds that measure; one that cannot be checked turns into a sales meeting.