A mold modification often starts with a simple email. A customer notices something during a product review, discusses it internally, and sends a message asking for an adjustment. The request might involve changing a feature, moving part of a design, or correcting an area that did not perform as expected.
At first glance, the instruction may seem straightforward. The customer knows what is wrong and expects the mold team to understand what needs to be done. But once the message reaches the design or manufacturing department, questions often begin to appear.
Which drawing is being referred to? Does the requested adjustment apply to the whole feature or only one section? Has the customer changed the product design, or is the request simply intended to correct an issue found during a trial? Is the existing work allowed to continue while the request is being reviewed?
These details can easily be missed in a short email. The result is usually another round of messages, revised attachments, and additional discussions before anyone can make a decision.
A mold change request does not need to be complicated, but it does need to be clear. Before reviewing whether a modification is practical, the team needs enough information to identify the request, understand its purpose, and determine what must be confirmed.
Start With the Right Project Information
One of the easiest mistakes to make is assuming that everyone knows which mold or product is being discussed.
This can happen when a customer has several projects running at the same time, or when a single product has different versions. An email might mention a product name that is familiar to the customer but does not match the identification used in the mold shop.
Even when the project is obvious to the person sending the message, the email may later be forwarded to another department. Someone who was not involved in the original discussion still needs to be able to identify the correct records.
A useful request begins with a few basic details:
- Project name or internal reference
- Mold identification
- Product or part name
- Relevant drawing number and revision
- Contact person handling the request
The drawing revision deserves particular attention. A product may have gone through several design adjustments, and an older drawing can still be circulating in an email thread. Without a clear reference, the design team may compare the request against the wrong version.
It is also worth stating the current stage of the mold project. A modification requested before machining starts is different from one received after several components have been completed. The same design adjustment can involve very different amounts of work depending on when it arrives.
These details may look administrative, but they help prevent a request from being recorded against the wrong project or reviewed using outdated information.
Describe the Change Without Leaving Room for Guesswork
The main part of the email should explain exactly what the customer wants changed.
Requests such as make this area smaller or adjust the surface are common, but they leave too much open to interpretation. A designer may understand the intended direction while still having no clear idea of the final result.
Consider a customer who wants a feature moved because it interferes with product assembly. The email might identify the general problem, but it should also show which feature is involved and where it is expected to sit after the adjustment.
A marked drawing is often more useful than several paragraphs of explanation. The customer can circle the affected area, add a note, and show the intended position. For a change involving several connected features, separate markings can help distinguish each requested adjustment.
The written explanation should cover three things.
First, what does the existing design look like? A reference to the current drawing or an actual sample is usually enough.
Second, what is expected to change? The request should describe whether a feature needs to be moved, removed, added, reduced, or reshaped.
Finally, what must remain as it is? This last point is easy to overlook. A customer may want one area modified without realizing that a loosely worded instruction could be interpreted as permission to change nearby features as well.
| Item | Information to include |
|---|---|
| Existing condition | Current drawing, sample, or photograph |
| Location | Exact feature, surface, or component involved |
| Requested adjustment | A clear description of what needs to change |
| Expected result | Marked drawing or visual reference showing the intended condition |
| Unchanged features | Areas that must retain the existing design |
| Related requirements | Any fitting, appearance, or assembly conditions that still apply |
There is no need to write a long technical explanation when a clear drawing can show the difference. The aim is to make the request understandable to someone who has not taken part in the earlier discussion.
Give the Reason Behind the Request
A request becomes easier to review when the reason for the modification is included.
Customers sometimes focus entirely on the solution they want. They may ask for a feature to be reduced or a surface to be adjusted without explaining what led to the decision.
That missing background can cause problems. The design team may follow the instruction but overlook the actual issue.
For instance, a customer may request a change to a product edge because two parts are difficult to fit together. Another request involving the same area might be related to appearance. Although both emails may ask for a similar adjustment, the intended result is not necessarily the same.
The reason for the request helps the team judge whether the proposed change addresses the problem.
Useful background may include:
- An issue noticed during mold trial or product assembly
- Feedback from a product inspection
- A revised product design
- A change in the way the finished product will be used
- A problem found when comparing samples with the approved design
A photograph of the affected area can make the explanation much clearer. If the problem occurs during assembly, a picture showing the parts together may provide more useful information than a photograph of a single component.
It is also helpful to separate what has actually been observed from what the customer believes will solve it.
For example, the observed problem may be that two parts do not fit together as expected. The suggested solution may be to adjust one feature. Both points should be recorded, but they should not be treated as the same thing.
The mold team can then review the proposed adjustment against the original problem rather than simply carrying out an instruction without understanding its purpose.

Make Sure the Affected Scope Is Clear
A request that appears to involve one feature can sometimes reach much further.
Changing a product shape may affect nearby mold surfaces, related components, or the fitting relationship between different parts. Whether these areas actually need modification depends on the design, but they should not be ignored during the review.
The customer may not know which mold components are involved. That is normally something for the technical team to assess. Still, the request should identify the intended product feature and explain how widely the change is expected to apply.
For example, does the adjustment concern only one product version? Will the same requirement apply to several related parts? Is the customer asking for a change to the current mold or requesting that future production use a revised design?
These distinctions matter, particularly when a mold has already been built or when different product versions are being handled together.
The existing work should also be taken into account. A design change received during early project planning may be relatively straightforward to discuss. A similar request received after machining has started requires the team to check which operations have been completed and whether existing components can still be used.
If assembly or trial work has already taken place, the previous results may also need to be reviewed.
A good change request identifies the intended scope, while the technical review determines whether additional areas will be affected.
Attachments Need Clear References
A revised drawing is often the most important attachment in a mold change request. However, sending a file named revised drawing or latest version does not tell the receiving team whether it is ready for approval or simply being shared for discussion.
This becomes particularly troublesome when several drawings are exchanged over a short period. One person may refer to the latest attachment, while another is still working from a file received earlier.
It helps to keep the supporting documents organized and clearly identified.
Depending on the request, the email may include:
- The currently approved drawing
- The proposed revised drawing
- A marked-up image showing the requested area
- Relevant product photographs
- A sample reference or inspection record
- A design file needed for technical review
Each attachment should have a clear connection to the requested change. When several areas are being modified, it is better to identify them separately instead of placing multiple unrelated changes in one unexplained image.
The status of a drawing also needs to be clear. A file submitted for review is not automatically an approved production document. Similarly, a drawing that has been discussed internally may still require formal confirmation from the customer.
If the customer sends a replacement file, the email should explain what has changed from the previous version. This makes it easier to identify whether the new attachment replaces the earlier one or introduces another request.
The receiving team should also check that all files are accessible. A missing attachment or a file that cannot be opened should be dealt with before the review moves forward.
Clarify the Requested Timing
Customers often include a date in their change request because another activity depends on the modification. It could be a planned trial, an internal product review, or a delivery arrangement.
That date is useful, but it should not be confused with an agreed completion date.
The project team first needs to understand why the timing matters and how much flexibility is available. A request that must be considered before the next trial may need different handling from a modification intended for a future production version.
The email can clarify whether:
- The change is needed before a particular trial or inspection
- Existing production work should continue during the review
- The previous design remains acceptable for current samples
- The modification applies to future production only
- There is a preferred date for receiving the revised mold
These details help the project coordinator discuss the request with the design and manufacturing teams.
It is especially important to mention whether current work should be paused. A customer may assume that machining will stop as soon as an email is received, while the workshop may continue following the previously approved drawings.
Unless there is a clear instruction and an agreed response, both sides may end up working with different expectations.
The team should check the actual production status before confirming a schedule. If completed work needs to be changed, the original timing may no longer be realistic. Any revised arrangement should be discussed and recorded rather than assumed from the date mentioned in the customer's email.
Identify the People Who Can Confirm the Change
Not every person who sends a request has the authority to approve it.
In a typical mold project, the request may pass through several contacts. An engineer may identify the issue, a project coordinator may forward the email, and a manager may be responsible for approving the final design.
The project team should know who is providing technical information and who has the authority to confirm the change.
This is particularly important when a request involves several rounds of discussion. One contact may agree with a proposed solution, but another person may later provide different instructions.
The email should therefore identify the person responsible for answering questions and, where applicable, the person who will provide formal approval.
It is also useful to agree on who should receive updates. If a drawing revision affects manufacturing, the relevant design and workshop contacts need the approved information. If the change affects timing or project scope, the people responsible for those matters should be included as well.
A simple contact arrangement can prevent messages from getting lost between departments.
Check the Possible Effect on Existing Work
The customer may see a modification as a small design adjustment. The mold team still has to check what the change means for work that has already been completed.
An adjustment may involve additional machining, new material, replacement components, or further trial activities. In other cases, the existing mold may only need a limited update. The actual effect cannot be determined from the email alone.
This is why the initial request should lead to a review rather than an immediate commitment.
Before approval, the main areas to examine include:
| Review area | Points to check |
|---|---|
| Existing work | Which machining or assembly operations have already been completed? |
| Mold components | Can the current components still be used after the change? |
| Design information | Do drawings and related records need revision? |
| Manufacturing workload | Is additional machining or component replacement required? |
| Trial arrangements | Will another trial or inspection be necessary? |
| Project timing | Could the modification affect existing milestones or delivery plans? |
The findings should be discussed with the customer before work begins.
If the change requires additional work or affects the agreed schedule, the project team should explain the situation and obtain the necessary acceptance. It is better to raise these points during review than to discover a disagreement after the modification has been completed.
What to Do When the Email Is Incomplete
Not every customer will submit a fully detailed request on the first attempt. Sometimes the email contains a useful photograph but no drawing. In other cases, the requested adjustment is clear, but the reason behind it has not been explained.
The team does not need to restart the entire discussion each time information is missing. It can identify the specific gaps and ask for the relevant details.
For example:
- If the affected area is unclear, request a marked drawing or photograph.
- If the current design version is uncertain, ask which approved revision should be used.
- If the expected result is difficult to interpret, request a revised drawing or a clearer description.
- If the purpose of the change is missing, ask what problem the modification is intended to address.
- If approval is not confirmed, clarify who is responsible for making the final decision.
A focused reply is generally more useful than asking the customer to provide more information without explaining what is needed.
The project coordinator should also keep the original request and the follow-up replies together. Important details can easily become scattered across separate email threads, particularly when design questions are handled by different people.
One practical approach is to maintain a change request record containing the original message, supporting files, open questions, review results, and approval status. This gives everyone a common reference when the request moves from discussion to implementation.
An incomplete request can be discussed, but it should not be treated as permission to change the mold. Until the requirements have been clarified and the necessary approval has been received, the existing approved information remains the reference for ongoing work unless a separate instruction has been agreed.
Keep the Email Simple but Complete
A formal mold change request does not need to read like a technical report. In many cases, a short email with the right attachments is enough to begin a useful review.
What matters is whether someone outside the original conversation can understand the request without having to guess.
The project reference, affected feature, expected result, reason for the change, supporting drawings, and approval contact form the basic information. Timing and possible effects on existing work should also be discussed whenever they are relevant.
Missing details are not unusual. The important part is to identify them before manufacturing decisions are made.
When the request is clear and the related documents are properly recorded, the design team can review the proposed adjustment against the actual requirement. The coordinator can then discuss its effect on ongoing work, obtain confirmation from the right people, and pass the approved information to the next department.
That is what turns a brief customer email into a usable mold change request.
