The story behind FlightDeck

FlightDeck was built by a working print and project manager, for the problems a wide-format print and sign shop hits every day.

I've spent more than twenty years in large-format and sign production, most of it in prepress, the spot every job funnels through before it prints. That seat teaches you one thing fast: the file is where jobs live or die. A missing font, a 16 dpi logo dropped into a ten-foot banner, a color that was never going to hold. Catch it early and it's a two-minute fix. Miss it and it's reprinted vinyl, a blown deadline, and a conversation nobody wants to have.

For years I did what everyone does, which is check all of it by hand, job after job, hoping I didn't blink at the wrong moment.

So I started building. First a script for the thing I did most, then another, then the pieces that watch a folder and check files before I even open them. None of it came from a product roadmap. Every part of FlightDeck exists because it solved a problem I actually had on a real deadline, then earned its place by saving me the same trouble the next week.

Over time the scripts became a pipeline: files land, get validated against real production rules, and reach the RIP print-ready. Alongside it grew Shop Traveler, a board to track the work across the floor. What started as a personal shortcut turned into the toolkit I always wished someone would hand me.

That's what FlightDeck is now, and why I'm sharing it. The people who feel these problems most are other prepress operators and print architects fighting the same troublesome files every day. If that's you, this was built by someone sitting in the same chair.