{"description":"Runs on the existing requirement item. Deliver the control, policy and process changes an obligation requires, validate readiness evidence, and approve the adoption record. Deliver the reviewed result and open actions to the responsible register owner and the named companion procedure.","edges":[{"id":"e-adoption-scope-adoption-closure","source":"adoption-scope","target":"adoption-closure"}],"isPublic":true,"itemTypeSlug":"requirement","metadata":{"capabilities":["obligation-implementation-adoption"],"controlVerbs":{"UC-GOV-03":"operates"},"controls":["UC-GOV-03"],"department":"compliance-legal","domains":["reg"],"kind":"obligation-implementation-adoption","library":{"aliases":[{"source":"studio-seed","sourceTemplateId":"coworkcanvas:template:obligation-implementation-adoption"}],"canonicalUrl":"https://workflow-library.com/all/?w=reg-requirement-implementation-adoption","contentDigest":"sha256:f22940cd7b33f0b669501991899fdb2549bcd7b42a044b520bde26f1c98fd3b9","prerequisites":{"anchorItemType":{"slug":"requirement"},"evidenceDestinations":[{"description":"Restricted native step results, attached documents, durable item fields and native approvals.","id":"review-evidence"}],"handoffs":[{"direction":"output","name":"Reviewed register result and open actions","sourceTemplateId":"workflow-library:reg-obligation-implementation"}],"roles":[{"contribution":"expertise","description":"Legal or regulatory specialist. Confirm implementation scope and readiness date.","id":"reviewer-1","nodeIds":["adoption-scope"]},{"contribution":"approval","description":"Compliance owner. Approve adoption record.","id":"reviewer-2","nodeIds":["adoption-closure"]}],"status":"declared"},"provenance":[{"source":"brain/scripts/studio-seed","sourceTemplateId":"coworkcanvas:template:obligation-implementation-adoption"}],"releaseId":"sha256:f22940cd7b33f0b669501991899fdb2549bcd7b42a044b520bde26f1c98fd3b9","schemaVersion":1,"sourceTemplateId":"workflow-library:reg-requirement-implementation-adoption"},"lineOfDefense":"monitor","mappingStatus":"mapped","risks":[],"slug":"reg-requirement-implementation-adoption","source":"coworkcanvas-gallery","standards":[],"teams":["compliance-legal"]},"name":"Obligation Implementation & Adoption","nodes":[{"data":{"instructions":"**Objective**\nConfirm implementation scope and readiness date. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Review the Requirement item, the approved impact assessment, gap inventory, affected controls, policies, processes and systems, delivery capacity, dependency and change calendars, and the obligation effective date.\n\n**Procedure**\n1. Convert each gap into a deliverable with an owner and date, sequence work against dependencies and freeze periods, reconcile the readiness date against the effective date, and escalate where capacity cannot meet the deadline.\n\n**Record in AssureSwarm**\n1. Capture the target readiness date, implementation scope and deliverables, owners, sequence and dependencies, capacity constraints, freeze-period conflicts, and escalations raised.\n\n**Exit criteria**\nLegal or regulatory specialist provides expertise: Every gap has a deliverable, an owner, and a date; the readiness date reconciles to the effective date or the shortfall is escalated rather than hidden.","kind":"task","label":"Confirm implementation scope and readiness date","requiredApprovals":1},"id":"adoption-scope"},{"data":{"controls":["UC-GOV-03"],"instructions":"**Objective**\nApprove adoption record. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Use the implementation scope and deliverable list, control and policy drafts, process narratives, system change records, training and communication plans, approval routes, and the change and release calendar.\n2. Use the obligation text and clause-level requirements, the change inventory and its evidence, control operation evidence since the change, policy publication records, training completion, and the original gap inventory.\n3. Review all stage records, the deliverable list and its execution evidence, deviations, clause-by-clause validation, residual gaps, blockers, and representations relied upon.\n\n**Procedure**\n1. Execute each deliverable through its normal approval route, record deviations from plan with reasons, keep superseded versions traceable, confirm communication and training reached affected roles, and surface blockers rather than silently deferring them.\n2. Test each clause against delivered evidence rather than intent, inspect operating evidence where the obligation requires operation, distinguish documented from operating readiness, and refuse to close clauses supported only by representation.\n3. Trace the readiness conclusion to inspected evidence, verify residual gaps carry owners and dates, confirm the implementation status to record matches the validated position, and return overstated readiness with precise comments.\n\n**Record in AssureSwarm**\n1. Document the change inventory with before-and-after references, execution status per deliverable, deviations from plan, approval records, communication and training evidence, and blockers with owners.\n2. Record the readiness conclusion, clause-by-clause validation with evidence references, residual gaps with owners and target dates, representations relied upon, and clauses that could not be validated.\n3. Capture the authorized reviewer, the adoption summary, accepted readiness conclusion, implementation status to record, adoption effective date, residual gaps, monitoring handover, owners, and due dates.\n\n**Exit criteria**\nCompliance owner provides approval: Delivered changes are traceable to approved deliverables, deviations are reasoned, and blocked work is visible with an owner rather than absorbed into the next stage. An approver accepts that the readiness conclusion follows from inspected evidence, residual gaps are owned and dated, and unvalidated clauses are declared rather than presumed satisfied. The authorized reviewer accepts the adoption as a traceable record of implementation work, monitoring can take over against a stated position, and closure implies no assurance beyond the clauses actually validated.","kind":"task","label":"Approve adoption record","requiredApprovals":1},"id":"adoption-closure"}],"sourceTemplateId":"workflow-library:reg-requirement-implementation-adoption"}