Skip to content

Overtime Management in Microsoft Teams

Enterprise client

Built and deliveredHR and peopleCross-industry

In short

How can overtime requests move from paper and chat into Microsoft Teams?

When overtime requests arrive by paper, mail, chat and phone, nobody can say with confidence who worked extra hours, and the data is too poor to report on. The client wanted to digitalise overtime requests but keep its formal PDF template. We delivered an app in Teams with multi-level approvals that prints each request on that template.

At a glance

  • Multi-level approvals in Microsoft Teams
  • Formal PDF template kept
  • One source of truth for overtime

The client

It is an organisation with a reporting structure held in Active Directory and a formal paper template for overtime.

What it was costing them

  • Poor data: the quality of the data collected for reporting was low.
  • File chaos: request files sent by employees were hard to manage.
  • No analysis: there was no way to analyse overtime.
  • Scattered channels: requests came by paper, mail, chat and phone.
  • No evidence: it was hard to show who worked overtime and how people were allocated.

What we built

We built an overtime app in Microsoft Teams with multi-level approvals that follow the organisation and print on the formal PDF template.

  • Easy requests: employees send overtime requests from an app in Microsoft Teams.
  • Approvals that follow the organisation: multi-level approvals follow the structure stored in Active Directory.
  • Action where people already work: custom Adaptive Cards notifications, including built-in forms, let approvers respond in Teams.
  • Work on record: employees report the tasks they carried out during overtime.
  • Reports that answer questions: reports with filtering and sorting.
  • Formal paperwork kept: each request prints on the formal PDF template.
  • Data for analysis: requests export to CSV files for further analysis.

Results

  • Control and evidence of the employees working overtime.
  • Better people allocation.
  • A single source of truth instead of paper, mail, chat and phone.

The risk most teams miss

Approval chains built on the organisation chart break when the chart changes. By month three, reorganisations, absent managers and gaps in Active Directory leave requests stuck. We add delegate and escalation rules, a check for requests with no valid approver, and a regular review of the directory data the app reads.

What we would add today

Improvements we would add on top of what is live.

  • Store requests in Dataverse with row security (employee, manager, HR) and auditing of every approval.
  • Use Power Automate approvals with delegation and escalation, and look up the manager from Microsoft Entra ID.
  • Send approved overtime to payroll through an integration instead of CSV exports.
  • Show overtime by team in Power BI or Fabric, with alerts when a team passes an agreed limit.
  • Generate the PDF from a template in Power Automate and archive it in SharePoint under a retention label.
  • Add a Copilot Studio agent where employees ask about the overtime rules and the status of a request.

Technology

Power Apps, Power Automate, Microsoft Teams, Adaptive Cards, Active Directory, PDF template.

Tell us how overtime requests reach your managers today, and we will tell you how to bring them into one approved record.

Products and capabilities

  • Power Apps
  • Power Automate
  • Microsoft Teams
  • adaptive cards
  • overtime management
  • multi-level approvals

Related use cases

HR and people

Have a Microsoft project in mind?

Tell us what you need built, fixed or supported. A senior consultant replies within one business day.