One loop, from signal to ground

This is a sketch of a loop. It is not an account from a book of business, and it is not an outcome. No odds are filled in. Those belong to the owner of the table.

Signal

A reply arrives on an open opportunity. The buyer is named. No timeline is named. That is the whole signal. It is enough to update the page before the pipeline review, and not enough to invent a story about the quarter.

Switch

The routing table says the route holds when a timeline is missing. The deal stays a topic for the review. The row carries an odds cell, and in this sketch the cell is still yours to write. A model may highlight the row. It does not get to replace it.

Current

The work that fits the row is a draft: a short question that asks for the timeline, plus a task so the owner of the account sees it. The draft quotes the rule. It is not sent.

Breaker

The question would reach a customer, so the written gate applies. A named person reads it and records the approval. They can release it, edit it, or hold it for the pipeline review. The receipt names the rule, the odds that were on the row that day, who decided, and whether the note went out.

Ground

Later the opportunity closes or it dies. The forecast call is scored against what was stated, not against the feeling in the room that week. The team also asks the attribution question: did the note change the outcome, or was the deal already on its way? If you cannot say, you say pending.

The same week, shorted

The short circuit is familiar. The reply feels warm. The draft goes out the hour it is written. Thursday has a story and no receipt. The forecast still moves, because someone sounded sure. Nothing in that motion can be scored, and nothing in it can be coached except the memory of who typed fastest.

The practice sandbox lets you practice the middle of this on simulated signals. The figures there are not this sketch, and they are not your book of business. Read forecasting before you treat a moving number as a call you would defend.