Custom Zoho Creator Attendance Dashboard
Budget: ₹1,500 – ₹12,500 INR
REQUIREMENT DOCUMENT
1. Document Overview
This document outlines the requirements for designing and developing a custom Attendance Report within our Zoho Creator HRMS application. It is intended for the vendor selected to build the solution and serves as the primary reference for scope, logic, and delivery expectations.
2. Client Context & Platform
Attribute Details
Zoho Plan Zoho One
Application Custom-built Zoho Creator HRMS application
License Model 1 Zoho One license + Portal User licenses for all other employees
Scope New report page/view within the existing Creator application
3. Existing Data Modules (Source of Truth)
The report will draw data from the following modules already built in the Zoho Creator application. The vendor must not alter the schema of these modules; only read access is required.
3.1 Associates
Master employee records. Key fields relevant to this report:
• Associate ID
• Associate Name
• Associate Email
• Functional Unit
• Business Unit
• Reporting Manager
• Secondary Reporting Manager
3.2 Attendance
Daily attendance entries punched by the manager. Fields:
• Associate Name (lookup)
• Attendance Date
• Status - values: P (Present) | A (Absent) | Half Day Present | WFH
3.3 Leave
Leave records. Fields:
• Associate Name (lookup)
• Leave Date
• Leave Type
• Status - values: Approved | Rejected
3.4 WFH
Work-from-home records. Fields:
• Associate Name (lookup)
• WFH Date
• Status - values: Approved | Rejected
3.5 Comp-Off
Compensatory-off records. Fields:
• Associate Name (lookup)
• Comp-Off Date
• Status - values: Approved | Rejected
3.6 Holidays
Company holiday calendar, tagged per employee due to multi-location / multi-LOB setup. Fields:
• Associate Name (lookup)
• Holiday Name
• Holiday Date
4. Report Requirements
4.1 Report Layout & Reference
The report must replicate the calendar-grid layout shown in the attached screenshot (Zoho People-style attendance view). The grid displays employees as rows and dates as columns, with the attendance status displayed in each cell.
4.2 Static Employee Fields (Column Headers)
The following employee attribute columns must appear to the left of the date columns. Columns 2-7 must each have a toggle to show or hide them individually (see Section 4.5).
# Field Notes
1 Associate ID Always visible; cannot be hidden
2 Associate Name Always visible; cannot be hidden
3 Associate Email Toggleable
4 Functional Unit Toggleable
5 Business Unit Toggleable
6 Reporting Manager Toggleable
7 Secondary Reporting Manager Toggleable
4.3 Date Columns & Cell Logic
Each date within the selected date range becomes a column. The column header must display the date (DD) and day abbreviation (Mon, Tue, etc.). The cell value for each employee-date intersection must be determined by the following priority logic:
Priority Source Module Condition Display Value
1 Holidays Holiday exists for associate on date Holiday Name (or “H” abbreviation)
2 Leave Approved leave record exists Leave Type (e.g., CL, SL, EL)
3 WFH Approved WFH record exists WFH
4 Comp-Off Approved Comp-Off record exists CO
5 Attendance Attendance record exists P / A / Half Day / WFH (as stored)
6 - No record in any module Blank / “—”
Note: Weekend columns (Saturday & Sunday) must be visually distinguished (e.g., shaded background), consistent with the reference screenshot.
4.4 Role-Based Views
The report must behave differently depending on the logged-in user’s role. Three views are required:
Role / View Behaviour
Employee Sees only their own attendance row. Cannot view other employees’ data.
Manager Sees their own row plus all rows for direct reports (employees where Reporting Manager or Secondary Reporting Manager = logged-in user). Cannot view employees outside their team.
HR / Admin Sees all employees across the organisation. Full filter access (see Section 4.5).
4.5 Filters
A filter panel must be available, allowing the report to be narrowed by one or more of the following criteria. Filter availability per role is noted:
Filter Field Input Type Employee Manager HR/Admin
Date Range Date picker (from / to) ✓ ✓ ✓
Associate ID Text search - Own team only ✓
Associate Name Text search / dropdown - Own team only ✓
Associate Email Text search - - ✓
Functional Unit Dropdown (multi-select) - - ✓
Business Unit Dropdown (multi-select) - - ✓
Reporting Manager Dropdown - ✓ (self only) ✓
4.6 Column Visibility Toggle
Above the report grid, provide a “Show / Hide Columns” control (e.g., a checkbox panel or dropdown with checkboxes) that allows the user to toggle the visibility of fields 3-7 (Associate Email, Functional Unit, Business Unit, Reporting Manager, Secondary Reporting Manager). Fields 1 (Associate ID) and 2 (Associate Name) must always remain visible and cannot be toggled off.
4.7 Export Options
The report must be exportable in atleast excel format.
5. Non-Functional Requirements
• The report must be built natively within Zoho Creator.
• Role enforcement must be implemented using Zoho Creator’s in-built portal user role / profile framework; no custom workarounds that bypass platform security.
• The solution must function correctly for Portal User license holders (employees accessing via the portal).
• Performance: The report must load within a reasonable time for up to 500 employees over a 1-month date range.
• Mobile responsiveness is not required for the initial version but should not be broken.
6. Out of Scope
• Any changes to the schema of existing modules (Associates, Attendance, Leave, WFH, Comp-Off, Holidays).
• Integration with third-party HRMS or payroll systems.
• Real-time biometric / device-based attendance capture.
• Mobile application development.
7. Deliverables
1. Fully functional Attendance Report within the Zoho Creator application meeting all requirements in Section 4.
2. Technical design document detailing the data-fetch logic, role-enforcement approach, and any Deluge scripts used.
3. User acceptance testing (UAT) sign-off from the client before go-live.
4. Post-delivery bug-fix support for 30 calendar days from UAT sign-off.
8. Reference Material
Screenshot of the desired report layout (calendar-grid attendance view from Zoho People). The vendor must replicate this grid structure within Zoho Creator.
1. Document Overview
This document outlines the requirements for designing and developing a custom Attendance Report within our Zoho Creator HRMS application. It is intended for the vendor selected to build the solution and serves as the primary reference for scope, logic, and delivery expectations.
2. Client Context & Platform
Attribute Details
Zoho Plan Zoho One
Application Custom-built Zoho Creator HRMS application
License Model 1 Zoho One license + Portal User licenses for all other employees
Scope New report page/view within the existing Creator application
3. Existing Data Modules (Source of Truth)
The report will draw data from the following modules already built in the Zoho Creator application. The vendor must not alter the schema of these modules; only read access is required.
3.1 Associates
Master employee records. Key fields relevant to this report:
• Associate ID
• Associate Name
• Associate Email
• Functional Unit
• Business Unit
• Reporting Manager
• Secondary Reporting Manager
3.2 Attendance
Daily attendance entries punched by the manager. Fields:
• Associate Name (lookup)
• Attendance Date
• Status - values: P (Present) | A (Absent) | Half Day Present | WFH
3.3 Leave
Leave records. Fields:
• Associate Name (lookup)
• Leave Date
• Leave Type
• Status - values: Approved | Rejected
3.4 WFH
Work-from-home records. Fields:
• Associate Name (lookup)
• WFH Date
• Status - values: Approved | Rejected
3.5 Comp-Off
Compensatory-off records. Fields:
• Associate Name (lookup)
• Comp-Off Date
• Status - values: Approved | Rejected
3.6 Holidays
Company holiday calendar, tagged per employee due to multi-location / multi-LOB setup. Fields:
• Associate Name (lookup)
• Holiday Name
• Holiday Date
4. Report Requirements
4.1 Report Layout & Reference
The report must replicate the calendar-grid layout shown in the attached screenshot (Zoho People-style attendance view). The grid displays employees as rows and dates as columns, with the attendance status displayed in each cell.
4.2 Static Employee Fields (Column Headers)
The following employee attribute columns must appear to the left of the date columns. Columns 2-7 must each have a toggle to show or hide them individually (see Section 4.5).
# Field Notes
1 Associate ID Always visible; cannot be hidden
2 Associate Name Always visible; cannot be hidden
3 Associate Email Toggleable
4 Functional Unit Toggleable
5 Business Unit Toggleable
6 Reporting Manager Toggleable
7 Secondary Reporting Manager Toggleable
4.3 Date Columns & Cell Logic
Each date within the selected date range becomes a column. The column header must display the date (DD) and day abbreviation (Mon, Tue, etc.). The cell value for each employee-date intersection must be determined by the following priority logic:
Priority Source Module Condition Display Value
1 Holidays Holiday exists for associate on date Holiday Name (or “H” abbreviation)
2 Leave Approved leave record exists Leave Type (e.g., CL, SL, EL)
3 WFH Approved WFH record exists WFH
4 Comp-Off Approved Comp-Off record exists CO
5 Attendance Attendance record exists P / A / Half Day / WFH (as stored)
6 - No record in any module Blank / “—”
Note: Weekend columns (Saturday & Sunday) must be visually distinguished (e.g., shaded background), consistent with the reference screenshot.
4.4 Role-Based Views
The report must behave differently depending on the logged-in user’s role. Three views are required:
Role / View Behaviour
Employee Sees only their own attendance row. Cannot view other employees’ data.
Manager Sees their own row plus all rows for direct reports (employees where Reporting Manager or Secondary Reporting Manager = logged-in user). Cannot view employees outside their team.
HR / Admin Sees all employees across the organisation. Full filter access (see Section 4.5).
4.5 Filters
A filter panel must be available, allowing the report to be narrowed by one or more of the following criteria. Filter availability per role is noted:
Filter Field Input Type Employee Manager HR/Admin
Date Range Date picker (from / to) ✓ ✓ ✓
Associate ID Text search - Own team only ✓
Associate Name Text search / dropdown - Own team only ✓
Associate Email Text search - - ✓
Functional Unit Dropdown (multi-select) - - ✓
Business Unit Dropdown (multi-select) - - ✓
Reporting Manager Dropdown - ✓ (self only) ✓
4.6 Column Visibility Toggle
Above the report grid, provide a “Show / Hide Columns” control (e.g., a checkbox panel or dropdown with checkboxes) that allows the user to toggle the visibility of fields 3-7 (Associate Email, Functional Unit, Business Unit, Reporting Manager, Secondary Reporting Manager). Fields 1 (Associate ID) and 2 (Associate Name) must always remain visible and cannot be toggled off.
4.7 Export Options
The report must be exportable in atleast excel format.
5. Non-Functional Requirements
• The report must be built natively within Zoho Creator.
• Role enforcement must be implemented using Zoho Creator’s in-built portal user role / profile framework; no custom workarounds that bypass platform security.
• The solution must function correctly for Portal User license holders (employees accessing via the portal).
• Performance: The report must load within a reasonable time for up to 500 employees over a 1-month date range.
• Mobile responsiveness is not required for the initial version but should not be broken.
6. Out of Scope
• Any changes to the schema of existing modules (Associates, Attendance, Leave, WFH, Comp-Off, Holidays).
• Integration with third-party HRMS or payroll systems.
• Real-time biometric / device-based attendance capture.
• Mobile application development.
7. Deliverables
1. Fully functional Attendance Report within the Zoho Creator application meeting all requirements in Section 4.
2. Technical design document detailing the data-fetch logic, role-enforcement approach, and any Deluge scripts used.
3. User acceptance testing (UAT) sign-off from the client before go-live.
4. Post-delivery bug-fix support for 30 calendar days from UAT sign-off.
8. Reference Material
Screenshot of the desired report layout (calendar-grid attendance view from Zoho People). The vendor must replicate this grid structure within Zoho Creator.