When Your Job Shop Outgrows Spreadsheets: An ERP Readiness Checklist

Start with a job your team knows well. This checklist helps a job shop or small manufacturer identify difficult handoffs, prepare useful data and decide what an ERP pilot should prove before committing to a wider rollout.

Look for repeated handoff problems

A spreadsheet can be a useful working tool. The question is whether the next person can act on the information it holds. When sales, purchasing and production keep separate versions of the same job, an update can reach one team while another continues using an older record.

Review a few recent jobs with the people who handled them. Identify the decision that became difficult, the information that was missing and who had to find it. A recurring problem is a stronger starting point than a long wish list of software features.

If your current records stay accurate, the team can find the approved version and handoffs work reliably, keeping the current tools may be reasonable. Document what works before deciding that a wider system change is needed.

  • A customer change is recorded in email but has to be copied into several planning files.
  • The planner cannot tell whether a material shortage has a purchase order or a confirmed receipt.
  • The shop floor and office give different answers about the next operation or current job status.
  • Shipping waits for someone to locate inspection results or confirm what is ready to leave.

Follow one job from quote to shipment

Choose a representative job and put its records in order: customer request, quote, sales order, part revision, materials, operations, inspection and shipment. Include an exception your team actually handles, such as a revised quantity or a late material receipt.

For each handoff, name the record being passed, the person responsible and the condition that means the next team can proceed. Record any work done outside your current system. This becomes the workflow you ask a provider to demonstrate.

Prepare a small, owned set of records

Do not begin by importing every file the business has accumulated. Prepare enough records to run the selected workflow and identify who can correct them. Keep units, identifiers and revision rules consistent; retain the source files so the team can check an import against its origin.

Agree where the approved version of each record lives and who is responsible for updating it. Mark unresolved records rather than silently guessing missing values. The pilot should test those responsibilities as well as the software screens.

Prepare a small, owned set of records
RecordWhat to prepareSuggested owner
Customer and orderCustomer identifier, current requirements and delivery dateSales
Part and revisionPart identifier, current drawing and revision ruleEngineering
MaterialsUnits, bill of materials and stock or shortage informationEngineering and inventory
OperationsOperation sequence, required resources and current progressPlanning and production
Purchasing and receiptSupplier, purchase order and received quantityPurchasing and receiving
Inspection and shipmentRequired checks, results and outgoing delivery recordQuality and logistics

Write down what the pilot must prove

Assign a business owner who can settle process decisions and a representative from every team in the selected workflow. Reserve time for those people to review records and try the work themselves. A demonstration by a provider is useful, but it does not show whether your team can operate the process.

Choose a small set of observations before the pilot starts. Define the same start and finish points for the current workflow and the trial. Set the sample, acceptance target and review date with your team; do not borrow a promised saving from another business.

For each observation below, record the current result, the proposed acceptance target, the person taking the measurement and the review date. Keep the job sample and measurement method attached so the comparison can be checked.

Write down what the pilot must prove
ObservationHow to record a baseline
Finding a job's current statusTime from asking the question to finding the agreed current record
Passing a change to the next teamWhich records are updated and whether the receiver sees the approved revision
Resolving a material shortageWhether the planner can trace the shortage through purchasing and receipt
Closing the handoff to shippingWhether required inspection and delivery information can be located together

Bring this checklist to an ERP demonstration

Use your sample job and ask the people who do the work to participate. Ask the provider to identify which steps are available now, which depend on your plan and which would need additional work. Keep the answers beside your workflow rather than relying on a feature checklist alone.

For an independent example of process-led selection, NIST MEP describes a manufacturer mapping its current processes and future requirements before preparing scope and evaluating providers. The recommendation here is to bring your own evidence to that evaluation; that external account is not a Zorveq customer case study.

Check items as you work. Selections reset when you leave this guide.

0 of 7 checked

Decide whether to pilot, prepare or pause

You are ready for a focused pilot when the workflow is understood, the sample records have owners, people can make time to test, and the team agrees what success would look like. You do not need every historical record cleaned first, but you do need a way to identify and resolve the gaps in the pilot.

If no one can approve a part revision, explain a stock discrepancy or own a handoff, settle that process first. Software cannot decide those responsibilities for you. If the difficulty is isolated to one report or one disconnected tool, discuss whether a smaller integration or process change would address it before planning a wider ERP project.

Discuss the workflow with Zorveq

Zorveq ERP is a hosted manufacturing workspace for job shops and small manufacturers. It connects sales, engineering, purchasing, inventory, production, quality, logistics and finance, with job and operation tracking through a shop-floor kiosk. Available modules depend on the company's plan, and pricing is quoted for each business.

Bring your workflow, team size, current tools and sample records to the first conversation. Use the brief below to describe the handoff you want to improve and the evidence a pilot should produce. Scope, included modules, implementation and ongoing support need to be agreed for your company.

Copy an ERP readiness brief

Use this starting point and replace it with your own requirements.

Business and type of manufacturing:
Team size and departments involved:
Current tools and systems:
Representative job or order:
Handoff that is difficult today:
Approved source records, their owners and known gaps:
Requirement changes or exceptions to test:
Baseline observation, current result and measurement method:
Pilot acceptance target and measurement owner:
People available to test and approve:
Integrations or constraints:
Proposed review date and next decision:

Bring one real workflow to the conversation

Share your current tools and the handoff you want to improve. We can discuss a practical starting scope for Zorveq ERP.

Discuss your ERP readiness