SANJIESAN LICENSING / Multi-partner coordination
Two production partners should still point to one master revision
One supplier names a file by its print job number, while another uses a sample-round code. Both may be working from the same approved visual. Keep a small cross-reference table so the project team can identify that relationship without forcing either supplier to abandon its own operational records.
Record the three references without merging them
For a hypothetical two-supplier project, give each row the project artwork revision, supplier name or internal reference, and that supplier’s file or job identifier. Keep actual confidential identifiers inside the controlled project record. Add the reference render the supplier is expected to match. An unfamiliar local filename should trigger a lookup, not an assumption that the supplier has created a newly approved visual version.
Route changes through the master decision
When one supplier requests an adaptation, identify whether it is specific to that process or changes the shared artwork. Put the question against the relevant master revision and follow the project’s review authority. Do not copy a process-specific workaround into the other supplier’s files automatically. The second supplier may use a different method and need a different production question answered.
Check each partner’s next file independently
After a decision, update the cross-reference and ask each affected partner to identify the file it will use next. Compare its output with the appropriate reference, preserving any process-specific exception. Keep acknowledgements separate for both partners. A response from one should not be recorded as confirmation from the other, even when the project manager sent both requests in the same message.