How to Write a Sourcing Diary When the Root Cause Is Still Unknown

Executive introduction

A reported sourcing problem can create pressure for an immediate explanation. A late shipment may be attributed to production planning, a damaged item to packaging, or an unexpected specification to supplier error. Yet the first plausible explanation is not necessarily the established root cause.

During issue investigation, the sourcing diary should slow that transition from problem to conclusion. Its purpose is to record what was reported, what has been checked, what the available evidence supports, what remains unresolved, and what should happen next. It should not assign responsibility merely because information is missing or because one explanation appears likely.

This approach is consistent with the ISO 9001 guidance on documented information, which distinguishes information maintained to support processes from information retained as evidence of results. The same guidance recognizes that the extent of documented information can vary according to the organization and its circumstances; it does not impose one universal diary format (ISO 9001:2015 documented-information guidance).

A well-written diary therefore preserves the investigation trail without pretending that uncertainty has already been resolved.

1. Set the diary’s purpose during issue investigation

Separate five types of entry

The most important writing discipline is to classify information before using it.

Category	Definition for the diary	Appropriate wording	Avoid
Confirmed fact	A statement directly supported by an identified record, observation, or other retrievable evidence	“The reviewed record states…”	“This proves the supplier caused…”
Open question	A material point that cannot yet be answered from the available evidence	“It remains unclear whether…”	Filling the gap with an assumption
Working hypothesis	A possible explanation that is being tested	“One possibility to examine is…”	Presenting a possibility as the root cause
Reported statement	Information attributed to its source but not independently verified	“The message reports that…”	Treating the report as proof of the underlying event
Decision	An action selected on the basis of the information currently available	“Pending verification, the next action is…”	Claiming that the decision settles the cause

A message can confirm that someone made a report. It does not automatically confirm that the reported event happened exactly as described. Similarly, the absence of a requested record establishes only that the record was unavailable for review at that point. It does not, by itself, prove that the underlying activity did or did not occur.

Apply a strict editorial rule

Attribute every important statement to an identifiable source. Include the relevant date or time reference when it is available, and distinguish between:

• The date of the event.
• The date shown on the source.
• The date the source was reviewed.
• The date the diary entry was created or updated.

Do not silently rewrite an earlier entry when new evidence appears. Add a dated correction, clarification, or status update. This preserves a readable trail showing what information was available at each stage of the investigation.

For example:

Earlier entry — 12 March: The received message reports that the inspection occurred before dispatch. The inspection record was not available for review.
Status update — 14 March: A record identified as the inspection record was received. Its relevance and completeness have not yet been verified.

The update does not erase the earlier uncertainty. It records how the evidence position changed.

2. Build the diary around facts, questions, and evidence

Start with a neutral issue statement

The opening statement should identify the affected item, process, or sourcing stage using confirmed identifiers only. It should also explain how the issue came to attention, the earliest supported time reference, and the immediate effect shown by available evidence.

Use this pattern:

On [date or time reference], [identified source] reported or recorded [neutral description]. The evidence currently reviewed confirms [supported point]. It does not yet establish [unresolved cause or responsibility].

Add an explicit investigation status:

Root-cause status: Not yet confirmed.

Avoid loading the opening statement with interpretations. “The received record shows a quantity difference” is narrower and more defensible than “the supplier shipped the wrong quantity because production controls failed.”

Create a dated evidence trail

For every meaningful development, record:

1. Date recorded
2. Source reviewed
3. What the source directly shows
4. What it does not establish
5. Related open question
6. Next verification action
7. Status or follow-up date

Prefer precise verbs:

• States
• Records
• Shows
• Was observed
• Was not available for review
• Has not yet been verified

Avoid unsupported causal or absolute language:

• Caused
• Proves
• Confirms responsibility
• Always happens
• Could only have occurred because

The verb matters. “The image shows visible damage” describes the image. “The image proves the factory caused the damage” adds a causal conclusion that the image may not support.

Separate observation from interpretation

A useful diary entry has three parts.

Observation

Record only what can be traced to the evidence. Identify the type of source, such as:

• Document or business record.
• Email or other communication.
• Image.
• Physical observation.
• Applicable external guidance.

Write:

The reviewed message states that the cartons were intact when dispatched.

Do not write:

The cartons were definitely intact when dispatched.

The first sentence attributes the statement. The second presents the statement as independently established.

Interpretation boundary

Explain what cannot yet be concluded. Make contradictory information visible, and record any limitation affecting relevance, reliability, or completeness.

For example:

The message provides one account of the carton condition. No dispatch image or other independently reviewed record was available at the time of this entry. The condition at dispatch therefore remains unverified.

A conflict should also remain visible:

The dispatch message reports no visible carton damage. The receiving note records visible damage on arrival. The available records do not establish when or where the damage occurred.

Investigation prompt

Convert the gap into one answerable question:

Were time-referenced dispatch images created for the affected shipment?

Then define what evidence could answer it:

Evidence needed: retrievable dispatch images linked to the confirmed shipment identifier, together with their available time reference.

Finally, assign an action:

Follow-up: Logistics role to request and verify the images before the next review date.

“Investigate further” is not enough. It does not identify the question, the required evidence, the action, or the review point.

Organize supporting documented information

The diary should make its sources identifiable and retrievable by authorized reviewers. It should also consider appropriate storage, access, preservation, protection from unintended alteration or loss, and retention when information is needed as evidence. These principles reflect the treatment of documented information in the ISO 9001:2015 guidance.

In practice, a diary entry may identify a source through a record title, reference number, controlled folder, communication thread, or another retrievable location appropriate to the organization. Avoid vague references such as “see files” or “supplier document.”

The diary and log presented here are practical editorial tools. They are not prescribed ISO forms.

Use an audit-minded review without turning the diary into an accusation

ISO 19011 provides guidance on auditing management systems, including managing audit programs, conducting audits, and considering auditor competence (ISO 19011). A buyer can borrow its traceability-minded approach without claiming to conduct a certification audit or using the diary to assign blame.

Before closing an entry, ask:

• Can another authorized reviewer trace each important statement to its source?
• Is the source relevant to the exact question being asked?
• Does the entry distinguish evidence from interpretation?
• Is contradictory information recorded rather than omitted?
• Has uncertainty been stated honestly?
• Are the source’s limitations visible?
• Would a later reviewer understand why the next action was selected?
• Has responsibility been left open where the evidence does not establish it?

The goal is disciplined review, not accusation.

Include product-safety questions where relevant

Some sourcing issues may raise a United States product-safety question. The U.S. Consumer Product Safety Commission’s Business and Manufacturing resources can be used as a starting point for identifying potentially relevant information.

Possible diary prompts include:

• Does the reported issue raise a product-safety question?
• Which CPSC business or manufacturing resource may be relevant?
• What product, process, inspection, or testing records are available for review?
• Does the team need qualified regulatory, product-safety, or legal review?
• Is an immediate protective action being considered separately from the unresolved root-cause investigation?

Consulting the CPSC page does not establish that CPSC requirements apply, and it does not demonstrate compliance. Applicability and compliance require case-specific evidence and appropriate qualified review.

3. Use an open-question and evidence log

The log turns uncertainty into controlled follow-up. Each row should connect an attributable statement to one focused question, the evidence required, and a defined next action.

Blank log template

Log ID	Date recorded	Confirmed fact or reported statement	Evidence source and location	Evidence status	Open question	Evidence needed	Follow-up action or owner role	Target review date	Outcome/status
[ID]	[Date]	[Neutral, attributable statement]	[Record title, identifier, or retrievable location]	[Available / incomplete / disputed / not yet received]	[One answerable question]	[Specific record, observation, or confirmation]	[Action and responsible role]	[Date]	[Open / answered / superseded]
[ID]	[Date]	[Neutral, attributable statement]	[Record title, identifier, or retrievable location]	[Available / incomplete / disputed / not yet received]	[One answerable question]	[Specific record, observation, or confirmation]	[Action and responsible role]	[Date]	[Open / answered / superseded]
[ID]	[Date]	[Neutral, attributable statement]	[Record title, identifier, or retrievable location]	[Available / incomplete / disputed / not yet received]	[One answerable question]	[Specific record, observation, or confirmation]	[Action and responsible role]	[Date]	[Open / answered / superseded]

How to complete each field

• Log ID: Create a stable reference so diary updates can point to the same question without changing its identity.
• Date recorded: State when the row was created or updated. Do not substitute an assumed event date.
• Confirmed fact or reported statement: Label the category clearly. Do not merge a report and an independently verified fact.
• Evidence source and location: Provide enough information for an authorized reviewer to retrieve the source.
• Evidence status: State whether the evidence is available, incomplete, disputed, or not yet received.
• Open question: Ask one focused question per row. Split combined questions into separate entries.
• Evidence needed: Define the specific record, observation, or confirmation that could answer the question.
• Follow-up action or owner role: Assign the action to an appropriate role without inventing a named person.
• Target review date: Set a review point so unresolved questions do not disappear into the diary.
• Outcome/status: Preserve the history when the question is answered, superseded, or found irrelevant.

When a question is answered, do not delete the row. Change its status and add the supporting source or a dated reference to the relevant update.

Evidence-handling checklist

• Every factual claim has an identifiable source.
• Reported statements are attributed and not presented as independently verified facts.
• Working hypotheses are visibly labeled.
• Missing records are described as unavailable or not yet reviewed.
• Conflicting evidence is recorded.
• The diary does not assign fault without sufficient support.
• Each material open question identifies the evidence needed.
• Each follow-up has an action, responsible role, and review point.
• Updates preserve the earlier investigation trail.
• Event dates and diary-recording dates are distinguished.
• Product-safety or regulatory questions are escalated for appropriate review where relevant.
• The diary states that the root cause remains open when it has not been established.

Suggested closing structure for each update

End every diary update under the same seven headings:

1. Confirmed since the previous entry
2. Still unconfirmed
3. New or revised questions
4. Evidence received or reviewed
5. Evidence still requested
6. Interim action taken
7. Next review point

An interim action may be necessary even while causation remains unresolved. Record the action and its basis without presenting it as proof of the root cause:

Pending verification, the identified role will hold the affected material for further review. This decision is precautionary and does not establish the cause or assign responsibility.

Sources

• ISO 9001:2015 — Guidance on the requirements for documented information
  Used for the treatment of documented information maintained to support processes and retained as evidence of results.

• ISO 19011 — Guidelines for auditing management systems
  Used for the audit-minded emphasis on traceable review, audit programs, conducting audits, and reviewer competence.

• U.S. Consumer Product Safety Commission — Business and Manufacturing
  Used to direct readers to CPSC business, manufacturing, and product-safety resources when an issue may have a United States product-safety dimension.

Scope and limits

This article addresses diary writing during issue investigation, before a root cause has been confirmed. It does not establish the cause of a real sourcing problem or provide evidence concerning any supplier, factory, product, shipment, price, test, certification, or compliance status.

It does not determine whether CPSC requirements apply to a particular product or event. It is not legal, regulatory, certification, or product-safety advice. Questions in those areas may require case-specific review by appropriately qualified roles.

The open-question and evidence log is a practical editorial template, not a form required by ISO or CPSC. ISO 19011 provides auditing guidance and should not be described as a product certification. Conclusions about responsibility, compliance, corrective action, or root cause must be supported by case-specific evidence and appropriate review.

Image credit

A sourcing diary should preserve what is known, what remains open, and which evidence must be checked next. Photo by Carolina Gonçalo on Unsplash, provided under the Unsplash License.

Final next move

Select the highest-priority unanswered question. Identify the specific evidence that could answer it, assign retrieval or verification to an appropriate role, and set the next review date. Do not choose the easiest question merely because its evidence is already available; prioritize according to the issue’s supported effects, urgency, and any relevant safety or regulatory considerations.

Close the current diary entry with:

Root-cause status: Not yet confirmed.
Next move: Obtain or verify [specific evidence] to answer [open question], then update the log without overwriting the current record.