Back to blog

Shop Floor Data Collection: Build a Useful Job-Time Record

6 minutes read

Key takeaways

  • Shop floor data collection can cover people, production, quality, and equipment. Decide which question your first records need to answer.
  • For job labor, define consistent employee and job identifiers, complete timestamps, and responsibility for reviewing mistakes.
  • Choose capture points around job changes and working conditions, rather than an arbitrary employee-count threshold.
  • MinuteMill records employee job time. Employees add notes; managers correct existing timestamps with a reason.
  • Review the records and test the receiving format before using an export for costing or payroll.

Shop floor data collection means recording information about work where it happens. Employee job time is one part of that picture. Production counts, inspection results, and equipment conditions answer different questions and may need different systems.

This guide focuses on building a useful employee job-time record: what belongs in it, when to capture a change, and how to handle the gaps before anyone uses the totals.

Start with the decision and define the record

Begin with a question such as, “How many employee hours went into this work order?” That requires different information from “Why was the machine unavailable?” A job timer alone cannot answer both.

NIST's guidance on manufacturing data emphasizes letting the intended use determine collection requirements and providing context for the data. Its equipment-data focus also shows why shop floor collection is broader than timekeeping.

For job labor, agree on these details before choosing screens or hardware:

Record detailRule to establish
EmployeeKeep each person's entries identifiable, including when several people work together.
Job identifierUse the same work-order number in the job list, time records, and receiving costing records.
Start and endKeep dates and timezone context with the times; leave unfinished entries visibly unfinished.
Work classificationDecide where setup, rework, meetings, maintenance, and other non-customer work belong.
ExplanationDecide when a note is needed and who confirms discrepancies.

Free-text notes can explain an entry, but they are not a substitute for a maintained operation-code or quantity field when your reporting depends on those fields. MinuteMill has a job number and notes, not separate production-count, operation-code, or machine-state records.

Capture the job change, not just the shift

A shift total does not show how work moved between orders. Define the event that ends one job entry and starts another, then teach that action where the change occurs.

Consider this illustrative recording example for one employee on November 16, 2026, in one company timezone:

JobRecorded intervalLabor hours
104207:30–09:45135 minutes ÷ 60 = 2.25
105509:45–10:3045 minutes ÷ 60 = 0.75
Total recorded job time07:30–10:303.00

In MinuteMill, switching jobs ends the employee's current entry and begins the next at the same saved instant. Each employee has one running timer. The example allocates three hours; it does not establish a full day's hours or decide which time is payable.

Put the capture point where work changes

Observe where employees begin work, receive another order, and finish. A phone, workstation browser, shared terminal, or scanner-supported system may fit different parts of that routine. Test the actual workflow rather than choosing by headcount.

Check device availability, workplace phone rules, network coverage, readability, gloves, and the distance to a shared device. Existing phones may reduce new hardware purchases, but do not assume everyone has a suitable device or may use it at work.

MinuteMill runs in a phone, tablet, or computer browser without an app installation. It uses individual employee logins; it has no shared kiosk, badge-reader, or barcode-scanning workflow. A shared tablet still requires keeping each employee's account separate. Our punch-clock guide examines device and identification choices.

Confirm what was saved

Recording an action, saving it on the server, and displaying it to a manager are separate steps. Check the saved job and history after a change instead of treating a tap or an elapsed-time display as proof.

MinuteMill requires an internet connection to save starts, stops, job switches, and notes. An already running timer continues on the server when the browser closes or the connection drops. There is no offline queue for new actions.

If a save is uncertain, note the intended action and actual time, reconnect, and check the saved state before repeating it. Establish a fallback record before a real outage. The connectivity guide gives a practical interruption test.

Review exceptions before using the totals

Assign someone to review missing starts, unexpectedly long entries, wrong jobs, and unexplained gaps while people can still explain what happened. A running timer does not establish the actual finish time.

In MinuteMill, employees add notes to their own running or past entries; they cannot edit times. Managers correct existing start and end timestamps with a reason, retaining the original times and correction details in the application.

Managers cannot create missing entries or move an entry to another job through that correction form. Document those discrepancies and reconcile them separately in the receiving records. MinuteMill does not detect an employee's shift end or reconstruct missed actions automatically.

Check the handoff to costing and payroll

Costing needs reviewed hours assigned to the right jobs and an appropriate cost rate. Payroll needs complete work records and the applicable pay calculations. Sharing some timestamps does not make those processes interchangeable.

MinuteMill's CSV contains one row per time entry: employee, job number, job name, company-local start and end, status, hours within the selected dates, and optional recorded labor cost. It may include running entries. Notes, original timestamps, and correction reasons are not export columns.

Review the period boundaries, summarize rows where needed, and test employee identifiers and column requirements with the receiving system. MinuteMill does not calculate payroll, overtime, labor burden, or overhead, and its CSV is not a guaranteed payroll import format.

Department of Labor guidance requires complete, accurate records for covered, nonexempt workers, including daily and weekly hours and wage information. A job-hours file is only part of that recordkeeping process.

Judge the workflow with your own records

Try recognizable jobs through a complete capture, review, and export cycle. Keep the existing record during the trial. Count unexplained entries and corrections, and note the time spent resolving them.

Use those observations to improve job naming, capture points, training, or the receiving spreadsheet. Do not replace them with an assumed payroll-error percentage or a promise that timestamps remove the need for review.

FAQ

Does collecting time measure production output?

No. Labor hours do not establish how many acceptable parts were made or why equipment stopped. Keep the relevant quantity, quality, and equipment records separately.

Can paper still be the right starting point?

Yes. A complete, consistent paper record can be useful. The question is whether your capture and review process produces records people can use without unexplained gaps or excessive re-entry.