Send a clearly identified set of files, say what the manufacturer may use it for, and ask them to confirm the revisions they received. Check that the model, drawing and specification belong together before sharing. If anything changes afterward, contact the manufacturer and agree which work the change affects.
Imagine a small team preparing a desk lamp for a prototype quote. The designer has changed the shade attachment in the CAD model. The PDF drawing still shows the earlier attachment, and a finish note sits in a separate email. Each file looks reasonable on its own. Together, they leave the manufacturer guessing.
A short package list gives both sides something concrete to check. It also helps when someone joins the project later and asks, """Which design did we send?"""
Start with what you are asking the manufacturer to do
Put the purpose at the top of the handoff: estimate a price, comment on the design, make a prototype, or carry out an approved order. Name the product or part, the contact who can answer questions, and any decision still outstanding.
For the lamp example, the message might say:
"""Please quote for five prototype units using package LAMP-04. This request is for pricing and manufacturing feedback. We will confirm the order separately. Please flag any conflict between the files before preparing the quote."""
Ask which formats the manufacturer needs. A drawing PDF, a CAD model, a parts list and a finish specification serve different purposes. Protolabs' sheet-metal guidance, for example, describes cases where a 3D file is sufficient and others where a 2D drawing supplies required details. Your supplier's process determines its requirements. Protolabs file guidance.
Also agree where the manufacturer expects to receive the package. If it requires files through its own quoting or order portal, use that process and record exactly what went there. A shared room can hold the supporting review documents without becoming a second, conflicting instruction to the factory.
Make a package list that someone else can check
Give the handoff a simple package reference and list the exact filenames and revisions. The package reference identifies the set. Each document can keep its own revision numbering; those numbers need to describe a compatible set, even when they differ.
After checking the files, the lamp team's package could look like this:
| Item | Revision in this package | What the team checked |
|---|---|---|
| Lamp assembly model | C | Matches the attachment shown in drawing D |
| Assembly drawing PDF | D | Updated from C to show the changed attachment |
| Finish specification PDF | B | Still applies to this prototype request |
| Prototype request PDF | A | States the quantity, purpose and questions for the supplier |
The designer confirms compatibility. The person sending the package checks that the listed files are the ones actually attached, uploaded or shared. A modified date or a filename ending in """final""" gives much less useful information.
Keep your existing design-review process. Dedicated engineering tools can help: Onshape's release workflow can include associated drawings and warns when those drawings are outdated. A shared folder or data room still needs someone to check which files are ready to issue. Onshape release workflow.
Use the free manufacturing handoff worksheet to list one package, record its destination and capture the manufacturer's reply. It includes the lamp example and blank sections for your own project.
Share the files needed for this job
Keep internal discussions, earlier rejected designs and unrelated customer material outside the manufacturer's review area. Choose the people who need access and decide which files they need to download to do their work.
A manufacturing engineer may need a CAD file in a local design tool. A commercial contact may only need to review the quote request and specification. Ask what their workflow requires before choosing download permissions. A downloaded copy remains separate from later changes to the shared source.
Check the recipient's view before sending the invitation. Can they find the package list and every file it names? Are internal documents absent? Arrange access for additional supplier colleagues through the agreed contact.
The viewing and downloading guide explains that choice in more detail.
Ask for a useful acknowledgment
"""Got the files""" leaves room for misunderstanding. Ask the manufacturer to confirm the package reference, file revisions and next step. Keep the reply with the handoff record in your normal project system.
For example:
"""Please confirm you can open the files listed in LAMP-04: model C, drawing D, finish specification B and prototype request A. Please identify anything missing or inconsistent. We are requesting a quote; the prototype order will follow separately."""
Record the name, date and any exception in the reply. A confirmation that the files open tells you about receipt. Design approval, an accepted price and authorization to start each need their own clear agreement.
If the manufacturer reports a mismatch, resolve it with the person responsible for the design before asking them to proceed. Keep the correction and reply together so another colleague can follow what happened.
Handle a later change as a new handoff
Suppose the lamp team changes the shade attachment again after the quote arrives. Replacing the model in a shared location does not tell the manufacturer whether to revise the price, pause preparation or change an order already underway.
Use a short change message:
- Identify the previous package and the proposed replacement.
- List the changed files and describe the change in ordinary language.
- Ask whether it affects the quote, material already ordered or work in progress.
- Agree what happens next and keep the manufacturer's reply.
For example, package LAMP-05 could contain model D and drawing E, with finish specification B unchanged. Keep a record of LAMP-04 as the earlier issued package. Mark which package the manufacturer has agreed to use for the next step.
Contact the manufacturer directly if work may already have started. Supplier processes vary. Protolabs' ordering guidance, for example, says part changes depend on the order's stage and cancellation can involve fees. Updating a shared file alone cannot change an accepted order. Protolabs ordering guidance.
Where Aurora can help
In Aurora, your team can keep review documents in a library and select which ones appear in a manufacturer's room. The manufacturer sees only that selection; internal material stays outside the room.
When you add a new version to a shared source document, rooms that include it show the current version the recipient can access when they reopen or refresh. Earlier versions remain in its history. You still need a package record and a clear message when a change affects the supplier's work. Files already downloaded do not update themselves.
Aurora does not check whether a CAD model matches its drawing or approve a design for manufacture. Keep engineering approvals and any required product-specific controls in the systems your team uses for that work. The example here concerns sharing and handoff, with the design already checked by the responsible person.
Try it with one small package
Start with four sample PDFs: a drawing export, a specification, a request and a package list. Check that the list matches the files, then ask a colleague to review them as the recipient. This exposes missing context before a real supplier has to ask for it.
Try Aurora with a sample project: use one library and one room for those PDFs, then add a revised specification and check the recipient's refreshed view. This small exercise fits the current 30-day Starter trial. Leave actual manufacturing instructions in your agreed approval process while testing.
You can also complete the handoff worksheet with your existing tools today. When it is filled in, you and the manufacturer should be able to point to the same file set and the latest agreed change.
Manufacturing file handoff worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use this free worksheet for one package sent to one manufacturing partner. Copy it into your project notes. Your designer checks technical compatibility; the sender checks the files actually delivered. Keep the manufacturer's reply with the record. This worksheet does not approve engineering work or replace your supplier's order process.
1. Say what this handoff is for
- Product or part:
- Package reference:
- Purpose: quote / design feedback / prototype request / approved order / other:
- Work the supplier is authorized to start, if any:
- Separate approval or order still required:
- Person responsible for design approval:
- Sender and question contact:
- Supplier contact and expected recipients:
- Destination: shared review area / supplier portal / other:
- Date and timezone sent:
- Supplier's required file formats:
- Supplier acknowledgment requested by:
2. Record the exact file set
List every issued file. Different revision labels can belong in the same package if the designer has checked compatibility. Include the document's revision and, if useful, the sharing tool's version number as separate fields.
| Exact filename | Document revision | Tool version or issued-copy reference | Checked by / date | Recipient use |
|---|---|---|---|---|
3. Check the recipient's view
- [ ] The package list matches the files actually delivered.
- [ ] The responsible designer has checked model, drawing and specification compatibility.
- [ ] The purpose and any separate authorization to start are clear.
- [ ] Required formats open in the supplier's agreed workflow.
- [ ] Only people and documents needed for this review are included.
- [ ] Download access matches the work the recipient must do.
- [ ] Internal material and superseded working drafts stay outside the current package.
- [ ] Files submitted through a supplier portal match this record.
- [ ] Earlier issued packages and their replies can still be found in the internal record.
4. Capture the supplier's reply
Suggested message: """Please confirm you can open the files listed in [package reference], with the revisions shown. Identify anything missing or inconsistent and confirm your next step. [State whether this is only a quote request or refer to the separately approved order.]"""
- Reply from / date / timezone:
- Confirmed package and revisions:
- Missing files or conflicts:
- Who will resolve them / by when:
- Agreed next step:
- Approval or order reference, if applicable:
- Reply saved at:
Receipt, engineering approval, price acceptance and authorization to start can be separate decisions. Record what the reply actually confirms.
5. Track a later change
| Previous package | Proposed replacement | Changed files and revisions | Effect on quote or work, confirmed by supplier | Agreed next step / name / date |
|---|---|---|---|---|
- Reason for change:
- Existing downloads, portal copies or work in progress to discuss:
- Person who contacted the supplier / date:
- Current agreed package after the reply:
- Earlier package record retained at:
- New files checked in the recipient's view by / date:
If work may have started, contact the supplier directly. A changed shared file does not by itself amend an order or recall downloaded copies.
Worked example: a desk-lamp prototype quote
Purpose: quote for five prototypes; order approval will follow separately. The designer finds that model C uses a revised shade attachment while drawing C still shows the previous attachment. The drawing is corrected and issued as D before the package is sent.
| Package LAMP-04 | Revision | Check |
|---|---|---|
| Lamp assembly model | C | Matches drawing D |
| Assembly drawing PDF | D | Attachment corrected from C |
| Finish specification PDF | B | Applies to the quote request |
| Prototype request PDF | A | Five units, quote and feedback only |
The sender asks the supplier to confirm these four revisions and that the next step is a quote. The acknowledgment fields stay blank until a real reply arrives.
A further design change would become LAMP-05 with model D and drawing E. The finish specification could remain B. The team would ask whether the change affects the quotation or any preparation, then record the supplier's reply before treating LAMP-05 as agreed.
The same method works with your current file-sharing tools. If trying Aurora, use sample PDF exports in one library and one room; keep actual design approval and ordering in your existing process.
