--- name: Headcount model updater number: "06" what_it_does: Stop copying roster changes into the model by hand. cadence: After [approved roster change] setup: Moderate risk: High — restricted pay data scales_to: More teams in the model owner: "[owner]" authority: Preserve the approved model and history; leave publication and synchronization for review inputs: - "[roster]" - "[draft model]" - stable IDs and effective dates - "[cost rules]" output: Proposed cell updates and a change log in [restricted review folder], updated after the owner replies works_standalone: true --- # Headcount model updater A standalone finance agent brief from *Agents for Finance*. It works in Claude, ChatGPT, Grok Bot, or the agent tool you already use. Adapt the placeholders to your setup. This is a starting brief, not an installable plugin. ## What it does After an approved roster change, prepare proposed model updates and a change log in a restricted draft. Match stable IDs and cost rules; resolve unclear dates before review. Preserve the approved model and history. Publication and synchronization stay with review. ## Role and instructions Replace the [bracketed placeholders] first, then paste this into your agent: ``` You are a finance agent running the headcount model updater for my team. After [approved roster change], compare [roster] with [draft model] using stable IDs, effective dates and [cost rules]. Prepare proposed cell updates and a change log in [restricted review folder]. Ask [owner] about ambiguous records and update the same draft after replies. Preserve the approved model and history; leave publication and synchronization for review. Do not change the approved model. Do not publish or synchronize. Keep the draft in the restricted review folder. If a department transfer is replayed, retain the revised allocation without adding another company FTE or duplicating the change. Cite sources on every update. ``` ## Setup checklist Fill these in before the first run. Use the systems you already have — a spreadsheet export is enough to start. - [ ] Trigger: [approved roster change] - [ ] Roster: [your approved roster source or export] - [ ] Draft model: [where the restricted draft lives] - [ ] Cost rules: [cost rules], including any agreed proration rule - [ ] Restricted review folder: [where proposed cell updates and the change log are kept] - [ ] Owner to ask about ambiguous records: [name and channel] - [ ] Out of scope: the agent may not change the approved model, publish, or synchronize; pay data stays restricted ## Output format Prepare proposed cell updates and a change log in the restricted review folder, then update that same draft after the owner replies. Include: - Headline: how many roster changes, and that the change log is ready for review - A table of positions, proposed changes, and checks - The math for any prorated amount, using the agreed cost rules - After a reply: which entries were retained, with effective dates, and that the draft is ready for model review - Sources: approved roster, draft model, agreed proration or cost rules - A reminder that the approved model is unchanged and sync remains separate Illustrative shape, from the playbook: Two roster changes, one reviewable change log. P-104: Nov 16 start, Nov base pay $5,000, start date verified (math: $120,000 / 12 x 15/30 = $5,000 prorated; benefits and taxes excluded). P-087: Sales to Customer Success, company FTE unchanged. After the owner confirms November 16 and asks to keep the transfer FTE-neutral, both entries are retained with effective dates; the draft is ready for model review, the approved model is unchanged, and sync remains separate. ## Pressure-test it Replay a department transfer. It should retain the revised allocation without adding another company FTE or duplicating the change. Run this test on historical or redacted data before you put the job on a schedule. ## Works standalone This brief is enough to run the job with files, exports, or the tools you already have. You do not need a special agent pack or plugin. Once the placeholders are filled in and the pressure-test passes, you can put it on a schedule. Easier with Aleph: Use enabled spreadsheets and mapped HR data to prepare a reviewable change log. Keep approved-model publication separate.