# Release, as-built and the fab package

> Mark which take was built or ordered, upload the fab package, and read the comparison against the reviewed design.

_Source: E-Sharp (esharp.se) · Probe guide_


When a design goes to manufacturing you want to be able to show *which* take was actually built, and to catch an export made after the review. You do that with release and the fab package.

## Mark a take as released or ordered

You record that a take was released for manufacturing or ordered, with a date and a fab/order reference. Then everyone knows which version is as-built — not just which was last reviewed.

## Copper changed after release

If copper changes after a take has been released, Probe raises it (the rule for copper changed after release). A late layout change on an already-released take is exactly the kind of thing that needs to be visible.

## Upload the fab package

The fab package (Gerber, drill, IPC-D-356) is uploaded over the API — the server can't see your disk. The upload recipe is in the ingest information, with an upload ticket for the upload routes only.

## Confirm the layer mapping

When the package has come in, you confirm or correct its layer mapping, so Probe's layers match the shop's. After that you can read the comparison between the fab package and the reviewed design.

---

Related: [boards, takes and the design line](/en/probe/support/boards-takes-and-the-design-line) and [compare takes](/en/probe/support/compare-takes).

*Probe is E-Sharp's design-review engine. A report always carries which board and which take it applies to.*
