Internal tools, sorted by the team that needs them.

Build an Internal Ticketing System. Core objects: Ticket (title, description, requester, assignee, team, category, priority low/medium/high/urgent, status Open/In progress/Waiting/Resolved/Closed, created date, due date) and Comment (ticket, author, body, date). Screens: 1. Queue view — table with filter chips for status, priority and team, plus a search box. Show an SLA countdown per ticket based on priority (urgent 4h, high 1 day, medium 3 days, low 7 days) and flag breaches. 2. Ticket detail — description, metadata sidebar, status/assignee controls, and a threaded comment feed. 3. New ticket form. Rules: status and assignee changes append a system entry to the comment feed. Add a "My tickets" filter. Design: dashboard with left sidebar, calm dark theme, priority shown as small uppercase mono badges.

Build an Internal Request System. Core objects: RequestType (name, owning team, form fields, approval steps) and Request (type, requester, submitted values, current step, status Submitted/In review/Approved/Rejected/Fulfilled, history). Screens: 1. Request catalogue — cards for each request type (Software access, Equipment, Budget spend, Legal review, Facilities fix) with a short description. 2. Dynamic request form rendered from the selected type's fields. 3. My requests — status timeline for each submission. 4. Reviewer inbox — filtered to the reviewer's team, with approve/reject and comment. Rules: a request moves to the next approval step only when the current one is approved; rejection ends the chain and notifies the requester. Every action is written to an immutable history log. Design: dashboard with left sidebar, mono uppercase status badges, dark mode support.

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 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 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 Bug Triage Board. Core objects: Bug (title, reporter, area, environment, steps to reproduce, expected, actual, severity S1-S4, status New/Triaged/Accepted/In progress/Fixed/Won't fix/Duplicate, assignee, duplicate of, first seen, occurrences). Screens: 1. Triage inbox — new bugs sorted by severity, with quick actions to accept, mark duplicate or decline with a reason. 2. Board — columns by status, cards showing severity badge and area. 3. Bug detail — full report, occurrence count, linked duplicates, and a comment thread. Rules: S1 bugs pin to the top of every view. Marking a duplicate links the two and merges occurrence counts. Design: dashboard with left sidebar, monospace for environment and steps, dark mode support.

Build a Deployment and Release Log. Core objects: Release (version, environment staging/production, deployed at, deployed by, changes list, risk level, rollback of, status Deployed/Rolled back/Failed, notes) and Incident (release, description, severity, started at, resolved at). Screens: 1. Timeline — reverse-chronological releases per environment with version, author and change count. 2. Release detail — the full change list, linked incidents, and a rollback action that creates a linked rollback record. 3. Release notes view — a clean, shareable summary of changes between two versions. Rules: never edit a released entry; corrections are appended as notes. Show time since last production release. Design: dashboard with left sidebar, monospace for versions and timestamps, dark mode support.

Build an On-Call and Incident Tracker. Core objects: Rota (week starting, primary, secondary), Incident (title, severity SEV1-SEV3, started at, acknowledged at, resolved at, services affected, summary, cause tags, responder) and ActionItem (incident, description, owner, due date, status). Screens: 1. Current on-call banner plus the rota for the next eight weeks. 2. Incidents list with severity filters, showing time to acknowledge and time to resolve for each. 3. Incident detail — chronological timeline, summary, cause tags and postmortem action items. 4. Trends — incident count and median resolve time per month, plus the most common cause tags. Rules: SEV1 incidents require a postmortem with at least one action item before they can be closed. Design: dashboard with left sidebar, calm dark theme, severity as mono uppercase badges.

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.