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 an internal Knowledge Base Manager. Core objects: Article (title, category, body in markdown, owner, status Draft/Published/Archived, last reviewed date, review interval in months, tags). Screens: 1. Browse — sidebar of categories, searchable article list, article reader with rendered markdown. 2. Editor — markdown editing with live preview, category, tags, owner and review interval. 3. Health view — articles past their next review date, articles with no owner, and articles never opened. Rules: next review date = last reviewed + review interval. Flag overdue articles clearly in the accent colour. Design: documentation-style dashboard, left sidebar, comfortable reading width, dark mode support.

Build a Policy Acknowledgement Tracker. Core objects: Policy (title, body, version, effective date, audience departments) and Acknowledgement (policy version, employee, acknowledged at, signature text). Screens: 1. Policies list — each with version, effective date and a completion percentage bar. 2. Policy detail — full text, the list of who has and has not acknowledged, and a chase action. 3. Employee view — outstanding policies to read, with a scroll-to-bottom-then-confirm flow. Rules: publishing a new version resets acknowledgements for that policy and marks it outstanding again. Add an export of the acknowledgement register. Design: dashboard with left sidebar, serious and legible typography, dark mode support.

Build an Expense Approval Tracker. Core objects: Expense (submitter, date, merchant, category, amount, currency, project or cost centre, receipt attachment, description, status Draft/Submitted/Approved/Rejected/Reimbursed, approver, decided at). Screens: 1. My expenses — submission form with receipt upload and a list of my claims by status. 2. Approvals inbox — expenses awaiting my decision, with the receipt shown side by side. 3. Finance view — all approved expenses, filterable by month, category and cost centre, with totals and a CSV export. Rules: expenses under 100 need one approval from the line manager; 100 and above also need finance approval. Rejections require a comment. Design: dashboard with left sidebar, mono for all amounts, 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 an Office Space and Desk Booking tool. Core objects: Space (name, type desk/meeting room/parking, zone, capacity, amenities) and Booking (space, person, date, start time, end time, recurring rule, checked in boolean). Screens: 1. Book — pick a date, see available spaces by zone as a simple grid, book in one click. 2. My bookings with cancel and check-in actions. 3. Occupancy report — utilisation per zone per weekday over the last month, plus a no-show rate. Rules: prevent double booking of the same space and time. Auto-release a desk booking not checked in by 11:00. Design: dashboard with left sidebar, zone grid with clear available/taken states, dark mode support.