Services

Staff Requests and Approvals

Vacations, permissions, missions, advances and overtime — on an approval plan you design, with a record of every decision.

Updated just now
Overview

Every office runs on requests: leave, an hour off, a trip to a court in another governorate, an advance, overtime, a day working from home. In most practices these are asked for in person or over WhatsApp, approved by whoever was available, and remembered by nobody. When a dispute arises months later, there is no record of who agreed to what.

LexPro turns each of them into a request that follows a path you designed, and keeps the record of every step.

01

Seven kinds of request, one system

  • Vacations — with leave balances and attachments.
  • Permissions — the hour or two away that otherwise goes unrecorded.
  • Outside missions — a hearing in another city, a registry visit, a client meeting.
  • Money requests — an advance or a cash float, routed for approval before it is paid.
  • Overtime — recorded as a request rather than claimed afterwards.
  • Work from home — asked for and answered in writing.
  • Support requests — what a member of staff needs from the office itself.
02

An approval plan you design

Approval is not a single yes or no. You build workflows with ordered steps, and attach a workflow to each type of request — so a day’s leave can be settled by a line manager while an advance climbs to a partner. Workflows can be switched on and off without being deleted, and the plan is visible as its own screen rather than buried in someone’s head.

03

The requester sees the path before sending

Before a request is submitted, the system shows who will be asked to approve it and in what order. Nobody has to guess where their request will go or chase it blindly — the route is visible from the start.

04

Clashes are caught, not discovered

Leave requests are checked for overlap as they are made, so two people asking for the same week is something you find out before approving, not on the morning a hearing has nobody to attend it.

05

Leave balances that are actually kept

Each member of staff has a balance, and leave is drawn against it. The balance is a record rather than an argument, and it is visible to the person whose balance it is.

06

Status, history and a log

Every request carries its state — pending, approved, rejected, cancelled — and every decision is written to an approval log with who decided and when. Each person can see their own history of requests, and managers can see the requests of their staff. “Who approved this?” always has an answer.

07

Attachments where they are needed

A medical certificate, a travel document, a receipt — attachments travel with the request, so the evidence sits with the decision rather than in an email somebody has since deleted.

08

A report on the whole picture

A staff requests report shows what was asked for across the office over a period — who took what leave, how much overtime was approved, which advances went out. It is the view a managing partner needs and rarely has.

Part of the integrated LexPro platform

Every module works with the rest of the system: data is entered once and appears wherever you need it, with no duplication.

All services