Operations overview

Operations Overview is the app’s control tower for construction delivery. It brings active and accepted work, pending review decisions, failed operations, planned hours by project and tasks past due into one page. It also includes a paginated exception queue. A Project Coordinator can use the screen to decide which package or task to open next. A Project Reviewer can move from a pending certificate to the package revision and evidence that matter for the decision.

The overview is useful when it leads to a record, not just a total. A late task has a parent package and due date. A failed operation has an operation key, expected revision and reason. Planned hours belong to task lines under work packages, which in turn belong to projects. These links let the team investigate a number or exception without losing its delivery context.

• Delivery position. Work package status separates active, accepted and other scope.
• Review queue. Submitted certificates and decision records guide the Project Reviewer’s work.
• Exceptions. Failed or review-needed receipts and overdue tasks point to records that need investigation.

Agree who watches the overview at the start of each shift or operating cycle. Decide how the Project Coordinator will assign follow-up for tasks past due and how the Project Reviewer will inspect a pending certificate. The team should also agree what to do with operation exceptions: open the receipt, inspect the expected revision and recorded effect, then document the resolution in the appropriate records.

Check project and membership setup before using cross-project planned hours. If a package is attached to the wrong project, the hours roll into the wrong project context. If a task’s planned or actual hours are stale, the overview can only reflect the current records. Owners should correct source records when they find a discrepancy, then revisit the summary.

At the morning review, a coordinator sees a package still active and a task past its due date. They open the task line, check its completion date and actual hours, then speak with the named package owner. A submitted certificate for another package appears in the review queue. The Project Reviewer opens it, checks the package revision and evidence, and gives the coordinator a reasoned decision. A failed receipt remains in the exception queue until its operation key and expected revision have been reconciled with the persisted result.

This cycle gives each person a clear next record to inspect. The Auditor can later examine the certificate, decision, attachments and receipt trail associated with the package. The overview helps direct work, while the underlying records preserve the details needed for a defensible project review.

• Operations Overview — Active work, pending reviews, overdue tasks and operation exceptions in one screen.
• Active Work Packages — Current delivery scope with project, owner and due date.
• Tasks Due — Task lines with due dates and completion details.

Start with package delivery, then certificate review and evidence reconciliation.