Supplier delivery reviews become unreliable when teams mix order promises, carrier events, warehouse receipts, inspection results, and later explanations in one percentage. A useful corporate gift supplier OTIF scorecard starts with a stable purchase-order line, keeps the original promise visible, records approved changes, and calculates on-time and in-full results separately before combining them. This guide provides that method, four localized workbooks, and two hypothetical cases for procurement and fulfillment teams.
Download the 2027 OTIF scorecard workbook
Download the English OTIF scorecard workbook. Version 1.0 is dated October 23, 2026. It contains Read Me, Input Lines, Exceptions, Scorecard, and Methodology Sources worksheets. The companion English CSV data dictionary defines every input and calculated field. Localized workbooks are also available for Traditional Chinese, Japanese, and Korean.
The workbooks contain hypothetical rows, not customer results or market benchmarks. All formulas were recalculated and tested against partial delivery, late receipt, approved and unapproved date revisions, rejected units, missing evidence, exclusions, duplicate line identifiers, and a blank denominator. Every worksheet was rendered and inspected, including CJK font checks. A correct score can still be unsuitable for a contract if the buyer has not agreed on the event, time zone, tolerance, and population being measured.
Define the decision before choosing the formula
OTIF is a service measure, not a complete supplier verdict. The Association for Supply Chain Management describes on-time in-full as whether the full order is received by the desired date. That concise idea still leaves operating choices. Does “received” mean carrier handoff, arrival at a booked site, warehouse scan, or acceptance after inspection? Is the denominator an order, shipment, schedule, or line? Does an approved buyer-requested postponement replace the original promise? Which cancellations are legitimately outside the population?
Write the decision statement first. A practical example is: “Measure each supplier’s ability to deliver every accepted unit for each eligible corporate gift purchase-order line by the buyer-controlled receipt deadline during the observation period.” This statement names the unit, outcome, clock, population, and period. It prevents a warehouse measure from being presented as a recipient-experience measure and prevents a shipment event from masquerading as quality acceptance.
Use OTIF with adjacent controls. The supplier continuity guide covers capacity failure, substitutes, and recovery. The campaign closeout workbook reconciles orders, claims, inventory, and credits after execution. This workbook has a narrower job: compare a promised line with documented receipt and accepted quantity. It does not rank security, price, product choice, sustainability, or the recipient experience.
Assign owners before measurement. Procurement owns the contractual promise and approved changes. Receiving owns the timestamp and quantity received. Quality or the authorized acceptance owner controls accepted and rejected quantity. The analyst applies the versioned method without changing outcomes to make a supplier look better. The business sponsor decides how the result affects sourcing, remediation, or a future program. Legal, tax, privacy, and finance retain decisions within their own remits.
Build one auditable line from source evidence
The minimum useful record is not “Supplier A was late.” It is a stable line identifier linked to its supplier, original promised date, any revised promised date, the approval for that change, required quantity, accepted quantity, receipt timestamp, eligibility decision, exclusion reason, and evidence location. The GS1 receiving advice specification distinguishes received from received-and-accepted line quantities. Oracle Procurement documentation separately identifies promised date, ordered quantity, received quantity, accepted quantity, and rejected quantity. SAP goods-receipt documentation likewise treats goods receipt as a controlled purchasing event. These sources support careful field separation; they do not impose one universal corporate-gifting formula.
| Field | Operational meaning | Owner and failure rule |
|---|---|---|
| Purchase-order line ID | Stable grain for the measured commitment | Procurement; blanks or duplicates stop use |
| Original promised date | First agreed delivery promise | Procurement; never overwrite it |
| Revised promised date | Later promise accepted by the buyer | Use only with a dated approval ID |
| Required quantity | Units required for that measured line | Buyer record controls the value |
| Accepted quantity | Units accepted after applicable inspection | Rejected units remain outside acceptance |
| Receipt timestamp | Buyer-controlled event selected by the method | Missing evidence produces a missing result |
| Eligibility and reason | Whether the line belongs in the denominator | Exclusion needs a documented rule and owner |
Preserve source identity. A screenshot without a stable order or receipt reference is difficult to reproduce. A mutable dashboard link can change after the review. Keep the authorized system record and record only the minimum evidence reference needed in the shared workbook. Recipient names, addresses, and other personal data rarely belong in a supplier scorecard. Use controlled identifiers and keep sensitive detail in the approved system.
Reconcile one-to-many relationships before scoring. If a line is delivered in two lots, decide whether the promise applies to the full line or to separately agreed schedules. Do not copy the full required quantity onto both receipts. Either aggregate receipts to the promised line using an explicit cutoff or establish stable schedule-level lines before the observation period. The same rule must apply to every supplier in the comparison.
Calculate on-time, in-full, and combined OTIF separately
The supplied workbook follows a transparent line method. The effective promise is the revised date only when an approved change ID exists; otherwise it is the original date. An eligible line is on time when the receipt timestamp is on or before the effective promise. It is in full when accepted quantity is at least required quantity. It passes OTIF only when both flags equal one.
| Result | Numerator | Denominator | Why it remains separate |
|---|---|---|---|
| On-time rate | Eligible lines with an on-time flag of one | Eligible lines with sufficient timing evidence | Reveals schedule performance |
| In-full rate | Eligible lines with an in-full flag of one | Eligible lines with sufficient quantity evidence | Reveals shortage or rejection performance |
| OTIF rate | Eligible lines passing both tests | Eligible lines with both results | Shows the combined service outcome |
Do not convert missing evidence to zero without a policy decision, and do not convert it to success. “Missing” tells the reviewer that the score cannot yet be determined. “Not applicable” means a documented rule removed the line from the denominator. A zero flag means the evidence is sufficient and the line failed. These states have different remedies.
The scorecard displays not applicable when no eligible line exists. Reporting zero would imply failure; reporting 100% would imply perfect service. Both would be invented. For a small population, always show the line count with the rate. A supplier with one passing line and a supplier with one hundred passing lines can both show 100%, yet they provide very different evidence about repeatability.
Avoid a universal tolerance hidden in a formula. If a contract permits a one-day window or a quantity tolerance, document the source, effective date, units, and scope. Version the method, test the boundary, and avoid comparing the tolerant series with a strict series as if they were identical. A visible method change is preferable to a retroactive formula edit.
Control promise changes and exception decisions
Late promises are easy to erase when a revised date replaces the original field. The workbook prevents that pattern by retaining both dates and requiring an approved change identifier before using the revision. Approval should show who accepted the change, when it was accepted, which line it affects, and why. A supplier email announcing a delay is evidence of the supplier’s statement; it is not automatically buyer approval.
Decision panel: which clock should control?
Use the buyer-defined event in the signed commercial and operating method. Carrier handoff may fit a term based on shipment. Warehouse arrival may fit a delivery commitment. Accepted quantity may require a later inspection event. If teams disagree, keep the line disputed, record both evidence paths, name the owner of the interpretation, and set a resolution date. Do not choose the event that produces the preferred score.
Exceptions need a stable ID, affected line, issue type, observation date, owner, evidence reference, decision, approver where required, resolution date, and notes. “Supplier says weather” is not a complete exception. The team must decide whether the contract recognizes the event, whether the evidence covers the affected line and period, and whether the line stays in the denominator. The event can still matter operationally even when it does not excuse performance.
Apply exclusions consistently. Buyer cancellation before production may be outside a supplier-delivery denominator if that rule was established in advance. A rejected shipment is not outside the denominator merely because it complicates the calculation. A missing receipt should not be excluded simply because the supplier cannot locate proof. Monitor exclusion count and reason by supplier; a rising exclusion share can make a seemingly stable rate less representative.
Hypothetical case A: 500 kits in two approved lots
Assume a corporate event needs 500 gift kits. The supplier and buyer approve two delivery lots before the original deadline. The first lot is accepted on time. Across both lots, receiving accepts 490 units and rejects 10 damaged kits. This is an illustrative scenario, not customer evidence.
Procurement first records the original promise and the two approved schedule references. Receiving records arrival against the buyer-defined clock. Quality records 490 accepted and 10 rejected; it does not type 500 accepted merely because 500 cartons arrived. The analyst calculates the promised line or approved schedule lines according to the method selected before review.
If the measured unit remains one 500-unit line, the line can be on time but not in full: on-time flag one, in-full flag zero, OTIF flag zero. If the parties established two independent schedule lines, each schedule is scored against its own required and accepted quantities. The choice affects the denominator and must not be changed after seeing the result.
The immediate alternatives are replacement, credit, conditional acceptance, or a documented no-replacement outcome. Replacement may preserve the event requirement but needs remaining time, inspection capacity, and a receiving window. Credit can address a commercial amount but does not create usable kits. Conditional acceptance may be appropriate only when the authorized quality owner confirms the units meet the agreed specification. Procurement and operations should preserve the failure, action, owner, due date, and final evidence.
Acceptance checks are concrete: the hand calculation and workbook agree; the approval IDs are retrievable; received, rejected, and accepted quantities reconcile; the 10 rejected units do not disappear; and the exception has an owner. If any source is missing, the line remains unresolved rather than being forced to pass.
Hypothetical case B: early shipment misses the booked site window
Assume a seasonal supplier ships early. The carrier arrives when the event site cannot receive freight, so the shipment is returned and reaches the authorized receiving point after the required window. The supplier argues that early carrier handoff proves on-time performance. Operations argues that the contract measures receipt at the booked site. This is another illustrative scenario.
The analyst records both events but uses neither by instinct. Procurement retrieves the agreed delivery term and the dated site-booking instruction. Operations supplies the appointment and return evidence. The supplier can submit its dispatch record. The method owner determines the controlling clock under the documented agreement, not under a later preference.
If site receipt controls, the line fails on time even though dispatch was early. If shipment handoff controls, it may pass timing while still creating an operational exception. If the governing language is genuinely ambiguous, the correct current score is disputed. Assign a decision owner, preserve the original values, and record the resolution before comparing suppliers or applying a remedy.
Alternatives carry different tradeoffs. A second attempt may protect the event but creates more handling, emissions, and duplicate-delivery risk. A local substitute can shorten recovery but may change specification, cost, or brand approval. A digital recipient choice may preserve recognition while changing the approved experience. A no-send decision requires the business owner’s authorization and must not be inferred from a failed appointment.
Accept the recovery only when the recipient or site outcome, cost decision, inventory disposition, and performance classification all have evidence. Closing the carrier ticket is not the same as completing the gifting obligation. The business-continuity plan should consume the incident and test whether the fallback actually worked.
Compare suppliers without hiding population differences
Compare like with like. Use the same observation window, eligibility rules, line grain, clock, time zone, and acceptance definition. Show eligible line count and missing-evidence count beside every rate. Segment only when the segment changes the operating promise: for example, custom production versus stocked goods, domestic versus cross-border delivery, or event appointments versus ordinary warehouse receipt.
Do not create a weighted composite unless the decision owner can explain every weight and the component measures have aligned populations. A 95% OTIF rate does not compensate automatically for missing privacy evidence, unsuitable products, or unacceptable total cost. Keep supplier qualification and price normalization in their respective processes. Use OTIF as one governed service signal.
Investigate the pattern behind the miss. On-time failures with strong in-full results may point to capacity planning, booking, or transport. In-full failures with strong timing may indicate quality rejection, pick accuracy, shortage, or specification ambiguity. Combined misses may require a recovery plan rather than a rate discussion. Avoid attributing cause until the evidence supports it.
Small denominators need narrative. One failure among four lines is 75%; ten failures among forty lines is also 75%. The second population offers more observations but can include a different mix. Report counts, not just percentages, and retain a short reason distribution. Never publish a supplier league table from populations that use materially different promises.
Run workbook acceptance and recovery tests
Before operational use, replace the hypothetical rows in a controlled copy and test the formulas with known outcomes. Confirm a zero accepted quantity is a valid zero, not a blank. Remove a receipt timestamp and confirm the timing result becomes missing. Add a duplicate line identifier and confirm both affected rows are flagged. Enter a revised promise without an approval ID and confirm the original promise remains effective.
Use this acceptance checklist:
-
Confirm the population reconciles to the authorized purchase-order control.
-
Confirm every included row has a stable line identifier and supplier.
-
Confirm original promises remain visible after any revision.
-
Confirm approved changes are dated and scoped to the correct line.
-
Confirm accepted quantity excludes rejected units.
-
Confirm the receipt event and time zone match the method.
-
Confirm exclusions have reasons, owners, and evidence.
-
Confirm blank denominators display not applicable.
-
Confirm formula error scans return no unexpected errors.
-
Confirm each exception has a next action and review date.
If a test fails, repair the source or method before using the rate. A status change is not a data repair. Preserve the previous version when formulas, fields, or eligibility rules change. Recalculate the affected period and mark the break in series. Do not overwrite a signed historical scorecard with a later method.
For recurring use, refresh at least quarterly and after a material supplier, contract, receiving, system, or formula change. That cadence is an operating recommendation, not a statutory retention requirement. The buyer’s records owner determines retention and access. Keep only the minimum evidence references needed for the decision.
Turn the score into a controlled supplier conversation
Send the supplier the measured population, method version, line-level exceptions, and evidence cutoff before the review. Allow a bounded correction window for wrong identifiers or missing records. A supplier should not be able to replace the buyer’s source silently, but it should be able to point to a specific approval or receipt that the buyer omitted.
Separate correction, interpretation, and remedy. A correction changes a demonstrably wrong input. An interpretation resolves which documented rule applies. A remedy addresses the operational or commercial outcome. Record each separately so that a negotiated credit does not rewrite the historical performance result and a data correction is not presented as supplier forgiveness.
The meeting should end with named actions. Examples include supplying an approval record, reconciling accepted quantity, revising a booking procedure, adding a fallback location, or testing a substitute. Each action needs an owner, due date, evidence of completion, and acceptance criterion. “Improve OTIF” is not an executable action.
Keep the scorecard reversible until review closes. Analysts should be able to trace every percentage back to lines and every line back to source evidence. If the source cannot be retrieved, mark the evidence gap. A polished dashboard cannot compensate for an unrepeatable result.
Use OTIF to improve gifting operations, not to replace judgment
A defensible OTIF scorecard makes promise changes, rejected units, missing evidence, and exclusions visible. It gives procurement and fulfillment teams a shared line-level record, exposes whether a miss is about time or quantity, and preserves a recovery path. Its value comes from consistent definitions and retrievable evidence, not from a universal target.
The next decision may be corrective action, a fallback supplier, a different receiving design, or no sourcing change at all. Make that decision with price, quality, capacity, risk, recipient needs, and authorized business constraints beside the service result. Keep human owners accountable for approvals and exceptions.
Giftpack can support a scoped global gifting and fulfillment workflow after the organization defines its recipients, policy, supplier requirements, evidence, and exception ownership. It does not replace procurement, legal, tax, privacy, payroll, finance, or employer decisions. Use the workbook to define the operating evidence a gifting partner must be able to support before commitment.