Build a defensible impact and compliance file for one order
A buyer asks your factory for the evidence behind an order's environmental claims before it will approve the purchase order. You have four weeks and no budget for new testing.
Who this is for: Compliance, sustainability and merchandising staff who answer buyer questionnaires.
What you produce: An evidence file index: each claim, the document that supports it, who issued it, its date and its limits.
Nobody marks this for you. Write your own answer, compare it with the guidance under each task, then mark the capstone done when you are satisfied with it. Your writing is saved on this device, and to your account when you sign in.
Task 1
List the claims attached to this order — material origin, certification, energy, water, chemical compliance, labour — exactly as the buyer stated them.
What a good answer contains: A good answer quotes the buyer's wording rather than paraphrasing it, because the wording decides what evidence is needed.
0/1500 characters — saved when you click away.
Task 2
For each claim, name the document that would support it, who issues that document, and what it does not cover.
What a good answer contains: A good answer distinguishes a transaction certificate from a scope certificate, and a test report from a management-system certificate, and states the scope limit of each.
0/1500 characters — saved when you click away.
Task 3
Identify the claims you cannot evidence and write the message you would send the buyer.
What a good answer contains: A good answer says plainly what is not evidenced and offers a route — a test, a supplier declaration, or removing the claim — instead of implying coverage that does not exist.
0/1500 characters — saved when you click away.
Task 4
Write the data you would start collecting now so the same request takes days, not weeks, next season.
What a good answer contains: A good answer names specific records with an owner and a frequency: meter readings, chemical inventory updates, supplier certificate expiry dates, consumption per style.
0/1500 characters — saved when you click away.
0/4 tasks have a written answer