Full-Stack Developer Build a Team Performance Dashboard Website (Trello + Time-Tracker Integration)

Title: Full-Stack Developer — Build a Team Performance Dashboard Website (Trello + Time-Tracker Integration) Description: I run a small fashion brand and need a developer to build an internal website (private dashboard) that manages my team’s performance. The full logic is already designed and documented below — your job is to turn it into a clean, multi-user website with a database, logins, filters, reports, and live integrations. Please read it fully before applying. Overview The website scores completed tasks on five criteria, tracks daily working hours against a 6-hour minimum, lets HR file leave and absences, and produces filterable per-employee reports that export to CSV. It connects directly to Trello (tasks) and a time-tracking tool with a built-in stopwatch (for logged hours). It is an internal admin tool for about 5–15 users. It is NOT a surveillance tool (no screenshots/keystrokes) and NOT a payroll system. Mandatory integrations: • Trello (required): the website must pull tasks/cards directly from Trello — task name, who created the card, which list it originated in (e.g. “Ideas”), dates, and the estimate field. Tasks should flow in automatically when moved to “Done.” • Time tracker with stopwatch (required): integrate a time-tracking tool (e.g. Everhour or similar) that provides a start/stop stopwatch on each Trello task, so actual hours are tracked live per task and per day, and pulled into the dashboard automatically. The estimate-vs-actual comparison depends on this. User roles (permissions enforced server-side): • Owner — full access; confirms Quality scores, awards Initiative points, sets thresholds, manages users. • HR — enters/edits data, logs attendance, files leave/absence, runs and exports reports. Cannot award Initiative or set thresholds. • Employee — view-only of their own scores and attendance. The scoring system (implement exactly — this logic is fixed) Each completed task is scored on 5 criteria. The user never types a score for the automatic ones — raw facts (hours, Yes/No) come in and the system calculates the score. Only Quality and Initiative are entered by a human. 1. Delivery (0–3) — automatic Inputs: on-time (Y/N), estimated hours, actual hours. • On time → 3 · over by ≤25% → 2 · over by ≤50% → 1 · more than 50% over → 0 • Finishing under estimate counts as on time → 3 2. Quality (0–3) — human Entered by the Owner. No formula — it’s a judgment. An optional AI step may suggest a score, but the Owner confirms it. Employees can never set their own quality score. 3. Reliability (0–3) — automatic Inputs: logged (Y/N), communicated (Y/N). Each Yes = 1.5 → both = 3, one = 1.5, none = 0. 4. Estimate Accuracy (0–3) — automatic Inputs: estimated vs actual hours. Finishing on or under estimate gets full marks — only overruns lose points. • Actual ≤ estimate → 3 · over by ≤25% → 2 · over by ≤50% → 1 · more than 50% over → 0 5. Initiative (0–3 extra credit) — human, gated Eligible only if the employee created the task themselves AND it originated as their own idea (in an “Ideas” list in Trello) — otherwise forced to 0. If eligible, the Owner awards 0–3. A normal assigned task scores 0 here, and that is fine. Totals: • Base = Delivery + Quality + Reliability + Estimate Accuracy (max 12) • Task total = Base + Initiative (only if eligible) • Monthly score = sum of the employee’s task totals → drives their tier (Bonus / Normal / Warning, using editable thresholds) The attendance system (6-hour daily compliance — kept SEPARATE from the task score) One record per employee per day, using hours from the time tracker: • Counts toward the day = tracked hours + approved-leave hours (if HR-approved). • Compliant if total ≥ 6 hours. • Flag: “OK”, “Short – approved”, or “SHORT – UNAPPROVED”. Critical rule: task score and attendance compliance are two separate numbers, shown side by side, never blended. The task score earns the tier; attendance gates it (e.g. great score but repeated unapproved short days → bonus held until attendance is fixed). This separation must be preserved. Leave & absence (HR can file): Sick leave, vacation, approved early-leave, absences. Filing leave automatically adjusts that employee’s attendance requirement (approved leave isn’t counted against them; unapproved absence flags the day). Each record stores who filed and who approved it. Dashboard & reporting: • Main dashboard: summary cards + per-employee table (task score, avg estimate accuracy, compliant days, unapproved short days, tier, final decision), color-coded. • Filters: by employee, date range, month, tier, flag — combinable. • Per-employee report page: full criterion breakdown per task, daily attendance, leave records, monthly totals, and charts (score trend, estimate-vs-actual, compliant vs non-compliant days). • Observe-only mode (Owner toggle): scores and reports everything but hides the bonus/warning decisions — for calibrating before real money is attached. CSV: export any filtered report to CSV; import task/attendance data via CSV with a column-mapping step. Data integrity (requirements): • Audit log of who changed any score/attendance/leave, with timestamps. • Period-locking: once a month is closed by the Owner, its data is read-only. • An “exceptions” filter showing suspicious rows (missing estimate, zero hours, actual far over estimate, etc.). • Employees can never edit their own scores or attendance. Tech: Your choice (React/Vue + Node/Python/Laravel + PostgreSQL/MySQL all fine). Small-data internal website for ~5–15 users — clean, simple, and responsive for desktop and mobile browsers. Must include working Trello and time-tracker API integrations. Deliverables: Working website, source code, all integrations configured, deployment/hosting setup, and a short handover doc. To apply, include: 1. Links to 2–3 similar dashboard websites you’ve built 2. Your estimate (cost + timeline) 3. Your suggested tech stack and one sentence on why 4. Confirmation you’ve built Trello (or similar) API integrations, role-based logins, and CSV import/export before Start your proposal with the word “CLOTHIVIA” so I know you read this. Generic proposals will be ignored.