Projects and technical decisions
Work, explained.
The challenge, the integration, and what the team could do afterwards. Each write-up says who delivered it.
The freight dashboard that replaced a spreadsheet
A twelve-tab spreadsheet turned into one page the dispatch team opens first thing.
An operations dashboard for a freight team, built by copying the spreadsheet they already trusted.
- Morning checks take minutes rather than the half hour the spreadsheet cost.
- Late loads are visible before the first customer calls about them.
- The TMS sync reports its own failures, so no one trusts a stale number.
A referral portal that could explain itself
Referrals moved off fax and onto a logged, auditable path between eleven clinics.
A referral system for a clinic network, built around an audit trail the privacy officer would sign off on.
- Median referral turnaround fell from four days to under nine hours.
- Every action has an author and a timestamp, so a dispute has an answer.
- Clinic staff stopped keeping a shadow spreadsheet because the portal reports it.
One codebase, fourteen regional sites
Fourteen microsites rebuilt as one distribution, with room for each campus to be itself.
A university network of fourteen sites consolidated onto one Drupal distribution without erasing campus identity.
- Core and security updates now land across every campus in one deployment.
- A regional editor publishes a page without waiting on central approval.
- Shared components mean one accessibility fix is a fix for all fourteen sites.