Tuling HCM module

HR AI Assistant

Ask management-desk questions in plain English and get answers from live attendance, leave, payroll, and settlement data — tool-calling into real ERP services, not a generic chatbot.

About this module

Most campus ERPs make you already know the answer before you can find it. You want to know who has been chronically late this month, so you open attendance, pick a date range, guess at a threshold, export a CSV, and sort it yourself. The data was always there — the path to it was the problem.

The HR AI Assistant removes that path. It sits on the management desk and answers workforce questions in plain English, using the same attendance, leave, payroll, and settlement services the rest of Tuling HCM runs on. This is the feature most campus ERPs still lack, and the reason it matters is not novelty: it is the difference between a principal getting an answer in a sentence and filing a request with the HR office.

Questions it is built for

  • “Who is repeatedly late this month?” — chronic late arrivals and attendance anomalies over any date range
  • “Who took the most leave last quarter?” — top leave takers, with the requests and approvals behind the number
  • “Anything odd in this month’s payroll?” — an anomaly scan for a period, before you finalize rather than after
  • “Is this separation ready for full and final?” — F&F preview, plus overdue settlement exposure across the institution

Grounded, not generative guesswork

The distinction that matters for an institution is where the answer comes from. A general-purpose assistant produces text that sounds right. This one calls your ERP services and reports what they return, which means it inherits the business rules already enforced upstream — finalized periods, active employees, approved leave. There is no second copy of your data to fall out of sync, and nothing to reconcile between what the assistant said and what the payroll register shows.

Access follows the same principle. The assistant runs inside the asking user’s authenticated session with tenant context, so it can only reach what that person could already open. Enablement is an entitlement per campus tenant and role, not a global switch.

From answer to action

An answer that ends in a number still leaves work to do. Responses include the next action and deep links into the relevant desk — the leave queue, the attendance exceptions, the payroll register, the onboarding checklist — so the question resolves into work completed in the correct screen rather than a figure someone writes down and acts on later.

Capabilities

  • Plain-English Workforce Questions

    Principals, registrars, and HR ask questions the way they'd ask a colleague — no report builder, no filter chains, no waiting on IT for a CSV. The assistant sits on the management desk where those questions actually come up.

  • Chronic Late Arrivals & Attendance Anomalies

    Surface who is repeatedly late over a date range, and where attendance patterns break from the norm — computed from the same synced biometric punches the attendance module works from, not a separate copy of the data.

  • Leave Pattern Analysis

    Ask for top leave takers across a period, or where leave queues are piling up before an approval cutover, and get the figures with the pending approvals behind them.

  • Payroll Anomaly Scan

    Scan a payroll period for anomalies before you finalize — variances and outliers worth a second look, so corrections happen before payslips go out rather than after.

  • Full & Final Preview and Overdue Exposure

    Check F&F readiness for a separation, and see overdue full-and-final exposure across the institution — the settlements that have been sitting too long, in one answer.

  • Tool-Calling Over Live ERP Services

    Answers are produced by calling the same attendance, leave, payroll, and settlement services the product itself runs on. There is no side database and no summarised snapshot, so the assistant cannot drift from what the ERP shows.

  • Entitlement-Aware and Tenant-Scoped

    The assistant runs inside the user's authenticated session with tenant context, and answers only from services that user can already reach. It is enabled per campus tenant for entitled roles rather than switched on for everyone.

  • Answers That Point Back Into the ERP

    Responses include the next action and deep links into the relevant leave, attendance, payroll, or onboarding desk — so a question turns into work done in the right screen instead of a dead-end number.

FAQ

Frequently asked questions