How to Enter Actual Hours for Yesterday in EDGEBIC

To enter actual hours for yesterday in EDGEBIC by User Solutions, open Log Actuals on the operation and type the hours into yesterday's row in the daily grid. The grid carries one row per calendar day, so past days are normal entry rather than a special case. Nothing about a date being in the past changes how the value is stored or how the next reschedule reads it.

The complete logging workflow, including setting the actual start and closing the step, is in how to log actual hours and pieces. This is the back-dated entry specifically.

Before You Start

Step 1: Open the Daily Grid

Select the job in the Job View tab. Right-click the operation's bar on the Schedule View Gantt and choose Log Actuals, or click the Log Actual header button and pick the work center. In the Actual Live view, double-click the step's card.

If the operation has no actual start yet, the Edit Actual Dates dialog opens first. Set the start to the day work genuinely began, not to today. Use Sched Start copies the planned start, which is often close enough when the job started on time.

Step 2: Find Yesterday's Row

The grid shows one row per calendar day of the operation's window, with the plan on the left and your entry on the right.

If the day you need is outside the planned window (work ran on a Saturday the plan never allocated, or started a day early), focus that date in the grid and the window extends to include it, which logging hours for a day outside the planned window covers in full. The row is created for that date and takes your values.

Step 3: Type the Hours

Enter the hours in Actual Hrs. With Auto Calc Hours (derive missing side from Rate) ticked, the pieces derive from the operation's rate. Type six hours on a step rated at two pieces per hour and twelve pieces fill in.

For a single-cell correction you do not need the full dialog. Double-click the Actual Hours cell on the operation row in the Job View grid and the Quick Log popup opens with date, hours, pieces, auto-calculate, and save.

Step 4: Answer the Prior-Days Prompt

If earlier days of the same operation are still empty, a prompt says so. Cancel and fill them if you can find out what happened. Accept and continue if yesterday is genuinely what you know. A related prompt covers earlier operations on the job rather than earlier days, and that one is handled in how to backfill actuals for earlier steps.

Step 5: Save, With a Reason If Asked

Click Save. If you changed a value that had already been reported, a reason is required and an empty reason cancels the save. The reason lands in the append-only logging history beside the old and new values.

What Changes When You Save

That last row is the whole reason back-dated entry matters. Rescheduling against a picture that stops on Monday re-plans the plant around Monday, however many days have passed since.

How to Check It Worked

The grid's row shows your hours next to the scheduled hours for the same day, so any gap is visible while you are still in the dialog. Open View History and confirm the entry is recorded with your name. On the Job View header, actual hours should have increased by exactly what you typed, and remaining should have fallen by the same amount. If the operation is now covered by its logged hours, the Actual Live card reads Complete even with no stamped end.

Common Mistakes

• Setting the actual start to today for work that started last week. The start defines where the engine believes the job is. Set it to the real day.
• Putting a week's hours on one row. Twenty-eight hours on Tuesday tells the engine capacity was consumed on Tuesday. Spread the hours across the days they happened.
• Entering hours on the parallel sibling row. Edit the primary. The sibling mirrors it at save time and a direct edit is overwritten on the next save.
• Skipping the reason on a corrected value. The save cancels and people assume it landed.
• Logging days and then not rescheduling. Entry makes the record honest. Only a reschedule makes the promise date honest.

Next Steps

If the step also finished on that past day, how to complete an operation covers the end stamp and the end-of-day snap. If the hours came in short against the plan, read how to record a partially finished operation. If a date rather than an hours value is wrong, how to correct a wrong actual date is the shorter path.

Every task in this library is indexed on the EDGEBIC how-to hub. Bring a week of paper time tickets to a demo of EDGEBIC and we will enter them and reschedule against them in one sitting.