25th Floor, IRIS Bay Tower, Business Bay, Dubai - UAE Business Aim: www.bisaim.com · QBM ERP · +971 4 325 4455

QBM employee clocking

QClock connects simple employee clock-in and clock-out to QBM.

Employees use an approved browser, QClock shows QBM server time, and managers can review device, network, browser, and optional GPS context when configured.

QBM Server Time08:30:15 AMConnected to QBM
StatusChecked in
Today4h 15m
Check out

Setup responsibility

QClock should be enabled with clear employee notice.

QClock can record personal data such as IP address, browser/device details, identity evidence, and optional GPS results. Customers should review employee notices, consent needs, record-retention rules, and local employment law before enabling it.

Customer privacy checklist

  • Tell employees what attendance evidence is collected and why.
  • Use GPS only when the company has a proper business reason and legal basis.
  • Limit manager review access to authorized staff.
  • Confirm the final setup with the implementation team before public use.

QClock screens

Clock views for employees and managers in the browser.

Employees can clock from approved devices, and managers can review attendance evidence while the company keeps control of its QBM data.

Sanitized QClock home screen.

Employee clock home

Shows connection, QBM server time, current attendance state, today's totals, and device security.

Sanitized QClock check-in screen.

Check-in confirmation

Employees confirm their own QBM password before a punch is saved.

Sanitized QClock check-out screen.

Check-out confirmation

The same identity confirmation and QBM time flow applies when checking out.

What it does

Simple clock-in and clock-out with manager audit context.

QClock keeps the daily employee workflow direct: sign in, confirm the device, see QBM server time, add an optional note, and save a check-in or check-out action.

Connected to QBMAttendance actions are tied to the customer's QBM environment and approved users.
Uses QBM server timeShows trusted QBM server time instead of relying only on the browser clock.
Supports device review and manager audit evidenceReview context can include device, IP, GPS, browser, identity evidence, and warning flags.
Requires proper employee notice and consent reviewCustomers should confirm notices, consent needs, and local employment-law requirements before enabling QClock.

Audit evidence

QClock records the context managers need to review time punches.

Because QClock can record personal data, customers should use it only with the required employee notices, consent, and local employment-law review.

Identity confirmation

Before each punch is saved, the employee re-enters the active QBM password. The app confirms the punch identity against the authenticated QBM user.

Device and network context

QClock captures registered device details, server-seen IP, browser context, and warning flags so managers can review unusual activity.

GPS result

Browser GPS can be tested and recorded as review evidence. It helps the manager, but it should still be treated as evidence, not absolute proof.

QClock FAQ

Common setup and privacy questions.

Is GPS required?

No. GPS is optional and should be enabled only when the customer has proper employee notice, consent where required, and a business reason.

Can employees use mobile?

Yes, when the company approves the device or browser and the final access setup supports that workflow.

Who reviews clock evidence?

Only authorized managers should review device, network, browser, identity, and optional location evidence.

Scope boundary

QClock is for employee check-in, check-out, status, history, and attendance audit review. It is not a payroll, HR, scheduling, CRM, inventory, or accounting entry app.

Request QClock access

Looking for the full QBM ERP?

Use the main QBM site for ERP modules, demos, support documents, and implementation enquiries.

Visit qbmis.com