Use case

Leave requests out of the group chat.

"Can I take the 14th-18th off?" asked in Slack, approved with a thumbs-up, remembered by nobody. Then two people from the same team are gone the same week. A generated leave system tracks balances, routes approvals, and shows the team calendar - shaped to your policy instead of an HR suite's idea of it.

What your generated system includes

Data model

  • Employees with leave balances per type
  • Requests: dates, type, status, approver
  • Leave types: vacation, sick, parental - your categories
  • Team calendar derived from approved leave

The flow

  • Employee submits dates and type
  • System checks balance and team overlap
  • Manager approves with full context: balance, who else is out
  • Balance updates automatically on approval

Automations

  • Overlap warning when teammates' leave collides
  • Approval reminder if a request sits 2 days
  • Monthly balance summary to each employee
  • Handover-checklist task before longer leaves

Policies, yours

  • Accrual rules as you actually run them
  • Carry-over limits and expiry if you have them
  • Different approval chains per team
  • Change any rule later in one sentence, with preview

Try this exact prompt

Paste into Chromoly

Build a leave request system. Employees request vacation with dates and type; the system checks their balance and warns if teammates already have approved leave overlapping. Managers approve with that context shown. Update balances on approval, remind managers after 2 days, and email each employee their remaining balance monthly. Vacation accrues 2 days per month with max 5 days carried into a new year.

State your real accrual and carry-over rules in the prompt - the generated system encodes your policy, and policy changes later show their blast radius before applying.

Why not just use the HR suite's module?

HR suites bundle leave into per-seat pricing and generic policy models. If your rules are simple, you pay for a platform to get a form; if your rules are unusual - department-specific chains, project blackout periods - the module can't express them. A generated system costs no seats and encodes exactly your policy, because the policy is written into the system definition from your own words.

Frequently asked questions

Can employees see their own balances?

Yes - each employee gets their own view: current balances, request history, and team calendar for their team. End users are included in the plan; there's no per-seat pricing.

What about public holidays and part-time schedules?

Describe them - country holiday calendars, part-time accrual proration, or team-specific schedules become rules in the system. If your setup is unusual, the preview shows how it was interpreted before anything goes live.

Who maintains the system after it's built?

Chromoly does - monitoring, security patches, AI model upgrades, and integration migrations are platform-owned for the lifetime of the account. Changes you request run through a dependency-aware preview showing the blast radius before anything ships.

Can I import my existing data?

Yes - export your current spreadsheet or tool to CSV and import with column mapping, or attach the spreadsheet to your prompt and Chromoly shapes the data model from it directly.

Know who's off before it's a problem

Describe your process in plain language. Preview the working system free - deploy when it's right.

Start free →

150 credits/month free forever · EU-hosted · maintained for life