Use cases

Automate leave requests

Leave requests are the process every company has and almost nobody has formalised. They live in emails, a shared spreadsheet and the manager's memory. InProcess turns them into an explicit flow, without forcing a full HRIS on a team that does not need one.

What goes wrong today

  • Requests arrive by email, chat or in person, and some get lost.
  • Managers approve without seeing who else is away on the same dates.
  • HR re-enters approved leave into a spreadsheet, with the errors that implies.
  • Employees chase because they cannot tell whether their request was seen.

The process you get

  1. 1

    The employee submits a request

    Start and end dates, absence type, optional comment. The form rejects inconsistent dates before submission.

  2. 2

    The manager approves or rejects

    They receive the request in the app or by SMS, with team context, and decide in one action. A rejection requires a reason.

  3. 3

    HR is notified

    Each approval triggers an HR notification and writes to the schedule, with no re-entry.

  4. 4

    The employee is informed

    The answer comes back automatically, with the reason if rejected. No more chasing.

What changes

  • Every request follows the same flow, including last-minute ones.
  • Managers decide with the context in front of them rather than from memory.
  • HR works on structured data instead of transcribing emails.
  • Absence history is traceable, which makes audits straightforward.

Other common processes

What is InProcess?

You could have this process live today

Describe it in a few sentences, AI builds it, you approve before it goes live.