HRManagement365 powered by Hubdrive · FaceClocking Add-on

AI Facial Recognition Clocking In System for Time, Attendance & Projects

Replace traditional clocking in machines, cards and shared PINs with an AI facial recognition clocking system that can run on a mobile phone or shared tablet.

FaceClocking records clock in, break and clock out events using Microsoft Power Apps, Dataverse and Azure AI. Run it as a standalone employee clocking in system, integrate it with another business application, or connect it using two-way synchronisation with HRManagement365 powered by Hubdrive.

Mobile clocking Shared tablets Facial recognition Project time recording
FaceClocking
✓ Employee recognised
Clock In
Start Break
End Break
Clock Out
No proprietary clocking machine required Use a suitable mobile phone or shared tablet.
A modern alternative to clocking in machines

Looking for a clocking in machine or staff time and attendance system?

Traditional employee clocking systems often depend on dedicated hardware, clock cards, fobs, fingerprint readers or PIN numbers. FaceClocking uses a mobile phone or shared tablet as the clocking point and identifies the worker using AI facial recognition.

Traditional clocking in machine

Dedicated attendance hardware

  • Clock cards or key fobs
  • PIN numbers
  • Proprietary clocking terminals
  • Separate attendance databases
  • Additional integrations to maintain
→
FaceClocking

Mobile Microsoft clocking

  • AI facial recognition
  • Shared tablet or mobile phone
  • Microsoft Power App
  • Clocking records in Dataverse
  • Microsoft-based integration options
Employee clocking in system

Clock in, record breaks and clock out where the work happens.

A time and attendance system is most effective when recording time is quick and straightforward. FaceClocking is designed for operational, mobile and field-based teams who may not have an individual PC or company device.

01

Clock in

The worker approaches the configured mobile phone or tablet. Facial recognition identifies the individual and creates the clock in event.

02

Record breaks

Start and end break events can be captured through the same clocking experience instead of reconstructed afterwards.

03

Clock out

Clock out and other recorded time events are stored in Microsoft Dataverse for the next stage of the process.

Mobile clocking in

A clocking in app for teams that do not work beside a clocking machine.

Field workers do not always arrive at a factory entrance or permanent attendance terminal. FaceClocking can run on a suitable mobile phone, giving authorised supervisors or team leaders a practical clocking point where the work takes place.

A shared tablet can provide the same clocking point at a warehouse, factory, depot, office or other fixed location.

This makes FaceClocking particularly relevant to organisations searching for a mobile clocking in system, staff clocking app or an alternative to installing physical clocking machines at every location.

Time and attendance for operational teams

One clocking approach across very different workplaces.

Field teams

Use a suitable mobile device where teams work away from a permanent office or fixed clocking terminal.

Manufacturing

Provide a shared clocking point for employees starting and finishing around production shifts.

Warehousing

Record staff attendance without issuing every employee a dedicated clocking card or device.

Multi-site operations

Use a common Microsoft-based employee clocking process across appropriate operating locations.

What is FaceClocking?

A facial recognition clocking system built on Microsoft Power Platform.

FaceClocking is a Microsoft Power Apps and Dataverse clocking solution using Azure AI Face to identify workers and record time and attendance events.

It can operate as a standalone Dataverse clocking in system. Organisations do not have to implement a complete HR platform simply to use FaceClocking.

Where a wider HR and Time & Attendance solution is required, FaceClocking supports two-way synchronisation with HRManagement365 powered by Hubdrive.

Standalone or integrated clocking

One clocking in system. Three ways to use the records.

Start with the clocking process you need today without forcing the organisation into another complete business application.

Option 1

Standalone Dataverse clocking

Use FaceClocking as a standalone employee clocking and time-recording solution built on Microsoft Power Apps and Dataverse.

  • Clock in and clock out
  • Break recording
  • Dataverse clocking records
  • Azure AI facial recognition
Option 2

Synchronise with another system

We can create synchronisation between FaceClocking and another HR, payroll, ERP or operational system using Microsoft Power Automate, suitable connectors and APIs.

  • Power Automate
  • Microsoft connectors
  • API integration
  • Customer-specific data mapping
Option 3

Two-way HR synchronisation

Connect FaceClocking with HRManagement365 powered by Hubdrive using two-way synchronisation between the clocking application and the wider HR environment.

  • Employee information to FaceClocking
  • Project information to FaceClocking
  • Clocking events back into HR
  • Project time back into HR
Microsoft clocking in system

Replace another attendance data silo with a Microsoft-based architecture.

The difference is not simply facial recognition. FaceClocking is designed around the Microsoft application and data platform many organisations already use.

Mobile phone or shared tablet

Where employees clock in and out
→

FaceClocking Power App

Employee clocking experience
→

Azure AI Face + Dataverse

Microsoft cloud and business data platform
Use directly in Dataverse Operate FaceClocking as a standalone Microsoft-based clocking solution.
Synchronise to another system Use Power Automate and appropriate integration methods to move the required information between systems.
Two-way HR synchronisation Exchange relevant data with HRManagement365 powered by Hubdrive.
✓
Azure AI Face runs in the customer's own Azure tenant.
This keeps the solution within the customer's Microsoft architecture and supports its security, administration and biometric-data governance approach.
Facial recognition clocking

No card to remember. No shared PIN to enter.

FaceClocking changes how the worker identifies themselves at the clocking point. Instead of presenting a card or entering a shared PIN, the configured Azure AI service identifies the worker.

01

Low-touch clocking

Workers do not need to carry a clocking card or remember another PIN simply to record attendance.

02

Shared devices

Use a suitably configured shared tablet where many employees need access to the same clocking point.

03

Mobile field clocking

An authorised supervisor's mobile phone can provide a practical clocking point for suitable field-team scenarios.

Coming in the new version
Project time recording

Clock into the project as well as the working day.

FaceClocking is being extended with two-way project synchronisation to HRManagement365 powered by Hubdrive. Relevant projects and processes can be made available to the worker in FaceClocking, while time recorded against those projects synchronises back into the wider Time & Attendance process.

This allows the system to answer more than “How long was this employee working?” It can also help answer “What were those hours actually spent working on?”

01 · Synchronise Relevant projects or processes are made available in FaceClocking
02 · Identify The worker is recognised using FaceClocking
03 · Record The worker clocks time against the relevant project or process
04 · Synchronise back Actual project time returns to HRManagement365 powered by Hubdrive
Example: agricultural and field teams

An agricultural business may represent each field as a project. A team can clock into the appropriate field when picking starts and clock out when the work finishes or when the team moves to another field. Management can then see the actual labour hours used to pick each field rather than allocating the labour from estimates afterwards.

Job and project time clocking

Record labour against the activity that consumed it.

Project clocking is useful wherever the organisation needs actual working time against a job, customer, field, activity, production process or project.

Agriculture

Record labour hours against individual fields, crops, locations or activities.

Construction

Associate actual working time with the relevant site, job or project.

Service teams

Capture time against appropriate customer jobs, contracts or operational work.

Production

Understand labour time associated with configured processes or areas of work.

Microsoft Dynamics 365 Business Central

Connect project time with the Business Central process behind it.

FaceClocking does more than send clocking events into HR. When connected to HRManagement365 powered by Hubdrive, the integration works in both directions.

Employee and project information can synchronise from HRManagement365 powered by Hubdrive into FaceClocking, giving workers the relevant information when they clock in, clock out or record time against a project.

FaceClocking then synchronises the resulting attendance and project-time records back into HRManagement365 powered by Hubdrive for the appropriate working-time, approval and reporting process.

For organisations using Microsoft Dynamics 365 Business Central, Hubdrive's Business Central integration can synchronise relevant projects/processes and timesheet information between the environments.

This creates a connected process from the project in Business Central, through HRManagement365 powered by Hubdrive, to the employee clocking point — and then back again with the actual working time recorded against that project.

Microsoft Dynamics 365 Business Central
Projects · Processes · Timesheets
↕
Project / process information
and approved time
HRManagement365 powered by Hubdrive
Employees · Projects · Time & Attendance · Approvals
↕
Two-way synchronisation
FaceClocking
Attendance and project time captured where work happens
↓ To FaceClocking Relevant employee, project and process information can be made available at the employee clocking point.
↑ Back from FaceClocking Clocking events and recorded project time synchronise back into HRManagement365 powered by Hubdrive.
Complete time and attendance

A clocking event is only the beginning of the working-time process.

A good clocking in system captures when somebody started and finished. The wider business usually needs more: checking, exception handling, approval, reporting and use of the approved time.

01

Capture

Use FaceClocking to create clock in, break, clock out and, where configured, project-time records.

02

Review & approve

When connected to HRManagement365 powered by Hubdrive, recorded time can participate in the configured working-time, exception and approval process.

03

Use

Make approved working-time information available to the relevant reporting, project, ERP, payroll or operational processes.

Built on Microsoft

A clocking in app that can participate in your wider Microsoft platform.

Power Apps

FaceClocking is delivered as a Microsoft Power App rather than another proprietary workforce application.

Microsoft Dataverse

Clocking events are structured as Dataverse records that can participate in the wider business process.

Azure AI Face

Facial recognition uses Azure AI Face provisioned within the customer's own Azure tenant.

Power Automate

Where another business system needs the clocking information, synchronisation can be developed using Power Automate, connectors and suitable APIs.

Biometric clocking

Keep the technology inside your Microsoft environment.

Facial recognition changes the data-protection considerations around an employee clocking system. Architecture therefore matters as well as usability.

Customer-controlled Microsoft architecture

FaceClocking uses Microsoft Power Platform, Dataverse and Azure AI Face, with the Azure AI service provisioned within the customer's own Azure tenant.

  • Azure AI Face within the customer's Azure tenant
  • Clocking records held in Microsoft Dataverse
  • Microsoft security and access controls can form part of the design
  • Standalone or integrated deployment options
  • No separate proprietary clocking database required by FaceClocking
Biometric data requires appropriate governance. Facial recognition used to identify workers involves biometric data. Organisations should assess lawful processing, necessity, transparency, security, retention, DPIA requirements and appropriate alternatives as part of deployment. Technical architecture supports governance but does not by itself determine regulatory compliance.
Choosing a clocking in system

Questions to ask before buying another clocking machine.

Where do employees actually work?

A fixed clocking machine may suit one factory entrance but can be less practical for farms, construction sites, distributed teams and mobile workers.

What happens after somebody clocks in?

Decide where working-time records need to go for approval, payroll, project management, operations and reporting.

Do you need attendance or project time?

Recording the working day and recording which project consumed those hours answer different management questions.

Do you already use Microsoft?

If Power Platform, Dataverse, Business Central or Dynamics 365 already form part of your environment, consider whether the clocking system should participate in that architecture.

Clocking in system FAQs

Common questions about clocking in machines, apps and facial recognition

What is a clocking in system?

A clocking in system records when employees start and finish work and may also record breaks, attendance and working time. Systems range from traditional clocking in machines and card readers to mobile apps, shared tablets and biometric clocking systems.

Can FaceClocking replace a traditional clocking in machine?

Yes. FaceClocking provides a digital alternative to card, fob or PIN-based clocking machines using a suitable mobile phone or shared tablet and AI facial recognition.

Is FaceClocking a time and attendance system?

FaceClocking captures time and attendance events such as clock in, breaks and clock out. It can be used as a standalone Dataverse clocking solution or connected to HRManagement365 powered by Hubdrive for the wider Time & Attendance process.

Can employees clock in from a mobile phone?

FaceClocking can run on a suitable mobile device. This is particularly useful for field-based scenarios where a supervisor or team leader provides the clocking point for the team.

Can we use FaceClocking on a shared tablet?

Yes. A suitable shared tablet can provide a practical clocking point for factories, warehouses, depots and other workplaces where many employees need to clock in and out.

Does FaceClocking require HRManagement365 powered by Hubdrive?

No. FaceClocking can run as a standalone Microsoft Power Apps and Dataverse solution. It can also be synchronised with another system or connected using two-way synchronisation to HRManagement365 powered by Hubdrive.

What synchronises between FaceClocking and HRManagement365 powered by Hubdrive?

The integration is two-way. Relevant employee, project and process information can be made available to FaceClocking, while clocking events and recorded project time can synchronise back into HRManagement365 powered by Hubdrive for the wider working-time, approval and reporting process.

Can FaceClocking integrate with another HR or payroll system?

Yes. Where the target application provides an appropriate integration route, synchronisation can be developed using Microsoft Power Automate, suitable connectors or APIs.

Can FaceClocking record time against projects?

Project FaceClocking is being introduced in the new version. Relevant project or process information can synchronise into FaceClocking and the resulting recorded project time can synchronise back into HRManagement365 powered by Hubdrive.

What is the difference between attendance clocking and project clocking?

Attendance clocking records when an employee starts and finishes work. Project clocking additionally records which project, job, field, process or activity consumed that working time.

Can project time connect with Business Central?

When using HRManagement365 powered by Hubdrive with the Hubdrive Business Central integration, relevant projects/processes and timesheet information can participate in the Business Central integration. This allows project information to move through the HR environment and approved time to support downstream ERP processes.

Does FaceClocking use Microsoft Power Apps?

Yes. FaceClocking is built as a Microsoft Power App using Dataverse and Azure AI Face.

Where does the facial recognition technology run?

Azure AI Face is provisioned within the customer's own Azure tenant. FaceClocking records are held in the customer's Microsoft Dataverse environment.

Is facial recognition clocking suitable for every employee?

Not necessarily. The appropriate time-recording method depends on the workforce, working environment, purpose and data-protection requirements. Organisations should assess whether biometric identification is necessary and appropriate for the intended use.

Need more than clocking?

Connect the clocking event to the complete working-time process.

If you also need working-time rules, exceptions, manager approval, employee records and downstream HR processes, explore the complete Time & Attendance capability within HRManagement365 powered by Hubdrive.

Replace your existing clocking process

Looking for a clocking in system? Show us how your people work today.

Whether you are replacing clocking in machines, looking for a mobile clocking app for field workers, need facial recognition attendance, want to record project hours, or need complete Time & Attendance, we can demonstrate FaceClocking around your actual working environment.

```