Quarter forecast call: drag deals between call lanes, roll them up by rep in a banded table and track won plus commit against target. ReUI Kanban, Data Grid, Filters, Badge. For forecast review, commit call.
Forecast Call is a sales workspace for a Sales owner to run a quarter's forecast review from one dataset, seen as a board of call lanes and a table rolled up by rep.
Sales owner
Run a quarter's forecast call from one dataset: move each deal to the call the rep will stand behind, roll the calls up by rep, and see won plus commit plus best case against the target.
workspace
solutions/crm/solution-crm-7
none
Containerless full-bleed workspace. One identity line carries the quarter title, a dot and a one clause subtitle, with an icon Undo and New deal on the right. Under it the call reads as a call sheet: a large headline of won plus commit against the quarter target with a derived status badge beside it, and one sub-line with the attainment and the week of the quarter; on the right a compact ledger keys won, commit and best case over one solid attainment bar whose end is the target, captioned with the linear pace and the gap. One toolbar band holds a rep picker and four hygiene chips on the left and search, Filter, Display and the Board and Table switch on the right. The board lands grouped by the forecast call with every lane (Not called, Pipeline, Best case, Commit, Closed won, Closed lost, Omit) at one width in a horizontal scroller; the table lands grouped by rep with Won, Commit, Best case and Pipeline as columns and a rollup on every band.
The forecast call is the unit of work: the board's default axis is forecast, so a drop writes the call through the one write path, and a closed deal refuses a call (rule 8). On the forecast board a settled deal sits on its outcome lane keyed by the stage id; a drop on that lane writes the stage, never the call, so call accuracy stays reportable. Locked and settled cards are disabled items, never vetoed on drop. The four call columns are derived and read the same rule as callTotals, so a band always adds up. The summary reads the whole book and counts only deals closing inside QUARTER against QUARTER_TARGET; a scope adds an in view note, never moves the track. A lane header prints the amount its share of target is taken from, and lost or omitted lanes read as outside the call. The call owns the hue (one blue ramp, strongest at Commit), open stages are a neutral ramp and only the outcomes keep a tint. The rep picker and hygiene chips own no state: each reads and writes one root rule of the shared filter query.
It changes the unit of work from the deal's stage to the rep's forecast call. solution-crm-7 is a four view pipeline operations workspace grouped by stage and by account, whose board drop settles a stage; solution-crm-2 is a hardcoded lane board with no write path. Here the board's lanes are calls (Not called, Pipeline, Best case, Commit) so a drop rewrites the rep's forecast, the won and lost lanes settle a deal without touching the call it was made on, the table bands by rep with Won, Commit, Best case and Pipeline as derived columns that roll up on every band, and the header measures won plus commit plus best case against a named quarter target and counts four hygiene states that filter both views through the shared filter query. It reuses crm-7's store, validator, selectors, DataGrid and kanban engine unchanged in behavior.
