Worker Cooperative Fabrication Lab Utilization and Queue Planner

Plan capacity, queues, and operator coverage for a co-op fabrication lab

This calculator helps a worker cooperative, community makerspace, or shared fabrication shop answer a practical question: Can we complete the work members request within our target turnaround time? It converts a few measurable inputs—machines, open hours, average job time, setup/cleanup, and uptime—into planning metrics you can use in scheduling meetings, training plans, and equipment expansion proposals.

What you get from the results

• Effective weekly capacity (hours): machine-hours available after uptime is applied.
• Weekly demand (hours): jobs per week multiplied by average time per job (fabrication + setup/cleanup).
• Utilization (%): demand divided by effective capacity. Higher utilization means less slack for maintenance, learning, and surprises.
• Queue projection (days): a rough backlog indicator when demand exceeds capacity.
• Recommended machines: an estimated machine count to meet your queue-length goal with a built-in slack target.
• Operator coverage: whether your cross-trained member count is likely to support the recommended usage level.

How to use the planner (quick steps)

1. Enter your current machine count and open hours per week.
2. Estimate an average job: fabrication time plus setup/cleanup time.
3. Enter jobs requested per week (intake volume).
4. Set machine uptime to reflect maintenance and breakdowns.
5. Choose a maximum queue length (your turnaround promise in days).
6. Enter how many members are cross-trained to operate the machines safely.
7. Select Plan Utilization to update the results panel.

Inputs and practical guidance (what each field means)

Use consistent units: all time inputs are in hours, and demand is in jobs per week. If you track minutes, convert to hours (e.g., 45 minutes = 0.75 hours). If your lab has multiple machine types, treat “machines available” as the number of machines that can serve the average job you are modeling.

Machines available (CNC, laser, etc.)

The number of machines that can be scheduled for the modeled work. Exclude machines that are out of service or restricted.

Open hours per week

Total hours the shop is staffed/accessible for production. If you have member-only hours vs. supervised hours, use the hours that actually allow the machines to run.

Average fabrication time per job (hours)

Machine runtime per job (cutting, engraving, milling, printing, etc.). Use an average across your typical mix of jobs.

Average setup and cleanup per job (hours)

Tooling changes, fixturing, material handling, calibration, cleanup, and safety checks. This is often the hidden driver of congestion.

Jobs requested per week

How many jobs arrive (intake) in a typical week. If demand is seasonal, run multiple scenarios (slow month vs. peak month).

Machine uptime (%)

Percent of open hours that machines are actually usable. Include planned maintenance and typical breakdown time.

Desired maximum queue length (days)

Your service-level target: the maximum backlog you want to tolerate before adding capacity, changing policies, or limiting intake.

Members cross-trained to operate machines

Count members who can run the relevant equipment safely and independently (or under your lab’s rules). This is a proxy for staffing resilience.

Model and formulas (what the calculator is doing)

The calculator uses a simple capacity model based on time. It is intentionally transparent so you can explain it in a member meeting.

• Time per job: timePerJob = fabricationHours + setupHours
• Effective weekly capacity (hours): effectiveHours = machines × openHours × (uptime% ÷ 100)
• Weekly demand (hours): demandHours = jobsPerWeek × timePerJob
• Utilization: utilization = demandHours ÷ effectiveHours
• Jobs capacity (jobs/week): jobsCapacity = effectiveHours ÷ timePerJob

To recommend a machine count, the tool adds a slack target derived from your queue goal. Shorter queue goals imply you need more slack. It then estimates the capacity required to keep demand below that threshold and rounds up to whole machines.

Worked example (with the default values)

Suppose your co-op has 6 machines, is open 72 hours/week, and averages 3.5 hours of fabrication plus 0.8 hours of setup/cleanup per job. You receive 38 jobs/week and estimate 88% uptime. Your queue goal is 7 days, and you have 18 cross-trained operators.

The average job takes 4.3 hours. Weekly demand is 38 × 4.3 = 163.4 hours. Effective capacity is 6 × 72 × 0.88 = 380.2 hours. Utilization is therefore about 43%, which typically indicates comfortable slack for maintenance, training, and rush work.

Now test a surge: if jobs rise to 76/week with everything else unchanged, demand becomes 326.8 hours and utilization rises to about 86%. That may still be workable, but queues become more sensitive to downtime and staffing gaps. This is exactly where the planner helps: you can compare “add a machine,” “extend hours,” or “reduce setup time” and see which lever moves the outcome most.

Planning notes for cooperative governance

Utilization planning is not just operations—it is governance. When utilization is low, you might schedule skillshares, preventative maintenance, or discounted community production days. When utilization is high, you may need to adjust intake rules, prioritize mutual-aid runs, add supervised shifts, or fundraise for additional equipment. A shared model makes these tradeoffs easier to discuss because members can see the assumptions.

Related tools in this collection include the cooperative laundromat water and energy recovery calculator, the community mesh network uptime and backhaul planner, the mutual aid fund runway calculator, and the community EV carshare utilization reserve calculator. Together, they support capacity planning across multiple cooperative services.

Limitations and assumptions

• Average-job approximation: the model assumes one representative job size. If your work mix is bimodal (tiny jobs + huge jobs), run multiple scenarios.
• Machine interchangeability: it assumes the modeled jobs can run on the machines counted. If only certain machines can do the work, count only those.
• Uptime as a single number: downtime is aggregated into one percentage; real failures can be lumpy and machine-specific.
• Queue estimate is coarse: the queue-days output is a planning signal, not a promise for any individual job’s wait time.
• Operators are a proxy: operator coverage is simplified; certifications, supervision rules, and two-person safety requirements may change real staffing needs.