NOTIFICATIONS THAT ROUTE THEMSELVES
Requests Reach The Right Approver, Not A Mailing List.
Leave applications, timesheet unlock requests, payroll milestones and security alerts are routed through your live org hierarchy to the person who has to act, with no distribution lists to maintain.
THE PROBLEM
Delayed Digests and Lost Approval Requests
Daily email digests and hand-maintained mailing lists leave urgent approvals waiting and send requests to people who no longer own them, and deadlines slip.
Delayed digests. bundling approvals into an end-of-day email leaves urgent leave and timesheet unlock requests waiting for hours.
Stale mailing lists. hard-coded lists keep notifying former managers after a team changes, so requests reach people who no longer manage the employee.
No link to the record. an alert without a direct link makes the manager log in and search menus for the item that needs action.
No escalation. when an approver is on leave there is no automatic route to the next level, so a pending request can hold up payroll or client billing.
CAPABILITIES
Alerts That Find The Approver Themselves
Four capabilities get each event to the right approver without anyone maintaining a routing list.
Hierarchy-Derived Routing
Recipients are calculated from the live organizational tree, so when a reporting line changes, alerts follow it.
Real Domain Event Triggers
Alerts fire on actual events: leave applied, timesheet unlocked, payroll finalized and OTP security changes, not on a daily schedule.
Multi-Channel Delivery & Deep Links
Alerts reach people in-app, by email and by SMS, with a link straight to the record that needs a decision.
SLA-Based Automated Escalations
A pending request that passes its review window is automatically re-routed to the next supervisory level.
DELIVERY SNAPSHOT
Notification Delivery & Event Mix, At A Glance
A sample view of notification volume, delivery time and event mix — illustrative data.
Notifications By Event Type
Recent Auto-Routed Events
HOW IT WORKS
From Domain Event To Approver Action
How an action in HRMS becomes an alert in the right person's hands, with a path to escalate if nobody acts.
Step 01
Domain Event Fires
An employee applies for leave, requests a timesheet correction, or finance completes a pay run, and the system records a structured event.- Alerts fire on the event itself, not on a daily digest schedule.
Step 02
Hierarchy Engine Resolves Recipient
The notification router reads the employee's current reporting line to find the exact approving authority.- No static mailing list to keep up to date.
Step 03
Multi-Channel Dispatch with Deep Link
The alert goes out in-app, by email and by SMS, each with a link to the record that needs action.- The approver opens the record from the alert instead of searching menus.
Step 04
Mirroring on Dashboard & Escalation Watch
The item appears in the manager's pending approval queue; if nobody acts, an SLA timer escalates it up the reporting chain.- A request stuck with one approver has a path to the next.
WHO USES THIS
Built For Distributed & Time-Critical Teams
Where staff are spread across shifts and locations, approvals cannot wait for someone to check an inbox.
Healthcare & Emergency Services
Round-the-clock shift rosters, where a leave request has to reach the right approver promptly.
Logistics & Field Distribution
Field staff and multi-state operations, where approvals follow the reporting line wherever the approver is.
IT & Distributed Knowledge Work
Distributed teams whose timesheet unlock requests and leave notices go to the right manager automatically.
FAQ
Self-Routing Notifications — Questions We Get Asked
Self-routing notifications are included in the Starter plan as part of the core platform, delivering real-time leave, timesheet, and operational alerts to all teams.
Leave applications and approvals, timesheet unlock requests, payroll milestones such as a finalized pay run and payslip release, and security events such as an OTP-verified password change.
The routing engine resolves recipients from the organizational reporting hierarchy closure table at the moment the event fires, so team changes redirect notifications automatically.
No. The approver is found from the live org hierarchy when the event fires, so when a reporting line changes, new requests follow it.
BizzField supports SLA escalation. If an approval request remains pending past the configured window, the system automatically escalates it to the next reporting manager.
No. Notifications appear in the in-app notification bell and on the manager's Real-Time Dashboard as well as in email, and each one links to the record that needs action.
Pending approvals appear in the manager's approval queue and on the Real-Time Dashboard, alongside the notification.
Yes. Users can configure their delivery preferences for specific event categories across in-app alerts, email notifications, and mobile SMS.
AT A GLANCE
Routed By Hierarchy, Escalated When Nobody Acts
AUTOMATED CHECKS
Variance Checks Before Payroll Is Approved
Before a pay run is approved, BizzField compares the draft with the previous cycle and flags what looks wrong, so reviewers examine the exceptions instead of every line.
PRE-APPROVAL SCAN
Automated Variance Checks
Key Capabilities
- Each employee's draft pay compared with the prior month
- Pay movement above 20% flagged for review
- Duplicate leave and expense submissions detected
- Flags resolved from one HR queue before approval
Every draft run is compared with the previous cycle. Sharp pay movements, duplicate expense or leave submissions and timesheet conflicts are flagged for HR, who resolve each flag from a single queue while the run is still a draft.
See Automated Variance ChecksSECURITY & PRIVACY
Role-Scoped Access And Privacy By Design
Access is enforced on the server from the reporting hierarchy, and data handling is designed around the principles of India's DPDPA. The security page sets out what is and is not certified.
DATA PRIVACY
DPDPA-Informed Data Handling
Key Capabilities
- Consent logging for employee data
- Data export for the employee
- Deletion rights supported
Data handling is designed around the principles of India's Digital Personal Data Protection Act. That describes how data is handled; it is not a certification.
ACCESS CONTROL
Server-Scoped Access And Encrypted Storage
Key Capabilities
- Server-side role-based access, not just interface-level visibility
- Manager visibility limited to their reporting hierarchy
- AES-256 encryption at rest for employee records, bank details and document files
Role flags are not left to the front end. Access is scoped on the server, so a manager retrieves records only within their own reporting tree.
See HRMS SecurityROLLOUT TIMELINE
Getting Started with BizzField Notifications
A structured path from configuration to pilot testing and full launch, guided by our onboarding team.
Step 01
Employee Data Import & Hierarchy Setup
Model your reporting hierarchy, upload employee records securely, and map custom document types to BizzField's structure.- Upload employee master data from a CSV file
- Map reporting lines & org hierarchy
- Configure custom document categories
Step 02
Policy & Rule Configuration
Configure multi-level approvals, custom shift templates, statutory compliance ceilings, and salary revision workflows.- Set leave types, accruals & sandwich rules
- Define shift rosters & overtime rules
- Configure state-wise PT/LWF compliance
Step 03
Parallel Run & Validation
Verify payroll calculations, shift check-ins, and approval chains alongside your existing setup before fully cutting over.- Run a parallel payroll draft for one month
- Compare attendance records with your current process
- Confirm role-scoped access for all managers
Step 04
Full Launch & Team Training
Release employee self-service credentials, activate mobile check-in, and turn on pay run approvals and notifications.- Distribute self-service app credentials to all employees
- Publish payslips to employee self-service on pay date
- Switch on approval and leave notifications
KEEP EXPLORING
Related Pages
Other HRMS capabilities teams usually evaluate alongside this one.
Statutory Filing Summaries
PF, ESI, PT, TDS and LWF liabilities summarized from every pay run each cycle, not totalled by hand.
ExploreEmployee Lifecycle Management
One record from onboarding to exit, so profiles, documents, designations and org placement are not kept in separate files.
ExploreOrg Hierarchy & Reporting Lines
An org chart derived from reporting lines and updated when someone is hired or moves, not redrawn by hand.
ExploreAttendance & Shift Tracking
Real-time check-in/out, shifts and overtime feed the pay run, and managers see only their own team.
ExploreSee Events Route Through Your Org Hierarchy
Walk through how leave, timesheet, and payroll events reach the right approver when they happen.