Most HR teams running Odoo hit the same wall: the native Attendances app records raw check-in/check-out pairs, but managers actually need to see patterns — who is chronically late, how many hours each person logged this month, which days had gaps, and how a department trends over a quarter. Out of the box that means exporting hr.attendance records to a spreadsheet, hand-building pivots, and repeating the exercise every pay cycle. The calendar view that would answer "what did March look like for this employee" simply is not there, and the stock pivot and graph views do not give leadership a single glanceable HR dashboard.

Attendance Dashboard Advanced is a build-to-order Odoo module ECOSIRE designs and develops to close exactly that gap. At its core is a monthly per-employee attendance calendar — an OWL client-side component backed by hr.attendance and hr.employee — that renders each day colour-coded by presence, absence, partial day, or leave, with worked-hours totals rolled up per week and per month. On top of it sits an advanced HR dashboard built from computed models: aggregate models.Model records with @api.depends compute fields and read_group queries that surface headcount present, total and average hours, late arrivals, early departures, and overtime, filterable by department, job position, work location, and date range. Where it helps, we also expose the metrics through Odoo's native pivot and graph views and ship printable QWeb monthly summary reports for payroll and audit.

Technically, the module is a clean, upgrade-safe addon with its own __manifest__.py, dedicated models and stored/computed fields, ir.model.access.csv plus record rules so an employee sees only their own calendar while HR managers see the whole company, XML and OWL views for the calendar widget, and optional ir.cron jobs or automated actions to pre-aggregate heavy metrics overnight for large databases. It reads existing attendance data with no destructive migration, respects multi-company boundaries, and integrates with hr.leave so approved time off shows correctly on the calendar. It can also be queried through Odoo's XML-RPC/JSON-RPC API if you want to feed the summaries into an external BI tool. We target Odoo 17.0, 18.0, and 19.0 and adapt to whether you run Community or Enterprise (for example, gracefully handling the presence of the Enterprise Planning and advanced HR apps).

Because this is made to order, delivery follows a scoping-first path: a short call to confirm which metrics, filters, and reports you need, a fixed quote against that scope, then development, UAT on a staging copy of your database, and installation on production with a support window afterward. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company consolidation, deep localization of overtime or shift rules, and larger historical-data aggregation increase the quoted scope.