Skip to main content
GullyHR

HR process design · General hospitals

HR Foundation Package for General 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 General hospitals

What this looks like in your business

A hospital with no real HR system has a stack of appointment letters, a leave notebook at the nurses' station and a great deal held in the memory of the matron or the office superintendent. The Foundation Package is for the owner who has seen that this works until the matron retires, a casualty night goes wrong, or a new ward opens and nobody knows whose rules apply. It sets down the basics once, in the hospital's own words: a handbook, five core processes, letters, first records and a simple report, all tested on the floors where they will be used.

Why basics are missing in busy hospitals

In a general hospital the work arrives first and the paperwork follows, if at all. A staff nurse is taken on because the ward is short that week. An ambulance driver starts on a handshake with the owner. A ward attendant is told the rules by the attendant standing next to her. Within a year the hospital has twenty people working to twenty slightly different understandings of leave, night duty, shift swaps and what to do when a relative shouts. The outpatient mornings leave no time to stop and write anything down, and casualty nights teach staff to improvise. Long-serving employees carry the routines, which makes the hospital strong and fragile together. When a dispute comes, there is nothing to point to, and the owner decides case by case, which staff read as favouritism. The missing basics are not exotic. They are a handbook that says how things are done here, a handful of agreed processes, letters that say the same thing to every joiner, and a record of who works where on what terms.

What gets built first, and in what order

GullyHR would start with the questions that block everything else: who approves a joining, who owns the roster for the wards, who decides a leave dispute, and who records an incident when a relative abuses a nurse. Those answers fix the owners of the five core processes, which are written as one-page documents in plain language that an attendant can read at the nurses' station. The handbook follows, drawn from how the hospital really runs and from what the owner decides on the open points, not copied from another institution. Standard letters come next, for staff nurses, pharmacy assistants, drivers and housekeeping, so a manager can issue one without calling the owner. The first records are set up last: a personal file for each person, a leave register and a simple monthly report. Every process is tested on a real ward or desk before handover, and staff who use it are asked what did not work. Where a step cannot be tested on a ward, it is tested at the front desk or the pharmacy counter instead, because a process that only works in the meeting room is not finished. The owner sees each document before it is handed over, and each is signed off by the person who will own it.

A charitable hospital writes its first handbook

Suppose a charitable trust hospital has run for thirty years on the goodwill of its sisters and a long-serving administrator. The trustees want a handbook before opening a new surgical wing. GullyHR sits with the matron, the administrator and a senior attendant for a morning. The question of shift swaps is the first snag: nurses have swapped by agreement with the sister for years, but one swap led to an empty ward at change of shift. The matron proposes that every swap is written on a sheet and countersigned by both nurses and the sister before the shift. The administrator worries that attendants will not use a form. A senior attendant suggests a tick-sheet kept on the ward board. They test it for two weeks on one ward. The nurses use it, the attendants use the tick-sheet, and the sister reports fewer gaps at handover. The trustees then approve it as policy. The handbook entry is written from what actually worked, in the words the matron used, and the process joins the five that are handed over.

Owners, records and what the trust keeps

Before handover, each process needs a named owner and a named stand-in, because a hospital cannot wait for one person to return from leave. The matron or nursing superintendent would own rosters and leave for nurses and attendants. The front office supervisor would own registration clerk attendance. The pharmacy in-charge would own pharmacy records, and the administrator would own personal files and standard letters. Handovers need a place to be written: a shift-change note for the ward, a duty manager's log for casualty nights, and one register for incidents involving patients' relatives. GullyHR hands over the documents, trains the owners on how to use them and stays available for questions during the agreed period. What remains with the owner or trustees is every decision of substance: pay, who is employed, what the policy actually says on contested points. Legal wording in the handbook and the letters goes to your own adviser before issue, and a new wing, ward or service is a decision for you, not for the package. Questions that come up in the first weeks are noted and answered in writing, so the same doubt is not raised ward by ward.

The first weeks

  1. 01

    Hold a first meeting with the owner, matron and administrator to settle who approves joinings, rosters, leave and incident records.

  2. 02

    List every current employee by ward, desk and role, and check which personal files hold a letter and which hold nothing.

  3. 03

    Draft the first process, starting with joining, as one page and read it aloud to a staff nurse and a ward attendant.

  4. 04

    Write the handbook sections on shifts, leave and conduct with patients' families from the owner's decisions, then test them on one ward.

  5. 05

    Issue the first standard letters and open the leave register, then review with the matron what staff found unclear.

The operating context

Build the minimum HR structure in a usable sequence

A general hospital treats whoever walks in, so its work is unpredictable. Casualty, the outpatient hall and the wards need steady hands every hour, and most of those hands belong to attendants, nurses and support staff.

Casualty medical officersStaff nursesWard attendantsOutpatient registration clerksPharmacy assistantsAmbulance drivers
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: Casualty medical officers, Staff nurses, Ward attendants.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. Confirm which records are held by the managers of Casualty medical officers, Staff nurses, Ward attendants.

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.

  • Taluk and small-town private general hospitals
  • Hospitals run by one or two doctors with an in-house casualty
  • Charitable trust and mission general hospitals
  • Hospitals empanelled under state and central health schemes
  • Industrial-area hospitals serving factory workers and ESI beneficiaries
  • Neighbourhood hospitals in city wards with a ground-floor pharmacy and lab

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

The people already running the floors: the matron, the pharmacy in-charge, the front office supervisor and the administrator. Each is named as owner of one process and trained on its one-page document before handover. GullyHR does not leave a folder on a shelf. It stays available for questions for the agreed period, so the first real leave dispute is settled using the document.

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