Build Guide Beyond the Buzz · Session 04 · Two HR Tools
Golden Gate ALA
June 4, 2026
←→ steps · ↑↓ tabs · T theme

Two tools. Two how-tos. One link.

Start Here

Both tools you are about to see were built with AI from documents the firm already had. This page holds the working tools and the steps to build them, so you can bookmark one URL and come back to it. Move with the arrow keys or the tabs above. Each how-to follows the same four moves.

Move 1

Gather

Collect the documents you already have, scattered as they are.

Move 2

Write it down

State the structure or the rules once, in plain text.

Move 3

Let AI assemble

AI reads the documents and builds a single working file.

Move 4

Host and maintain

Put it where you control it. Feed it updates to keep it current.

The tools are on tabs 2 and 4. The how-to for each is the tab right after it.

Example 1: The benefits portal.

Live Tool

An employee-facing triage portal. The front door routes a person by their situation, the office selector filters plans, and search reads across every section. Click around inside it. Set the office in its top bar and open the Life Events page.

https://spencerxsmith.com/ala/benefits-portal-demo.html

Generic demonstration build. Fictional firm, sample rates throughout.

How to build the portal.

How-To · Example 1
Before
  • PDF Benefits 2026 FINAL.pdf, buried in an email thread
  • PDF SBC_carrier_v2.pdf on a shared drive nobody opens
  • PDF 50-plus carrier documents across folders, no index
  • ? Employees email HR: "which plan covers my kid's braces?"
No map. You have to already know the filename.
After
benefits-portal/
index.html
medical/
chicago/  denver/   newyork/
dental/  vision/   voluntary/
forms/
enrollment.pdf, 401k-beneficiary.pdf ...
One front door. Reachable by question, not by filename.
The Tool · Claude

Build it in a Project

A Project keeps your source documents in one place so every chat can read them. On a paid plan it scales to a large document set automatically.

  1. Create a Project at claude.ai and name it for the plan year.
  2. Add your benefit PDFs and a short brand note (colors, font, logo) to the project knowledge.
  3. Ask Claude to generate the single-file portal from those documents.
  4. Review on screen, ask for changes, download the finished HTML file.
Projects need a paid plan. Without one, attach the PDFs in a single chat instead. Current details: support.claude.com.
What the AI is doing

Reading your PDFs, organizing them into your structure, and writing the HTML, CSS, and JavaScript so the portal is one file with no server.

Alternatives

ChatGPT or Gemini can generate similar HTML. The real difference is how each reads a stack of PDFs. Pick the one your firm already trusts with this data.

Hosting

Static file. SharePoint, an internal IIS server, or Azure. HR keeps write access and updates it. See the IT spec for the handoff.

Prompt 1 · Build it
Build a single self-contained HTML file (inline CSS and JS, no server, no build step) for an employee benefits portal. Use the PDFs in this project as the source of truth for plans, rates, and forms. Requirements: - A sidebar with sections for Medical, Dental, Vision, HSA/FSA, 401(k), Life and Disability, Voluntary, EAP, Life Events, FAQ, Forms, and Contacts. - An office selector that filters the medical plans by office. - A live search across every section. - A landing page titled "What brought you here today" that routes new hires, life events, form requests, and plan comparisons to the right section. - Link each plan to its source PDF by relative path. - Use our brand: [colors, font, logo note]. - Label all rates as drawn from the attached documents. Return the complete HTML file.
Prompt 2 · Keep it current
Here are the updated benefit documents for the [2027] plan year. Update the portal you built: replace changed rates and plan details, add or remove plans as the documents show, update the Life Events deadlines if they changed, and leave everything else as it was. List what you changed and why, then return the updated HTML file.

Example 2: The licensing tracker.

Live Tool

An HR-facing compliance dashboard. It reads each state's CLE rule against each attorney's earned credits and computes status. Expand a row to see the requirement read against the credits and the exact gap. Look at Sofia Marchetti and Priya Anand.

https://spencerxsmith.com/ala/licensing-cle-tracker-demo.html

Generic demonstration build. Sample attorneys and simplified rules, verify with each jurisdiction.

How to build the tracker.

How-To · Example 2
Before
  • XLS CLE_tracking_v7_FINAL.xlsx, one person maintains it
  • PDF Loose CLE certificates in scattered folders
  • ? The rules live in someone's memory and old bar emails
  • ! A multi-state attorney's second state quietly slips
Status is a guess. Deadlines surface too late.
After
cle-tracker/
index.html  the dashboard
rules/
illinois.md   colorado.md   newyork.md
transcripts/
reyes-IL.csv   marchetti-NY.csv ...
README.md
Rules written down once. Status computed, not remembered.
The Tool · Claude

Give it the rules and the transcripts

The interpretation is the whole point, so the inputs are two things: the rule for each state, and each attorney's earned credits.

  1. Write one rule file per state: total credits, cycle length, and each subcategory such as ethics. Claude can draft these from the bar's site for you to verify.
  2. Export each attorney's CLE transcript from the bar or your tracker as a CSV or PDF.
  3. Ask Claude to build the dashboard that reads the rules against the transcripts and computes status.
  4. Review the flagged attorneys, then download the file.
The tool is only as right as the rule files. Have HR or counsel confirm them. Current details: support.claude.com.
What the AI is doing

Matching each attorney's earned credits to each state's total and subcategory requirements, then computing what remains, the days to deadline, and the status.

Alternatives

ChatGPT or Gemini can build the same dashboard. Whatever you choose, keep the attorney data on a tool your firm controls.

Maintenance

Drop in a new transcript export and the status recomputes. Change a rule file when a state changes its requirement.

Prompt 1 · Build it
Build a single self-contained HTML file (inline CSS and JS) that tracks attorney CLE compliance across jurisdictions. Inputs: - The rule files in [rules/] define each state's requirement: total credits, cycle length, and each subcategory such as ethics. - The transcript exports in [transcripts/] give each attorney's earned credits. For every attorney and every state they are admitted in, compute remaining total credits, remaining subcategory credits, days to the cycle deadline, and a status of compliant, on track, action needed, or overdue. Show summary tiles, a roster filterable by office and status, and an expandable row per attorney that shows the requirement read against earned credits with the exact gap. Compute everything from the data so updating a transcript updates the status. Label all data as sample pending verification. Return the complete HTML file.
Prompt 2 · Keep it current
Here is [attorney]'s updated CLE transcript, and a rule change for [state]: [describe the change]. Update the rule file and the transcript, recompute that attorney's status, and tell me anyone whose status changed as a result. Return the updated HTML file.

Your takeaway.

One Link to Keep

Both tools came from the same four moves: gather the documents, write the structure or rules down once, let AI read and assemble a single file, then host it where you control it and feed it updates. The hard part was never the code. It was deciding what the tool should know.

Tab 2

The portal

Employee-facing triage. Click in and try it any time.

Tab 3

Portal how-to

Structure, tools, and the two prompts to copy.

Tab 4

The tracker

HR-facing compliance. Expand a row to see the read.

Tab 5

Tracker how-to

Rule files, transcripts, and the two prompts.

Bookmark this page. Pick one tool, gather its documents, and run the build prompt this week. Questions? Spencer X. Smith · AmpliphI · spencerXsmith.com

Next in the series.

The Finale

This was Session 4 of 5. One session remains, and it ties the whole series together: the IT foundation that lets everything you have seen actually run inside a firm.

JUN 18
Session 05 of 05
From Systems to Strategy

IT Enabling AI

Where the IT function moves from keeping the lights on to making AI safe, governed, and usable across the firm. The hosting, the data access, and the guardrails that turn a good demo into a capability people trust.

Same time, two weeks out. See you on June 18.