Work / Case study
UW Triage Board — Developer Handoff for a Web-Platform Rebuild
Packaging a production Apps Script system so an outside developer can rebuild it with feature parity on Vercel and Supabase, without access to the agency's Google account.
Source code is private. Walkthroughs are available on request.
Business impact
Turns a system that only its builder fully understands into something another engineer can rebuild with confidence, protecting two months of iteration and the agency's stated business rules through a platform change.
Problem
The underwriting triage system grew to two Apps Script projects, a dozen-plus sheet tabs, dozens of Config keys, scheduled triggers and Slack, AI and scorecard integrations over 24 board releases. The agency wants it inside its own web platform (Vercel + Supabase), and the developer doing that work has no access to the Google account and no history of the decisions behind the behaviour.
Solution
A self-contained handoff bundle built from the live code rather than archived copies: a hash-verified source snapshot of both projects, a machine-readable description of every sheet, column, Config key, trigger, deployment, scope and secret name (never values), architecture and state-machine documentation, a dated decision log, an Apps Script → Vercel/Supabase mapping with a proposed Postgres schema, the pure business logic ported with its test vectors, and a context file so the developer's own AI assistant starts from verified facts.
Results & highlights
- Live code wins: every file is pulled from the editor's current version and hash-verified, because archived copies stop several releases behind production
- Secrets and client data swept out by rule, with the sweep commands and zero-hit results recorded in the package manifest
- Business rules carried over verbatim with dates, so parity questions are settled by the record instead of by memory
- Pure logic (next-step rules, due-date math, duplicate detection, scorecard metric definitions) handed over as portable functions with their existing tests, so it is ported rather than re-invented
Competencies demonstrated
- Technical documentation: Architecture, state machine, config catalog and dated decision log written for a developer starting cold.
- Migration planning: Apps Script → Vercel/Supabase mapping with a proposed Postgres schema and API description.
- Security hygiene: Secret names documented, values never included; recorded PII and secret sweep before handoff.
Architecture
- Live source snapshothash-verified, both projects
- System inventorysheets, config, triggers, scopes
- Docs + decision logarchitecture, state machine
- Platform mappingPostgres schema, API shapes
- Developer bundlecontext file, logic + tests
Notes
- Delivered 2026-10-26 to the internal developer. The package itself stays private; this page describes the approach.