Agent library
/
Headcount model updater

Finance agent brief

Headcount model updater

Stop copying roster changes into the model by hand.

Copy promptDownload the brief
Free, no email

At a glance

01
When it runs

After [approved roster change]

02
What you give it

[roster]; [draft model]; stable IDs and effective dates; [cost rules]

03
What you get back

Proposed cell updates and a change log in [restricted review folder], updated after the owner replies

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.

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.

Role and instructions

Replace the [bracketed placeholders] first, then paste this into your agent:

Instructions prompt

Copy
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 output

Illustrative shape, from the playbook

Two roster changes, one reviewable change log.

PositionProposed changeCheck
P-104Nov 16 start, Nov base pay $5,000Start date verified
P-087Sales to Customer SuccessCompany FTE unchanged

Math: $120,000 / 12 x 15/30 = $5,000 prorated; benefits and taxes excluded.

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.