{"description":"Policy Exception & Risk Acceptance as a decision-aware workflow. It carries a waiver from request and justification through risk assessment, compensating controls, time-bound approval, registration with expiry, and re-review so no exception outlives its rationale. The exception IS an Issue item (issue_type: policy_exception) — the workflow runs on it, and the exception register is simply the set of those Issues, queryable by their filterable exception_expiry_date. The affected policy is a Policy item the Issue links to; a granted acceptance also sets treatment: accept on the linked Risk item. In scope: time-bound exceptions/waivers to an existing policy that are risk-accepted for a bounded window. Out of scope: permanent policy-change proposals, which route to the Policy Lifecycle Management workflow (the Policy item's revision process) rather than this waiver workflow. No upstream or downstream workflow feeds or consumes this one; the exception request is the initial input, and recurring-exception patterns are compiled as feedback onto the affected Policy items at close.","edges":[{"id":"e-assess-and-package-route-for-approval","source":"assess-and-package","target":"route-for-approval"},{"id":"e-route-for-approval-register-and-implement","label":"Approved","source":"route-for-approval","target":"register-and-implement","whenValue":"approved_time_bound"},{"id":"e-route-for-approval-monitor-to-expiry","label":"Rejected","source":"route-for-approval","target":"monitor-to-expiry","whenValue":"rejected"},{"id":"e-route-for-approval-committee-review","label":"Escalated","source":"route-for-approval","target":"committee-review","whenValue":"escalated"},{"id":"e-committee-review-register-and-implement-time-bound","label":"Accepted time-bound","source":"committee-review","target":"register-and-implement","whenValue":"accepted_time_bound"},{"id":"e-committee-review-register-and-implement-conditions","label":"Accepted with conditions","source":"committee-review","target":"register-and-implement","whenValue":"accepted_with_conditions"},{"id":"e-committee-review-monitor-to-expiry","label":"Rejected","source":"committee-review","target":"monitor-to-expiry","whenValue":"rejected"},{"id":"e-register-and-implement-monitor-to-expiry","source":"register-and-implement","target":"monitor-to-expiry"}],"isPublic":true,"itemTypeSlug":"issue","metadata":{"capabilities":["policy-exception-risk-acceptance"],"controlVerbs":{},"controls":["UC-ASSET-10","UC-RISK-09","UC-RISK-08","UC-AUDIT-17"],"department":"risk-management","domains":["grc"],"formRespondents":{"assess-and-package":{"missingInputs":"The policy clause that cannot be met and why, the compliant alternative considered and rejected, the cost and timeline of full compliance, the in-scope and out-of-scope boundary, the requested end date and the remediation milestone it is tied to","nonExecuting":true,"role":"Business exception requestor outside every executing and approving role; the accountable sponsor is resolved from the exception ownership record"}},"kind":"policy-exception-risk-acceptance","library":{"aliases":[{"source":"studio-seed","sourceTemplateId":"coworkcanvas:template:policy-exception-risk-acceptance"}],"canonicalUrl":"https://evidenceflows.com/workflows/all/?w=grc-policy-exception-risk-acceptance","contentDigest":"sha256:479bf2c2088fc4cc37edf5c06bf7f37fb8d193809232a5e926ca354bb14fcc07","prerequisites":{"anchorItemType":{"slug":"issue"},"evidenceDestinations":[{"description":"The exception Issue (issue_type policy_exception) carrying exception_approver, exception_expiry_date, issue_owner and linked Remediation actions with native plan, completion and verification dates, linked to the waived Policy and the accepted Risk; the packet, minutes, monitoring trail and notices as step documents; decisions in native approvals and step results.","id":"exception-record"}],"fields":[{"itemTypeSlug":"issue","key":"issue_type"},{"itemTypeSlug":"issue","key":"issue_owner"},{"itemTypeSlug":"issue","key":"exception_approver"},{"itemTypeSlug":"issue","key":"exception_expiry_date"},{"itemTypeSlug":"policy","key":"policy_owner"},{"itemTypeSlug":"risk","key":"treatment"},{"itemTypeSlug":"remediation","key":"target_date"},{"itemTypeSlug":"remediation","key":"completed_date"},{"itemTypeSlug":"remediation","key":"verified_date"}],"handoffs":[{"direction":"input","name":"Exception request submitted by the business requestor on the first step’s form"},{"direction":"output","name":"Recurring-exception feedback for the next policy review","sourceTemplateId":"workflow-library:grc-annual-policy-review"}],"roles":[{"contribution":"expertise","description":"Risk owner. Endorses the assessed packet (the rated risk position against appetite, the compensating-control plan and the approval authority it requires) and, once approved, validates the live register entry, the control monitoring and the notices.","id":"risk-owner","nodeIds":["assess-and-package","register-and-implement"]},{"contribution":"approval","description":"Delegated approval authority named by the authority matrix for the packet’s residual rating. Approves the exception time-bound with an explicit expiry, rejects it, or escalates it to the risk committee.","id":"approval-authority","nodeIds":["route-for-approval"]},{"contribution":"approval","description":"Risk committee chair. Decides an escalated exception whose exposure exceeds delegated authority and verifies that the minutes and the recorded decision match what was decided.","id":"risk-committee","nodeIds":["committee-review"]},{"contribution":"approval","description":"Accountable exception owner. Rules on control breaches and the waiver end state; on direct or committee rejection, authorizes the realistic compliance deadline and response using the prior risk decision.","id":"exception-owner","nodeIds":["monitor-to-expiry"]}],"status":"declared"},"provenance":[{"source":"workflow-library","sourceTemplateId":"coworkcanvas:template:policy-exception-risk-acceptance"}],"releaseId":"sha256:479bf2c2088fc4cc37edf5c06bf7f37fb8d193809232a5e926ca354bb14fcc07","schemaVersion":1,"sourceTemplateId":"workflow-library:grc-policy-exception-risk-acceptance"},"lineOfDefense":"monitor","mappingStatus":"mapped","risks":[],"slug":"grc-policy-exception-risk-acceptance","source":"coworkcanvas-gallery","standards":["coso-erm","iso-27001"],"teams":["risk-management","compliance-legal"]},"name":"Policy Exception & Risk Acceptance","nodes":[{"data":{"description":"The requestor and sponsor submit the exception on this step's form; the agent de-duplicates it, drafts the rated risk assessment against appetite and the compensating-control plan, and the risk owner endorses the packet and the approval authority it requires","formData":{"fields":[{"key":"policy_clause","label":"Policy and specific clause you cannot meet","required":true,"type":"text"},{"key":"why_not_met","label":"Why the requirement cannot be met as written","required":true,"type":"textarea"},{"key":"alternative_considered","label":"Compliant alternative you considered, and why it was rejected","required":true,"type":"textarea"},{"key":"cost_and_timeline_of_compliance","label":"Cost and timeline of achieving full compliance","required":true,"type":"textarea"},{"key":"scope_in_and_out","label":"Assets, systems, or processes the exception covers - and what it explicitly does not cover","required":true,"type":"textarea"},{"key":"requested_end_date","label":"Date the exception should end","required":true,"type":"date"},{"key":"remediation_milestone","label":"Remediation milestone that end date is tied to","required":true,"type":"textarea"}],"resultType":"form","submittedAt":null,"values":{}},"instructions":"**Objective** — Produce a risk-owner-endorsed approval packet for a single policy exception: business justification, a rated risk assessment positioned against appetite, a compensating-control plan, and the residual rating that determines which approval authority the request needs.\n\n**Inputs**\n- The exception request, submitted by the requestor on this step's form (the workflow's initial input): the affected Policy item and the specific clause that cannot be met, named requestor and business unit, accountable sponsor, in-scope assets/processes with explicit out-of-scope items, and the requested duration. A request that is really a permanent policy-change proposal is out of scope — return it to the policy owner (the Policy item's policy_owner) rather than assessing it here.\n- The risk register — Risk items touching the same assets/requirement — the org's standard likelihood/impact scale, and documented appetite/tolerance thresholds.\n- The control inventory — Control items as candidate compensating controls — and the governance approval/authority matrix.\n- Prior exception history for the same clause: query Issue items with issue_type policy_exception linked to the same Policy (active duplicates, prior rejections).\n\n**Procedure**\n1. Validate intake completeness and de-duplicate: confirm the requestor has supplied each missing business fact and resolve the sponsor from the exception ownership record, then query the exception register and prior history for the same policy clause. Flag duplicates of an active exception or a re-submission of a previously rejected request. Confirm exactly one accountable requestor and one sponsor, and that the requested duration is a genuine time bound, not an open-ended waiver.\n2. Test the submitted business justification rather than restating it: why the requirement cannot be met as written, the cost and timeline of full compliance, the compliant alternative that was considered and why it was rejected, and the remediation milestone the requested duration is tied to. Send the form back where any of these is assertion rather than argument.\n3. Draft the risk assessment consistent with COSO ERM risk-response practice and ISO 27001 risk-acceptance expectations: identify what the waived requirement protects against, rate likelihood and impact over the requested window on the standard scale, and state the inherent position before mitigation.\n4. Position against appetite: link the affected risk-register entries, compare the exposure to documented appetite/tolerance, and flag any breach explicitly (a breach forces escalation at the approval decision).\n5. Build the compensating-control plan: enumerate candidate controls (heightened monitoring, restricted access, segmentation, added review gates, reduced data scope), each with a proposed owner, operating frequency, the evidence it produces, and a required-by date; then re-estimate residual risk with those controls in place.\n6. Assemble the packet and identify the approver the authority matrix requires for that residual level: request, justification, risk assessment with appetite position, compensating-control plan, residual rating, and required approver.\n7. Route the assembled packet to the risk owner for endorsement.\n\n**Record in AssureSwarm**\n- Create/update the exception's Issue item — issue_type: policy_exception, identified_date (request date), issue_owner (the accountable sponsor), severity (from the residual rating) — with the policy clause, bounded scope, duration, duplicate-check result, ratings, and required approver in its description (item create/update).\n- The form on this step, answered by the business exception requestor outside the workflow’s executing and approving roles, captures the request itself: the policy clause at issue, why it cannot be met, the compliant alternative rejected and why, the cost and timeline of full compliance, the in-scope and out-of-scope boundary, the requested end date, the remediation milestone it is tied to, with the accountable sponsor resolved from the exception ownership record.\n- Link the Issue to the affected Risk items and the Policy item (items link).\n- Attach the assembled approval packet document (document upload).\n\n**Exit criteria** — Risk owner has endorsed the packet; ratings follow the standard methodology and cover the full duration and scope; the appetite position is stated honestly; every compensating control is operable by a named owner rather than aspirational; the required approver is identified.\n\n**Form recipient** — this step's form is answered by the business exception requestor outside the workflow’s executing and approving roles, not by any executing risk owner, sponsor, control owner, approver or monitor; those roles record their work in native results. Send it with a form assignment; the owner's own work goes in the step result.","label":"Assess and package","performedBy":{"primitives":["coach-query-data","coach-item-create","coach-items-link","coach-document-upload"]},"requiredApprovals":1},"id":"assess-and-package"},{"data":{"decisionField":"approval_decision","description":"Agent stages the endorsed packet with the approver the authority matrix requires; the approver decides: approve time-bound, reject, or escalate","formData":{"fields":[{"key":"approval_decision","label":"Route for approval","options":[{"label":"Approved time-bound","value":"approved_time_bound"},{"label":"Rejected","value":"rejected"},{"label":"Escalated to risk committee","value":"escalated"}],"required":true,"type":"select"}],"resultType":"form","submittedAt":null,"values":{}},"instructions":"**Objective** — Resolve who bears the exposure and whether the exception proceeds. The approver the authority matrix names for the packet's residual level decides to approve the exception time-bound, reject it, or escalate it to the risk committee.\n\n**Decision criteria**\n- `approved_time_bound` — Residual risk sits within the approver's delegated authority and within documented appetite; the compensating-control plan is operable by its named owners; and the requested window ties to a real remediation milestone. Approve with an explicit expiry date — an approval is never open-ended.\n- `rejected` — The exposure is not acceptable at any compensating-control level the organization will fund, the justification does not hold, or a compliant alternative exists. The policy requirement stands and a dated compliance deadline applies.\n- `escalated` — The residual exposure exceeds the approver's delegated authority or breaches appetite/tolerance, so the decision belongs to the risk committee rather than this approver.\n\n**Record in AssureSwarm** — Submit `approval_decision` (SELECT). Enter the step result citing the specific evidence references (risk rating, appetite position, compensating-control plan) and, for an approval, the approved expiry date; record the step's approver record (approver name and role).\n\n**Exit criteria** — `approval_decision` is submitted with a rationale that cites evidence; for an approval, an explicit expiry date is recorded; the branches not selected are prunable.","kind":"decision","label":"Route for approval","performedBy":{"primitives":["coach-query-data","coach-document-upload"]},"requiredApprovals":1},"id":"route-for-approval"},{"data":{"decisionField":"committee_decision","description":"The risk committee decides whether an escalated exception is accepted time-bound, accepted with conditions, or rejected; the agent prepares the reviewed packet and records the decision.","formData":{"fields":[{"key":"committee_decision","label":"Risk committee decision","options":[{"label":"Accepted time-bound","value":"accepted_time_bound"},{"label":"Accepted with conditions","value":"accepted_with_conditions"},{"label":"Rejected","value":"rejected"}],"required":true,"type":"select"}],"resultType":"form","submittedAt":null,"values":{}},"instructions":"**Objective** — Obtain and record the risk committee's decision on an escalated exception whose exposure exceeds delegated authority: accept time-bound, accept with conditions, or reject.\n\n**Decision criteria**\n- `accepted_time_bound` — The committee accepts the documented residual exposure for an explicit bounded scope and expiry date, and the compensating-control plan can operate throughout that window.\n- `accepted_with_conditions` — The committee accepts the exposure only with specific conditions. Every condition has a named owner, due date, evidence requirement and approved expiry; activation waits for any condition required before the waiver is relied upon.\n- `rejected` — The committee declines the exposure or the conditions needed for acceptance cannot be met. The policy requirement continues to apply; record the rejection rationale and a realistic dated compliance response. No waiver is activated.\n\nThe agent prepares the review from the endorsed approval packet, documented appetite breach or authority overflow, compensating-control plan, and committee schedule, quorum rules and submission template:\n1. Schedule the item at the next quorate committee session, or an authorized interim review where waiting would leave an ungoverned gap.\n2. Distribute the decision memo and complete packet ahead of the session, including quantified exposure, appetite position, remaining gaps, options and a recommendation.\n3. Draft minutes recording attendees, quorum, questions and the committee's decision as stated.\n4. Translate any acceptance conditions into named owners, due dates and evidence requirements; record the approved scope and explicit expiry. For rejection, record the committee's rationale and compliance guidance without setting an acceptance or expiry for an active waiver.\n5. The committee chair reviews the complete packet and minutes, authorizes the outcome, and records the routing choice below.\n\n**Record in AssureSwarm**\n- Submit `committee_decision` (SELECT) for routing; record the evidence-backed rationale, quorum, conditions and approved expiry or rejection compliance guidance in this step's native result.\n- Record the committee chair's sign-off in the native approval record.\n- Attach the minutes and signed decision as step documents, linked to the exception Issue and affected Risks.\n- Update the exception Issue description with the verbatim decision; for rejection, close it as rejected without activating a waiver.\n\n**Exit criteria** — The committee chair has authorized the decision and verified the minutes; acceptance has an explicit expiry and owned conditions, or rejection has a rationale and dated compliance guidance. The routing SELECT matches the signed decision; unused branches are prunable.","kind":"decision","label":"Committee review","performedBy":{"primitives":["coach-query-data","coach-document-upload"]},"requiredApprovals":1},"id":"committee-review"},{"data":{"description":"The risk owner judges whether an accepted waiver can operate within its approved conditions; the agent registers expiry, checks first-run control evidence and prepares the notices.","instructions":"**Objective** — Bring an approved (or committee-accepted) exception live: create the register entry with a hard expiry and an accountable owner, stand up monitoring for every compensating control, schedule the pre-expiry re-review, and notify stakeholders.\n\n**Inputs**\n- The approval decision and expiry date from the `approved_time_bound` branch, OR the committee's accepted_time_bound or accepted_with_conditions decision, conditions, and expiry from committee review. This is a join: it starts once whichever approving path applies has delivered its reviewed decision (only one path fires per request).\n- The compensating-control plan (owners, frequencies, evidence) from the endorsed packet.\n- The related risk-register items, the affected policy record, and the approval evidence.\n\n**Procedure**\n*Only an accepted path enters this checkpoint. Before any registration, risk acceptance or monitoring write, verify the native delegated-authority or committee decision is accepted. A rejected decision routes to end-state review and cannot activate a waiver.*\n1. Complete the exception's Issue item as the register entry: set exception_approver (the approval authority), exception_expiry_date (the hard expiry — this filterable field IS the register's expiry index), and issue_owner (the accountable owner); record the approved conditions, compensating controls, and the remediation milestone the expiry is tied to in the Issue description and the linked Remediation.plan.\n2. Link the entry to the related Risk items — setting treatment: accept on the Risk whose exposure this waiver accepts — the affected Policy item, and the approval evidence.\n3. Implement the monitoring hooks for each compensating control: where its operating evidence lands, the check frequency, and the breach condition that raises a flag. Capture first-run evidence that every control the approval requires to be live is actually operating before the waiver is relied upon.\n4. Schedule the pre-expiry re-review and reminder triggers well ahead of the expiry date.\n5. Draft and send the decision notice to the requestor, sponsor, policy owner, control owners, and assurance functions — stating the exact scope, the expiry, and each owner's compensating-control obligations — and collect acknowledgements from owners carrying ongoing obligations.\n\n**Record in AssureSwarm**\n- Field updates on the exception's Issue item: exception_approver, exception_expiry_date, issue_owner, with conditions and compensating-control obligations in the Issue description and the linked Remediation.plan (item update).\n- Link the Risk items (treatment set to accept where the waiver accepts that exposure), the Policy item, and the approval evidence (items link).\n- Attach first-run control evidence and the decision notice (document upload).\n\n**Exit criteria** — No exception is registered without exception_expiry_date and an accountable issue_owner; every approval condition is present with its owner and date; first-run control evidence is real rather than documented intent; obligation owners have acknowledged; the exception window is confirmed live.\n\n> **⚡ Audit Artist accelerator:** `/coach-workflow-scan` wires the compensating-control checks and the pre-expiry reminders; `/coach-notify` sends the decision notice and collects owner acknowledgements.","label":"Register and implement","performedBy":{"primitives":["coach-item-create","coach-items-link","coach-document-upload","coach-workflow-scan","coach-notify"]},"requiredApprovals":1},"id":"register-and-implement"},{"data":{"description":"The exception owner rules on breaches and the end state of an approved waiver, or releases the compliance response to a direct or committee rejection; the agent retains the authorized outcome, archives evidence and sends policy feedback.","instructions":"**Objective** — Keep the compensating controls honest across the exception window and drive the pre-expiry re-review that sets the exception's end state before it lapses silently. Retain the prior authorized exception outcome, process a direct or committee rejection only on its rejected route, and archive the full record with recurring-policy feedback.\n\n**Inputs**\n- The live exception Issue with its exception_expiry_date, compensating-control obligations, and remediation milestone (from register and implement). The expiring-exceptions watchlist is a query on issue_type: policy_exception ordered by exception_expiry_date.\n- Operating evidence for each compensating control as it accrues.\n- The rejected exception record plus the approver's rationale and compliance guidance (from the `rejected` branch of the delegated-authority or committee decision).\n- The in-scope systems/processes and their owners.\n- The final-state record from whichever terminal path reached here: a monitored exception's re-review outcome (retired / expired / renewed) from the reviewed monitoring work in this checkpoint, or a rejected exception's compliance-tracking outcome from the direct or committee rejection route.\n- The full trail: request, justification, risk assessment, compensating-control plan and evidence, approval or committee records, register entry, monitoring trail, re-review outcome, and stakeholder communications.\n\n**Procedure**\n*The agent incorporates Close and archive after the authorized decision. The exception owner contributes approval: rules on failed controls and the waiver end state, or authorizes the dated compliance response on a direct or committee rejection. Filing and retention run inside that review.*\n1. For an approved live waiver only, on the agreed cadence, pull operating evidence for each compensating control and verify it ran as designed — sample the actual evidence rather than accepting attestations alone.\n2. For an approved live waiver only, chase gaps with the control owner within the period; log each monitoring cycle's date, evidence checked, control status, and gap resolution.\n3. For an approved live waiver only, watch for scope creep beyond the approved boundary and for material shifts in the risk profile; raise a finding to the exception owner and approver when a control fails or exposure deteriorates, since that can force an early re-review.\n4. For an approved live waiver only, ahead of expiry, trigger the scheduled re-review and prepare the brief: remediation-milestone status, the full monitoring trail, and whether the policy requirement can now be met.\n5. For an approved live waiver only, if renewal is sought, stage it as a fresh request with updated justification and risk assessment through this same workflow — never a silent auto-renewal.\n6. Only for a direct or committee rejection, draft the rejection notice to the requestor and sponsor, explaining the rationale in terms of risk appetite and policy intent and restating that the policy requirement stands as written.\n7. Only for a direct or committee rejection, derive the compliance deadline from the rejecting authority's guidance and state the date by which the in-scope systems/processes must be brought into compliance.\n8. Only for a direct or committee rejection, open a tracked issue for the outstanding compliance gap with a named owner and the communicated due date, so the gap lives in the system of record and not only in the notice.\n9. Only for a direct or committee rejection, send the notice; log the notification date and recipients; attach the issue reference and any requestor response to the exception record.\n10. Verify the register entry status matches the final outcome — retired, expired, renewed under a new request, or rejected — and that no compensating-control obligation remains active on a closing record.\n11. Archive the complete package where audit and certification reviews can retrieve it (every artifact listed under Inputs).\n12. Update the linked Risk items (re-confirm treatment and residual_rating now the waiver has ended) and the Policy item to reflect the closure.\n13. Compile policy feedback for the Policy item's policy_owner — surfacing recurring-exception patterns such as repeated waivers against the same clause (query the closed policy_exception Issues linked to that Policy) as input for its next review cycle (next_review_date) — and record the closure date, closer, final status, and archive location.\n\n**Record in AssureSwarm**\n- Record monitoring findings, the end-state decision and the compliance response in this step's native result; record the exception owner's sign-off in native approval records.\n- On retirement, update Remediation.completed_date, Remediation.verified_date and Remediation.verified_by on the linked corrective action from the evidence; update the exception Issue's status and describe the outcome.\n- For a direct or committee rejection, create a compliance-gap Issue (issue_type: deficiency, source: compliance_review, issue_owner, identified_date) linked to the affected Policy, and a linked Remediation with action_owner and target_date for the dated compliance plan.\n- Attach the monitoring trail, pre-expiry brief or rejection notice, approval trail and retained archive package as step documents.\n- Update the linked Risk treatment and residual_rating after the waiver ends; attach the recurring-exception feedback to the Policy for policy_owner's next review.\n\n**Exit criteria** — The exception owner has ruled on breaches and approved the evidence-supported end state before expiry, or authorized the direct or committee rejection's compliance deadline and accountable response. Rejected requests have no active waiver or monitoring obligation. The full record is retrievable, native Issue and Remediation status/date updates match the reviewed outcome, and the linked Policy carries recurring-exception feedback.\n\n> **⚡ Audit Artist accelerator:** `/coach-render-package` compiles the audit-ready archive from the workflow's linked artifacts.","label":"Monitor to expiry","performedBy":{"primitives":["coach-query-data","coach-item-update","coach-workflow-scan","coach-document-upload","coach-item-create","coach-notify","coach-workflow-export","coach-render-package"]},"requiredApprovals":1},"id":"monitor-to-expiry"}],"sourceTemplateId":"workflow-library:grc-policy-exception-risk-acceptance"}
