Checking data at each hand-off before an error reaches the next department

Every hand-off is a control point, not just a message

Order A is confirmed between Northline Apparel and Delta Garments: 15,000 T-shirts in single jersey, 180 GSM, Ne 30/1. Delta Garments buys the greige fabric from Rowad Knits, the knitting mill, which then hands the fabric-ready information to Delta's planning team before dyeing and cutting begin. When one department or company sends information to another, the receiver normally does something with it: planning reserves capacity, sourcing buys materials, production schedules work, quality prepares inspection. If the incoming information is wrong, the next team can do the wrong job correctly.

That is why the hand-off itself must be treated as a control point, not simply a delivery of a message. The receiver's task is not only to confirm that something arrived. The stronger habit is to confirm that the right information arrived, from the right source, in a usable form, early enough to act on safely.

The practical rule in this lesson is simple: before accepting a hand-off, check completeness, validity, consistency and timing. If one critical field fails, stop, return or escalate the hand-off before downstream work begins.

You need the first three lessons from this course

Before this lesson, you should understand three ideas:

• every important data item needs a clear owner;
• the team should keep one approved current version;
• reusable master data is different from order-specific transaction data.

By the end of this lesson you can:

• identify a hand-off between two roles, departments or companies;
• decide which fields are critical before the receiver acts;
• check whether each field is complete, valid, consistent and timely;
• distinguish a missing field from a conflicting field;
• accept, reject or escalate a hand-off with a clear reason;
• record the result in the course worksheet.

Not covered here: a specific software system. The same control works in email, spreadsheets, shared drives, workflow tools, ERP, PLM or a paper-based operation.

Use these terms when you review a hand-off

A field can pass one test and fail another. For example, a quantity may be present, so it is complete, but it can still conflict with the approved buyer purchase order, so it is inconsistent.

Accept a hand-off only when the receiver can safely act on the critical information

A good hand-off has three parts: a sender who knows what is being sent, a receiver who knows what must be checked, and an approved source that proves the critical values. The receiver does not need to re-audit the whole business. The receiver needs to verify the fields that matter before the next action begins.

The check should happen at the boundary between activities. Mill to factory is one boundary. Merchandising to sourcing is another. Planning to production is another. Quality to shipping is another. Rowad Knits may hand fabric-ready confirmation to Delta Garments' planning team, planning may hand a cutting instruction to production, and quality may hand release information to dispatch.

If the receiver notices a conflict after work has already started, the cost of correction is usually higher because more people, materials or time are already involved.

The same four checks work across different business situations

The control is not tied to a particular company size or software. It depends on the decision that the receiver is about to make.

Rowad Knits hands off Order A fabric data, and Delta Garments stops one conflicting field before cutting

Rowad Knits, the knitting mill, is producing the greige fabric for Order A: 15,000 T-shirts in single jersey, 180 GSM, Ne 30/1, for the export order confirmed with Northline Apparel. Rowad Knits' planning team sends a fabric-ready hand-off to Delta Garments' planning team ahead of cutting. Commercial and technical information arrives through a mix of controlled records, spreadsheets and messages.

The hand-off contains the fabric quantity, construction, GSM and timing. Most fields are present. One field, however, does not match the current approved specification: the GSM figure quoted does not match the controlled tech pack. The planner at Delta Garments could continue and tell production that the field will be confirmed later. That would keep the schedule moving, but it would also allow a known conflict to enter the next department.

The correct action is to stop the hand-off on that critical field, identify the approved source, and return or escalate the exception. Planning should not create a downstream cutting instruction from information it already knows is inconsistent.

This does not mean every small typo stops the business. The team should define which fields are critical to the next action. A harmless note-format issue may be corrected locally. A field that changes material, quantity, construction, colour, finish, timing, price, compliance or shipment instruction needs controlled correction.

Correct arithmetic cannot rescue a wrong input

Use Order A as the approved calculation example. Order A contains 15,000 T-shirts. The approved fabric consumption is 0.205 kg per piece including 7% marker wastage.

The multiplication is straightforward. Imagine instead that the quantity handed to Rowad Knits' fabric-planning team came from an old, unapproved source. The team could calculate perfectly and still plan the wrong fabric quantity because the input itself was wrong.

That is the key lesson: data quality comes before calculation quality. The receiver should confirm the critical input against its approved source before using it in a downstream calculation.

The same principle applies to commercial values. Order A uses USD 3.20 per piece, so the approved example is:

Again, a correct formula produces a wrong business answer if either quantity or unit price came from the wrong version.

Use six steps at every important hand-off

1. Name the sender and receiver. Write who is giving the information and who will act on it. A vague hand-off with no clear receiver is difficult to control.
2. Identify the critical fields and their approved sources. Do not try to check everything equally. Focus first on the fields that can change the receiver's decision or work.
3. Check completeness. Confirm that required values, documents and approvals are present. A blank critical field means the hand-off is not ready.
4. Check validity. Confirm that the value is allowed and usable. Dates, units, codes, status values and formats should follow the agreed rule.
5. Check consistency. Compare the value with the approved source and with related fields. A field can be present and valid-looking but still conflict with the approved specification, PO or current revision.
6. Check timing, then decide. If the information is too late for safe action, record the exception. Accept the hand-off only when the receiver can proceed safely; otherwise reject, return or escalate it.

Record the outcome in the data-quality worksheet. The purpose is traceability: what failed, who owns the correction, and what action was taken.

A common mistake is treating "filled in" as "correct"

Teams often perform a visual completeness check: every cell contains something, so the hand-off is accepted. This is weak control. A complete-looking row can contain an old date, an invalid code, a conflicting specification or a late approval.

Another trap is accepting a known conflict because "production can fix it later." That moves the problem to a more expensive stage. Once material is ordered, capacity is reserved, a machine is set or documents are prepared, correction becomes harder.

The hand-off check should therefore happen before the receiver commits resources or sends the information further downstream.

• A hand-off is a control point between sender and receiver.
• Complete means all required information is present.
• Valid means the value follows the allowed rule or format.
• Consistent means it agrees with the approved source and related fields.
• Timely means it arrives early enough for the receiver to act safely.
• A filled field can still be wrong.
• Correct arithmetic can still produce the wrong business answer if the input is wrong.
• Critical conflicts should be stopped before downstream work begins.
• Accept, reject, return or escalate with a clear reason.

Planning receives a complete-looking hand-off with one conflicting fabric field

Delta Garments' planning team receives the fabric-ready hand-off for Order A from Rowad Knits through the normal hybrid workflow. The mill has sent the fabric quantity, construction, GSM and timing. Nothing is blank. The planner compares the GSM field with the currently approved tech pack and finds that it does not match.

The cutting schedule is tight. Someone suggests that planning should continue, release the cutting instruction and confirm the GSM figure later so no time is lost. Everyone in the room agrees the mismatch is probably a typing error, but nobody has actually called Rowad Knits to check.

Decide what the planner should do before opening the answer.

The correct decision protects speed rather than slowing it. It prevents the schedule from being built on information that may later force rework.

Add one hand-off row to the T17-C01 worksheet

Use the course workbook and record:

Do this for one real or practice hand-off, starting with the Rowad Knits to Delta Garments fabric example. The worksheet should make the decision visible, not create extra narrative.

[Download the Data ownership and data quality workbook](../../templates/T17-C01-data-ownership-data-quality.xlsx)

Download the Data ownership worksheet (Excel)

Lesson 1.5: Building a data ownership and data-quality worksheet for a live order

Next you will combine ownership, approved versions, master and transaction data, and hand-off checks in one working worksheet. Back to the course map