Techseria Roster by the numbers

  • Metric 01
    10
    Built-in hard rules
    Never broken. Shortfalls are reported, not hidden
  • Metric 02
    8
    Leave-ballot scoring rules
    Transparent, defensible leave decisions
  • Metric 03
    7
    Roster reports
    Coverage, gaps, fairness, ballots and more
  • Metric 04
    180
    Staff per department
    Designed for hospital departments of this size across sites

A hospital roster is a patient-safety document. Spreadsheets were never built for it.

Rostering 50 to 200 pharmacists, technicians, nurses and allied-health staff across outpatient, inpatient, night cover and several sites is one of the hardest admin jobs in healthcare.

The Challenge

Days of work every month

Planning takes days, depends on one or two senior clinicians, and pulls them away from patients to wrestle with a spreadsheet.

Unsafe gaps found too late

Too little rest after nights, too many consecutive days, an unqualified person on a service point, or a shortfall discovered on the day itself.

Unfair rosters and burnout

The same people get the nights, weekends and public holidays, festive leave feels like a lottery, and good staff leave.

What Techseria Roster delivers

Safe by design

Staffing, credential, leave, rest and fatigue rules are mathematical constraints the engine cannot break, not reminders for a planner to remember.

Fair and measurable

Nights, weekends and duty are shared using each person's history, and the Fairness Summary shows exactly how.

One platform, no re-keying

Approved leave blocks the roster and published shifts feed attendance and payroll on the same employee record.

Explained and auditable

Every unfilled slot is reported with a reason and a remedy, and every change is on the audit trail.

How It Works

From leave ballot to payroll in seven steps

One connected flow replaces the spreadsheet, the leave email chain and the payroll reconciliation.

  1. 01
    Step 1

    Plan leave fairly

    Run a leave ballot for each six-month window. Ranked preferences, weighted rules, capacity limits and a waitlist allocate popular and festive leave, then create HRMS leave records.

  2. 02
    Step 2

    Define demand

    Roster templates describe each day's slots: role, shift, minimum headcount, minimum seniority and required skills.

  3. 03
    Step 3

    Generate

    One click runs the optimisation engine and builds a full roster that satisfies every hard rule and shares duty fairly.

  4. 04
    Step 4

    Expose gaps

    The Gap Report names the date, slot and shortfall with a suggested fix. Nothing is hidden.

  5. 05
    Step 5

    Review and approve

    A built-in workflow runs Draft, AI Proposed, Under Review, Approved, Published and Acknowledged with role-based sign-off and a full audit trail.

  6. 06
    Step 6

    Publish to HR

    Published rosters create native HRMS Shift Assignments that drive check-in, attendance, overtime and payroll.

  7. 07
    Step 7

    Handle change

    Late leave or a swap raises an exception, and a rebalance proposal shows a before and after diff for one-step approval.

Core Capabilities

Everything a safe, fair roster needs in one system

Five pillars set Techseria Roster apart from a scheduling grid.

  • Hard-rule optimisation engine

    Builds the whole department roster in one run using Google OR-Tools CP-SAT, with ten hard rules that are never broken.

  • Skill and credential-based rostering

    Only qualified, in-date, sufficiently senior staff are placed in each slot, and expired credentials stop applying automatically.

  • Fair leave ballot

    Transparent allocation of popular and festive leave with scoring rules, capacity caps, a waitlist and manager override.

  • Native HRMS and payroll integration

    One employee, leave, shift and attendance record. The roster you plan is the roster you pay.

  • Exceptions and rebalancing

    Sick leave and swaps raise exceptions automatically, with before and after proposals for quick approval.

  • Governance and compliance

    Approval workflow, audit trail, role-based and row-level access and PDPA-aligned retention controls as standard.

Find your setting

Techseria Roster adapts to the way each type of healthcare organisation actually rosters.

Hospital pharmacies

Outpatient and inpatient dispensing, satellite and ward pharmacies, night and on-call cover and clinic commitments.

Learn more

Retail and community pharmacy chains

A qualified pharmacist on every outlet's opening hours, with staff shared across nearby outlets.

Learn more

Hospitals and clinical departments

24x7 cover for nursing units, laboratories, radiology and therapy teams with credential-based deployment.

Learn more

Healthcare groups and polyclinics

Several hospitals or centres, each with local rules, managed under one group structure.

Learn more
Value For Every Role

Everyone who touches the roster gets something back

Techseria Roster is designed around the people who plan, approve, work and pay from it.

  • Heads of pharmacy, nursing and departments

    Safe coverage on every shift, credential compliance and a workforce that stays, with decisions backed by the coverage heatmap and gap report.

  • Roster planners

    Days of spreadsheet work become hours of review and approval. Manual edits, overrides and swaps always remain possible.

  • Operations directors and hospital COOs

    Coverage visibility across sites, less agency and overtime spend and fewer escalations.

  • HR and payroll

    Rosters, leave, attendance and pay agree because they share one record, with an audit trail for compliance evidence.

  • Pharmacists, nurses and allied-health staff

    A fair share of nights and weekends, a fair chance at festive leave and early visibility of their schedule on their phone.

  • IT, compliance and data protection

    Open-source platform, deployment on your terms, role-based and row-level access, audit evidence and a full API.

Why a complete platform

A standalone roster tool is one more system to integrate.

Techseria Roster extends Frappe HRMS and ERPNext, so the employee, leave, shift and payroll records you already depend on are the same ones the roster uses.

Swipe horizontally to view comparison
Feature / CapabilityStandalone rostering toolTechseria Roster on Frappe HRMS and ERPNext
Employee listA separate list that drifts from HR One employee master shared by every module
LeaveImported or keyed twice Approved leave is a hard rule automatically, and ballot outcomes create HRMS leave
PayrollExports with monthly reconciliation Published shifts are native HRMS Shift Assignments feeding attendance and payroll
Cost modelPer-user subscription that grows with headcount Open-source foundation with no per-seat platform licence
DataVendor-hosted On-premise, private cloud or managed hosting, owned by you
AuditA separate trail per system One audit model across HR, roster and finance
Beyond rosteringMore products for recruitment, appraisal, expenses and accounting Recruitment, onboarding, performance, training, expenses, payroll and accounting are included
Proof You Can Inspect

Engineering rigour behind every roster

Healthcare rostering demands confidence. Here is what stands behind it.

  • Industrial-grade optimisation

    Google OR-Tools CP-SAT with a fixed random seed, so the same inputs always produce the same roster.

  • Transparency built in

    Gap Report with remedies, on-demand explanation of unfilled slots, a fairness report and a full audit trail.

  • Built for healthcare

    Designed around a large public-hospital pharmacy department of about 180 staff across multiple sites and roles.

  • Tested

    More than 150 automated test files covering about 1,300 test cases across the application and engine.

  • Upgrade-safe

    Extends HRMS only through supported extension points and never modifies HRMS core, so platform upgrades stay clean.

  • Operations runbooks

    Documented runbooks for backup, disaster recovery, monitoring and security review.

Built on an open, proven stack

Open-source Frappe, ERPNext and HRMS with an OR-Tools optimisation engine and a modern React roster app.

Frappe Framework
ERPNext
Frappe HRMS
Google OR-Tools CP-SAT
Frappe Framework
ERPNext
Frappe HRMS
Google OR-Tools CP-SAT
React 18 + TypeScript
Python
MariaDB
Redis
React 18 + TypeScript
Python
MariaDB
Redis

Upgrade-safe by design

Extends HRMS through custom fields, document events and fixtures. HRMS core is never modified.

Deploy your way

On-premise, private cloud or managed hosting, with the customer owning the data.

Dedicated solver queue

Optimisation runs as a background job that can have its own worker queue.

Integration-ready

Full REST/RPC API, webhooks, bulk APIs and iCal export.

From first conversation to first roster

  1. 01
    Phase 01

    Discover pain areas and KPIs

    We start with your rostering pain, goals and measures of success: planner hours, gaps, overtime, fairness and leave disputes.

  2. 02
    Phase 02

    Configure your reality

    Load your staff, skills, credentials, shift types, sites and demand templates.

  3. 03
    Phase 03

    Pilot on a real month

    Run the optimiser on actual data and compare with your current roster before you commit.

  4. 04
    Phase 04

    Go live and track outcomes

    Roll out department by department and track the outcome against the KPIs we agreed.

Faq

Frequently Asked Questions

See Techseria Roster build your next roster

Book a demo and we will run the optimiser against a real month of your staff, skills and rules, so you can compare it with the spreadsheet.