Operations overview

Operations Overview brings pipeline value, qualification work and blocked operations into a practice-level screen. The principal can use it to start a review with the fee pursuits that need a decision. The underlying opportunity keeps the owner, counterparty, expected value and close date; the operation receipt keeps the action attempted and its result. Seeing both prevents a failed operation from being mistaken for a completed change in the pipeline.

A receipt carries an operation key, action, expected revision, result state and occurrence date. Failed and needs review results can also carry a failure reason. The receipt points to a parent opportunity, so the team can move from a blocked action to the exact pursuit affected. Pending and Completed results provide the same trail for work that is still in progress or has finished. A principal should inspect the receipt and source record together before retrying a time-sensitive action.

• Pipeline context. Start with the opportunity’s owner, client, status and expected value.
• Operation result. Check whether the attempted action is Pending, Completed, Failed or needs review.
• Source revision. Compare the expected revision with the current pursuit before another person acts.

Agree who reads the practice overview and who can investigate operation exceptions. Decide when a Failed result goes back to the business development lead and when needs review calls for the principal. Choose how long the team waits on Pending work before checking its result. Define the handoff between the proposal coordinator, reviewer and principal when a submission action has a receipt but the related RFP still needs attention. Prepare a stale-revision example for a qualification and for an RFP submission.

The lead opens a new civic-center pursuit and begins qualification. A colleague changes the opportunity before the qualification action is completed. The action fails its expected-revision check, leaving the opportunity unchanged. The principal opens the current pursuit, compares its revision and asks the lead to review whether qualification still makes sense. When an operation receipt exists for an exception, the principal follows its parent link to the affected opportunity.

On another pursuit, the coordinator submits a design RFP at the expected revision. The receipt shows Completed and the RFP shows Submitted. The principal can separate this successful submission from a later internal review decision and from the ultimate customer outcome. That separation makes the weekly review more precise: it shows what the team attempted, what the app recorded and what still needs a human decision.

• Operation exceptions — Failed and needs review actions with reason and parent pursuit.
• Open pursuit pipeline — The active fee work and expected values behind the overview.
• New pursuits to qualify — Work awaiting the early qualification decision.

Account to qualified pursuit and Design RFP submission show where receipts enter the work.