Supplier code acknowledgment tracker

What does the supplier code acknowledgment tracker produce?

Track exact supplier code versions, recipients, dispatch and reported acceptance evidence.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define the authorized source population and your review rules.
• Keep the unchanged original files and record the snapshot and exclusions.
• Review missing and invalid inputs before preparing the finalized pack.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Workflow review reference. Customer-controlled reference.
• Review version. Customer-controlled version.
• Review owner. Responsible customer owner.
• Review date. YYYY-MM-DD. Your observation date, not an inferred statutory deadline.
• Selected population and scope. State the actual selected population and your boundaries.
• Supplier code versions and reported acceptance. Structured task-specific rows. Original imported JSON strings remain exact until a row is edited.
• Actual reported workflow transitions. Unique event ID, item/version, exact offset timestamp, from/to states, actor, reason and actual source-file IDs.
• Your expected requirements. Unique requirement ID, version, item scope, title, approver/date and actual source-file IDs. Missing expected requirements remain visible.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the supplier code acknowledgment tracker work?

1. 1
   Define the selected workflow

   Workflow review reference. Customer-controlled reference.

2. 2
   Freeze the review rules

   Bind the supplier/recipient to the required code version. Distribution requires actual dispatch evidence and date. Reported acceptance requires its actual record and date. Missing your requirements remain explicit. No signature or contractual acceptance is authenticated.

3. 3
   Inspect complete findings

   Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.

4. 4
   Keep recoverable work

   Exact source bytes and original input strings save locally. A validated backup replaces current work only after source hashes and history pass. The prior checkpoint and all earlier generic work remain separately downloadable.

5. 5
   Prepare the finalized pack

   Prepare seven core files and the exact selected attachments, then download them free. Review the fictional sample below.

How do you run a supplier code acknowledgment campaign?

A supplier code of conduct helps only when you can show which suppliers received which version and what each one sent back. This tracker keeps that chain in one ledger. Each row names the supplier, the person who received the code, the code reference and version, the dispatch record and the acceptance record with its date.

A typical cycle

1. Add one row for every supplier in the campaign with the stage Required. Use your own supplier IDs so the ledger lines up with your vendor master file.
2. When you send the code, move the row to Distributed. Add the dispatch reference, such as an email message ID or a supplier portal notice ID, and the date you sent it.
3. When the supplier replies, move the row to Acceptance reported. Record where the reply is kept, for example a signed PDF, a portal click-through log or a return email, and the date on it.
4. After someone on your team has checked the reply against the right code version, move the row to Reviewed.

Gaps the ledger brings to the surface

• An acceptance dated before the code was sent. This usually means the reply belongs to an earlier campaign or an older version.
• A row linked to a requirement ID, version or scope that does not match exactly one requirement you approved, such as a version 2 row in a version 3 campaign.
• An approved requirement with no supplier rows at all, which shows a supplier group was left out.
• Suppliers that have not reached Reviewed by your target date, listed as overdue rather than silently dropped.

When you issue a new code version

Add new rows for the new version instead of editing the old ones. The earlier acceptance stays on record for the period it covered, and the new rows start again at Required. When someone later asks what a supplier had agreed to on a given date, the answer is still in the file.

What a reported acceptance does not prove

The tracker does not confirm that the person who replied could bind the supplier, and it does not check a signature. It also cannot tell you whether a supplier actually follows the code. Treat a reported acceptance as a record of what you received. Supplier audits, questionnaires and site visits remain separate work.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• PROV-DM. The PROV Data ModelDomain-independent relationships among source entities, actual reported activities and responsible agents. This modeling reference supplies no legal requirements or approval authority. Section 2.1 modeling overview and Sections 5.1 through 5.3 describing entity, activity and agent relationships.World Wide Web Consortium. Reviewed 2026-10-09.
• Date and Time on the Internet. TimestampsExact timestamp and UTC-offset syntax. The supported subset uses seconds and confirmed offsets, without leap seconds or unknown local offsets. It supplies no legal clocks or deadlines. Section 4 local offsets and Section 5.6 the Internet date/time format, used only for exact reported chronology.Internet Engineering Task Force. Reviewed 2026-10-09.

Common questions

What still needs review?

This ledger records your supplied facts, decisions, evidence and selected requirements. It does not authenticate consent, signatures, authority, completion, legal applicability or population completeness. It does not send, file, approve, execute a provider operation or change an external system. Exact inputs and files stay in this browser. Original files are not saved to the cloud.

At most 200 rows per task table, 20000 characters per answer, 20 local source files, 10 MB per file and 25 MB total. Formal reports show the first 100 findings with explicitly bounded previews. Complete Excel, CSV and JSON retain every accepted finding.

Exact timestamps use confirmed UTC offsets and seconds. Date-only row fields use your review-date boundary. No legal duration, approval power or business calendar is inferred.

Customer transitions describe actual reported activity. Browser-observed save events are separate, bounded local observations that do not authenticate a rewritten history.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all vendors and supply chain tools.

• Supply-chain entity mapLink suppliers, facilities, intermediaries and supplied products. Try a free example. Review your inputs and result. No account or payment required.
• Country and facility evidence registerPreserve reported origins and supporting documents. Try a free example, then review your inputs and the result. No account or payment required.
• Forced-labor due diligence preparationOrganize traceability, sources and unresolved risks. Try a free example, then review your inputs and the result. No account or payment required.
• UFLPA evidence-pack organizerStructure relevant supplier and shipment records. Try a free example, then review your inputs and the result. No account or payment required.
• Modern slavery statement preparationDraft only from verified actions and conclusions. Try a free example, then review your inputs and the result. No account or payment required.