Sara, the buyer at Northline Apparel, does not sit inside Delta Garments' own systems, yet she depends on the factory's shared order record to be accurate: the ship date, the approved specification revision, and the production status she reports to her own management. If that record can be changed by anyone, at any time, with no trace of who made the change, Sara has no way to know whether the figure she is looking at is the one both sides actually agreed.
This lesson builds on Lesson 5.1's access rights by adding the second half of the control: an audit trail that records who changed a field, what it changed from and to, and when, so a change can always be checked later. Without this record, even a well-designed permission system cannot answer the buyer's most basic question after a disagreement: who actually made a given change, and on what authority.
You need: Lesson 5.1 on setting data responsibilities and access rights, plus a basic understanding of a shared order record and a purchase order.
By the end of this lesson you can:
Not covered here: software configuration or a specific ERP or PLM product. Lesson 5.1 covers setting up the access rights an audit trail then records changes against; this lesson stays vendor-neutral and focuses on the business rule first.
| Term | Meaning |
|---|---|
| Permission level | The specific set of actions, such as view, enter or approve, a role is allowed to perform on a record. |
| Audit trail | A record of who did what and when, kept so a decision or change can be checked and reviewed later. |
| Change log | A time-stamped list of each change made to a record, who made it and when. |
| Version history | The ordered record of every saved version of a file or record, showing what changed and when. |
| Access right | Permission that allows a specific role to view, enter or change a specific piece of business information. |
A permission level decides who is allowed to change a field. An audit trail records what actually happened every time someone used that permission. The two work together: the permission stops most unauthorised changes before they happen, and the audit trail proves, after the fact, exactly what changed, who changed it and when, for the changes that were made.
Without an audit trail, a permission system can still fail silently. A person with a legitimate change right can make an error, and nobody downstream can tell whether today's figure is the original one, a corrected one, or an unapproved one, because there is no record connecting the current value to its history.
| What can differ | The shapes you will meet | Why it matters to you |
|---|---|---|
| Export order under Make to Order | An export buyer and a factory in different countries share one order record but each works from their own copy or view of it. | Neither side can see the other's own internal file being edited, so the audit trail is the only shared proof of what changed and when. |
| Domestic order under Make to Stock | A domestic brand's own standing forecast is updated often by a small internal team inside one building. | Even inside one building, an audit trail still matters, because a frequent, routine update is exactly the kind of change that becomes hard to trace without one. |
| Hybrid order handled through an agent | An agent relaying a change between a factory and a buyer on a hybrid mix of order types needs the audit trail to show the change came from the buyer's own side, not from the agent's own judgement. | Without a trail, a factory cannot tell whether an agent is passing on an actual buyer instruction or acting on their own initiative. |
| A genuine correction versus an unexplained change | A correction to a typing error looks the same as an unauthorised change unless the entry states a reason and an approver. | An audit trail without a reason field still shows what changed, but a reason field lets a reviewer judge whether the change was legitimate without asking around. |
| Different product families | Socks, knit-to-garment, terry and bedding orders each have their own controlled fields, but every one needs the same audit-trail entry when a controlled field changes. | The fields differ; the need for a trace of who changed what and when does not. |
Northline Apparel and Delta Garments are working against Order A: 15,000 T-shirts, agreed FOB USD 3.20 per piece, required ship week 16. Sara logs into the shared order record and sees the ship date has moved from week 16 to week 17. She did not ask for this change and needs to know whether it is legitimate before she updates her own retail delivery plan.
Sara does not need edit access to Delta Garments' internal record to check this; she only needs to read the audit trail. The entry shows the field changed, the old value (week 16), the new value (week 17), who made the change (Karim, production manager), the date, and the reason recorded: a fabric delivery delay confirmed by Rowad Knits. Because Karim's role has the access right to change the production timeline field, and the change is fully recorded, Sara can accept the new date with a clear reason to report to her own team, rather than simply seeing a different number with no explanation.
If the audit trail had shown no entry for that field, or an entry with no name and no reason, Sara would have had to stop and query the change before trusting it, because an unexplained change to a shared record is not the same as a corrected one.
The worked numberOrder A's fixed 16-week timeline allocates 4 weeks to shipping after production and inspection are complete. If the ship date genuinely moves from week 16 to week 17 because of a confirmed 1-week fabric delay, and this is recorded and accepted, both sides plan around the new date. If the same 1-week slip happens but is never recorded anywhere Sara can see, she may only discover it when the goods do not arrive as expected.
A 1-week delay against Order A's total order value of USD 48,000 (15,000 × USD 3.20) is not itself a cost in the calculation; the cost is what an unrecorded 1-week delay does downstream — a missed retail delivery slot, an unplanned air-freight decision, or a late markdown into the selling season — none of which Sara can plan for if she only learns about the delay after it has already happened.
That habit works fine until the day a field shows a value neither side remembers agreeing to. Without an audit trail, there is no way to tell whether the value was corrected, changed by mistake, or changed by someone without the right to do so, and the two sides are left arguing about which memory of the conversation is correct instead of checking a recorded fact.
The better rule is simple: treat the audit trail, not just the current value, as the real record of what happened to a shared field, and check it whenever a figure changes without an explanation you already know.
A permission level is like a rule about who is allowed to write in a shared notebook. An audit trail is like a stamp next to every entry, showing whose handwriting it is and when it was written. The rule alone tells you who is allowed to write; the stamp tells you what they actually wrote and when they wrote it.
When you see a number change in a shared record, do not just accept the new number. Look for its stamp: who changed it, what it changed from, and why. If the stamp is missing, treat the change as unconfirmed until someone can explain it.
While preparing her own costing check, Sara opens the shared order record for Order A and notices the FOB field shows USD 3.15 instead of the agreed USD 3.20. She checks the audit trail for the price field and finds no entry recording any change: the field's history shows only the original confirmed value of USD 3.20.
Should Sara treat USD 3.15 as the new agreed price for her costing check? Decide before opening the answer.
No. Sara treats USD 3.20 as the current confirmed price and raises the discrepancy with Delta Garments before using either figure.
1. The audit trail is the proof of a legitimate change, and it shows none for this field. A field that shows a different value with no audit-trail entry is not evidence of a real price change; it is evidence of a data problem that needs investigating. 2. No written amendment exists, and merchandising is the only role permitted to change this field, so there is no approved path by which USD 3.15 could be the new confirmed price. 3. Using USD 3.15 in a costing check would embed an unverified figure into Sara's own commercial planning, which is a larger error to unwind later than pausing now to ask Delta Garments to explain the discrepancy.
The audit trail turns "which number do I trust" into a checkable question rather than a guess: if there is no recorded, approved change, the last confirmed value stands until one is shown.
Order A's fixed profit is USD 0.26 per piece, or USD 3,900 total on the order (15,000 × 0.26).
A single untraceable field change rarely wipes out this profit by itself. Its real cost is time and trust: hours spent by both sides trying to reconstruct what happened from memory and email threads, a delayed decision while the discrepancy is investigated, and a weakened level of confidence in the shared record itself, which then makes every future figure from that record slower to act on. An audit trail turns that investigation from a memory exercise into a two-minute check of a recorded fact.
Use the T17-C05 Data governance decision tool workbook. In the Change log sheet, record each change to a controlled field: the date, the field, the old and new value, who changed it and who approved it. Use it to check Order A's own ship-date and price fields, then apply the same sheet to a shared record you use with a buyer or supplier.
[Download the Data governance decision tool workbook](../../templates/T17-C05-data-governance-decision-tool.xlsx)
1. Why does Sara accept Order A's ship-date change from week 16 to week 17, but not the FOB field showing USD 3.15?
2. Order B (3,000 jeans, required ship week 22) shows an audit-trail entry: field 'ship week', old value 22, new value 23, changed by 'Karim, production manager', reason 'washing delay confirmed by Cairo Wash Works'. What should a buyer reviewing this entry conclude?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Permission level | مستوى الصلاحية | Niveau d'autorisation | Yetki seviyesi | The specific set of actions, such as view, enter or approve, a role is allowed to perform on a record. |
| Audit trail | سجل التدقيق | Piste d'audit | Denetim izi | A record of who did what and when, kept so a decision or change can be checked and reviewed later. |
| Change log | سجل التغييرات | Journal des modifications | Değişiklik kaydı | A time-stamped list of each change made to a record, who made it and when. |
| Version history | سجل الإصدارات | Historique des versions | Sürüm geçmişi | The ordered record of every saved version of a file or record, showing what changed and when. |
| Access right | حق الوصول | Droit d'accès | Erişim hakkı | Permission that allows a specific role to view, enter or change a specific piece of business information. |
Next you will learn to recognise the signs that a working spreadsheet has outgrown its own controls, using a domestic stock programme's own growing order book as the case. Back to the course map