Internal tools, sorted by the team that needs them.

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 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 a Contract Repository. Core objects: Contract (title, counterparty, type MSA/NDA/SOW/Vendor/Employment, owner, status Draft/In review/Signed/Expired/Terminated, start date, end date, notice period days, auto-renew boolean, value, currency, payment terms, attachments, notes). Screens: 1. Contracts table — search by title or counterparty, filter chips for type and status, sortable by end date. 2. Contract detail — all metadata, attachment list, and a renewal panel showing the last date to give notice (end date minus notice period). 3. Renewals dashboard — contracts expiring or requiring notice in the next 30/60/90 days. Rules: highlight contracts where the notice deadline is within 30 days. Never delete records; archive instead. Design: dashboard with left sidebar, mono for dates and amounts, dark mode support.

Build a Legal Intake and Review Queue. Core objects: LegalRequest (title, requesting team, request type Contract review/Marketing claim/Data privacy/Partnership/Other, description, urgency, attachments, risk level Low/Medium/High, reviewer, status New/Triaged/In review/Needs info/Approved/Approved with changes/Rejected, submitted at, closed at). Screens: 1. Intake form with type-specific questions. 2. Triage queue — new requests sorted by urgency, with a risk level selector and reviewer assignment. 3. Review workspace — request details, internal notes, outcome selection with required rationale. 4. Metrics strip — median turnaround time and open requests by risk level. Rules: turnaround = closed at minus submitted at, only counted for closed requests. Design: dashboard with left sidebar, restrained palette with accent used only for risk and status, dark mode support.