My Jobs

Stage-based job routing for workers and supervisors. Navigate here with Ctrl+7.

What is My Jobs?

My Jobs is a stage-based job routing system that connects workers to the entries they need to work on. Instead of manually assigning individual jobs, work flows automatically through pipeline stages — and workers see only the entries at stages they are assigned to.

The concept draws from kitchen display systems (KDS) in restaurants, hospital patient tracking boards, and manufacturing MES dispatch boards. The core idea is the same: workers pull jobs from a queue rather than waiting for a manager to push assignments to them.

My Jobs has two main views:

My Work Bin — A personal work queue for individual workers
Team Board — A supervisor/manager view showing workload across the entire team

Tip My Jobs requires stage assignment to be configured. Assign workers to pipeline stages in Tools > Edit Pipeline so entries appear in their bins automatically.

My Work Bin

My Work Bin is the personal work queue for an individual worker. It shows all entries at pipeline stages that the worker is assigned to, organized into sections that help prioritize what to work on next.

My Work Bin Screenshot of the My Work Bin view showing the active job with elapsed timer, Up Next queue, and On Hold section

Sections

Section	Description
Now	The active job the worker is currently working on. Displays an elapsed timer showing how long the job has been in progress.
Up Next	The upcoming queue, sorted by priority and due date. The most urgent jobs appear at the top. Workers pick from this list when they finish the current job.
On Hold	Jobs that are paused — waiting for materials, customer approval, or other external factors. These remain visible but are not expected to be actively worked on.
Rework	Jobs that were returned to a previous stage due to quality issues or corrections. These are flagged for attention and typically take priority.
Later	Lower-priority jobs that are not yet due. These are available for pickup but do not require immediate action.

Actions

Each entry card in My Work Bin provides quick action buttons:

Done — Advance the entry to the next pipeline stage. The entry moves out of your bin and into the next worker's queue.
Return to Stage — Send the entry back to a previous stage if work cannot be completed (e.g., welding cannot proceed because the parts were not prepped correctly).
On Hold — Move the entry to the On Hold section. The entry stays in your bin but is marked as paused.
Log Note — Add a timestamped note to the entry without leaving the My Jobs view. Useful for recording observations, issues, or shift handoff information.

Tip The elapsed timer on the active job helps workers self-manage their pace. If a job is taking longer than expected, it is a signal to flag the issue or request help — before it becomes a bottleneck.

Team Board

The Team Board is a supervisor and manager view that provides visibility into workload distribution across the entire team. It has three sub-views accessible via tabs at the top of the page.

Team Board — By Stage Screenshot of the Team Board By Stage view showing stage lanes with entry counts and entry cards

By Stage

The By Stage view shows stage lanes — one column per pipeline stage. Each lane displays:

Entry count — The total number of entries at that stage
First 10 entries — Entry cards showing ref number, customer, priority, and due date. Only the first 10 entries per lane are rendered to keep the interface responsive.

Click any entry card to open the side panel with full details and action buttons.

By Worker

The By Worker view organizes the team into rows grouped by department. Each worker row shows:

Currently working on — The active job reference number, if any
Queue depth — The number of entries at the worker's assigned stages (their fair share of the work)
Idle/Active status — Whether the worker currently has an active job or is between jobs
Load bar — A visual indicator of how much work is queued for the worker relative to the team average

Department grouping uses collapsible Expanders with summary headers showing the count of working and idle workers (e.g., "Fabrication — 3 working, 1 idle").

Tip The By Worker view is ideal for morning stand-ups. At a glance, a supervisor can see who is busy, who has capacity, and whether work is evenly distributed across the team.

Workload (Bottleneck Analysis)

The Workload view presents a table that highlights capacity imbalances across pipeline stages. Each row shows:

Column	Description
Stage	The pipeline stage name
Entries	Total number of entries currently at this stage
Workers	Number of workers assigned to this stage
Per Worker	Entries divided by workers — the workload per person
SLA Target	The configured SLA target for this stage (in business days)
Status	Color-coded indicator: green (on track), yellow (approaching capacity), red (bottleneck — workload exceeds capacity)

The table is sorted by worst bottleneck first, so the stages that need attention are always at the top.

Note Bottleneck analysis works best when SLA targets are configured for each pipeline stage. Without SLA targets, the status column uses a default threshold based on the entries-per-worker ratio.

Pipeline Filter Tabs

When your project uses multiple pipelines, filter tabs appear at the top of the Team Board. Click a tab to show only entries from a specific pipeline (e.g., "Fabrication", "Service Call", "Rush"). The "All" tab shows entries from every pipeline combined.

The pipeline filter applies to all three Team Board sub-views (By Stage, By Worker, and Workload).

Side Panel

Click any entry on the Team Board to open a detail side panel on the right side of the screen. The side panel provides a focused view of the selected entry without leaving the Team Board context.

Side panel contents

Stage workers — Lists all workers assigned to the entry's current pipeline stage (from the pipeline configuration)
Stage timeline — Shows the entry's progression through pipeline stages with timestamps
Status, priority, and due date badges — Visual indicators for the entry's current state
Action buttons:
- Advance — Move the entry to the next pipeline stage
- Put On Hold — Pause the entry
- Open Full Detail — Open the full Entry Detail Window for comprehensive editing
Per-entry assignment override — Optionally assign the entry to a specific worker, overriding the default stage-based routing

Stage-Based Routing

My Jobs uses a pull system for job routing. Instead of a manager manually assigning each job to a specific worker, work flows through pipeline stages automatically and workers pull from their queue.

How it works

Configure stage assignments — In Tools > Edit Pipeline, assign workers to each pipeline stage. For example, assign 4 welders to the "Welding" stage and 2 inspectors to "Quality Check".
Entries enter the pipeline — When a new entry is created or an entry advances to a stage, it becomes visible to all workers assigned to that stage.
Workers pull from their queue — Each worker sees entries at their assigned stages in My Work Bin. They pick the next job from their Up Next list based on priority and due date.
Entries advance automatically — When a worker marks a job as Done, it moves to the next pipeline stage and appears in the next group of workers' bins.

Tip The pull system means managers only need to intervene for exceptions — reassigning a specific rush job or rebalancing after a worker calls in sick. Day-to-day routing happens automatically through the pipeline configuration.

Why pull systems work

Pull-based routing reduces management overhead and keeps work flowing smoothly. Workers always have a clear view of what to do next, and the system naturally balances work across the team based on who finishes their current job first.

Bulk Assignment

For exception cases where a manager needs to override the default stage-based routing, My Jobs supports bulk assignment:

Select multiple entries on the Team Board using checkboxes
Click the Assign button in the toolbar
Choose a specific worker from the dropdown
The selected entries are assigned to that worker, overriding the default stage-based routing

Bulk assignment is useful for scenarios like assigning a batch of related jobs to the same worker, or redirecting work when a team member is unavailable.

Note Per-entry assignments are overrides, not permanent changes to the routing configuration. The next time an entry advances to a new stage, it returns to the default stage-based routing unless another manual assignment is made.

Performance

My Jobs uses a SQL-first architecture designed to handle large datasets efficiently. Key performance characteristics:

Counts-first rendering — Stage lanes and worker rows load entry counts first, then lazy-load the actual entry cards. This means the page structure appears immediately even with 100,000+ entries in the database.
Lazy loading — Entry cards are loaded on demand as you scroll or expand sections, rather than loading everything at once.
SQL-level filtering — All filtering and sorting happens in the database query, not in application memory. Only the entries you see are transferred from the database.

Tip If your project has thousands of entries and the My Jobs page feels slow, check that your pipeline stages are well-defined. Stages with hundreds of entries may indicate a bottleneck in your workflow rather than a performance issue with the software.