Codeaza
CODEAZA · HR PORTAL · NEXT PHASE
Internal Platform Spec · June 2026

HR Portal
Next Phase.

Unification is live — reporting & analytics now run inside the HR Portal. Here are the four moves — a focused 2-week sprint — that take it from unified to complete, trustworthy & insightful.

Owner · Mubeen Aftab Engine · Wazir For · Team discussion v1.0 · June 2026
00 — STATUS

The foundation is already built.

We're not starting from zero. The hardened HR Portal — security, approvals, RBAC, self-service — shipped 19–20 June (PRs #21–#25), and the unification (reporting & analytics inside the portal) is live and demoed.

✓

Unification — shipped & live

HR Portal is the single platform; reporting & analysis are built in. This deck is the next phase — four items to make the platform complete and the data trustworthy.

ARCHITECTURE

One engine. One platform.

Wazir pulls every source, normalises it, and feeds the HR Portal — the single place the whole team works from.

⏱️ WebWork🌴 Leaves🐙 GitHub + HR records · perf Wazir merge engine HR Portal single platform · role-based
🌴
01 — FEATURE

Quarter-Wise Leave Policy

FEATURE

Define and enforce leave entitlements in the portal, allocated quarter by quarter — the request → approval flow honors the policy automatically.

What we build

  • Leave types with per-quarter allocation
  • Quarter-wise accrual & balance per employee
  • Carry-over / lapse rules at quarter boundaries
  • Enforced on request — can't exceed balance
  • Admin-editable config, no code change

Decide with the team

  • Exact quarterly allocation per type
  • Carry over to next quarter, or lapse?
  • Pro-rata for mid-quarter joiners
  • Approval chain — manager → HR?
🔍
02 — QUALITY

Data Validation & Correctness

QUALITY

Now that analytics live in the portal, prove the numbers are right before anyone makes a call on them.

What we do

  • Reconcile portal analytics vs WebWork raw data
  • Spot-check attendance, leaves & headcount
  • Validate edge cases — paid breaks, idle, partials
  • Define acceptance criteria + re-runnable checklist

Output

  • A sign-off that the data is trustworthy
  • Discrepancy list + fixes
  • A repeatable validation routine
⚠️ This gates wider rollout — managers shouldn't decide on unverified numbers.
✉️
03 — INFRA

Email / SMTP Notifications

INFRA

Wire up outbound email so the portal can notify the team — first use case: auto-email everyone when a company / leave policy changes.

What we build

  • SMTP config (provider + secrets)
  • Branded templates — policy update, approvals, reminders
  • Trigger: policy change → notify affected team
  • Extensible to approvals, reminders, onboarding

Decide

  • Provider — Zoho / SES / existing AgentMail infra?
  • Which events trigger emails?
  • Audience controls — all / dept / role
🔄
04 — INTEGRATION

Leaves → WebWork Sync

INTEGRATION

Today leaves live only in the portal. Push approved leaves into WebWork so time-tracking & attendance stay consistent — no false absences.

What we build

  • On approval → create matching WebWork time-off
  • Map portal employees ↔ WebWork members
  • Handle edits / cancellations in sync
  • Reflect leave in attendance / SOP reports

Check

  • WebWork API support for time-off entries
  • One-way vs two-way sync
  • Backfill existing approved leaves
⚠️ Closes the loop on the attendance reporting we just unified — leaves & time-tracking finally agree.
LATER

Parked for the next sprint.

Valuable, but out of the 2-week scope — WebWork already covers project management today, so these wait.

Next sprint

  • 🐙 GitHub integration — commits, PRs, lines of code merged
  • 📈 Improve WebWork reporting — richer trend & SOP dashboards

Why parked

  • Keep the 2-week sprint shippable & focused
  • WebWork covers PM needs for now
  • Revisit once the core four are live
05 — PLAN

Suggested sequence.

Ordered by dependency — trust the data first, then build on it.

1

Data Validation

Verify analytics first — everything builds on trusted data.

2

Leave Policy

Define & enforce the quarter-wise policy in-portal.

3

Leaves → WebWork

Push policy-driven leaves so reports agree.

4

Email / SMTP

Layer notifications — policy emails first.

06 — NEXT

Ownership & next step.

Owner
Mubeen Aftab — Internal Tools / HR Portal
Engine
Wazir — data sync, automation & analytics
Status
✓ Unification live — this is the next phase
Immediate action
Team discussion → confirm policy details, provider choices & lock the sequence

Codeaza Technologies · HR Portal — Next Phase · v1.0 · June 2026