TechAppForce

Approvals and back office

Leave and HR requests

Leave requests, balances and new-starter onboarding in one place, with manager approval.

Book a demoSee how it runs
  1. Requested
  2. Manager reviewApproval
  3. Approved
  4. TakenDone
  5. CancelledSide exit
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Leave is booked by email and tracked in a spreadsheet only HR can open, so nobody trusts the balances. New starters arrive before their accounts, equipment and paperwork are ready, because each step lives with a different person.
Who feels it: HR teams, line managers and every employee who asks for time off

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. An employee books a week offAt a mid-sized engineering consultancy, an analyst requests five days in August. The form shows he has eight days left.
  2. His manager checks the calendarApprove or rejectThe request is in his manager’s inbox. She opens the team calendar, sees nobody else is away that week and approves.
  3. The balance updatesThe approval updates his balance to three days and notifies him in-app and by email.
  4. Meanwhile, a new starterHR creates an onboarding case for a designer starting on Monday. Tasks appear for IT, facilities and her manager, each with a due date.
  5. Nothing missed on day oneOn Thursday, IT gets a reminder that the laptop task is still open. By Monday every task is done.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 4

  • Leave request6 fields + history, files, comments
  • Leave balance5 fields + history, files, comments
  • Onboarding case4 fields + history, files, comments
  • Onboarding task4 fields + history, files, comments

Stages 5

  1. Requested
  2. Manager reviewdecides
  3. Approved
  4. Taken
  5. Cancelled

Automatic 4

  • CodeA post-approval workflow updates the leave balance, or a C# record hook does it where the rules are specific to you
  • NotifyHR is notified by email when a new onboarding case is created
  • WorkflowCreating an onboarding case creates the standard task list for IT, facilities and the manager
  • ScheduleA weekly scheduled workflow reminds owners of onboarding tasks that are due

Screens and reports 6

  • Leave request form that shows the current balance
  • Team calendar on the scheduler component, showing who is away
  • Kanban of onboarding tasks by owner
  • Employee view with requests, balances and history
  • Leave taken by team and type, in Excel, for payroll each month
  • Onboarding checklist as a PDF for the new starter’s manager
Who approves, in detail

Leave goes to the employee’s reporting manager. Requests longer than a set number of days also need the HR role. A reminder goes out if the manager has not decided in two working days, then the request escalates to their own manager.

When the rules change

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Lifecycle: leave request

Leave types
Unchanged: Annual · Sick · Unpaid
Added: + Parental · Study
Approvals
Added: + HR review above 10 days
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.