Prompt Details
Model
(claude-5-opus)
Token size
2,640
Example input
[POLICY_TOPIC]: Remote work and hybrid schedule eligibility
[COMPANY_CONTEXT]: 120-person B2B SaaS company, remote-first culture, stated values of 'ownership, transparency, and flexibility'
[JURISDICTION]: United States (multi-state remote workforce, primarily CA, TX, NY)
[EXISTING_POLICY_TEXT]: none — first draft; the company has operated informally without a written policy since founding
Example output
# Handbook Policy Draft
## Remote Work and Hybrid Schedule Eligibility — 120-Person B2B SaaS, Remote-First Culture (Ownership, Transparency, Flexibility)
---
### CARD 1 — EXECUTIVE SUMMARY
- **Policy intent:** This policy sets eligibility criteria, the application/approval process, and baseline expectations for employees working remotely or on a hybrid schedule.
- **Scope limitation:** Jurisdiction was provided as "United States," with California, Texas, and New York named as the primary states where the remote workforce is located. This is a **multi-jurisdiction operation**, and only these three states receive named (still-placeholder) treatment below. The company context does not confirm whether employees reside in any state beyond CA/TX/NY — given the remote-first model, that is plausible, and this draft does **not** cover those unconfirmed states. Every state-specific number, threshold, and procedural requirement — even for CA, TX, and NY — is a placeholder requiring confirmation, not settled law.
- **Readiness flag:** 1 of 7 framework components is fully `ADDRESSED`; 4 are `PARTIALLY ADDRESSED`; 2 are effectively `REQUIRES LEGAL REVIEW` at the jurisdiction layer (see Card 2 and Card 9 for the consolidated list).
---
### CARD 2 — POLICY COMPLETENESS MAP
| Framework Component | Status | Note |
|---|---|---|
| Purpose & Scope | PARTIALLY ADDRESSED | Purpose is clear and generic-safe; scope is only fully addressed for CA/TX/NY, and even those three need confirmation — other states, if any, are open items. |
| Eligibility & Coverage | PARTIALLY ADDRESSED | Default-eligible framework is drafted; non-exempt timekeeping classification implications vary by state and are not settled. |
| Procedure & Process | ADDRESSED | Application, approval, and review cadence are operational choices the company can set directly; no legal threshold blocks this. |
| Enforcement & Consequences | PARTIALLY ADDRESSED | General performance-management tie-in is drafted; notice periods and final-pay timing on eligibility changes/termination are jurisdiction-sensitive. |
| Exceptions & Special Cases | PARTIALLY ADDRESSED | Exception-request pathway is drafted; disability accommodation interactive-process requirements are jurisdiction-sensitive. |
| Legal Compliance Notes | REQUIRES LEGAL REVIEW | Expense reimbursement (CA Labor Code §2802 exposure), multi-state payroll/tax nexus, timekeeping/overtime rules, and pay-transparency requirements are all unresolved. |
| Related Policy Cross-References | ADDRESSED | Adjacent policies are identifiable and named in Card 7. |
---
### CARD 3 — DRAFT POLICY TEXT
**3.1 Purpose** *(GENERIC-SAFE)*
This policy establishes eligibility criteria, application procedures, and expectations for employees who work remotely or on a hybrid schedule. It reflects the Company's remote-first operating model and its stated commitment to ownership, transparency, and flexibility, while ensuring consistent, compliant treatment of employees across all work locations.
**3.2 Scope** *(GENERIC-SAFE, with a JURISDICTION-SENSITIVE gap noted)*
This policy applies to all regular full-time and part-time employees. It does not apply to independent contractors, who are governed by their individual service agreements. This draft addresses employees based in the United States, with specific placeholders for **California, Texas, and New York**. **{Confirm whether any employees reside in states outside CA/TX/NY, or outside the United States — this draft does not yet address those locations}**.
**3.3 Eligibility** *(GENERIC-SAFE default; one JURISDICTION-SENSITIVE line)*
- By default, all roles are eligible for remote or hybrid work unless a role is designated on-site-required due to the nature of the work (e.g., hardware lab access, in-person client demonstrations) and documented in the eligibility exception log maintained by People Ops.
- Eligibility is determined by role requirements and manager approval, not by tenure or level.
- **{Non-exempt employees may be subject to additional timekeeping requirements when working remotely — confirm against applicable state wage-and-hour rules}**.
**3.4 Application & Approval Process** *(GENERIC-SAFE)*
- Employees submit a remote/hybrid work request through **{HRIS system name}** specifying proposed work location(s) and schedule.
- Managers review requests within **{X business days}** and document approval or denial with a brief business reason.
- Approved arrangements are reviewed at least annually or upon a significant change in role, location, or business need.
**3.5 Work Location Changes** *(JURISDICTION-SENSITIVE)*
- Employees must notify People Ops **{X days}** before relocating to a new state or country, even temporarily, because a change in work location may trigger new payroll tax withholding, workers' compensation coverage, benefits eligibility, and employment-law obligations. **{Confirm payroll registration/tax-nexus process for new employee locations}**.
- Relocation outside a previously approved state or country requires renewed approval and is not guaranteed.
**3.6 Schedule & Availability Expectations** *(GENERIC-SAFE)*
- Hybrid employees are expected to be available during core collaboration hours of **{X:00–X:00 local time}**, with flexibility outside those hours.
- Remote and hybrid employees remain subject to the same performance, meeting-attendance, and responsiveness expectations as on-site employees.
**3.7 Equipment & Expenses** *(JURISDICTION-SENSITIVE — see Card 7 cross-reference)*
- The Company provides a standard remote-work equipment package described in the Expense Reimbursement Policy. **{California Labor Code §2802 requires reimbursement of necessary business expenses incurred while working remotely — confirm reimbursement scope, amount, and documentation standard with counsel}**.
- This policy does not restate reimbursement mechanics; see the Expense Reimbursement Policy for current amounts and process.
**3.8 Data Security & Confidentiality** *(GENERIC-SAFE)*
Remote and hybrid employees must follow the Company's Data Security and Acceptable Use Policy, including use of company-approved devices and networks, secure storage of confidential information, and prompt reporting of lost or stolen equipment.
**3.9 Performance, Enforcement & Consequences** *(GENERIC-SAFE process; JURISDICTION-SENSITIVE notice/pay terms)*
- Failure to meet availability, security, or performance expectations while working remotely is addressed through the Company's standard performance-management process, applied consistently regardless of work location.
- Remote/hybrid eligibility may be modified or revoked based on documented performance or business need, with notice consistent with **{applicable state notice requirements}**.
- **{Final pay upon termination or role change is subject to state-specific timing rules — for example, California generally requires immediate payment of final wages upon involuntary termination — confirm by state}**.
**3.10 Exceptions** *(GENERIC-SAFE pathway; JURISDICTION-SENSITIVE accommodation note)*
Requests for exceptions to standard eligibility or schedule requirements — including disability-related accommodation requests — are directed to People Ops and evaluated individually. **{Accommodation and interactive-process obligations vary by federal and state disability law — confirm requirements before finalizing this clause}**.
**3.11 State-Specific Addenda** *(JURISDICTION-SENSITIVE — placeholders only, not settled language)*
- **California:** **{expense reimbursement, meal/rest break, and daily-overtime provisions — confirm with counsel}**.
- **Texas:** **{confirm final-pay timing and any applicable local ordinances}**.
- **New York:** **{pay transparency/wage notice requirements, and any NYC-specific rules if employees are located within NYC — confirm}**.
- **All other states:** Not yet addressed in this draft — see Card 9.
---
### CARD 4 — CLAUSE-BY-CLAUSE JURISDICTION-SENSITIVITY REGISTER
| Clause (from Card 3) | Sensitivity | Why Sensitive | What to Confirm Locally |
|---|---|---|---|
| 3.1 Purpose | GENERIC-SAFE | Statement of intent; no legal threshold | — |
| 3.2 Scope (states beyond CA/TX/NY) | JURISDICTION-SENSITIVE | Multi-state remote workforce may extend beyond the three named states | Full list of states/countries where employees reside |
| 3.3 Non-exempt timekeeping | JURISDICTION-SENSITIVE | Wage-and-hour tracking rules vary by state (e.g., CA meal/rest break logging) | Required timekeeping method per state |
| 3.4 Application/approval process | GENERIC-SAFE | Internal operational process, not statute-driven | — |
| 3.5 Work location change / payroll nexus | JURISDICTION-SENSITIVE | Relocation can trigger new tax withholding, workers' comp, and benefits obligations | Payroll registration process per new state |
| 3.6 Schedule/availability expectations | GENERIC-SAFE | Internal expectation-setting | — |
| 3.7 Equipment reimbursement | JURISDICTION-SENSITIVE | CA Labor Code §2802 mandates reimbursement of necessary expenses; other states vary | Reimbursement scope/amount, confirmed with counsel |
| 3.8 Data security | GENERIC-SAFE | Internal policy cross-reference, not jurisdiction-dependent | — |
| 3.9 Notice before eligibility revocation | JURISDICTION-SENSITIVE | Notice obligations and mini-WARN triggers differ by state | Applicable notice period per state |
| 3.9 Final pay timing | JURISDICTION-SENSITIVE | CA requires immediate final wages on involuntary termination; TX/NY differ | Final-pay timing rule per state |
| 3.10 Accommodation/interactive process | JURISDICTION-SENSITIVE | ADA plus state disability law (e.g., CA FEHA) impose distinct steps | Interactive-process requirements, confirmed with counsel |
| 3.11 State addenda (CA/TX/NY) | JURISDICTION-SENSITIVE | Placeholder only; no rule stated as settled | Each state's specific rule set, individually |
---
### CARD 5 — CULTURE FIT DIAGNOSTIC
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Tone Alignment | STRONG FIT | Scored | The draft uses direct, default-in language ("by default... unless documented") rather than approval-committee framing, tracing directly to the stated ownership and flexibility values. |
| Flexibility Level | STRONG FIT | Scored | Default-eligible stance, manager-level (not centralized) approval, and annual rather than rigid re-approval reflect the stated flexibility value and the company's existing remote-first operating model. |
| Enforcement Rigor | MODERATE FIT | Scored | Documentation requirements (exception log, relocation notice, approval records) are necessary for multi-state legal defensibility and actively serve the stated transparency value, but they add more process than a purely unstructured "informal" approach — a deliberate trade-off, not a mismatch. |
| Culture Fit Index (OPERATIONAL EXTENSION — NOT A COMPLIANCE MEASURE) | STRONG FIT | Scored | Overall the draft tracks the three stated values closely because the company context supplied explicit values and an existing remote-first culture to draft toward, rather than requiring assumption. |
**Core Fit Reading:** The company context is specific enough (named values, remote-first status, 120-person scale) to score confidently rather than `UNKNOWN`. The main tension is between "flexibility" and the documentation the multi-state legal exposure requires (3.5, 3.9) — that documentation is framed as serving transparency rather than bureaucracy, but HR should watch that exception logs and relocation-notice steps don't read as contradicting the "low-friction" expectation the culture implies. No jurisdiction-sensitive flag has been softened to fit this score, per Rule 5.
---
### CARD 6 — EDGE CASE COVERAGE
| Scenario | Covered? | Suggested Language |
|---|---|---|
| International remote work request | No | **"International remote work requests are evaluated separately and require Legal and People Ops approval; approval depends on the Company's ability to lawfully employ or engage workers in that country."** |
| Employee relocates without notifying People Ops | Partially | 3.5 requires advance notice; add: **"Failure to notify People Ops of a location change may result in a pause of payroll processing until compliance requirements for the new location are confirmed."** |
| Home office equipment failure | No | **"Employees experiencing equipment failure should contact IT within {X business days}; the Company will provide a loaner or replacement consistent with the Expense Reimbursement Policy."** |
| Timezone overlap for cross-functional teams | Partially | 3.6 sets core hours generically; add: **"Teams spanning more than {X} time zones will establish team-specific overlap windows documented in the team's working agreement."** |
| Non-exempt overtime unrecorded while remote | No | **"Non-exempt employees must record all hours worked, including time outside scheduled hours, using {timekeeping system}; unrecorded overtime is a policy violation regardless of whether it was pre-approved."** |
| Accommodation requiring on-site equipment or modified schedule | Partially | 3.10 routes requests to People Ops; add explicit interactive-process language once confirmed with counsel (see Card 9). |
| Home office unusable (outage, disaster) | No | **"Employees unable to work from their approved location due to circumstances outside their control should notify their manager as soon as practicable; options may include temporary co-working arrangements or adjusted deliverables."** |
| Performance decline attributed to remote setting | Yes | Covered by 3.9 — standard performance-management process applies regardless of location. |
| Employee hired remote later reassigned to on-site-required role | No | **"Reclassification of a role as on-site-required will be communicated with {X weeks} notice where feasible, and eligibility for remote-work exception will be considered per Section 3.10."** |
| Workers' comp claim for home-office injury | No | **{State-specific — confirm whether home-office injuries during scheduled work hours are presumptively covered, and what documentation is required}**. |
---
### CARD 7 — RELATED POLICIES TO CROSS-CHECK
- **Expense Reimbursement Policy** — explicit overlap named per Rule 10: Section 3.7 references equipment/home-office cost handling rather than restating it, and CA Labor Code §2802 exposure sits primarily in that policy, not this one. Both documents must state the same reimbursement scope.
- **Timekeeping & Overtime Policy** — non-exempt remote employees' hour-tracking obligations (3.3, edge case above) must match this policy's eligibility language exactly, or the two will conflict on classification.
- **Data Security & Acceptable Use / IT Policy** — 3.8 cross-references device and network requirements; must stay consistent on what counts as a security violation.
- **Anti-Harassment & Code of Conduct Policy** — applies identically regardless of work location; this policy should not be read as creating a separate remote-work code of conduct.
- **PTO & Leave Policy** — schedule flexibility under this policy is distinct from leave entitlements; the two should not be conflated in employee communications.
- **Business Travel / HQ Attendance Policy** — if hybrid employees are ever required to travel to a physical office, that expectation and its expense treatment should live there, cross-referenced from 3.6.
- **Reasonable Accommodation / ADA Policy** — 3.10's accommodation routing must mirror the interactive-process steps defined there, not duplicate or contradict them.
- **Multi-State Payroll & Tax Policy** (if one exists) — 3.5's relocation-notice trigger should map directly to whatever process that policy defines for new-state payroll registration.
---
### CARD 8 — REVISION DELTA
No existing policy text was supplied; this is a fresh draft. The company has operated informally on remote/hybrid work since founding, which is why Card 5 treats the stated values and remote-first status as an existing baseline to draft toward, rather than as a change being introduced.
---
### CARD 9 — LEGAL REVIEW CHECKLIST
- Confirm the full list of states (beyond CA, TX, NY) — and any countries — where employees currently reside or may work remotely (3.2).
- Confirm CA Labor Code §2802 reimbursement scope and amount for home-office equipment/expenses, and how it's documented (3.7).
- Confirm state-specific non-exempt timekeeping and meal/rest-break requirements, especially California (3.3).
- Confirm the payroll tax registration/nexus process and required advance-notice period for employee relocation to a new state (3.5).
- Confirm state-specific final-pay timing rules on termination or eligibility revocation — e.g., California's immediate-payment rule vs. Texas/New York standard timing (3.9).
- Confirm notice-period requirements for modifying or revoking remote/hybrid eligibility, including any mini-WARN Act triggers in NY or CA for larger-scale changes (3.9).
- Confirm ADA and state-specific disability accommodation/interactive-process requirements (e.g., CA FEHA) as applied to remote-work exception requests (3.10).
- Confirm New York pay-transparency/wage-notice requirements, and any NYC-specific rules if employees are located within NYC (3.11).
- Confirm workers' compensation coverage terms and claims process for home-office injuries, by state (Card 6).
- Confirm whether any employees are engaged internationally and what entity/compliance structure (EOR, local entity, contractor) governs them (Card 6).
---
### CARD 10 — COMMUNICATION ROLLOUT NOTES
- **Frame it as formalizing, not restricting:** since this is the first written policy after years of informal practice, lead the announcement with the ownership/transparency/flexibility values and make clear the default posture (remote/hybrid-eligible) matches how the company already operates.
- **Brief managers first:** hold a manager-only session 1–2 weeks before broad rollout so managers can answer eligibility and approval questions consistently and aren't caught off guard by employee questions.
- **Company-wide announcement:** an all-hands or async video/Slack post from a People/Leadership sponsor, paired with the written policy and a short FAQ addressing "does this change anything for me today?"
- **Grace period:** give a 30-day window for existing informal arrangements to be logged into the new exception/approval system without penalty, so the rollout doesn't feel punitive.
- **HRIS follow-up:** once state-specific placeholders are confirmed (Card 9), update the request form to capture work-location data needed to route employees to the correct state addendum.
- **Checkpoint:** schedule a 90-day review to collect manager and employee questions before treating the policy as final.
---
### CARD 11 — METHOD NOTE
This draft is a starting point for internal review, not final legal language, and should not be published or relied upon as-is. Each of the seven framework components — Purpose & Scope, Eligibility & Coverage, Procedure & Process, Enforcement & Consequences, Exceptions & Special Cases, Legal Compliance Notes, and Related Policy Cross-References — was assessed individually in Card 2, and every jurisdiction-specific number or requirement in Card 3 is marked as a placeholder rather than settled fact, even for the three named states. The Culture Fit Index in Card 5 is an operational, non-compliance diagnostic: it was scored directly against the stated values of ownership, transparency, and flexibility and the company's existing remote-first status, not against an assumed or invented culture, and no culture score was allowed to soften a jurisdiction-sensitive flag. Because "United States" was named alongside California, Texas, and New York specifically, this draft treats those three as the confirmed scope and explicitly flags every other possible state or country as an open item rather than generalizing the named states' treatment across the whole company; because no existing policy text was supplied, Card 8 reflects a fresh draft rather than a revision. Given the multi-state legal exposure identified in Card 9 — particularly around expense reimbursement, wage-and-hour compliance, and termination/final-pay timing — this draft should be routed to employment counsel for review before it is published or communicated to employees.
---
**VERDICT: NEEDS LEGAL REVIEW — the biggest open item is confirming state-specific compliance obligations (expense reimbursement, non-exempt timekeeping, final-pay timing, and eligibility-revocation notice) across California, Texas, and New York, plus identifying any additional states or countries where employees reside that this draft does not yet address.**
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View SelectBy purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
📘 Turn a policy topic (remote work, PTO, anti-harassment, expense reimbursement) and your company context into a publish-ready handbook section — plus an 11-card completeness and risk diagnostic. Clearly separates generic-safe language from jurisdiction-sensitive placeholders that need local legal confirmation, and scores how well the draft fits your stated company culture. Works for a fresh draft or a revision of existing policy text. HR teams get a strong first draft in minutes, not days. ✍️
...more
Added over 1 month ago
