We took three separate things — waivers, inspection forms, and checklists — and rolled them into one feature: Forms.
It's a form builder. You build your own custom forms, as many as you need, for whatever use case your shop has — instead of working around a template someone else wrote. A performance shop and a restoration shop don't collect the same information, and neither of them collects what a general repair shop does. So rather than shipping a fixed set of forms and hoping they fit, MSA gives you the builder and gets out of the way.
Build whatever your shop actually uses
Anything you currently hand someone on a clipboard or chase down as a PDF can become a form you build:
- A customer waiver before the car goes on the dyno
- A vehicle intake sheet documenting condition on arrival
- A project inspection sheet for a long build
- A Form for documenting what modifications has a car before you start to tune the car
- A standard operating procedure your techs follow on every job of a given type
- Build the NASA race inspection form straight into your task
- Engine blueprinting, track all the clearances, torques, and process for building any engine
- A pre-delivery checklist before the car goes back to the customer
Build one for each thing your shop does. Build a dozen. Build a different intake sheet for engine work than the one you use for a full restoration. The builder doesn't care what you're making — what changes is what you put on it.
Each form can do several jobs at once
This is the part worth understanding: you're not picking a form type when you build one. A form isn't a waiver or an inspection or an SOP — any form you build can be all three at the same time.
Think about what a dyno tune actually involves. There's a procedure your tech follows every time to make sure its ready to go. There is a list of mods that change the base map you need to build. And there's a waiver the customer needs to sign before any of it happens. Under the old way of thinking that's three documents. Here it's one form you built: the SOP steps, the inspection fields, the list of mods the car has, and the signature, all in the same place.
Same for a project intake. The procedure for receiving a car is a standard operating procedure. The condition you record while doing it is an inspection. The customer's acknowledgment of that condition is a waiver. Both built from the same Forms builder.
Building your SOPs this way means the procedure isn't a separate document your techs are supposed to remember — it's built right into the task they are already tracking time on and manually adding comments and notes to it.
Why one builder instead of three features
Most of the functionality used in each type of form, can be used accross other forms as well. It only made sense to combine the functionality of all three into a single feature, making it easy for you to build a form, copy it to use for other use cases, and utilize them however you want.
Everything lands on the job
Every form is attached to a job, so the record lives with the work it belongs to. Users can sign the forms you build, which means the acknowledgment is captured right there rather than living in a filing cabinet or an email thread.
The practical value shows up on the jobs that go sideways. When a customer says the scratch wasn't there before, an intake form with the answers filled in and signed on arrival settles it. When a build has been sitting for three months and nobody remembers what was checked, the inspection is on the job.
And when a tech follows the same SOP on every engine that comes through, you get consistent work rather than consistent hope. This is what makes your task history worth trusting when you go to price the next one.
Watch the walkthrough above to see the builder in action.