Prepare pharmaceutical supplier ESG evidence for the actual manufacturing route
A pharmaceutical shipment can leave the same packing site twice and still have visited another contractor in between. An active pharmaceutical ingredient (API) invoice can name a distributor while the material was made and milled elsewhere. Those relationships matter when a customer asks which operations its supplier evidence actually covers.
This guide helps procurement, supplier-quality and reporting teams reconstruct an existing manufacturing route before requesting site evidence. The fictional case produces a route with one unresolved API origin and a newly visible packing contractor. It assesses no real supplier and makes no manufacturing, release, GMP or regulatory-compliance decision.
Fix the delivered lots and the selected operations
Every organisation, site, product, record and date below is invented. Buyer Nera requests the sites used for API synthesis, final API milling, tablet manufacture and packaging for delivered lots T31 and T32 of placeholder product AX. It also requests existing environmental records for those operations during May–June 2026. AX is not a real medicine or a process recommendation.
The exercise starts with controlled extracts supplied by the responsible owners. Product suitability, route authorisation and the decision to perform the recorded work are outside this review. The selected question excludes manufacture of ingredients other than the selected API, packaging-material production, transport and storage performance. These exclusions describe Nera’s narrow request; they do not establish a full supply-chain or product-footprint boundary.
PSCI’s Principles v3.0 address supplying locations, traceability of raw-material sources, environmental practices and documentation. They provide industry context for following a route beyond the invoice entity. The schedule below is an original preparation aid, not a PSCI audit or a finding that a supplier meets those expectations.
Separate the seller from the places doing the work
Distributor Vale invoices both API lots A81 and A82. Its invoice identifies warehouse W as the dispatch address. The warehouse receipt and onward-delivery records confirm storage and shipment from W. Neither record claims that synthesis or milling took place there. Vale is retained as the commercial contact, and W as a logistics location.
For A81, origin extract O81 identifies synthesis at Site S operated by Oren. Finishing record M81 identifies final milling at Site M operated by Lumen. Transfer and receipt references link A81 from S to M, then through W to contract manufacturer Corin’s Site F. Issue extract F31 connects that received lot exclusively to tablet lot T31.
For A82, M82 confirms milling at the same M, and the transfer and F32 issue records connect it through W to T32 at F. Its synthesis-origin extract is absent. A supplier master file lists S and U as possible synthesis sites but does not assign A82 to either. The route therefore starts with an unresolved synthesis location, followed by confirmed M, W and F.
Do not copy S from A81 or select U because it is the other listed site. Nor should W become the origin simply because it appears on the invoice. Request the controlled A82-to-synthesis-site relationship and its supporting reference. Until it arrives, the pack supports a partial route for A82, not a complete list of its manufacturing locations.
Follow the packaging return journey
Corin’s completed-operation extracts C31 and C32 identify F as the tablet-manufacturing site for T31 and T32. Packing records P31 and P32 then identify Site P, operated by Packwell, for primary packing and outer cartoning of both lots. The material-to-lot and lot-to-packing links are stipulated as complete; no formulation details or yield calculations are needed here.
T31 is dispatched from P to Nera. T32 follows an additional documented sequence: P sends it to Site R, operated by Rebox, for outer-carton replacement; R returns the same identified lot to P; P then dispatches it to Nera. Records PR32, RR32 and RP32 preserve the T32 reference at each step. The supplied work description expressly excludes opening or changing the primary packs.
P’s final dispatch does not erase R’s completed activity. Record P and R against different packaging operations, with R applying only to T32. This is a reading of the stipulated records, not a conclusion that outer-carton work has a particular regulatory classification. The reviewer neither approves the work nor infers why it was needed.
The selected-operation routes are now A81/T31: synthesis S, milling M, tablet manufacture F, packaging P; and A82/T32: synthesis unresolved, milling M, tablet manufacture F, packaging P, outer-carton replacement R, return to P for dispatch. Keep W visible in the movement history without assigning it an unsupported manufacturing role.
Attach each environmental file to the operation it covers
Oren supplies environmental schedule ES for S’s synthesis operations during May–June. Its stated scope matches that known operation for A81. Keep the document’s actual measures, methods and limitations with it. ES cannot be assigned to A82 while its origin remains unresolved, even if the distributor says that S is normally used.
Lumen supplies file EM headed with its company name. The scope note identifies its administrative office H and explicitly excludes milling Site M. EM remains an office record. The next request names M and the recorded milling activity, rather than asking Lumen to resend a file bearing its corporate name.
Corin supplies EF for the whole F campus, including tablet manufacture and shared support areas, for the requested period. That is a potentially relevant site record with a wider operational boundary. Preserve that boundary; EF contains no T31/T32 assignment and this guide creates none. A route link identifies where to seek evidence, not how much campus activity belongs to a product.
Packwell’s EP covers P’s packing operations for the period. It expressly excludes work performed by other businesses. Rebox’s R is consequently a separate evidence request; EP cannot answer it through Packwell’s contract or final dispatch address. No R environmental record is supplied in the initial pack.
The resulting gaps have different causes. A82 lacks a synthesis-site identity; M has a document for the wrong location; R has a known activity but no supplied environmental file. F has a wider site record whose boundary must stay visible. Calling every row “supplier information pending” would conceal what each owner actually needs to resolve.
Close the missing relationship before extending coverage
Consider a separate follow-up state. Vale supplies controlled extract O82 identifying U, operated by Ulen, as A82’s synthesis site and linking it to the existing M82 record. This closes the origin question for A82. It does not supply U’s environmental evidence, change the confirmed downstream route or extend ES from S to U.
Add U to the named site request and keep O82 beside the route. M and R remain open for their existing reasons. If O82 instead identified S, the reviewer would recheck ES against that operation and period before linking it to both lots. Either outcome changes a specific relationship; neither justifies marking the entire supplier response complete.
Hand over a route that another reader can reproduce
Use one row per lot, operation and actual site. Retain the operating business, commercial contact, dated movement or completed-operation reference, environmental-file boundary and exact unresolved link. The same M, F or P file can be referenced from both lots without creating a second assessment. Treat return visits as events, rather than silently creating a new site identity.
For the initial pack, ask a second reader to explain why S is confirmed only for A81, why W is not assigned synthesis, why R appears only for T32, and why EM does not cover M. The reader should reach those answers from the named records without relying on supplier reputation or a summary slide.
Before sharing a real route, obtain permission for the actual recipient and the proposed extracts. A controlled site-and-operation confirmation may be sufficient without disclosing formulations or unrelated customers. If restrictions prevent establishing the requested link, preserve the limitation and agree an acceptable evidence route rather than substituting an unqualified confirmation.
The supplier questionnaire guide covers the broader response process, while the confidential evidence guide addresses controlled disclosure. This case concentrates on reconstructing the physical operations behind those requests.
For a scoped review, contact Nitium Advisory. Start with a non-confidential description of the delivered lots, known operations and missing relationship.
Source and limits
PSCI Principles v3.0 (2023), pages 1–2 and 9: supplying locations, traceability, documentation and environment.
Primary source checked 14 October 2026. The case and documentary relationships are original teaching material. No actual site, route or environmental result was assessed. Legal conclusions, quality qualification, technical process advice, certification, supplier ratings and independent assurance are outside this resource.
Comments