Skip to content
HRby R&D COPILOT, home
Request a quote

01 — People platform

People operations, without the chasing.

Employee records, leave, onboarding, reviews and exits in one place. Each request reaches the right manager, and every decision stays on the employee’s file.

Request a quote See how setup works

One-off setup, monthly licence, hosted in the EU, supported by the team that builds it.

RDCopilot HR: an employee file open on the Leave tab, with balances and the approvals inbox
Leave request Example data
Ana CostaCustomer support Pending
Leave type
Annual leave
Dates
14–16 Oct 2026
Days
3 working days
Available
12 of 21 days 3 days held until you decide
Approver
Marco Bianchi (manager)

HR · Example data

What do you want to sort out first?

02 — A year in the record

Hire, onboard, time off, review, exit. One record carries it all.

A year in one employee’s file, screen by screen. Every screen is the product, shown with example data.

  1. 01 Hire

    Candidates move through your own stages.

    Positions, applications and interview notes in one pipeline. The person you hire moves straight into onboarding.

    RDCopilot HR: a hiring pipeline for one position, with candidates in the applied, screening, interview and offer stages

  2. 02 Onboard

    The first week is planned before day one.

    Every task has an owner and a day: HR, the manager, IT or a buddy. Progress is visible to HR and the manager.

    RDCopilot HR: first-week onboarding plan with an owner and a day for every task, one task completed

  3. 03 Time off

    Leave is asked once and answered once.

    The team calendar shows approved and pending leave side by side, and balances update the moment a request is approved.

    RDCopilot HR: team leave calendar with approved and pending leave side by side

  4. 04 Review

    Reviews start from what was agreed.

    Objectives, key results and feedback rounds with your own questions. When review time comes, the history is already on the file.

    RDCopilot HR: a yearly review with an objective, key results and a feedback question

  5. 05 Exit

    The last day leaves nothing loose.

    Handover, the exit conversation and returned equipment are ticked off in one list, and the record stays complete after the person leaves.

    RDCopilot HR: an exit in progress, with the notice period, handover checklist and assigned equipment to return

Example data

03 — Try it

Pick a moment and use the screens yourself.

Pick a moment in someone’s time with you. The record stays the same; only the work around it changes.

A first week that is planned before the first day.

Build an onboarding plan per role. Each task has an owner — HR, the manager, IT or a buddy — and a day it is due, so nobody wonders who was meant to set up the laptop.

  • Onboarding plans per role
  • Named owner for every task
  • Progress visible to HR and the manager
Onboarding plan
Monday
Tuesday
Wednesday
Thursday
Friday
Selected task Walk through the workflow Prepare the information needed and note what needs clarification before moving on.
Task owner
Onboarding buddy
When
The first week · Tuesday
0 of 15 steps complete

Choose a role, explore the weeks, and open a task to mark it complete. Your changes stay in this tab.

See all modules

04 — Time off

Who is off next week? Now it is one glance.

Employees check their balance and ask for days off from their phone’s browser. The team calendar shows approved and pending leave side by side, so a manager can say yes without checking a spreadsheet first. Balances update the moment a request is approved, and attendance sits next to it.

The employee’s view · Example data

Hi, Ana

Annual leave 2026

Before she sends her 14–16 Oct request

Entitlement
21
Taken
6
Pending
0
Available
15
Your requests this year Annual leave · 3 days3–5 Jun Annual leave · 3 days18–20 Aug Upcoming Public holiday25 Dec · Christmas Day
The manager’s view · Example data

Support team · October 2026

  • Approved
  • Pending
Ana Costa Marco Bianchi Julia Weber Tom Becker Sofia Lind
Select a leave bar to see its details.
Team leave, 12–23 October
PersonTypeDatesDaysStatus
Ana Costa Annual leave 14–16 Oct 2026 3 days Pending
Julia Weber Annual leave 19–21 Oct 2026 3 days Approved
Tom Becker Annual leave 22–23 Oct 2026 2 days Approved
Sofia Lind Sick leave 12 Oct 2026 1 day Approved
Marco BianchiNo leave in these two weeks

  1. Ana requests 3 days

    She picks the dates and leave type; her remaining balance is shown before she sends.

  2. Her manager decides

    The request lands with the manager set on her file, with the team calendar beside it.

  3. HR keeps the record

    The decision, the date and who made it stay on Ana’s file. Payroll can pick it up from there.

Leave rules — types, entitlements, carry-over, approvers — are set up with you during implementation.

05 — Modules

Eight modules around one employee record.

Which ones you start with is agreed in your scope.

HR workspace Signed in as HRExample data

Employees · Customer support

Julia WeberSupport specialist · Customer support Active
Position
Support specialist
Department
Customer support
Reports to
Marco Bianchi
Start date
3 Mar 2025
Contract
Full-time, open-ended
One employee file, with every module around it. The modules below are the tabs and lists you see here.

  • Employee records

    One file per person, with the access each role needs.

    • Personal and job details
    • Documents with expiry reminders
    • Org chart and reporting lines

  • Leave

    Requests, approvals and balances without email threads.

    • Leave types and entitlements
    • Manager approval
    • Team calendar

  • Attendance

    Time worked, next to time off.

    • Daily start and end times for each person, kept as the working-time record local labour rules ask for
    • Worked hours and overtime
    • Validation by the manager

  • Onboarding

    A planned first week for every new colleague.

    • Plans per role
    • Tasks with owners and dates
    • Progress for HR and manager

  • Recruitment

    Positions, candidates and interviews in one pipeline.

    • Your own hiring stages
    • Interview scheduling
    • Hired candidates move straight into onboarding

  • Performance

    Objectives, check-ins and feedback over the year.

    • Objectives and key results
    • Feedback rounds
    • Review history

  • Offboarding & assets

    Exits handled carefully, equipment accounted for.

    • Exit stages and tasks
    • Asset assignment and return
    • Complete record after leaving

  • HR helpdesk

    Questions to HR, answered and tracked.

    • Requests by type
    • Assigned to the right person
    • Status the employee can see

Payroll is a separate RDCopilotOS module, and REGES is the localisation module for employers in Romania. See how they connect Who sees what

06 — Access

Who sees what is decided once, not every time someone asks.

Access follows the role a person has. An employee sees their own file, a manager sees their team, HR sees what HR needs. You agree the rules with us, and we test them with real scenarios before go-live.

Show access for
Example configuration. Your rules are agreed during setup.
AreaEmployeeManagerHRAdministrator
Personal details Own only—EditEdit
Job and contract details Own only (view)Team (view)EditEdit
Documents Own only—EditEdit
Leave requests Own onlyTeam (approve)EditEdit
Attendance Own onlyTeam (validate)EditEdit
Performance reviews Own onlyTeamViewEdit
Users and roles ———Edit
Example data Example configuration. Your rules are agreed during setup.

07 — Connections

HR keeps the people record. Neighbouring products do the rest.

What leaves HR, and where it goes
No.FromToWhat movesWho owns it
01 HR Payroll Approved leave, validated attendance, job changes HR prepares and approves the inputs; Payroll does the calculation.
02 HR REGES For employers in Romania: new contracts, changes, suspensions and terminations HR keeps the record; the REGES localisation module handles the filing.
03 HR Reports Headcount, leave and turnover figures HR is the source; Reports puts them next to the rest of your business figures.
04 HR Integrations Data another system you already use needs Scoped with you and built by our team in RDCopilot Integrations.

RDCopilot HR does not calculate payroll and does not file with national employee registers itself. Each connection above is defined in your quote, so you know exactly what moves where.

Each person signs in to the HR workspace with their own account, and the role HR gives them decides what they see.

Part of RDCopilotOS

HR is one module of the operating system for your company.

RDCopilotOS connects operations, finance, people, customers, data and compliance. Start with HR and connect the modules you need, with every handoff defined in your quote.

Explore RDCopilotOS All products and services

08 — Implementation

From your spreadsheet to a working HR system, step by step.

Every company starts from a different place, so timings are set in your quote. The steps are always the same.

  1. Step 1

    Scoping call

    We look at how you handle leave, onboarding and records today, and agree which modules you start with.

    Scoping call · agendaExample data
    1. How leave is asked for and approved today
    2. Where employee data lives now: files, folders, spreadsheets
    3. Who approves what, team by team
    4. Which modules you start with
    5. What has to reach Payroll, local registers or other systems

    You leave with: a scope, a timeline and a quote

  2. Step 2

    Your structure

    Departments, job positions, leave types, entitlements and approvers are set up to match how you actually work.

    Leave type · Annual leaveExample data
    Entitlement
    21 working days (your policy, above the legal minimum)
    Carry-over
    unused days move to next year, within your policy and local law
    Counts
    working days, public holidays excluded
    Approver
    Line manager on the employee file
    Visible to employee
    Yes
    Agreed with you · not a default

  3. Step 3

    Your data

    We import your employee list and opening leave balances from the files you already keep, then check them with you.

    Import preview · employees.xlsxExample data
    Column in your fileHR fieldStatus
    Full name Full name Mapped
    Start date Date joined Mapped
    Team Department Mapped
    Leave days left Opening leave balance Check with you
    Personal phone — Not imported

    42 rows read · 1 column to check with you

  4. Step 4

    Access and a dry run

    Roles are set and tested with real scenarios: a request, an approval, a new joiner, a leaver.

    Dry run · rolesExample data
    • Ana requests 3 days Employee Reached Marco
    • Marco opens Julia’s documents Manager Blocked as expected
    • HR adds a new joiner HR Plan created
    • Tom’s exit is closed HR To run with you

  5. Step 5

    Go-live and support

    Short sessions for HR and managers, then ongoing support from the team that builds the product.

    First week liveExample data
    Day 1
    Session for HR: records, leave rules, exports
    Day 2
    Session for managers: approvals and the team calendar
    Day 3
    Employees sign in and send their first requests
    Ongoing
    Support from our team
    Dates set in your timeline

09 — Pricing

Setup once, then a licence per month.

One card: what happens before go-live, and what keeps running after it.

Once · Before go-live

One-off setup

Scoping, configuration of your structure and leave rules, data import, role testing and training.

Set in your quote, according to the scope we agree and the state of your current data.

Go-live

Every month · From go-live, month by month

Licence per month

Hosting in the EU, updates, scheduled backups and support from our team.

The monthly licence is set in your quote, according to the scope we agree.

What the licence covers

  • EU hosting, location in your quote
  • Updates
  • Scheduled backups, frequency agreed in your quote
  • Support from the team that builds it
  • Your data, exportable

Exact terms are written into your quote.

Request a quote

Not sure what to include? Book a walkthrough first.

10 — Questions

Straight answers on payroll, registers and your data

Does RDCopilot HR calculate salaries?

No. Salaries are calculated in RDCopilot Payroll. HR keeps the approved leave, attendance and job changes that Payroll needs, and the handoff between the two is defined in your quote.

Does it file employee contracts with national registers?

Not by itself. HR is where the employee file lives; filing goes through a localisation module for each country. For employers in Romania, the RDCopilot REGES module files to REGES-ONLINE, the national employee register.

Where is our data hosted, and who owns it?

On EU infrastructure, at a location written into your quote. The data is yours: you can export it, and we agree backup frequency and retention with you before go-live.

We keep everything in Excel today. Can we move it over?

Yes, that is a common starting point. We prepare the import of your employee list and opening leave balances from your files and check the result with you before anyone uses it.

How long does setup take?

It depends on how many people you have, which modules you start with and how tidy the current data is. You get a timeline with your quote, before you commit.

Can we start with leave only?

Yes. You can start with employee records and leave, then add onboarding, reviews or recruitment later. The monthly licence is set in your quote, according to the scope we agree.

Can employees use it from their phone?

The employee views are responsive and work in a phone browser, without installing anything. Which actions employees can take themselves is agreed in your scope, and we show you the views before you decide.

11 — Next step

Tell us how HR works for you today.

How many people, which requests take the most time, and where the data lives now. We come back with a scope, a timeline and a quote.

Request a quote

From idea to implementation

Guides for your workflow

© 2026 R&D COPILOT Made in EU Contact form