Contingent Worker Roster & End-Date Tracker

The problem this kills

Your employees live in an HR system. Your contractors, temps, and agency workers live... somewhere else. A shared spreadsheet. Three shared spreadsheets. A folder of PO emails. Someone's head.

So the end dates slip. A six-month contractor is still badging in at month eleven and nobody noticed. Tenure limits get blown past, quietly building co-employment risk. People who left months ago still have logins, VPN, and a building badge because no one closed the loop. And when a manager wants to extend or convert someone, the "approval" is a Slack thumbs-up that nobody can find later.

The core problem is that contingent workers are deliberately not employees, so they fall outside the system that would otherwise watch their dates and their access. They need their own watchful roster.

What you'll build

A small, secure web app - just for your team - that holds your contingent workforce in one place and actually pays attention to it:

• A clean roster of every contractor, temp, and agency worker with their agency, owning manager, rate, scope, start and end dates, and the access they were granted.
• Automatic flagging of engagements that are nearing their end date or about to cross a tenure limit, so they surface before they become a problem.
• A human approval gate: a manager or HR must approve any extension, tenure exception, or conversion-to-employee before it's recorded.
• An end-of-engagement handoff that fires the offboarding and access-revocation checklist the moment an engagement ends.
• A full audit trail and a clean CSV export of the roster.

What's inside the Implementation Plan

The plan is a step-by-step runbook you paste into an AI coding agent (Claude Code), and it builds the tool with you - no coding required from you.

It opens by interviewing you about your business - your current process, where your roster lives today, the exact field names and worker-ID convention you use, your tenure rules (12 months? 18? per-agency?), your approval chain, and your messy edge cases. It reads a short tailored spec back to you, you confirm it, and only then does it build. The result fits how you actually run a contingent workforce, not a generic template.

From there it walks you through standing up the database, the login, the roster screens, the end-date and tenure flagging, the approval gate, the email alerts, the offboarding handoff, 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 spreadsheet with a coat of paint. The plan builds in the controls that make a contingent-workforce tool defensible:

• Login so only your team can open it.
• Row-level security so people only ever see their own organization's data.
• A hard human-in-the-loop approval gate before any extension, exception, conversion, or offboard is recorded - the tool drafts, a person approves, then it commits.
• A complete audit trail of who approved what and when.
• Duplicate guards keyed on worker ID (agency + person) so the same worker can't be entered twice and only one engagement is active at a time.
• Clear separation from employees to keep co-employment risk visible and contained, and access that ends with the engagement.

Who it's for

HR operations, procurement, and hiring managers who run a contingent workforce out of scattered spreadsheets and keep losing track of end dates, tenure limits, and who still has access. If "wait, is that contractor still here?" sounds familiar, this is for you.

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