1---2name: draft-standard-contractual-clauses-addendum3task_id: data-privacy-cybersecurity/draft-standard-contractual-clauses-addendum4description: SCC addendum drafts fail when the agent selects the wrong SCC module for the controller-processor relationship, does not populate the Annexes from the engagement documents, and omits any separate UK transfer instrument when both EU and UK personal data are in scope.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-standard-contractual-clauses-addendum8---910# Skill: Draft Standard Contractual Clauses Addendum for Cross-Border Data Processing Agreement1112## 1. Subject-matter triage13- Confirm the deliverable is a drafting task, not a pure review: produce the SCC addendum first, then the client cover memo.14- Identify whether the engagement includes EU/EEA data, UK data, or both; if both are in scope, plan for a separate UK transfer instrument in addition to the SCC addendum.15- Determine the legal role alignment from the DPA, MSA, and related engagement materials before selecting any clause set.1617## 2. Failure modes the skill is correcting18- Drafting the wrong SCC module because the party roles were not confirmed from the source agreements.19- Leaving Annexes as generic placeholders instead of translating the engagement record into populated transfer terms.20- Treating security language as descriptive rather than contractual, so the final annexes do not bind specific safeguards.21- Omitting a UK transfer addendum when UK personal data is also transferred.22- Failing to reconcile the SCC package with the DPA, leaving duplication, inconsistency, or silent conflict.23- Ignoring transfer-risk findings and therefore omitting supplementary contractual commitments where needed.24- Writing the cover memo as a narrative summary only, without explaining the drafting choices, alternatives considered, and remaining open items.2526## 3. Legal frameworks / domain conventions that apply27- Use the applicable SCC structure for cross-border personal data transfers under the EU transfer framework, with the module determined by the exporter/importer relationship.28- If the data transfer assessment indicates non-adequate destination law or access-risk concerns, incorporate supplementary contractual and technical commitments consistent with the transfer framework and the assessment findings.29- If UK personal data is in scope, use the applicable UK transfer addendum or equivalent UK transfer mechanism as a separate instrument alongside the SCCs.30- Treat the DPA as the baseline processing agreement; the SCC addendum supplements it and should avoid inconsistency with the DPA’s scope, definitions, and operational terms.31- Populate Annex I with the parties, roles, transfer description, categories of data, data subjects, purposes, frequency, processing period, and supervisory authority information drawn from the engagement documents.32- Populate Annex II with concrete technical and organizational measures, stated as obligations rather than generic security aspirations.33- Populate Annex III with the authorized subprocessors, their locations, the work they perform, and any associated safeguards or transfer mechanism.34- Use the governing transfer text and the DPA together as the legal frame; where the addendum addresses the same topic more specifically, ensure the documents are coordinated rather than duplicative.3536## 4. Analytical scaffolds37- Start by mapping the processing chain: exporter, importer, controller/processor roles, transfer direction, and the data sets covered.38- Read the DPA, MSA, SOW, security summary, subprocessor list, and transfer-impact assessment as a single package; do not draft from one document in isolation.39- Confirm whether the SCC package needs one module or more than one transfer instrument based on the documented role structure; if only one relationship applies, say so in the memo and explain why.40- Translate security controls into enforceable drafting: specify access controls, encryption, incident handling, logging, segregation, backup, and onward-transfer constraints as applicable to the record.41- Translate the transfer-impact analysis into drafting choices: if supplementary measures are needed, state them as commitments, restrictions, or operational conditions in the addendum package.42- Populate every annex from the source record; if a requested item is missing, flag it as an open item rather than inventing a placeholder.43- For the cover memo, explain the module selection, the basis for any optional or supplemental clauses, how UK data is handled, how transfer-risk findings are reflected, and what remains to be confirmed.4445## 5. Vertical / structural / temporal relationships46- The SCC addendum supplements the DPA and should be drafted to sit downstream of, and consistent with, the existing processing framework.47- If the SCC addendum and the DPA overlap, the addendum should control only for the transfer-specific terms within its scope; the DPA should continue to govern the broader processing relationship.48- A UK transfer addendum is a separate instrument that cross-references the SCC package; it does not replace the EU/EEA transfer clauses.49- Annex content should track the actual processing lifecycle: what data is transferred, for what purposes, for how long, by whom, and under what safeguards.5051## 6. Output structure conventions52- Prepare two deliverables: an SCC addendum package and a client cover memo.53- Draft the SCC addendum as an operative contract form with the selected transfer clause set, any required supplemental provisions, and fully populated annexes.54- If UK personal data is in scope, include the UK transfer addendum as a distinct document or distinct attachment within the package, clearly tied to the main SCC addendum.55- Write the cover memo as an advisory document that explains: why the clause set was selected, what assumptions were made, what optional provisions were included or omitted, how the transfer-risk analysis was addressed, and which items still need client confirmation.56- Use conventional legal drafting headings and annex structure; do not copy an internal checklist or placeholder-heavy format.57- Deliverable filenames must match the instructions exactly: `scc-addendum.docx` and `client-cover-memo.docx`.58- Before finishing, confirm that `scc-addendum.docx` exists and contains operative contractual text, and that `client-cover-memo.docx` exists and contains substantive drafting guidance.