Engineering change management
Engineering changes that reach everyone they should.
One change to one part has to reach the approver, the operator who needs the new file, whoever updates the website, & every salesperson who shows that product. Launchglass routes each engineering change order to all of them, chases every open step, and shows you who’s blocking — autonomously.
The problem
An engineering change is easy to approve and easy to lose.
Somebody downstream always gets missed.
The ECO gets approved. Then the new drawing never reaches the shop floor, the catalog still shows the old part, and sales hears about it from a customer.
Nobody confirms they saw it.
An email announcing the change isn’t proof anybody acted on it. When something goes wrong, there’s no record of who was told, or when.
The routing lives in one person’s head.
Which changes need a second approver, which ones touch showroom stock. Whoever knows becomes the bottleneck, and the process stops the week they’re out.
The solution
Write the routing once. Launchglass runs it on every change.
Rules that read the change
Conditions look at what’s actually on the change, not just whether the form is complete. An expensive change goes to a different approver than a cheap one; one that touches showroom stock pulls in sales.
Assignments, not notifications
Every rule creates real work: these fields, this person, due then. It sits in their My Work queue until it’s done, so nothing depends on somebody reading an email.
Chasing, handled
Launchglass chases what’s overdue & shows who each change is waiting on, how long it’s waited, and how many times they’ve been reminded.
Where your team already works
Requests & reminders land in email, Slack or Microsoft Teams, with a link straight to the change.
A history on every change
Field history & comments record who changed what, and when — the audit trail a spreadsheet can’t give you.
Files travel with the change
Drawings, photos & files live on the change itself, so whoever makes the part gets the right one without having to ask.
Questions
Common questions.
What is engineering change management software?
Software that runs an engineering change from request to done: the request (ECR), the order (ECO) and the notice (ECN). It routes each change for approval, makes sure everybody affected acts on it, and keeps the record. Launchglass does it with rules you write yourself, so it fits the way your plant already works — not the other way round.
What’s the difference between an ECR, an ECO and an ECN?
An engineering change request (ECR) proposes a change and says why. An engineering change order (ECO) approves it and lists what has to happen. An engineering change notice (ECN) tells everybody affected. In Launchglass they can be stages on one board or separate boards — whichever matches how you work today.
Do we need an IT team to set it up?
No. Boards, fields & rules are all set up in the browser, with no code. Whoever runs the process can change the rules themselves, without a consultant.
Does Launchglass work with our PDM or ERP?
Yes, alongside them. Your PDM & ERP stay the record of models, parts & production; Launchglass runs the process around them — who approves, who has to act, and whether they did. Files attach to each change, and data moves in & out by CSV.
Can people outside the core team take part?
Yes. Anybody in the workspace can be assigned work on a change, and a board can be shared by link so people outside it can view, vote & comment — and nothing else.
Get started
Get started free, or let us show you.
Start on the Free plan, no credit card required, and run your first process on it. Rather see it first? Book a 15-minute demo on a process like yours.