Use the recorded timing
Allocate overlapping start-and-stop entries as operations begin and end. A period with one active entry stays with that entry; shared periods are divided among the employee’s concurrent entries.
NEPTUNE SOLUTIONS · FOR JOBBOSS
Balance overlapping labor for clearer JobBOSS costing.
When one employee works across several operations at the same time, Neptune Weighted Labor Balancing allocates that shared time across the concurrent work and recalculates the affected JobBOSS labor costs. Run selected jobs when needed or use a configured schedule, then review the recorded before-and-after results.
Training guide: PDF · 15 pages. Demonstration: a short public recording on ECI’s resource site.
THE BUSINESS CASE
A production employee may start several operations and keep them active at the same time. Assigning each operation the full elapsed period can record more job labor than the employee’s available time. Weighted Labor Balancing evaluates that employee’s overlapping entries and divides the shared periods among the concurrent work.
Give production and accounting a consistent way to address overlapping start-and-stop labor entries without manually recalculating every affected job. Original start and stop timestamps remain available, while allocated labor hours and related costs reflect the concurrent work.
PRACTICAL CAPABILITIES
Allocate overlapping start-and-stop entries as operations begin and end. A period with one active entry stays with that entry; shared periods are divided among the employee’s concurrent entries.
Process selected jobs on demand or establish a configured Windows schedule for recurring work. Both ways of running use the installed allocation configuration.
Open the recorded process event to compare before-and-after job totals and related employee and operation details, then verify the affected values in JobBOSS.
THE ALLOCATION APPROACH
The allocation follows one employee’s recorded start and stop times. Time spent on one active entry stays with that entry; time shared with other entries is divided among them as operations start and stop.
Both eligible operations are active for the same complete hour, with no break deduction.
60 minutes recorded
30 minutesof allocated labor60 minutes recorded
30 minutesof allocated laborCombined: 120 recorded minutes across two entries become 60 minutes of allocated labor.
This illustrates the timing rule, not a reduction in payroll paid. Actual results depend on eligible entries, their timestamps, configured scope and the installed allocation configuration.
MATCH THE CALCULATION TO YOUR SHOP
The difference is how operation machine hours are treated alongside employee labor. Neptune confirms the installed configuration when establishing or changing the process.
Allocates employee labor while retaining operation setup and run machine-hour totals. Useful when equipment continues running while the employee attends other work.
Allocates employee labor and operation machine hours across concurrent entries. Use when that treatment matches how the shop intends to record its production time.
These are descriptive configuration labels, not separate editions or an in-app mode toggle. The installed package determines the calculation. The distinction concerns operation setup and run machine-hour totals; both configurations also update related transaction-level labor and machine-hour fields.
Refresh the eligible job list, check the jobs to process and use PROCESS SELECTED JOBS. The operator controls the intended batch.
A configured Windows scheduled task can process eligible jobs without an operator opening the application. Set its timing after the relevant labor entries close, coordinate it with manual runs and review the execution and resulting job data.
Manual and scheduled processing are ways to run the installed configuration—not additional product editions.
GENERAL USAGE
The operator selects jobs; the calculation works on their eligible underlying labor entries. Use the training guide for the illustrated steps and detailed result checks.
Wait until the relevant concurrent labor entries have closed. Use REFRESH DATA and open BALANCE LABOR ENTRIES, then check the PROCESS boxes for the intended batch. Highlighting a row is not the same as selecting it for processing.
Choose PROCESS SELECTED JOBS when the selection is ready. This action recalculates and writes the affected JobBOSS data; it is not a preview. Allow the run to finish, read the completion status and retain any error details.
Refresh the data, open Historical Adjustments and choose the process event. Select a job to review TOTAL LABOR BEFORE, TOTAL LABOR AFTER and the related employee and operation details.
Check representative job and operation results, including allocated labor hours and the installed configuration’s machine-hour behavior. Compare equivalent fields: historical totals include burdens, while the queue’s ACT LABOR is base labor only.
If a run reports an error or the outcome is unclear, inspect its status, historical details and affected JobBOSS records before retrying. A job disappearing from the selected list does not by itself establish that all writes completed.
LEARN THE TOOL · KEEP THE REFERENCE
Share the overview with production and accounting, use the guide to establish the operating routine, and return to the demonstration for a quick product orientation.
PDF · 3 pages · 744 KB · November 2026
Understand how overlapping employee time is allocated across concurrent work. Compare the two installed configurations and see how manual or scheduled processing connects to job-cost review.
PDF · 15 pages · 996 KB · November 2026
Follow first-run preparation, eligible-job selection, live processing, historical review and JobBOSS verification. Includes allocation examples, machine-hour treatment, scheduling, exceptions and a practice exercise.
RECORDED DEMONSTRATION
Watch the Weighted Labor Balancing demonstration for a short introduction to Balance Labor Entries, Historical Adjustments and the separately installed assessment report. Keep the current training guide alongside it for your installed configuration and review steps.
Opens ECI’s resource site in a new tab, without registration. The demonstration shows an earlier layout; use the current guide for your installed configuration and review steps.
A QUICK WORKING REFERENCE
The original timestamps remain. The utility uses them to calculate allocated hours for the overlapping work and recalculate the affected costs.
The calculation uses the employee’s recorded overlapping timing. Shared periods are divided among concurrent entries as work starts and stops; the operator does not assign a percentage to each job.
That depends on the installed configuration. Labor-hour balancing retains operation setup and run machine-hour totals; Labor-and-machine-hour balancing allocates those totals as well. Both configurations also update related transaction-level labor and machine-hour fields.
It performs the update. Review the selected jobs before using it, then check the completion status, Historical Adjustments and affected JobBOSS records. There is no separate preview-and-accept stage after this action.
The job may still be active. Wait until the relevant concurrent labor entries have closed so the allocation can consider their recorded start and stop times.
A job may receive new overlapping labor entries after an earlier run. Those new eligible entries can bring it back to the list. Review the current entries and any previous manual corrections before processing.
Historical totals include base labor plus labor, machine and G&A burdens. The processing queue’s ACT LABOR is base labor only. Use like-for-like JobBOSS fields when checking the result.
Historical Adjustments is a review screen. It does not provide an undo or restore command. Investigate an unexpected result using the recorded event and affected JobBOSS records before deciding on a correction.
A run with no eligible jobs does not create a new process event. Check the scheduled task’s last-run result as well as the job data and history when verifying the routine.
Need help with a run or configuration? Contact Neptune with the installed configuration, job and operation, employee, original time range, process event and exact status or error message. Include what JobBOSS shows and whether an operator or the schedule initiated the run. Sales@NeptuneNetworking.com
IS THIS THE RIGHT TOOL?
Production and accounting teams using timestamped start-and-stop job labor where one employee runs concurrent operations. Attendance, payroll, elapsed-time-only entry and balancing one job across a crew are separate workflows.
Talk through your use caseWe’ll confirm the applicable configuration and setup for your JobBOSS environment.
START WITH YOUR WORKFLOW
Tell us how your team records concurrent operations and reviews job costs today. Your inquiry will already identify Weighted Labor Balancing.