On this page
The document addresses the supplier’s decision process
Massachusetts’ published 2019 Bosch consent-judgment text concerns vehicle-emissions software. It sets out evaluation of customer requests for new or revised programming, recording determinations and raising concerns with the customer. It also expressly provides for no admission and no finding of wrongdoing.
The court-signature and date fields are blank in the published copy reviewed here, so this case does not assert a verified court-entry date. The useful evidence is the published control design, not a finding that a particular allegation was proved.
Make the request understandable before asking someone to approve it
For a technology or equipment supplier, a change can look small in engineering effort while changing how the customer uses the product. Start with the requested function, intended application, product version and information needed to evaluate it. A vague instruction such as “make it work for the U.S.” leaves too much undefined.
Use this ELN request record. It is an original management exercise, not a reproduction of Bosch’s internal process or a statement that the settlement’s terms apply to your company.
| Record | Question to answer | Person to identify |
|---|---|---|
| Requested change and use | What exactly changes, for which product/version and intended application? | Customer requester and your account lead |
| Evaluation | What technical, contractual or regulatory questions must be checked? | People qualified for those specific questions |
| Decision boundary | What may be supplied, with what limits and remaining conditions? | Person authorised to approve that scope |
| Concern or uncertainty | What is unresolved, and what evidence or specialist input is needed? | Owner of the unresolved issue and escalation decision |
| Delivery record | Does what was supplied match the approved version and scope? | Delivery lead and person responsible for retaining the relevant record |
A familiar customer can still make a new request
Fictional example: a customer asks an industrial-software supplier to disable a check for one U.S. installation. The request describes the desired behaviour but not why the check exists or the conditions at the site. Treating the email as sufficient approval would skip the actual evaluation question.
Management should obtain the missing context, involve the appropriate technical and specialist people, and record the supported decision before the change is supplied. Whether work must be refused, paused or modified depends on the actual facts and applicable requirements; this case cannot decide that for the reader.
Ask for a decision record rather than a general reassurance
Choose one proposed customer change and ask who can explain its intended use, review evidence, approval scope and unresolved issues. If all authority rests with the owner, give management a clear escalation route without expecting it to guess outside its competence.
Use Partner evidence to record what is supported and what still needs an answer. Keep private specifications and customer correspondence in your authorised business systems; the learning tool is for the summary and next decision.
Scope
- This case reads Massachusetts’ published 2019 settlement/consent-judgment text. The reviewed copy does not verify judicial entry, and allegations are not findings or admissions.
- ELN’s request record is a planning suggestion. It does not impose the document’s case-specific duties, retention periods or approval rules on another business.
Next step
In Partner evidence, record a customer change’s intended use, qualified evaluation, approval scope and unresolved concern. Give each missing answer a responsible person before supplying the change.
Sources & review notes
Massachusetts Attorney General / Massachusetts government
Passage, dates and research notes
official-published-consent-judgment-text · Published 2019 text, paragraphs 14–16 and 33–34; judicial-signature field on PDF page 18
Read recitals, supplier-request evaluation provisions, compliance provisions, no-admission/no-finding clauses and execution pages. Publication is not an independently verified court-entry date: the judicial signature/date fields on page 18 are blank, visually checked. No allegations are presented as findings.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.