Skip to main content
GullyHR

HR process design · Banks

HR Foundation Package for Banks

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 Banks

What this looks like in your business

For a bank, the Foundation Package means writing down the basics that branch life keeps in people's heads. A newly licensed bank, a small cooperative or a business correspondent network runs on one manager's memory of how transfers, cover and targets are handled. An owner or chief executive reaches for the package when branches multiply, a first transfer causes an argument, or head office cannot say who approved what. GullyHR writes a handbook, five short processes, letters and first records around the branch, the counter and the zone, tests each one with your staff, and hands them over.

Where a young bank has no written rules

A bank grows by adding branches, and each new branch arrives with a manager who has brought habits from somewhere else. One manager lets tellers swap counters freely. Another insists on written approval. One treats a sales target as a conversation and another as a threat. At head office there is no handbook to settle which is right, so every dispute becomes a personal ruling. Transfers are the sharpest case, since a posting can end a person's career and nothing says how much notice, explanation or appeal they should expect. Promotion has the same gap: the top seller gets the branch and no one tells them what a manager must now do. Without written basics, the first serious complaint becomes a precedent by accident. The Foundation Package is meant for exactly this stage, when the bank is real enough to need rules but too young to have an HR department that writes them. It turns the habits of the best managers into a shared standard that every branch can follow.

The first documents a bank should have

GullyHR starts by asking who does what across the branch roles: manager, teller, customer service officer, relationship officer, credit processor and back-office clerk. The handbook is then written for those roles, not borrowed from another sector, with plain wording on cover at the counter, behaviour with cash and customer records, targets and how they are explained, and how transfers are communicated. Five core processes follow as one-page documents. Joining, so a new teller has access, training and a named buddy before the first shift. Branch cover, so a short branch has a known route to borrow staff. Transfer, with the reason, notice and conversation recorded. Target setting, split by role. Exit, so keys, access and customer files are handed over on a checklist. Standard letters sit beside them: offer, appointment, transfer order, warning and exit. A first employee record and a simple monthly strength report complete the set. Your legal adviser reviews the wording before anything is issued. Where the bank already has a practice that works, such as one manager's careful cover routine, GullyHR keeps it and writes it down rather than replacing it.

Testing the transfer process with real branches

Suppose the bank has just opened its twelfth branch and a relationship officer in an older branch is asked to move there. Before the process is handed over, GullyHR tests it with the zonal manager and two branch managers. The one-page transfer process asks for the reason, the date the person is told, the date they move, who covers the vacated desk and what the person was promised about their grade. The test turns up two problems. The zonal manager has no place to record the conversation, and the draft letter does not say who the person speaks to if they object. GullyHR adds a short conversation note to the employee file and names the head of HR as the contact for objections. The letter is rewritten and tested again on a second, invented posting. The owner then decides one real question: whether a transfer order may be issued before the conversation or only after it. That ruling is written into the process. Each document is kept short enough that a branch manager reads it once and uses it.

Who keeps the basics alive after handover

A foundation set that nobody maintains decays within a year, so handover names owners. Head-office HR holds the handbook and the five processes and decides when a branch practice should change them. Branch managers use the letters and templates unaided and keep the employee record for their own branch current. Zonal managers send the monthly strength report on the agreed date. The bank's accountant or payroll provider continues to handle pay, and GullyHR does not run it. The owner keeps every decision on people, pay, grades and transfers, as well as any legal question about banking conduct or employment, which your own adviser confirms. Scope and fee are agreed in writing before the work starts, and you receive the documents in editable form so they stay yours. If the bank later wants help running these routines each month, that is a separate conversation about ongoing management and not part of the package. The process is then issued with the corrected letter, and the zonal managers are briefed on it in one short meeting. Every later transfer uses the same page.

The first weeks

  1. 01

    Hold a half-day session with the chief executive, head-office HR and two branch managers to list what is currently decided by habit.

  2. 02

    Draft the handbook sections on counter cover, cash and customer record behaviour, and target explanation, then read them aloud to a teller.

  3. 03

    Write the five one-page processes: joining, branch cover, transfer, target setting and exit, each with a named owner.

  4. 04

    Test the transfer and exit processes on an invented posting and an invented resignation, then rewrite wherever staff hesitate.

  5. 05

    Hand over the letters, first employee record and monthly strength report, and send the handbook to your adviser for review.

The operating context

Build the minimum HR structure in a usable sequence

A bank is a network of small branches handling other people's money daily, with staff rotated between them. This covers the people side of a network where every counter must stay covered and honest.

Branch managersTellers and customer service officersRelationship and sales officersLoan processing and credit staffOperations and back-office staffZonal and regional managers
Workplace scene for Banks: Branches, Transfers and Customer Trust

The decision to work through

Prioritise employee records, essential policies, role ownership and recurring processes around the starting workforce. Workforce to consider: Branch managers, Tellers and customer service officers, Relationship and sales officers.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: Rotation protects control, but a posting to another town at short notice with no reason pushes a strong officer to resign.

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.

  • Private sector bank branches
  • Public sector bank branches
  • Regional rural banks
  • Cooperative banks
  • Small finance banks
  • Business correspondent networks

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 copied handbook describes another bank's branches, grades and approval chain, so your managers stop trusting it the first time it contradicts what they do. GullyHR writes yours from your own roles and routines and tests each process with your staff. The result matches how a branch of six actually works, and your adviser reviews it before issue. Your managers then see their own work reflected.

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