Internal tools, sorted by the team that needs them.

Build an Employee Onboarding Tracker. Core objects: Hire (name, role, department, manager, start date, status), ChecklistTemplate (name, tasks) and Task (hire, title, owner role e.g. HR/IT/Manager/Facilities, due offset in days from start date, status Not started/In progress/Done/Blocked, notes). Screens: 1. Hires board — cards or table showing each new hire with a progress bar, start date, and count of overdue tasks. 2. Hire detail — the full checklist grouped by owner role, with checkboxes, due dates computed from the start date, and a notes field per task. 3. Templates screen to create and edit reusable checklists; creating a hire copies the chosen template. Rules: progress is the percentage of tasks marked Done. Highlight overdue and blocked tasks in the accent colour. Design: dashboard layout, left sidebar, dark mode support, soft cards with clear section headers.

Build a Leave Management System. Core objects: Employee (name, team, manager, annual allowance), LeaveRequest (employee, type Annual/Sick/Parental/Unpaid, start date, end date, working days, reason, status Pending/Approved/Rejected/Cancelled, decided by, decided at). Screens: 1. My leave — remaining balance, a request form with a date range picker that computes working days, and a list of my requests. 2. Approvals inbox for managers — pending requests with approve/reject buttons and a required comment on rejection. 3. Team calendar — month view showing who is away, with a warning when more than two people from the same team overlap. Rules: balance = allowance minus approved annual leave days. Never allow overlapping requests for the same employee. Design: dashboard with left sidebar, dark mode support, calendar cells using subtle accent fills.

Build a Budget Planning Board. Core objects: BudgetLine (department, category, fiscal year, quarterly planned amounts, owner) and Actual (budget line, month, amount, source note). Screens: 1. Plan grid — departments as rows, quarters as columns, editable planned amounts with row and column totals. 2. Plan vs actual — the same grid showing planned, actual and variance, with over-budget cells in the accent colour. 3. Department detail — monthly actuals against the plan with a simple line chart. Rules: variance = actual minus planned; show it both absolute and as a percentage. Lock planned amounts once a quarter is closed. Design: dashboard with left sidebar, spreadsheet-like grid but with generous spacing, mono numerals, dark mode support.

Build a Project Portfolio Dashboard. Core objects: Project (name, owner, sponsor, team, start date, target date, status Not started/On track/At risk/Off track/On hold/Done, summary), Milestone (project, title, due date, done) and Risk (project, description, impact, likelihood, mitigation, owner, status). Screens: 1. Portfolio grid — one card per project showing RAG status, next milestone, days to target and open risk count. 2. Project detail — milestone timeline, risk register and a status update feed. 3. Weekly review — a printable summary of all projects with this week's status commentary. Rules: a status change requires a short commentary. Automatically flag At risk when the next milestone is overdue. Design: dashboard with left sidebar, RAG shown with restrained colour, dark mode support.

Build a Meeting and Action Tracker. Core objects: Meeting (title, series, date, attendees, agenda, notes), Action (meeting, description, owner, due date, status Open/Done/Cancelled) and Decision (meeting, description, decided by). Screens: 1. Meetings list grouped by series, newest first. 2. Meeting workspace — agenda on the left, notes in the middle, actions and decisions captured inline with quick-add. 3. Actions view — all open actions across meetings, filterable by owner, with overdue items flagged. Rules: opening a new meeting in a series automatically carries over open actions from the previous one. Design: dashboard with left sidebar, fast keyboard-friendly capture, dark mode support.

Build a Resource Capacity Planner. Core objects: Person (name, role, weekly capacity hours, team), Allocation (person, project, week starting, hours) and Absence (person, start date, end date). Screens: 1. Capacity grid — people as rows, weeks as columns, each cell showing allocated hours out of capacity with a subtle fill bar; cells over capacity use the accent colour. 2. Project staffing — for one project, who is allocated and for how many hours per week. 3. Availability view — people with free hours in the next four weeks. Rules: absences reduce that week's capacity proportionally. Allocations are editable inline. Design: dashboard with left sidebar, horizontally scrollable grid with sticky first column, mono numerals, dark mode support.

Build a Product Roadmap Planner. Core objects: RoadmapItem (title, outcome, success metric, horizon Now/Next/Later, quarter, owner, team, confidence High/Medium/Low, effort T-shirt size, dependencies, linked feature requests, status) and Change (item, field, from, to, reason, date). Screens: 1. Roadmap board — Now / Next / Later columns with cards showing outcome, confidence and effort. 2. Quarter view — items grouped by quarter and team, with dependency warnings when an item depends on something scheduled later. 3. Item detail — outcome, metric, linked requests and full change history. Rules: every item must state an outcome and a success metric before leaving Later. Moving an item between horizons requires a reason. Design: dashboard with left sidebar, confidence as mono uppercase badges, dark mode support.