runbookify
← All plans
Human Resources / Employee Records & Org Chart

Employee Directory & Profile Manager

Build a searchable employee directory where staff request their own profile updates and HR approves before anything changes - so the directory is finally current, accurate, and trustworthy.

BeginnerAn afternoonBuilds onNext.js (App Router) on VercelSupabase (Postgres, Storage, Auth + RLS)Resend (email notifications)
What you'll build

A live, searchable employee directory with photos and org info, a self-service "request a change" flow for staff, an HR approval gate before any record changes, a full audit trail, and a one-click CSV export of the current roster.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A free Supabase account
  • A free Vercel account
  • A free Resend account
  • Your current employee roster as a CSV or Google Sheet

The problem this kills

Your employee directory is wrong the day after you publish it. Someone changed teams, someone moved offices, someone got a new manager, and nobody told HR. So the spreadsheet rots: people email the wrong person, new hires can't find who owns what, and the org chart is a polite work of fiction.

The usual "fix" is to chase everyone once a quarter with a survey, paste replies into a sheet by hand, and hope you didn't fat-finger a manager's name. It never holds. The directory is only as fresh as the last painful round of manual updates.

This plan kills that loop. Employees keep their own profiles current by requesting changes; HR approves the ones that matter before they ever touch the live record. The directory stays accurate because the people who know the truth keep it up to date - without HR losing control of who reports to whom.

What you'll build

A clean internal web app where:

  • Everyone on your team can search and browse the directory - by name, role, department, location, or manager.
  • Each person has a profile: photo, role, department, manager, location, contact info, and start date.
  • Employees can request an update to their own profile (the fields you allow them to touch).
  • HR sees a review queue, compares the requested change to the current value, and approves or rejects it. Only on approval does the live record change.
  • Sensitive fields (role, manager, anything you flag) always require HR approval; trivial ones can be configured to as well.
  • Every change is logged - who requested it, who approved it, old value, new value, timestamp.
  • You can export the current roster as a CSV in the exact columns your HR system or payroll expects.

What's inside the Implementation Plan

The plan is a single markdown file you paste into Claude Code. It walks the AI agent through the whole build, one copy-paste prompt at a time.

It opens by interviewing you about your business - your current roster, your field names, which fields employees may edit versus HR-only, your privacy rules, and your messy exceptions (contractors, dual reporting lines, people between managers). It reads back a short tailored spec and waits for your thumbs-up, so what you build fits your organization - not a generic template.

From there it builds the database, the import, the directory screens, the request-and-approve flow, the audit log, and the CSV export - each step ending in a ready-to-paste prompt.

The governance it includes (this is the point)

This isn't a public address book. It's an internal HR tool, so the plan bakes in real governance from the start:

  • Login - only your team can open the directory.
  • Row-level security - people only ever see your organization's data, never anyone else's.
  • Human-in-the-loop approval - the AI and the employee can draft a change, but a real HR person reviews and approves before it's written to the live record.
  • Full audit trail - who requested what, who approved it, the old and new values, and when.
  • Duplicate guards - one profile per employee (keyed on employee ID or work email) so the same person can't be entered twice.
  • Privacy controls - hide personal contact details per your rules so the directory shares what's useful without oversharing.

Who it's for

HR ops people and office managers who are tired of maintaining a directory that's stale the moment it's published - and the employees who can never find the right person to ask. If you can fill in a spreadsheet, you can build this. No coding background needed.

You've got this - paste the first prompt and let the agent interview you.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.