Manufacturing · Build Blueprint

How to Track Work Orders on monday.com: A Build Blueprint

Use one item per work order on a dedicated board, a short set of stages with one owner each, and linked boards for orders, products and materials.

Worktables 15 min read

A supervisor and a planner review a work order on a tablet in a metal fabrication shop, next to the headline “Track every job from release to shipping.”

To track work orders on monday.com, give each work order its own item on a dedicated board, move it through a short set of production statuses with one owner per stage, and connect it to the customer order, the product and the materials it consumes. Dashboards and automations then show what is late, blocked or ready to ship.

This blueprint is for production managers, planners and operations leads at small and midsize manufacturers who currently run the shop floor from spreadsheets, whiteboards and email. It is also for monday.com admins asked to "build something for production" without a clear brief.

We walk through what a work order has to carry, the board structure we use, the statuses and handoffs from release to shipping, how materials and inventory fit in, the views each role needs, and a rollout plan. A hypothetical worked example shows the build end to end, and a list of common mistakes covers what usually goes wrong in the first month.

What a work order needs to carry

A work order is the instruction to make a specific quantity of a specific product by a specific date. Everything else on the shop floor hangs off it: who builds it, what material it pulls, which machine runs it, and when it can ship. If the work order is vague or hard to find, every one of those questions turns into a conversation.

Before building anything, we agree with the team on what a complete work order looks like. In most of the manufacturers we work with, it comes down to the same handful of fields.

FieldWhat it answersWho usually fills it
Work order numberWhich job is this, without ambiguity?Planner (or generated automatically)
Product or partWhat are we making?Planner
Quantity ordered and quantity completedHow many, and how far along?Planner, then production
Customer order or stock replenishmentWho is waiting for it?Sales or planner
Due date and planned startWhen does it have to be done, and when must it start?Planner
Current stage and statusWhere is it right now, and is it moving?Stage owner
Owner for the current stageWho do I ask?Supervisor
Work center or machineWhere is it being made?Planner or supervisor
Materials and availabilityCan we actually start?Purchasing or inventory
Drawings, specs and work instructionsHow exactly do we build it?Engineering
Quality resultDid it pass?Quality

You will not need every field on day one. You do need to decide which of them are required before a work order can be released to the floor, because that decision is what stops half-finished jobs from reaching production.

Why spreadsheets break at this point

Spreadsheets are a reasonable place to start. They are flexible, everyone knows how to use them, and a good planner can run a small shop from one well-kept file. We have seen plenty that work.

The trouble starts when more than one person needs to change the same row. The planner updates due dates, the supervisor updates progress, purchasing notes a late delivery, and quality adds a hold. Each person keeps a copy, or edits at a different time, and the file stops being the single answer to "where is this job?"

The other limit is handoffs. A spreadsheet row does not tell the next person that the job is ready for them. Someone has to notice, or someone has to send an email. That gap between "done here" and "started there" is where a lot of lead time quietly disappears.

The board structure we use

The core of the build is one Work Orders board, where every item is a single work order. Around it sit a few supporting boards that hold information the work order points to but does not own. Keeping those separate is what lets the same product, customer or material be used by hundreds of work orders without being retyped.

BoardOne item equalsWhy it is separate
Customer OrdersOne sales order or order lineSales owns it; one order can create several work orders
Work OrdersOne production jobProduction owns it; this is where status lives
ProductsOne part or finished goodSpecs, drawings and the bill of materials change rarely and are shared
MaterialsOne raw material or componentPurchasing and inventory own stock levels
Work CentersOne machine, cell or lineCapacity and maintenance live here

Small shops can start with just Work Orders and Products and add the others later. What matters is that each board answers one question and has one owning team.

Linking the boards

The boards are tied together with the Connect Boards column. According to monday.com's documentation, this column links items on one board to items on another, and it can link to more than one board at a time. Its two-way option adds a matching column on the other board, so a customer order shows its work orders and each work order shows its customer order.

To show details from the linked item without copying them, add a Mirror column. monday.com's support article explains that a Mirror column displays a chosen column from the connected item, such as a product's drawing revision or a material's on-hand quantity, and that it requires a Connect Boards column first. When the source changes, the mirrored value changes with it.

Two limits are worth knowing before you design. monday.com documents a maximum of 60 Connect Boards columns per board, which is far more than a work order build needs. It also allows mirroring a Mirror column only two levels deep, so avoid chains like order to work order to material to supplier on a single board.

Columns on the Work Orders board

This is the column set we start from. We trim or rename it with the team during the first working session.

ColumnTypeNotes
Work order numberItem name or Auto numberKeep it short and readable on the floor
Customer orderConnect BoardsTwo-way link to Customer Orders
ProductConnect BoardsLinks to Products
Drawing revisionMirrorPulled from Products, never retyped
Quantity orderedNumbersSet at release
Quantity completedNumbersUpdated by production
StageStatusThe production stages described below
Stage ownerPeopleOne person per stage
Work centerConnect BoardsLinks to Work Centers
Planned start and due dateDateOr a Timeline column if you schedule by range
Materials readyStatusYes, Partial, No
Quality resultStatusPass, Rework, Scrap
Hold reasonDropdownMaterial, Machine, Engineering, Quality

Resist the urge to add a column for every question someone has ever asked. Every extra column is one more thing that someone has to keep current, and stale columns are the fastest way to lose trust in the board.

Stages, owners and handoffs

A work order moves through a short, fixed sequence of stages, and each stage has one owner. The Stage column is the single source of truth for where the job is. If people need more than about eight stages to describe the flow, the extra detail usually belongs in a checklist inside the item, not in the status column.

This is the default sequence we start with:

  1. Draft. The planner creates the work order from a customer order or a replenishment need. It is not visible to the floor yet.

  2. Released. Required fields are complete, materials are confirmed or reserved, and the job is scheduled. The supervisor owns it from here.

  3. In production. The job is running at its work center. Production updates the completed quantity.

  4. On hold. Something stopped the job. The Hold reason column says why, and the person who can clear it is assigned.

  5. Quality check. Production is done and quality inspects. The result is Pass, Rework or Scrap.

  6. Ready to ship. Quality passed, and shipping or the warehouse takes over.

  7. Closed. Shipped or moved to stock, with final quantities recorded.

Each handoff is a change of owner. When the stage changes, the Stage owner column should change too, and the new owner should be told. That is exactly the gap a spreadsheet cannot close on its own, and it is the first thing we automate.

Rules that keep the stages honest

Three rules prevent most of the confusion we see in new builds:

  • Release means ready. A work order cannot move to Released while its required fields are empty or its materials are marked No. Teams that skip this rule find jobs "in production" that are really waiting for steel.

  • Hold is a stage, not a comment. If a job is stopped, it goes to On hold with a reason. A note in the updates is easy to miss; a status is counted on the dashboard.

  • One owner at a time. Two names in the owner column means nobody owns it. Use the updates section to bring others in.

Rework and partial quantities

When quality sends a job back, return it to In production with the Quality result set to Rework, rather than adding a stage for every loop. For partial completions, the two quantity columns show progress, and a partial batch that ships separately becomes its own work order so each part can close.

Materials, inventory and the ERP question

A work order is only as reliable as its "can we start?" answer, and that depends on materials. There are three common setups, and the right one depends on what you already run.

If you have no ERP

Many smaller manufacturers track stock in a spreadsheet or not at all. In that case, the Materials board becomes the inventory record, and each work order links to the materials it needs. A Mirror column on the work order shows on-hand quantity, and the planner sets Materials ready before release.

We covered how to structure that inventory board, including reorder points and stock movements, in our guide to replacing inventory spreadsheets on monday.com. Build that first if materials are the bottleneck.

If you already run an ERP

This is the most common case for midsize manufacturers, and it is where expectations need to be clear. monday.com is a work management platform, not an ERP or MRP system. It does not replace your ERP's material requirements planning, costing or accounting.

What it does well is coordinate the work around the ERP. The ERP stays the system of record for the bill of materials, stock and costs. monday.com holds the job's stage, owner, holds, quality result and conversation, which ERPs tend to handle poorly or not at all on the floor. An integration can bring the work order number, product, quantity and due date across from the ERP, so nobody types them twice.

Be fair to the ERP here. It is usually very good at transactions and very bad at visibility for the people doing the work. Putting a work management layer on top is not a criticism of the ERP; it is a recognition that supervisors and operators need a different screen than accountants.

One more expectation to set early: barcode or QR scanning on the floor usually needs a monday.com Marketplace app or an integration rather than the core platform alone. If scanning is a must-have, scope it before you promise it.

Views, dashboards and automations

The same Work Orders board has to serve very different people. A planner wants every open job by due date. A supervisor wants today's jobs at their work center. An operator wants one job, its drawing and its instructions, without fifty columns in the way. We give each role its own view rather than one board that tries to please everyone.

RoleViewWhat it shows
PlannerTable, grouped by StageAll open work orders, sorted by due date, with materials status
SupervisorKanban by Stage, filtered to their work centerWhat is waiting, running, on hold and done today
OperatorThe item itselfOne job: product, quantity, drawing, instructions, quality steps
ManagerDashboardLate jobs, jobs on hold by reason, work in progress by stage
SchedulerTimeline or Gantt by work centerLoad and overlaps across the coming weeks

The operator view is where most builds struggle, because a standard item card shows every column on the board. If the people on the floor need a focused screen with only their fields, required inputs before a stage can change, and the drawing embedded next to the checklist, an app such as Better Item Views can give each role its own item layout without changing the board underneath.

Dashboards that change decisions

A dashboard is only useful if someone acts on it. We start with three widgets and add more only when a meeting asks for them:

  • Late and at-risk jobs. Work orders past due, or due within three days and not yet in Quality check.

  • Holds by reason. A count of On hold jobs by Hold reason. If Material is always the biggest bar, the fix is upstream.

  • Work in progress by stage. How many jobs sit in each stage right now. A growing pile in one stage is a bottleneck.

Automations for the handoffs

monday.com's documentation describes every automation as a trigger, an optional condition and one or more actions. For work orders, the useful ones are almost all about handoffs:

  1. When Stage changes to Released, assign the supervisor of that work center and notify them.

  2. When Stage changes to On hold, notify the planner and the person responsible for the hold.

  3. When Stage changes to Quality check, assign and notify the quality inspector.

  4. When Quality result changes to Rework, set Stage back to In production and notify the supervisor.

  5. When the due date is three days away and Stage is not Quality check or later, notify the planner.

  6. When Stage changes to Ready to ship, notify shipping and update the linked customer order.

Check the column types before you design these. monday.com's automation guide lists several column types that automations do not support, including Mirror, Dropdown and Dependency. That is why we keep Stage, Materials ready and Quality result as Status columns, and why a mirrored stock level should not be the trigger for anything.

Automations also count against a monthly action allowance that depends on your plan, so a build with many work orders and chatty notifications should be sized before go-live. Our rule of thumb is one automation per handoff, not one per opinion.

A worked example (hypothetical)

The following example is hypothetical. It does not describe a Worktables client, and the numbers are illustrative assumptions chosen to show the math.

Imagine a metal fabrication shop with three work centers: cutting, welding and finishing. It releases about 40 work orders a week, each for one customer order line. Today the planner keeps a master spreadsheet, prints a daily job list for each work center, and spends the first hour of every morning walking the floor to update the file.

The build. The shop sets up four boards: Customer Orders, Work Orders, Products and Work Centers. Materials stay in its accounting system for now. The Work Orders board uses the seven stages above, one owner per stage, and the column set from this blueprint minus Work center capacity, which they leave for phase two.

The automations. Five handoff automations fire on each work order: release, quality check, ready to ship, plus the due-date warning and a hold notification when needed. In a four-week month that is about 40 × 4 = 160 work orders. If every work order fires all five, the shop runs about 160 × 5 = 800 automations a month. Because some automations include more than one action, the real action count will be higher, which is worth checking against the plan's monthly allowance before go-live.

What changes. The morning walk becomes a five-minute look at the dashboard. Holds show up with a reason instead of a hallway conversation. When a customer calls, sales opens the customer order and sees each linked work order's stage without asking production.

Rollout plan

We roll out work order tracking in four steps, each one small enough to correct before the next:

  1. Map the work (week 1). Walk one real job from customer order to shipping with the people who touch it. Write down every stage, owner and handoff, and agree on what "released" means.

  2. Build in the open (weeks 2 and 3). Build the boards with the planner and one supervisor in the room. Load a handful of real, current work orders and run them in parallel with the spreadsheet.

  3. Switch one work center (week 4). Move one area fully onto the board. Fix the views and automations based on what its supervisor and operators actually do.

  4. Hand over the keys (weeks 5 and 6). Move the remaining work centers, retire the spreadsheet, and train the team that will own and adjust the board from now on.

Timelines vary with the number of work centers and integrations. The order of the steps matters more than the dates.

Common mistakes

These are the problems we see most often in the first month:

  • Too many stages. Twelve statuses that nobody remembers. Keep the stages to what changes ownership, and move the detail into checklists.

  • No definition of released. Jobs reach the floor without materials or drawings, and the board loses credibility on day one.

  • Retyping master data. Product specs typed into every work order drift out of date. Link to the Products board and mirror what you need.

  • Running two systems forever. A parallel spreadsheet is fine for two weeks. After that, it quietly becomes the real system again.

If you're planning this for your shop, see how we approach manufacturing operations on monday.com.

Frequently asked questions

Can monday.com replace our ERP for work orders?

No, and it should not try. monday.com is a work management platform, not an ERP or MRP system, so it does not handle material requirements planning, costing or accounting. What it can do is track each work order's stage, owner, holds and quality result, and give the floor a clearer screen. Many manufacturers keep the ERP as the system of record and use monday.com to coordinate the work around it.

Should each work order be an item or a board?

An item. A board per work order quickly becomes hundreds of boards that nobody can report across, and dashboards struggle to pull them together. One item per work order on a single Work Orders board keeps every job searchable, filterable and countable. Use subitems or a separate operations board only if you genuinely need to track individual operations or routing steps inside a job.

Which monday.com plan do we need for this build?

It depends on volume. monday.com's support documentation lists 250 automation actions per month on Standard and 25,000 on Pro. A shop releasing 40 work orders a week with five handoff automations each would run about 800 automations a month, well above the Standard allowance. Formula and dependency features also matter for many builds, so confirm plan features against monday.com's current pricing page before deciding.

How do we track operations or routing steps inside a work order?

Start without them. Most teams only need the job-level stage at first. If you later need operation-level tracking, add subitems for each operation, such as cut, weld and paint, each with its own status and owner. For complex routings that several work orders share, a separate Operations board linked to the work order is easier to report on than deep subitem lists.

Can operators update work orders from the shop floor?

Yes. Operators can open the work order on a tablet or phone, update the completed quantity, change the stage and add a photo or note in the updates. The practical question is how much they should see. A focused item layout with only their fields reduces mistakes, and shared floor devices need a clear sign-in approach that your IT team is comfortable with.

Do we need barcodes or QR codes to make this work?

Not to start. Many teams run work orders well with search and filtered views alone. Scanning helps when operators handle many jobs per shift or when materials move between locations. Barcode and QR workflows usually require a monday.com Marketplace app or an integration rather than the core platform, so scope that as a separate phase once the stages and owners are stable.

Sources

monday.com Silver Solution Partner

Want a second opinion on your work orders?

See how your work orders could move from release to shipping on monday.com, in a free 30-minute working call or a two-minute readiness check.