# Draft Workplace Policy Memorandum > Guides the drafter in producing a legal risk memorandum analyzing a return-to-office policy against accommodation obligations, collective-bargaining constraints, notice-act considerations, caregiver protections, and retaliation risks. - Skill: `finchipaiorg/draft-workplace-policy-memorandum` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-workplace-policy-memorandum` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-workplace-policy-memorandum/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/draft-workplace-policy-memorandum --- # Skill: Draft Workplace Policy Memorandum on Return-to-Office and Remote Work Compliance ## 2. Failure modes the skill is correcting - Treating the policy as a generic attendance issue instead of testing it against existing remote-work accommodations, leave status, bargaining obligations, and protected-family-status constraints. - Analyzing implementation only at the company-wide level and missing the distinct treatment required for employees with individualized accommodations or recent protected leave. - Flagging notice-act risk in the abstract without separating federal and state regimes, site-specific thresholds, and the effect of aggregated voluntary and involuntary separations. - Recommending termination or discipline for non-compliance without analyzing whether a “for cause” label is contractually supportable or collateral consequences attach. - Missing that a blanket return-to-office rule can create disparate impact or caregiver-status concerns even when facially neutral. - Describing risks without converting them into prioritized, actionable recommendations tied to who must act and when. - Stating legal conclusions without naming the governing authority or rule that supports each proposition. ## 3. Legal frameworks / domain conventions that apply - Accommodation and return-to-office: employees with current remote-work accommodations must be treated through an individualized interactive process before any blanket in-office enforcement is applied to them; a prior accommodation is not automatically extinguished by policy revision. Cite the governing disability-accommodation statute and implementing regulations applicable to the jurisdiction. - Protected-leave retaliation risk: employees returning from protected leave may not be penalized for leave-related absences or a leave-caused compliance gap; a post-return performance or attendance process can be retaliatory if causally tied to leave. Cite the applicable leave statute and anti-retaliation provision. - Collective-bargaining constraints: if any workforce segment is covered by a collective-bargaining agreement, remote-work terms, scheduling, and return-to-office conditions may be mandatory subjects of bargaining or contract interpretation; unilateral change risk must be assessed before rollout. Cite the labor statute and any contract provisions identified in the source set. - Notice-act analysis: mass-layoff or plant-closing notice statutes may be implicated if return-to-office enforcement causes enough involuntary separations, and some jurisdictions have lower thresholds or longer notice periods than federal law. Cite the federal statute and each applicable state analogue as relevant. - Caregiver and family-responsibility protections: state or municipal laws may prohibit discrimination or retaliation based on caregiver status or family responsibilities; facially neutral attendance mandates can still create liability if they disproportionately burden employees with childcare or eldercare obligations. Cite the local ordinance or state law where applicable. - “For cause” characterization: discipline or termination labeled as for-cause must satisfy the definition in the employment agreement, handbook, equity plan, or governing policy; the label can affect unemployment eligibility, equity forfeiture, and litigation posture. Cite the controlling agreement language and any governing plan or policy. - Disparate impact: a neutral policy that predictably produces higher separation or discipline rates for a protected group warrants a demographic pre-check and, if needed, a business-necessity and alternatives review. Cite the relevant anti-discrimination statute and disparate-impact doctrine. - Retaliation framing: adverse action should be separated from protected leave, accommodation requests, or complaint activity by clear contemporaneous documentation and non-retaliatory rationale supported by the governing law. ## 4. Analytical scaffolds - Build the analysis around distinct affected populations, not a single blended employee group. - First identify whether the source documents create multiple employee populations, then evaluate each population under the applicable framework before synthesizing risk. - Test each risk by asking: what rule applies, who is affected, what document or policy conflicts with that rule, and what downstream consequence follows if the policy is enforced as written. - For accommodation cases, distinguish between employees with a current approved remote-work accommodation, employees with pending requests, and employees whose accommodation history should inform a new interactive process. - For leave cases, distinguish between employees on active protected leave, employees scheduled to return, and employees who have recently returned and may face proximity-based scrutiny. - For bargaining cases, identify whether the policy touches hours, location, scheduling, discipline, or workplace terms that may require bargaining or notice to representatives. - For notice-act cases, evaluate both involuntary terminations and voluntary departures that are likely to be induced by enforcement, using the most conservative threshold analysis where the facts are uncertain. - For caregiver and disparate-impact cases, assess whether the policy is likely to burden a protected subgroup more heavily and whether feasible alternatives exist with less discriminatory impact. - For for-cause analysis, compare the contemplated conduct to the contract or plan definition before recommending that label; if the definition is unclear or absent, avoid the label or narrow it. - For each issue, end with the legal basis, the affected population, the operational consequence, and the recommended mitigation. ## 5. Vertical / structural / temporal relationships - Separate pre-implementation obligations from post-implementation monitoring; do not place bargaining, accommodation review, or notice analysis into the same bucket as routine enforcement. - Sequence the review from highest-risk gatekeepers first: accommodations, protected leave, bargaining, notice, then discipline and collateral consequences. - Treat employees with existing accommodations and those on protected leave as time-sensitive populations requiring review before enforcement begins. - Treat site-level notice exposure as location-specific and time-sensitive; do not aggregate across sites unless the statute or governing rule requires it. - When the policy allows exceptions, assess whether the exception process is documented, standardized, and capable of being applied before discipline decisions are made. ## 6. Output structure conventions - Draft as a legal risk memorandum, not as a generic HR summary. - Open with a short executive priority section that ranks the highest-risk items and states what must happen before enforcement, what should happen before rollout, and what should be monitored after rollout. - Use an ordinal severity scale defined once near the top, and apply it consistently to each risk item. - Organize the body by risk category, and within each category include: controlling authority, affected population, why the policy creates risk, operational consequence, and recommended mitigation. - State the controlling authority by name and section or other pinpoint reference for every legal proposition relied on. - Distinguish mandatory actions from best-practice recommendations, and do not blur the two. - For any issue that turns on a threshold, scale, count, site, or group, state the relevant scope explicitly before analysis and tie the recommendation to that scope. - End with a Recommended Actions section that uses imperative verbs, assigns a responsible role, and includes a timing anchor tied to rollout, enforcement, or any applicable statutory deadline. - Keep the memo concise but complete; every recommendation should be usable by counsel or HR without further translation.