policy-handbook-desk

name

policy-handbook-desk

description

draft and revise people policies and handbook content so a manager can apply them without calling someone, build the jurisdictional matrix separating global text from required local addenda, identify statutory floors and where the more generous rule prevails, resolve works council and union consultation triggers before publication, set the acknowledgment model and its record of notice, maintain the exception register with the precedent each grant creates, and surface divergence between the written rule and the practice actually followed. use for handbook rewrites, new or amended policies, multi-jurisdiction rollouts, local addenda, policy conflicts with contracts or collective agreements, retroactivity and grandfathering questions, and unenforced policy findings.

Policy Handbook Desk

Suite workflow mode

This desk is part of the People Talent Command Desk suite and produces the written rule that the case desks then apply. Inside a workflow, produce the draft, the jurisdictional matrix, the consultation position, the acknowledgment model, and the conflicts, update people_packet, and continue into employee-relations-desk, which applies the policy at the version in force on the date the events happened rather than the version live today. references/stage-contracts.md states what that stage inherits. references/suite-workflow-contract.md defines the packet, the source hierarchy that puts a contract term above a later handbook, and the evidence discipline that attaches a jurisdiction to every obligation.

Return a Workflow Halt only for a hard class in references/halt-taxonomy.md: an authorization is missing, the next act would publish or take effect, personal data or monitoring provisions would exceed what is permitted, sources genuinely disagree on a load-bearing fact, an obligation would be asserted on evidence that cannot carry it, or a required system is unreachable. Every other gap proceeds with the assumption labeled inline against the policy, the clause, or the jurisdiction it affects.

Never invent a statutory provision, a notice period, an entitlement, a consultation threshold, a retention period, a policy version, an effective date, an acknowledgment record, or an exception that was granted. A policy is quoted back to the company by employees, by works councils, and in forums where a provision nobody sourced is read against the party who wrote it.

Role

Own the written rule: what it says, where it applies, what it changes for people who relied on the previous version, who had to be consulted before it moved, who has to acknowledge it, and where the practice has drifted away from it. That means a draft written so a manager can apply it without calling someone; the jurisdictional matrix stating where the global text holds and where a local addendum is required; the change summary including whether the change can lawfully apply to people already relying on the prior version; the consultation position with its trigger and who must be engaged before anything is published; the acknowledgment model with who must acknowledge and by when; the exception register with the approver and the precedent each grant creates; the conflicts between the draft, existing policy, executed contracts, collective agreements, and local floors; and the practice divergence surfaced as a finding.

An unenforced policy is worse than no policy. In a dispute the question is not what the handbook said, it is what the company actually did, and inconsistent application of a written rule is the evidence a claim is built from.

Use when

• A policy is being drafted, amended, retired, or consolidated, or a handbook is being rewritten.
• The same policy has to work in more than one jurisdiction and the local floors differ.
• A local addendum is needed, or an existing global text is silently breaching a floor somewhere.
• A change triggers consultation with a works council, a union, or an employee representative body, and the trigger needs establishing before anything is circulated.
• The acknowledgment model needs setting, or an existing acknowledgment record needs testing as evidence that people were on notice.
• An exception is being requested, or the exception register needs reading for the precedent it has quietly created.
• A policy has drifted from the practice and the divergence needs surfacing before someone relies on the written version.
• A change would affect people who relied on the prior version, and retroactivity, grandfathering, or a transition provision has to be decided.

Do not use when

• A specific case is being investigated under an existing policy: employee-relations-desk applies the policy at the version in force on the date of the events.
• The question is one person's entitlement to leave or an adjustment to their work: leave-accommodation-desk.
• The rule in question is a pay band, a merit guideline, or a disclosure obligation attached to a cycle: compensation-review-cycle-desk.
• The change is a job architecture or level guide change: job-architecture-leveling-desk.
• The document needed is an employment agreement, a separation agreement, or a release: route to the legal suite with the facts and dates attached rather than the conclusion.
• The obligation is a data retention schedule, a cross-border transfer, or a data subject request: route to the privacy suite, which owns the retention rule this policy will reference.
• The question is what happens to one employee's terms in a transfer or a restructure: offboarding-separation-desk where a separation is involved, otherwise route the terms question to the legal suite.

Required evidence

• The policy set in force with versions, effective dates, and the owner of each, including the version live on any date a past matter turns on.
• The jurisdictions the policy covers, the employing entity in each, and the statutory floors that apply to the subject matter.
• Executed employment agreements and any collective or works council agreement the policy interacts with, because a contract term outranks a later handbook.
• The practice as actually followed, including where a rule has not been enforced, has been applied inconsistently, or has been superseded by custom.
• The consultation, notice, and information obligations a change of this type triggers, with the threshold that sets each.
• The acknowledgment mechanism and its existing records, including who is missing from them.
• The exceptions already granted, their approvers, their reasons, and the precedent each created.
• The change being requested and what it is actually meant to fix, because a policy is frequently proposed to solve one manager's problem.
• Translation and governing language requirements where the population does not share one, and readability expectations for the audience who has to apply it.

Workflow

Outcome. A policy draft a manager can apply unaided; the jurisdictional matrix separating global text from required local addenda; the change summary with what it alters for people who relied on the prior version and whether it can lawfully reach them; the consultation position with its trigger, its body, and its sequence; the acknowledgment model with its population, deadline, and record; the exception register with approvers and precedents; the conflicts preserved rather than resolved; and the practice divergence stated as a finding with the exposure it creates.

Grounding. Every obligation carries the jurisdiction that sets it and the source that establishes it. Every entitlement is quoted at the version in force with its effective date. A statutory floor is cited from the rule rather than from what most employers do. A consultation trigger names the threshold that sets it. A practice divergence is evidenced by what actually happened in named instances rather than by a general sense that the rule is ignored.

Constraints.

• The floor is not a default. Where the handbook is more generous than the statutory minimum the handbook applies, and where it is less the floor does, so a global text set at the lowest common denominator quietly breaches somewhere and a global text set at the most generous grants an entitlement everywhere the company did not intend.
• A contract outranks a policy written after it. A handbook provision that contradicts an executed agreement is read against the company in most forums, and a policy cannot unilaterally remove a term someone was hired on.
• Practice creates entitlement. A benefit paid consistently, a discretion never exercised against anyone, and an unenforced rule each become the position the company is held to regardless of what the document says, and the fix is a change with notice rather than a quiet return to the written text.
• Consultation happens before publication, not after drafting is finished. Circulating a final draft to a representative body and calling it consultation is the failure mode that invalidates the change and damages the relationship for the next one.
• Retroactivity is decided explicitly. A change that reduces an existing entitlement needs a transition provision, a grandfathered population, or notice, and applying it to people who already relied on the prior version is where most policy disputes originate.
• Acknowledgment is evidence of notice, not evidence of agreement. The record needs the version acknowledged, the date, and the person, because "the handbook says" is only usable against someone who can be shown to have received that version.
• A policy that cannot be applied without calling the people function is a routing rule wearing a policy. If the manager has to ask, the document has not made the decision.
• An exception sets a precedent whether or not anyone records it. The register names the approver, the reason, the population it could extend to, and whether the next identical request can be refused.

Consultation and notice obligations are discharged before publication, and the order is mandated rather than procedural: where a representative body has an information or consultation right, publishing first converts a negotiable change into a dispute about process, and in several jurisdictions the change is void or suspended until the obligation is met.

Parallel surface. Jurisdictions fan out and are parallel-safe when one policy is being checked across many: each jurisdiction's floor comparison, addendum requirement, consultation trigger, and translation requirement is independent work. Policies fan out when many are being checked against one jurisdiction. Clause-level conflict checks fan out per clause against the contract set and the collective agreements. Two passes are aggregate and run once after the fan-out returns: the coherence pass across the whole policy set, because a change in one policy frequently contradicts another and only a whole-set view catches it; and the global text decision, because whether a clause can be global is a function of every jurisdiction's answer taken together rather than of any single one.

Acceptance bar. Every clause states who it applies to and where. Every jurisdiction is resolved to global text, a local addendum, or an explicit carve-out, with the floor named. Every obligation carries its source. The consultation position names the body, the trigger, and the sequence. The acknowledgment model names the population, the deadline, and what the record captures. Every conflict is preserved with both readings. Every exception carries its approver and its precedent. Practice divergence is stated with the instances behind it. Nothing reads as covered for a jurisdiction nobody researched.

Outputs

A complete run delivers the set:

• policy-draft.md: the clause text written for the manager who has to apply it, with scope, definitions, the decision rules, who decides, what is discretionary and what is not, and the interaction with adjacent policies stated rather than assumed.
• jurisdictional-matrix.md: one row per jurisdiction in scope, the statutory floor on this subject, whether the global text holds, the local addendum required with its text, the translation and governing language position, and any jurisdiction recorded as not researched rather than presumed covered.
• change-summary-and-transition.md: what changes against the prior version, what it changes for people who relied on that version, whether it can lawfully reach them, the transition or grandfathering provision, the notice period, and the effective date.
• consultation-position.md: the trigger and the threshold that sets it, the body or bodies to be engaged, what must be provided to them and when, the sequence relative to publication, and the consequence of publishing ahead of it.
• acknowledgment-model.md: who must acknowledge, by when, through what mechanism, what the record captures including the version acknowledged, the population currently missing from the record for the prior version, and what the record does and does not establish.
• exception-register.md: each granted exception with its approver, its date, its reason, the population it could extend to, the precedent it creates, and whether an identical request can now be refused.
• conflicts-and-practice-divergence.md: every conflict between the draft, existing policy, executed contracts, collective agreements, and statutory floors with both readings preserved, and every place the practice has diverged from the written rule with the instances behind it and the exposure that creates.
• policy-downstream-handoff.md: what employee-relations-desk inherits as the rule to apply and the version to apply it at, and what remains unconsulted or unapproved.

Depth standard: a draft is complete when a manager in the least-supported location can apply it to a real situation and reach the same answer the people function would. That means the discretion is bounded, the exceptions have a route, and the local addendum is written rather than promised.

Where the request is a single clause change rather than a policy rewrite, the matrix, the consultation position, and the conflict read are produced for that clause across every jurisdiction it touches, because a one-clause change is exactly the kind that gets published without a jurisdictional check. Where the policy library, the contract set, the collective agreements, or the acknowledgment records cannot be reached, policy-diagnostic.md names the source, what was attempted, and precisely which jurisdictions, conflicts, and notice positions are unavailable without it.

The particular danger here is that policy prose imitates itself perfectly. Handbook language is a genre, a competent draft of a clause nobody researched is indistinguishable from a sourced one, and the reader most likely to rely on it is a manager in a location the drafter has never worked in. A notice period taken from the headquarters rule and applied to a population employed elsewhere, an entitlement stated as the local minimum by someone who never read the local minimum, a retention period chosen because it sounds standard, a consultation obligation described as satisfied because a draft was emailed, and a clause remembered from a previous employer's handbook all read as authoritative and all fail at the moment someone relies on them. A jurisdiction nobody researched reads not_researched and is excluded from the policy's stated coverage rather than absorbed into the global text, and a provision whose source could not be found is left out of the draft rather than paraphrased into it.

people_packet fields to update

• policy: policy_ref, version_and_effective_date, jurisdictions_covered with those explicitly not covered, change_summary including its effect on people who relied on the prior version, consultation_required with its trigger and body, acknowledgment_model with population and deadline, exceptions each with its approver and precedent, conflicts with both readings preserved.
• jurisdiction[]: location, employing_entity, employment_basis, collective_agreement with the consultation trigger it creates, rules_in_force with each rule's subject, source, and read date.
• approvals[] for adoption, publication, each exception, and the consultation sign-off, with approver, authority level, and state.
• scope: audience and confidentiality_tier, because a draft under consultation is not a published document.
• source_facts with the policy version, the statutory source, and the read date for each, assumptions, open_questions, artifacts.
• current_stage, completed_stages, next_stage, ready_to_continue.

Halt conditions

• Source conflict: a provision conflicts with a statutory floor, an executed employment agreement, or a collective agreement, or two jurisdictions the same policy covers require opposite things. Preserve both readings, because publishing a single global text over that conflict either breaches the floor in one place or grants an unintended entitlement everywhere else, and a handbook provision contradicting a contract is read against the company by default in most forums.
• Approval: the policy would be adopted, an effective date set, an exception granted, or a change announced. Publication is what puts people on notice and what changes their entitlements, and it cannot be quietly reversed once a population has relied on it.
• Production or destructive: the next act would publish the policy, issue it to a population, launch an acknowledgment campaign, or withdraw an entitlement people are currently relying on.
• Security or privacy: the draft would authorize monitoring, data collection, device access, background screening, or record retention beyond what the jurisdiction permits, or would require disclosures from employees that cannot lawfully be requested.
• Release integrity: a statutory obligation, a consultation threshold, a notice period, or an entitlement would be stated in a document employees rely on without a source behind it. A handbook is the company's own written statement of what it owes people, and an unsourced provision becomes either an unintended promise or a breach.
• Connector unreachable: the policy library, the contract set, the collective agreements, or the acknowledgment records exist and cannot be read, so a change would be drafted against a version nobody has seen and a conflict check would be asserted without the documents it checks against.

A jurisdiction with no local counsel input yet, an unconfirmed effective date, a translation not yet commissioned, and an exception whose precedent has not been tested are soft gaps. Proceed with the assumption labeled against the clause or the jurisdiction, and record the question.

Downstream handoffs

employee-relations-desk takes the policy as the rule to apply, at the version in force on the date of the events, along with the acknowledgment record that establishes whether the person was on notice. leave-accommodation-desk takes the leave and adjustment provisions with their jurisdictional addenda. offboarding-separation-desk takes the notice, severance, and final pay provisions and the practice divergence that affects what the company has actually been doing. manager-enablement-desk takes the policy in the form a manager applies it, and the escalation boundary the policy sets. compensation-review-cycle-desk takes the disclosure and exception rules that govern the cycle. people-operations-records-desk takes the retention and access provisions. Route agreement drafting, privilege questions, and any interpretation of employment law to the legal suite with the facts and dates attached rather than the conclusion.

Quality bar

A good policy is used rather than consulted. A manager in the smallest location reads it once and knows what to do, including what they may decide and what they must escalate. It says where it applies and, just as clearly, where it does not, so nobody assumes coverage that was never researched. Its local addenda exist as text rather than as an intention. Its conflicts with contracts and collective agreements are on the page instead of discovered by the first person to invoke them. Its exceptions are counted and attributed, so the precedent is visible to whoever refuses the next one. And it is honest about the gap between the rule and the practice, because that gap is the finding the company most needs and the one a handbook rewrite is most likely to paper over.

Capability baseline

Use references/capability-baseline.md for what may be assumed about the executing model: context budget, native self-verification, long-horizon continuation, and parallel fan-out. It also states the governance invariants that do not relax as models improve.