The machines are there. The materials are there. Skilled people are there. But time keeps disappearing into the gaps between them: email threads about which CAD version worked, whiteboards that only make sense to one shift, and spreadsheets assembled at month-end to work out what the lab actually cost.
The equipment is only part of the system. The workflow around it determines how reliably the team can use it. This guide is for internal labs and teams that combine internal requests with external customer orders.
Two types of work, one manufacturing team
An internal lab may produce R&D prototypes, one-off requests from other departments and recurring parts for production. There may be no commercial quote to win, but the team still needs the right file, a clear requirement, an agreed priority and a record of what was made.
A mixed team has those responsibilities alongside commercial pricing, shipping and accounting. Treating every request as an informal email makes it difficult to see which jobs are ready for production and which are still waiting for information.
Start with a request that someone can manufacture
A CAD file rarely provides the whole brief. Before releasing a job, capture the intended use, required quantity, material, important dimensions, finish, required date and the person who can answer technical questions. Record the project or cost reference using the fields and integrations configured for your organization.
An illustrative request for a fixture might say: “Revision C, four units, nylon, check clearance against the supplied assembly, required for the test on Friday.” That gives the lab a much better starting point than “please print attached.” It also identifies the acceptance question before anyone chooses a process.
Keep unresolved requirements visible. An urgent request with an unanswered material question is not ready work simply because its due date is close.
Keep the design and manufacturing specification together
Phasio distinguishes part designs, revisions, manufacturing specifications and customer requisitions. A revision identifies the geometry; a specification records how that geometry is to be manufactured. Keeping both matters when an engineer changes the file but expects the same finish, inserts or inspection requirements.
The part design guide explains how to view revisions and similar designs. The specification guide covers materials, post-processing, customer references and manufacturing constraints.
Before a revised design enters production, check which previous decisions still apply. A similarity match is useful history, not an engineering approval. Record the approved change so the next operator does not have to reconstruct the conversation.
Give each production run a clear route
A prototype may need printing, cleaning and a fit check. A recurring component may need a controlled sequence with additional inspection. They can share equipment without sharing every operation.
In Phasio, a work order is a production run with its own routing and quantity tracking. Production routing can use the current process configuration or an approved template on a part specification. The route is snapshotted when the run is created; later template changes do not rewrite the route of work already in progress.
For an internal lab, this provides a practical way to distinguish experiments from repeat work. Start with the normal process, and create an approved template where a part needs a consistent sequence. Define who may approve a route and what evidence they need before approval.
Record problems while the job is happening
When a part fails, record the reason while the circumstances are still clear. Phasio's scrap and trace workflow records movement through production and supports adding replacement quantities to the existing run. Its documentation also describes a limit: replacement units do not have a separate lineage connecting them to an individual scrap record.
Those records can support investigations and your quality system. They do not, by themselves, establish certification, validate a process or guarantee that every fact an auditor needs has been captured. Decide which additional material, inspection and approval records your work requires.
Remove repeat administration
The administrative work worth removing first is the work that adds no new decision: finding the agreed file, re-entering the material, asking for the same project reference, or rebuilding a familiar production route.
For recurring parts, a customer-specific catalog stores predefined parts and specifications. For financial administration, the accounting integration guide describes supported systems and configuration. Confirm the required account mappings and your internal cost-allocation process before assuming a commercial invoicing integration covers internal chargebacks.
Do not confuse these changes with automating engineering judgment. A request can be easy to submit while still needing someone to assess whether it is appropriate for the selected process.
Introduce the workflow one queue at a time
Choose one repeatable request type. Agree its intake requirements, identify the person who resolves missing information, and document its normal route. Then run real jobs through the process and review the exceptions with the people doing the work.
Useful measures include requests returned for clarification, time spent waiting for approval, jobs made from the wrong revision and repeat orders that require manual reconfiguration. Review those measures alongside the team's observations rather than relying only on machine utilization.
The machine is the asset. A clear workflow helps the team apply its skill consistently. See how Phasio production management connects the request, part record and production run.
READY TO TRY PHASIO?
See how Phasio transforms manufacturing workflows
From instant quoting to order management, explore the platform and get hands-on in minutes.