How to Find At-Risk Jobs on the EDGEBIC Dashboard

The At-Risk Jobs grid on the EDGEBIC by User Solutions dashboard lists every job whose projected end runs past its due date, which makes it the earliest warning list you have. Nothing has been missed yet. That is exactly why it is worth reading before the day starts rather than after a customer calls.

For the wider board, see how to use the EDGEBIC dashboard tabs. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Jobs are scheduled. Every status figure on the dashboard is derived from the plan.
• Orders carry due dates. A job with no due date can never be flagged as at risk.
• Products carry an end-item lead time where one applies, because classification judges the date the item is actually ready to deliver.

Step 1: Open the Jobs Sub-Tab

Open Dashboard from the main navigation. You land on the CAPACITY tab. Switch to the Jobs sub-tab.

It holds two grids:

Click Refresh now before you read either one. The cockpit does not refresh in the background, so a board left open since yesterday is showing yesterday.

Step 2: Read At-Risk as a Forward Statement

An at-risk job has not missed anything. The plan says it will.

That is a useful distinction because it changes what you do. A job that has already missed its date needs a phone call. A job the plan says will miss needs one of four things: more capacity on a specific day, a different sequence, a different machine, or a renegotiated date. All four are still available to you while the job is on this grid.

Step 3: Cross-Check the Job Status Donut

Go back to the Overview sub-tab and read the Job Status donut beside the Active Jobs list. It buckets every active job into exactly one slice:

The Active Jobs list under the donut sorts worst-first, so it doubles as an attention queue. Whether a job has physically started is shown as an In progress badge on its row rather than as a slice of its own, because being started says nothing about whether a job will be on time. Full reading method: how to read the job status donut.

Expect the At-Risk grid and the Late slice to tell the same story. When they do not, the difference is usually a job with no due date.

Step 4: Drill Into the Late Jobs Report

The dashboard tells you which jobs. The report tells you why. Open Reports and click the 🚨 Late Jobs tile.

It ranks jobs worst-first and carries the columns that decide your response: Due Date, Scheduled End, Days Late, % Complete, Status of not started, in progress or behind, and a Blocker Hint such as no actuals so never started, significantly behind plan, or schedule slipped. See how to run the late jobs report.

The hint is the fastest triage tool on the report. A job that has never started and a job that is 80% done are both at risk, and they need entirely different mornings.

Step 5: Pick the Cheapest Fix

Work down the shortlist in this order:

1. Is the capacity number wrong? Maintenance finished early, or overtime is agreed. Set that day's hours in the per-day capacity dialog: how to override capacity for one day.
2. Can the work move? Another job on the same station has slack. Move it, or let the optimizer propose a better ordering.
3. Can the work run elsewhere? Check the alternates and work center groups on the routing.
4. Does the date need to change? If none of the above gives, the honest answer is a customer conversation held three weeks early rather than on the due date.

Then re-run the schedule. Nothing you read on a dashboard moves a job by itself.

A Five-Minute Morning Routine

The grid is most useful as a habit rather than as an investigation.

1. Open the dashboard and click Refresh now.
2. Read the Jobs sub-tab. Note how many jobs sit on the At-Risk grid and whether the count moved since yesterday.
3. Read the donut on Overview. The top of the Active Jobs list is your worst job, sorted for you.
4. Open the 🚨 Late Jobs report only for the names that are new, since the ones you triaged yesterday have not changed overnight.
5. Fix at most two, then re-run the schedule.

A count that falls week over week means the plan is absorbing disruption. A count that climbs while the shop feels fine is the signal worth acting on, because structural lateness always shows up on the board before it shows up on the floor.

What Changes When You Read It

Nothing. The dashboards are read-only except for the per-day capacity override reached from them, and even that moves no job until the next scheduling run re-plans against the new hours. Switching tabs and clicking Refresh now change the displayed snapshot only.

How to Check It Worked

After you act and re-run the schedule, click Refresh now and return to the Jobs sub-tab. The job you fixed should have left the At-Risk grid, and on the Overview sub-tab it should have moved out of the Late slice of the donut. If the grid is unchanged, the change did not reach the plan, which almost always means the schedule was not re-run.

Common Mistakes

• Reading a stale board. The cockpit tabs load when you switch to them and otherwise wait for Refresh now.
• Expecting a job without a due date to appear. It cannot, on this grid or in the Late Jobs report.
• Treating at-risk as a failure. It is a warning with time still on the clock, which is the whole point of the grid.
• Fixing six jobs one at a time. Two at-risk jobs queueing on the same constraint are one sequencing problem.
• Quoting the dashboard in a customer conversation. The dashboard is the glanceable layer. The reports carry the authoritative formulas and the Column Details glossary behind every number.

See how early warning, capacity, and the plan stay in one system on the EDGEBIC product page.