Skip to main content
GullyHR

HR process design · Children's hospitals

HR Foundation Package for Children's hospitals

The HR Foundation Package is a fixed-scope engagement for a business with no real HR system yet. On a schedule agreed in writing, GullyHR writes, tests and hands over an agreed set of basics: an employee handbook, five core processes, standard letters, first HR records and a simple report. Scope and fee are agreed in writing before the work starts.

Colleagues organising HR folders and reviewing a setup plan.

HR Foundation Package for Children's hospitals

What this looks like in your business

Some children's hospitals grow from a clinic and a handful of nurses into a ward, an emergency desk and a neonatal unit while HR still lives in a cupboard and in the memory of the matron. The Foundation Package suits that moment. GullyHR writes a handbook, five core processes, standard letters and first records in the hospital's own terms: ward duty, night cover, vaccination desk hours, play and counselling staff, child-safe conduct. Each piece is tested with the people who must use it, then handed over for managers to run without us.

Why a young children's hospital needs a foundation first

A hospital that has outgrown its first small team feels the gaps in particular places. The ward sister knows every nurse by name, but the appointment letter was a single page and the duty pattern was agreed over tea. A paediatrician joined on a visiting basis and then took on weekend calls, yet nothing records when the arrangement changed. The neonatal unit has been staffed by two or three experienced nurses whose terms differ because each was hired in a different year. Fever season arrives, leave is requested by word of mouth, and the leave register is a notebook at the nursing station. Meanwhile child-safe conduct, the most important rule in the building, is held in the heads of senior staff. None of this is failure. It is what happens when care comes first and paperwork follows later. The trouble comes when a second ward opens, when a nurse leaves in the middle of a busy week, or when a parent asks what the hospital expects of its staff around children. A foundation puts the basics in writing before those moments arrive.

What goes into the handbook and the first records

The handbook is written for this hospital, not copied from a retail chain. It would open with how a shift works on the children's ward, the emergency desk and the vaccination clinic, and what happens at handover. It would set out leave in a way that accepts the seasonal fever weeks, with a written rule for notice, approval and who decides when cover is thin. A section on conduct around children comes next: who may be alone with a child, where, and what to do if something worries you. Standard letters follow, for appointment, confirmation, transfer between units and exit, so a nurse moving from the general ward to the PICU receives a letter that says so. The first records are small and practical: one employee file for each person, a leave register that matches the roster, a training record for neonatal and PICU staff, and a short monthly report for the owner. Everything is drafted, then read aloud with the ward sister and the doctor in charge before it is finalised.

Suppose the five processes are tested on one ward

Suppose the hospital chooses its five core processes: joining, leave, transfer between units, conduct concerns and exit. Before handover, GullyHR tests each with the people who will run it. Take joining. A new ward nurse is due to start on Monday. The test follows the process page: the appointment letter, the child-safety undertaking, the unit induction, the first-week buddy and the record in her file. The ward sister notices that the buddy step lacks a name, and that the undertaking has no place for a date. Both are fixed in the page, not in a meeting. Then the leave process is tried against a fever fortnight in the previous year's register. It works for ordinary weeks but gives no rule for when three nurses ask for the same days. The owner has to choose: first request wins, or the ward sister decides with a note. GullyHR writes the choice into the page. The test is the work, because a process nobody has tried is only a wish. Once each page is read without our help, it is handed over.

Who keeps what once the foundation is in place

A foundation is useful only if someone owns each piece. The owner or administrator keeps the master set of letters and the handbook, and decides when to revise them. Each nurse in charge holds the leave register for her unit and the transfer notes. The person who runs the front desk keeps the joining checklist for vaccination and outpatient desk staff, attendants and security. A named senior person receives conduct concerns, and the page says what that person does next. The monthly report goes to the owner on a set day and covers joiners, leavers, leave taken and open items, so that decisions are made on evidence. Handovers worth writing down are the night-to-day nursing handover for HR matters, the transfer of a resident at rotation, and the hand-back of the package from GullyHR to your team. What stays with the owner is every decision: pay, staffing, which roles to keep, and the wording that a legal adviser must confirm under your local rules. GullyHR writes, tests and hands over; it does not run the hospital.

The first weeks

  1. 01

    Meet the owner and the matron to agree which five processes matter most, such as joining, leave, transfer, conduct concerns and exit.

  2. 02

    Gather the current appointment letters, the nursing station leave notebook and any duty roster, so the handbook starts from what already happens.

  3. 03

    Draft the conduct-around-children section with the ward sister and the doctor in charge, and read it aloud with night nurses present.

  4. 04

    Write the first joining process page and test it on the next real joiner, whether ward attendant, desk staff or nurse.

  5. 05

    Set up one employee file format, a leave register matching the roster, and a monthly report that the owner reads on a fixed day.

The operating context

Build the minimum HR structure in a usable sequence

A children's hospital treats small patients whose parents stay at the bedside all day. Paediatric nurses, play and child-life staff and attendants must be patient with children and calm with frightened families, hour after hour.

Paediatricians and resident doctorsPaediatric ward nursesNeonatal and PICU nursesPlay and child-life staffCounsellors and dietitiansWard attendants
Hospital colleagues reviewing a staff duty roster and credential records

The decision to work through

Prioritise employee records, essential policies, role ownership and recurring processes around the starting workforce. Workforce to consider: Paediatricians and resident doctors, Paediatric ward nurses, Neonatal and PICU nurses.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: The child and the parent both need care. Staff absorb crying, questions and blame from relatives, and few are taught how to cope with it.

An exception to test

Check which missing decisions block the next step and separate setup work from ongoing transaction handling.

Which parts of your business should the scope cover?

The right workforce and approval structure depends on the operations you run. Confirm which of these apply, and whether they share one HR process.

  • Standalone children's hospitals with paediatric emergency
  • Women and children hospitals that also run maternity
  • Paediatric multispeciality hospitals with surgery and subspecialties
  • Hospitals with a NICU and PICU taking referrals from nursing homes
  • Neighbourhood children's hospitals with a strong OPD and vaccination clinic
  • Hospitals with developmental paediatrics and child therapy units

When to consider this service

  • Each manager joins, approves leave and confirms probation in their own way, and you only hear about the difference when two employees compare notes.
  • The appointment letter is a file copied from a former employer, and nobody is sure which version is current.
  • Month-end payroll starts with a scramble to find who joined, who left and who took unpaid leave.
  • You have no handbook, so every question about notice, holidays or conduct is answered from memory and sometimes answered differently.

Businesses this service is designed for

  • Founder-led businesses of roughly 20 to 100 people where HR has so far been handled by the founder, an admin manager or an accountant.
  • Companies that have grown past the point where one person's memory can carry hiring, leave and payroll inputs.
  • Businesses preparing to hire a first HR manager, who want a working base for that person to inherit.
  • Companies with several managers who each handle people matters in their own way and want one consistent method.

What we design

GullyHR does the drafting, testing and handover; you decide how your business wants to run. We start from what you do today, write the agreed basics in plain language, try each one on real cases from your own team, and correct it before it is handed over. You give us access to your people, current documents and decisions on policy. The work is a defined package with a scope agreed in writing, a mid-point review and a handover session. It is not open-ended consulting, and anything outside the agreed list is scoped separately. Where a document touches employment law, we flag it for review by a qualified professional rather than giving a legal opinion.

An employee handbook written for your business, not copied from another.

Working hours, holidays, leave, conduct, notice and the everyday rules are set down in plain language, using the decisions you make with us. Points that depend on law are marked for confirmation with a qualified professional.

Five core processes written as one-page documents.

Joining, attendance and leave, monthly payroll input, probation and confirmation, and exit. Each page shows the steps, who does each one, what gets recorded and when the document will next be reviewed.

Each process is tested before it is handed over.

We run every process on real or recent cases from your team, such as a recent joiner or a leave request, and see where it breaks. The page is corrected after the test, not before it.

Standard letters and templates your managers can use unaided.

Appointment, confirmation, warning, relieving and the other letters you actually send are drafted once, in a consistent form, with clear fields to fill. Legal wording is flagged for professional review.

A first set of HR records and a simple report on a schedule agreed in writing.

An employee master, a leave record, an exit record and a probation tracker are set up, along with a short monthly set of figures such as headcount, joiners, leavers and open confirmations.

From current practice to a working process

Walk through the present process with the people who run it. Identify the trigger, missing information, decisions and exceptions before drafting the future workflow.

  1. 01

    Weeks 1 and 2: baseline

    We agree the scope in writing, collect your current documents and speak to the people who do the work. We write down how each of the five processes runs today and list what is missing, so the starting point is clear to everyone.

  2. 02

    Weeks 3 to 5: decisions and first drafts

    We bring you a short list of policy decisions to make, such as leave types, notice and probation length. Once you decide, the first drafts of the handbook, process pages and letters are written.

  3. 03

    Weeks 6 and 7: testing on real cases

    Each process is run on recent or live cases with the people who will use it. We note every point where it hesitates, a missing step or an unclear owner, and fix it.

  4. 04

    Week 7 or 8: mid-point review

    A review with you on what is written, what has been tested, what is slipping and what has changed. Scope changes, if any, are agreed in writing at this point rather than assumed.

  5. 05

    Weeks 8 to 10: records and reporting

    The first HR records are set up and filled from your existing information, and the recurring reporting set is built and run once on real data, so the first report is seen before handover.

  6. 06

    Weeks 11 and 12: manager briefing and refinement

    The people who will run each process are briefed on their part. We make final corrections from what they find and from the first live use of the documents.

  7. 07

    Week 13: handover

    A handover session covers each document, who owns it and when it is next reviewed. You receive everything in editable form, with a short note on what to look at in the next quarter.

Test normal and exception cases with the process owner, record changes, and agree acceptance before handing responsibility to the internal team.

The tools your team takes over

  • An employee handbook written for your business, with law-dependent points marked for professional confirmation.
  • Five one-page process documents covering joining, attendance and leave, monthly payroll input, probation and confirmation, and exit, each with an owner and a review date.
  • A record of the test run for each process, showing what was tried and what was corrected.
  • A set of standard letters and templates for the stages you actually use.
  • A first set of HR records: employee master, leave record, probation tracker and exit record.
  • A simple reporting set with a short note on how to read and use it.
  • A responsibility sheet showing who in your business owns each document and each step.
  • A handover session with the people who will run the processes.

What your team provides

  • Access to the people who run joining, leave, payroll input, probation and exit today, for short conversations.
  • Your current documents, letters and records, even where they are rough or incomplete.
  • Decisions on policy points that only you can take, such as notice terms and leave entitlements.
  • Real cases from your own team to test each process against, shared in confidence.

Share personal records only after the scope, access and handling arrangements are agreed.

Responsibilities and approvals

The client owns employee records and approves policies, spending and employment decisions. GullyHR's assigned responsibilities are documented in the engagement.

Scope and plan

GullyHR
Proposes the scope, the 90-day plan and the dates for the mid-point review and handover, and records them in writing.
Your team
Confirms the scope, names one point of contact and keeps the review dates in the diary.

Policy decisions

GullyHR
Lists each decision needed, sets out the options and says what other businesses of your size commonly do.
Your team
Makes the decisions promptly, since drafting waits on them.

Drafting

GullyHR
Writes the handbook, process pages, letters and templates in plain language.
Your team
Reviews drafts, corrects facts about how the business really works and approves the final versions.

Testing on real cases

GullyHR
Runs each process on live or recent cases and records what needed to change.
Your team
Provides cases, makes the managers and staff involved available and shares the records needed.

Records and a report on an agreed schedule

GullyHR
Sets up the first records, loads your existing information and builds the report format.
Your team
Supplies employee information, confirms its accuracy and keeps the records updated after handover.

Employment law points

GullyHR
Marks every point that depends on law and coordinates review by a qualified professional where you ask for it.
Your team
Engages its own legal adviser, or asks GullyHR to arrange the coordination, and decides what to adopt.

Measures to agree before work starts

These are measures to track against your baseline, not promised results. Agree definitions, record sources and review dates at the start.

  • Processes written and tested
  • Processes with a named owner
  • Processes with a review date
  • Letters and templates in use
  • Employee records complete
  • Report produced on the agreed schedule
  • Handover session completed

Tools and implementation dependencies

The records and the report can be kept in a spreadsheet you already own, and that is a perfectly sound way to start. If you want them held in software, the employee master, leave record and attendance data can be set up in GullyHR's HRMS software, because the process pages already name the fields, owners and approvals the software needs. That decision is yours and is made after the processes are settled, not before. Nothing in the package requires you to buy software.

Read the full HR foundation package service guide →

Agree the engagement before work starts.

The standard package

The full set described on this page, run over about 90 days against a scope and fee agreed in writing before work begins.

Package with a software follow-on

After handover, the records and processes are set up in HR software as a separately scoped piece of work, built from the pages already written.

Package with ongoing support

After handover, a light monthly arrangement through fractional HR management to run, review and refresh the documents as the business changes.

Package after a process review

For businesses that have already seen a process audit, the package starts from its findings instead of repeating the baseline.

Scope and exclusions

  • The written scope defines the process, templates, testing and handover included. Continuing transaction handling and additional systems work are agreed separately.
  • You already have written processes and want them reviewed rather than rebuilt; the HR Process Audit rates what exists.
  • You need one process fixed, not five; a single process design project is smaller and quicker.
  • You are a very small team not yet hiring regularly; a sector starter pack gives you the basics without the 90-day programme.
  • You want someone to run HR for you rather than hand it over; outsourced HR management does that.
Confidentiality, specialist review and accountability

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Applicability depends on locations, workforce arrangements and the issue under review. Confirm applicable requirements with your qualified adviser before adopting policies or employment actions; this service is not a legal certification.

Employment-law opinions, statutory filings, professional or clinical standards and safety-critical technical decisions require the appropriate qualified professional; include those dependencies in the scope.

Questions before you decide

A handbook is how your habits become shared rules. When the ward sister, a night nurse and a new attendant all read the same page on leave, duty and child-safe conduct, arguments shrink. We write it for your hospital, with your units and shift patterns, and keep it short enough to be read. Your own legal adviser reviews it before issue, because local rules differ.

Discuss this process

Tell us the teams and locations involved, what is happening today and what you want this work to resolve.

Start with your business need

What does your HR team need to solve?

Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

Include your country code, for example +44 or +1. Indian numbers can be 10 digits.

Your details stay private. Privacy policy