Skip to content
Back to skills

Policy Exception Log

ASecurity

Record a policy exception so the company can see who accepted the risk and when it expires. Use when the user mentions policy exception, risk acceptance, exception log, waiver of policy, or asks for a policy exception record. Legal operations skill by Yasir Jilani.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 30, 2026
ai-agentspythonawsgitapisecurity

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add SYasJ/claude-business-skills --skill policy-exception-log --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Policy Exception Log?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Policy Exception Log
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/syasj-policy-exception-log/badge)](https://www.skillsdirectory.com/skills/syasj-policy-exception-log)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: policy-exception-log
description: "Record a policy exception so the company can see who accepted the risk and when it expires. Use when the user mentions policy exception, risk acceptance, exception log, waiver of policy, or asks for a policy exception record. Legal operations skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
  author: Yasir Jilani
  version: "1.0.0"
  domain: legal
---

<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
     Edit the 'policy-exception-log' entry in source/, then run:
       python3 scripts/generate.py && python3 scripts/validate.py
     See CONTRIBUTING.md. -->

# Policy Exception Log

Record a policy exception so the company can see who accepted the risk and when it expires.

## When to use this skill

Use this skill when the user:

- policy exception
- risk acceptance
- exception log
- waiver of policy

## When not to use this skill

- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.

## Professional boundary

This is not legal advice and does not create an attorney-client relationship. Do not invent statutes, case names, or filing deadlines. Drafts are for qualified counsel in the relevant jurisdiction.

## Operating boundaries

- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.

## Inputs to collect

- The policy
- The exception requested
- The business reason
- The proposed expiry

## Workflow


### 1. State the rule and the break

What the policy requires and what the team wants to do instead.
### 2. Reason

The business reason in specific terms. 'We are busy' is not enough unless they truly have no other reason, in which case say that.
### 3. Risk

What bad outcome the policy was meant to prevent, in plain language.
### 4. Compensating step

What they will do meanwhile, and how someone will check.
### 5. Expiry and owner

An exception without an end date is a silent policy change. Name the acceptor.
### 6. No retroactive cover

Do not backdate an exception to hide something that already happened. Record the real dates.

## Output

Deliver a **policy exception record**.

- Purpose of this policy exception record, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.

## Quality bar

- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.

## Example

### Scenario

Elena Voss, operations lead at Northline Studio in Calgary, needs a policy exception record by 30 September 2026. A team wants to skip a vendor security review for a tool they already bought.

### Example data

```text
From: Elena Voss, operations lead
Organization: Northline Studio, Calgary
Date: 14 September 2026
Needed by: 30 September 2026

A team wants to skip a vendor security review for a tool they already bought.

The policy: their one-page rule dated 2 Mar 2026. No exception log
The exception requested: Harbor renewal is open. Contractor NDA was raised verbally and never logged
The business reason: Harbor renewal, recorded 14 September 2026. No supporting file attached
The proposed expiry: Harbor renewal, recorded 14 September 2026. No supporting file attached
```

### Example outcome

**Policy exception record**
To: Elena Voss, operations lead, Northline Studio
Date: 14 September 2026 · Needed by: 30 September 2026

**Decision**
An exception record with the skipped step, a short compensating review, a real expiry, and no backdating.

**What the file supports**

| Input | Value | Status |
| --- | --- | --- |
| The policy | their one-page rule dated 2 Mar 2026. No exception log | Needs confirmation |
| The exception requested | Harbor renewal is open. Contractor NDA was raised verbally and never logged | Carried into the draft |
| The business reason | Harbor renewal, recorded 14 September 2026. No supporting file attached | Carried into the draft |
| The proposed expiry | Harbor renewal, recorded 14 September 2026. No supporting file attached | Needs confirmation |

**How this draft was built**

**1. State the rule and the break**  
What the policy requires and what the team wants to do instead.

**2. Reason**  
The business reason in specific terms. 'We are busy' is not enough unless they truly have no other reason, in which case say that.

**3. Risk**  
What bad outcome the policy was meant to prevent, in plain language.

**4. Compensating step**  
What they will do meanwhile, and how someone will check.

**5. Expiry and owner**  
An exception without an end date is a silent policy change. Name the acceptor.

**Deliberately not done**
- A permanent exception with no owner.
- Backdating.
- Logging an exception for conduct the user describes as deceptive.

**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.

Next: Elena Voss by 30 September 2026. This is a draft, not a sign-off.

## Anti-patterns

- A permanent exception with no owner.
- Backdating.
- Logging an exception for conduct the user describes as deceptive.

## Related skills

- `security-exception`
- `policy-writer`
- `vendor-security-review`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…