Case study
EVP Connect
Schedules, shift sign ups and news for staff at a 400+ person poultry plant in Nova Scotia, with no monthly bill per person.
The problem
The plant runs on paper. Schedules go up on a wall, and people queue in the hallway to read them or miss them because they are rushing. Overtime and volunteer shifts are signed up for on a sheet, where a name can be written by mistake, or by somebody else on purpose. Phones are not allowed on the floor, and most staff have no company email, so anything sent by email reaches the office and stops there.
Announcements and changes go out by email, so anyone who joins today has no access to anything sent before they arrived. Giving every employee a company email address would have meant a recurring cost for every head on the floor, so I built around that rather than into it. One platform carries the schedules, the sign ups, the announcements and the contact list, and it adds no monthly bill per person.
What it does
Staff open EVP Connect on their own phones, before or after a shift. They see the schedule for their own department, read news and announcements, and put their name down for internal postings and Sunday overtime. They can find office staff, send them a message, and fill in forms that already know who they are.
New accounts wait until People Services approves them. When someone leaves, People Services marks them as gone and their access ends. Supervisors add names from the paper sheets, export them, and print clean lists for the notice boards, because the wall is still how news reaches people during a shift.
How I built it
I built it from scratch in Next.js and TypeScript, with PostgreSQL on Supabase and hosting on Vercel. Sign in uses my own signed cookies rather than a hosted login service.
The server is the only thing trusted. The browser is told what a person may do so it can draw the right buttons, and every action is checked again on the server. Five roles decide who can do what.
Sign in lasts nine days, because staff open the app only a few times a week. That created a real problem: a removed person would keep access until their pass expired. So I built a way to cancel every pass for one person before I built the offboarding screen. Every privileged action is written to a record the database itself refuses to change or delete, and I tested that against the live database.
How it went
Feb 12, 2026
Presented to People Services and the CFO.
Jul 14, 2026
Presented to the full executive team.
Jul 31, 2026
First IT security review.
Aug 6, 2026
Every change IT asked for was built.
Aug 26, 2026
Second IT security review. IT approved it after this review.
Where it stands
Reviewed by the executive team over several rounds. Approved by IT after two security reviews, with every change IT asked for built and shipped.
I check every change with a full build and by working through the screens by hand.
Why I built it
Nobody asked for this to be built. I built the whole thing from scratch in my own time, with no funding and nothing behind it, because the people dealing with that friction every day deserved better than paper on a wall.
Inside the app
The clip and these screens show the real app running in a demo mode, on made up people and records.
Features at a glance
Digital Shift Sign Ups
One click overtime and volunteer shift registration with auto generated reports.
Production Schedules
Accessible from any phone, anytime, anywhere. Replacing paper schedules that were easy to miss.
Smart Announcements
Company wide notifications that auto expire when no longer relevant.
Staff Directory
Quick access to office contacts. Critical for night shift workers who start at 4:30 PM after office staff have left.
News Feed
Central place for company updates and team connections, keeping all shifts informed and connected.
Online Forms
Digital forms replacing paper processes, reducing errors and making submissions accessible from anywhere.