“GDS uploaded” is not the same milestone as “design accepted,” and neither means samples are ready to test. A useful MPW handoff connects one frozen layout release to its verification evidence, owners and downstream packaging/test plan. This checklist helps reveal missing dependencies before a deadline becomes urgent.
Define the milestones instead of quoting one lead time
| Milestone | Evidence to request | What it does not establish |
|---|---|---|
| Project/run registration | Provider acknowledgement and remaining conditions | Design acceptance or guaranteed capacity |
| Design submission | Receipt of the specified files and release identifier | Successful signoff |
| Design acceptance | Provider confirmation against the applicable requirements | Wafer fabrication completion |
| Wafer start | Confirmed manufacturing milestone | Packaged-sample delivery date |
| Fabrication completion | Status of wafers/dies and release to the next operation | Passing packaged chips |
| Assembly/test completion | Agreed quantity, inspection/test results and disposition | Receipt at your laboratory |
| Laboratory receipt | Shipment received and incoming checks complete | Functional success on your board |
Ask which dates are contractual, provisional or dependent on other participants. A public calendar is a planning input. For example, GlobalFoundries describes platform-specific shuttles and directs customers to its portal for current schedules; it is not evidence of a reserved MST slot. See the GlobalShuttle program (https://gf.com/manufacturing/services/multi-project-wafer-program/) .
Build a release manifest
Record the following in a controlled handoff package, with an owner for every unresolved item:
| Manifest field | What must agree |
|---|---|
| Layout artifact | Filename, format, revision, checksum, top cell and units |
| Process identity | Foundry/platform, process options, PDK and rule-deck releases |
| Layer interpretation | Required layer mapping and any provider-specific submission conventions |
| Verification evidence | DRC/LVS reports, run configuration and exact layout/netlist revisions checked |
| Exceptions | Remaining errors or waivers, rationale and named approval authority |
| Physical interfaces | Die outline/thickness assumptions, pad map and package/assembly drawing revisions |
| Test handoff | Sample allocation, test owner, required data and acceptance criteria |
Do not pair a clean report from an earlier layout with a new file merely because the top-cell name matches. A checksum can identify the artifact; it cannot prove that the circuit passes DRC/LVS or that a waiver is accepted. Follow the actual provider's verification and submission requirements.
Worked example: schedule backward from the laboratory
Suppose an invented planning exercise allows 7 calendar days for shipment, 21 calendar days for packaging/test and 14 calendar days of contingency after fabrication. The total is 7 + 21 + 14 = 42 calendar days. In that simplified sequence, fabrication must complete at least 42 calendar days before the target laboratory receipt date.
These are teaching assumptions, not observed supplier lead times. This calculation does not determine the GDS submission date: fabrication duration, run acceptance, queueing, holidays and upstream review time still need provider confirmation. If operations overlap, model the actual dependencies instead of simply summing every duration. Test-board and fixture preparation may run in parallel but still block useful measurements if unfinished.
Use the tools for the checks they actually perform
The report revision checker (https://mst-sg.com/tools/report-revision-check/) helps compare report metadata with a selected release. The handoff manifest generator (https://mst-sg.com/tools/gds-handoff-manifest/) organizes artifact identity and handoff information. Neither runs signoff DRC/LVS or approves a design for a foundry.
Try the synthetic exercise in the MPW handoff handbook (https://mst-sg.com/tools/mpw-handoff-handbook/) before using your project's controlled data. Use the procurement timeline planner (https://mst-sg.com/tools/mpw-procurement-timeline/) to record assumptions and owners. Keep restricted design files out of public discussion threads.
Primary references and further reading
- GlobalFoundries GlobalShuttle program (https://gf.com/manufacturing/services/multi-project-wafer-program/) : current platform/calendar context and provider confirmation.
- EUROPRACTICE access and registration (https://europractice-ic.com/access-and-registration/) : project/run registration is a separate workflow.
- MST first-silicon tapeout checklist (https://mst-sg.com/news/how-to-tapeout-a-chip-first-silicon-checklist/) : design, handoff and downstream sample preparation.
Next step: request an MPW readiness review (https://store.mst-sg.com/mpw#mpw-inquiry-form) with a non-confidential milestone plan and list of missing evidence. Continue with the packaging and quotation guides in the MPW community (https://store.mst-sg.com/community/c/mpw) .