Skip to main content
GullySystem
AI for HR · Solutions

Hire for the work you expect, not for last month’s panic.

AI Workforce Planning reads orders, project schedules, attendance, exits and skills records, then shows how many people each department needs and in which month. Gaps are listed by role, with the skills each one needs. Hiring and internal moves are proposed, never started. Both approve.

What it is

Hiring usually follows a complaint. A supervisor reports that the night shift is short, a requisition goes out, and the new person arrives long after the work has piled up. Nobody saw it coming.

Existing records already allow a forward view. Expected work, current headcount, known exits and the skills people hold share one screen, and the gap is split by department and month. Setup begins by connecting your orders, attendance and employee records.

Where it goes wrong today

The problems this is meant to ease.

Hiring starts after the pain starts

A supervisor complains, a requisition is raised, and the replacement turns up only after weeks of overtime have worn the existing team down. The gap showed in the order book. Nobody looked.

Headcount ignores the work ahead

Staffing is argued from last year’s numbers. When a big order or a new contract arrives, nobody has counted how many extra hands it needs or by which month.

Skills hide behind job titles

Same title, different work. When a gap opens, nobody knows who already holds the skill, who could learn it quickly, and who would need weeks of training before taking the job on.

Internal moves are overlooked

A vacancy is advertised outside while a capable person in a quieter team could have moved across, because the records that would show it are scattered over several sheets. Nobody connects them.

Plans are rebuilt by hand each year

The manpower sheet is copied, patched and argued over every budget season by people who each hold a different version of it. By approval, the business has changed. Stale again.

Inside the module

What AI workforce planning does.

Current capacity by team

Headcount, shifts, leave and attendance are combined to show how many working hours each department really has this month, with agency and contract staff counted apart from permanent employees. Nothing is guessed.

Staffing forecast from expected work

Orders, projects and bookings are turned into the people each team will need in coming months, using work-to-people ratios that your supervisors have confirmed. Ratios stay visible and editable.

Skill gap view

Each role lists the skills it needs, and the training records show who holds them today, so a team short of coming work gets its missing skill named. Gaps are specific.

Planning by role and department

Plans are kept for each role inside each department, so a shortage of welders is not hidden behind a surplus of packers. Every figure traces back to records.

Hiring and internal mobility options

A gap can be met by recruiting, by moving someone from a quieter team, or by training someone already here, and the page lists each route with its people. The HR head picks.

Growth scenarios

Model a new branch, a second shift or a lost client, and each version lists the extra people needed and the month the gap opens. Scenarios sit beside the base plan for comparison.

Plan against actual

Each month, joiners and leavers are compared with the plan, and ratios that proved clearly too high or too low are corrected. Next year then starts from evidence.

Where it gets used

What this looks like in a working week.

A garment factory ahead of a season

Confirmed orders are turned into operator and finisher needs by month. The HR head then sees the tailoring gap early enough to train helpers in the factory instead of paying for agency staff at the last minute.

A hospital opening a new ward

A scenario adds beds and shifts, and the plan lists the nurses, technicians and cleaners needed by month, ready for the owner and matron to weigh against the budget. Posts follow approval.

A security agency winning a contract

Extra guard posts go in as a scenario. The plan shows how many guards can move from existing sites and how many must be hired, with the month each is needed.

A logistics company planning drivers

Route bookings and driver retirements are read together. The operations head sees which depot runs short of licensed drivers. Internal training can then start well ahead of the gap, using the people already on the payroll in quieter depots.

A staffing agency balancing its own team

Open client requests set the recruiters and coordinators needed. The founder sees which team is stretched, and whether a coordinator could move across before anyone is hired from outside.

Who touches it

The people who open this every day.

HR head

Owns the yearly manpower plan. Approved gaps become requisitions.

Department head

Checks the ratios for their team. Makes the case for an extra post.

Owner or finance head

Sets the plan against the salary budget. Approves or declines each new post.

Plant or branch manager

Sees upcoming gaps by shift. Arranges cover or overtime early.

How it is set up

From first conversation to daily use.

  1. Discovery with HR, finance and operations

    Agree which departments to plan first and which work records drive their staffing. Then list the decisions the plan must support, such as approving a post or moving people between teams, and who takes each one.

  2. Data readiness

    Clean the headcount, grade and shift records, and link orders or projects to the department that does the work. Supervisors confirm the first ratios. Everything else builds on them.

  3. Trial on one department

    Plan one department for the coming quarter from its real orders and headcount. Then set the proposed gaps beside what the supervisor already knows from the floor, and note every difference between the two.

  4. Walk-through with HR, heads and finance

    HR, the department head and finance review the trial plan together. Ratios, skill lists and notice periods are corrected wherever the numbers look wrong to the people who know the work.

  5. Going live

    Every department and site then joins the plan. A requisition is raised only after the HR head and the owner have both approved the gap in writing. Nothing opens by itself.

  6. Review afterwards

    Each month, planned and actual headcount are compared. After a few cycles the ratios are tuned, and any department that never opens the view is asked why it does not find the view useful.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Staffing gaps count roles where expected work exceeds available people, and the baseline is the manpower plan or open requisitions held before go-live.
  • Workforce utilisation is the share of available hours spent on recorded work, with the starting figure read from attendance and project or order records.
  • Forecast accuracy compares planned and actual headcount per department each month, and the baseline is the last manual manpower sheet you kept.
  • Time to fill runs from an approved gap to a joined employee, with the baseline read from earlier requisitions in your recruitment records.
  • Internal fill count records vacancies met by moving existing staff, and its baseline is the transfers already logged in your employee database before go-live.
Used responsibly

Where a person stays in charge.

Humans approve every post

The software proposes gaps and months. It never opens a vacancy, makes an offer or moves an employee, and the HR head and the owner sign off first.

Ratios are agreed with supervisors

Work-to-people ratios start from your records but are confirmed by supervisors on the floor, because a wrong ratio makes a wrong plan. Each ratio is shown and can be edited. Nothing is hidden.

Internal moves need consent and fairness

Candidates for a move appear on the same terms, by recorded grade, skills and training, with no manager’s favourite placed first. Choosing among them, and asking the person, stay with the managers.

Employment rules differ by country

Notice, contract and working-time rules vary from place to place, so each plan should be checked with your own labour lawyer before posts are filled. This tool prepares numbers. It offers no legal advice.

Forecasts are only as firm as the orders

Where work is lumpy or unconfirmed, a forecast becomes a wide range, and the page shows that band beside the reason it is wide. A narrow figure would pretend to know more. It stays honest.

How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • Employee database
  • Recruitment and onboarding
  • Attendance and time tracking
  • Payroll management
  • Order management or project management
Common questions

Questions owners ask about AI workforce planning.

Does it open vacancies on its own?

No. It proposes a gap and a month. Approval of a post stays with the HR head and the owner, and only after that does a requisition appear in recruitment.

Which records must exist before it helps?

A year or two of headcount, exits and workload records, kept in a consistent form, is the minimum. Supervisors must also agree the ratios between work and people, because the software cannot guess how your own floor runs day to day.

How accurate are the forecasts?

They are ranges built from your own orders and history, and they are only as firm as the orders behind them. Uncertain work gives a wide band. You see it.

Is it worth setting up for thirty employees?

Probably not. A sheet kept by the owner will do. The planning view starts to matter once several departments, sites or shifts compete for the same hiring budget and the same pool of candidates.

How does it support internal moves without favouritism?

Candidates appear on the same terms, ranked by recorded grade, skills and training, not by whom a department head happens to like. Choosing among them stays a human decision.

Who sees the plan and the skills data?

Only the roles you grant. Department heads see their own team, while individual skill records stay with HR and the person’s manager, and every viewing is recorded in an access trail that can be checked later. Nothing is open by default.

What does it connect to?

It reads your employee database, attendance, payroll bands, recruitment records and order or project data, with each link agreed alongside whoever looks after that system. A system without an export needs a one-time load.

What does it cost and how heavy is the setup?

Effort depends on how many systems hold your headcount, orders and skills, and how tidy those records are today. We scope it after looking at your data. The quote is written.

Talk to us

Tell us how you handle AI workforce planning today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements