The Return Form Is the Last Paper Process in the Shop
When we mapped the five workflows at the high-performance transmission shop in Kokomo, four of them had clear digital solutions: AI triage for the spec form, routing rules for the shared inbox, status texts for repair updates, automated follow-up for open quotes. All identifiable, all buildable in weeks.
The fifth one was different. Not because it was more complex, but because it's the kind of workflow that gets treated as an exception until you count the hours.
Returns.
The shop's return process runs off a downloadable PDF. A customer who needs to return a part downloads the form from the website, fills it out by hand, and emails or mails it back. A staff member receives it, reads it, re-keys the information manually, and processes the return. No tracking number is issued. No confirmation goes to the customer. The customer has no way to know the form was received.
What "Exception" Workflows Cost
Returns feel like exceptions because they're low-volume relative to the main business lines. If you're handling 30 to 45 spec-form submissions per week and 10 to 20 repair intakes, 5 to 10 returns don't jump out as a systems problem. They get handled individually, by hand, and they work. Nobody tracks the aggregate cost because each return is just a thing that happened.
At 5 to 10 returns per week, at 10 to 15 minutes each to process and re-key manually, that's 1 to 2 hours per week. At $25/hr admin time, it's $1,300 to $2,600 per year. Not a headline number. But it's real, and it's recoverable.
More importantly, the PDF process fails in a specific way that doesn't show up in the hour count: customers who email a return form don't know it was received. They call to check. That's another category of inbound status calls on top of the "where's my converter" calls already taxing the bench.
The Fix Is Three Parts
Digital RMA intake is not a complex build. There are three functional requirements.
First, a web form replaces the PDF. Same fields, submitted through the site.
Second, the submission creates a record and issues a tracking number automatically. The customer gets a confirmation with that number immediately. They know the return was received. They stop calling.
Third, staff see the return in their dashboard without anyone having re-keyed it. Status updates on the return propagate back to the customer the same way repair status updates do: one field change, one automatic text.
That's it. No separate RMA platform. No new integration. The same infrastructure that handles repair status tracking handles this. The fields are different. The shape is the same.
Why This Persists
Paper returns survive in digital operations for a specific reason: they were never prioritized because the volume doesn't force the issue.
A spec form that comes in 30 times a week gets automated because not automating it costs too much. A return form that comes in 8 times a week gets handled manually because 8 doesn't feel like a number that justifies a project.
The audit surfaces it because we're adding up all five workflows together. Any one of them, in isolation, might not pass the threshold where someone builds the fix. Combined, the five workflows at this shop represented $18,000 to $37,700 per year in manual labor. The return form is the smallest line on the list. It still belongs on the list.
The Pattern Across Shops
We see this in every operation we audit. The intake forms are digital. The quotes are digital. The scheduling is digital. Then somewhere in the workflow, there's a PDF someone downloads and emails back. Usually for returns, warranty claims, or something that gets treated as a special case.
Special cases aren't always rare. When 5 to 10 of them happen every week, they're a workflow with a cost. They just don't look like one until someone maps them.
If your operation has a PDF that customers download, fill out, and email back, that's the next build. It's also probably not the only one.