Cases & Tasks

Totals, stacking and target tracking

In the case list you group cases into stacks — per template or per value of a field such as “Congress”. Each stack shows its totals, and with target tracking you see how far it is from its target.

On this page

How to: stack by template or field and trace the totals

  1. 1In the case list, open “Display” and under “Stack by” pick “Template” or a field such as “Congress” instead of “Attention”. The ✕ in the field resets to “Attention”.
  2. 2Each template or congress now sits in its own frame: the name at the top (with the deadline for a field), below it the boxes “Whole inventory” and “Shown”.
  3. 3Read the total row at the foot of “Shown”, for example “Total of 5 cases” — exactly one figure per overview column.
  4. 4When stacking by a field, read the sentence with the target in “Whole inventory”, the traffic-light dot before it and the bar below.
  5. 5Click a figure — a weighted sum, target, committed, the compared column or gap — to see how it comes about. “Set up in the template” leads to the setting.
Frame “ESMO 2026”: header with deadline, box “Whole inventory · … cases” with traffic-light dot, “Weighted offer amount … of …”, the gap and the bar, below it the box “Shown” with “… of … cases”
Stacked by the field “Kongress” (congress): the header shows the deadline, “Whole inventory” the target from the dataset, the compared column and the gap, “Shown” the cases of the view.

Overview columns

If a template defines overview columns (up to eight, say quote value or customer), their values sit on a line of their own below the next step, in the same place for every case. If the list shows that template only, they appear as real columns labelled in the header (see “The cases list”).

A column the template shows “only in the total” does not appear in the row, only in the total row. A cell without a value stays empty — Bricksta invents no zero. Which columns exist and what they are called is set by the template (see “Creating templates”).

Stacking by template

With “Stack by: Template” each template forms its own stack, ordered by count, in its own frame: its name at the top, below it — if the template has a key figure band — the box “Whole inventory”, and below that the box “Shown” with the cases and the total row. Within a stack, cases needing attention still come first. A saved view remembers the stacking.

The total row at the foot of the stack carries the chosen aggregate per column — for instance the sum of all open quotes. It starts with its scope (“Total of 5 cases”) and carries exactly one figure per column, in every tab, including “Completed”. It covers every match of the filter, not just the loaded rows, and only counts what you are allowed to see: “3 not visible to you” names the rest.

How much of it was won and how much lost is shown by the template’s key figure band: that is where you set up tiles such as “Won” and “Declined” yourself (see “Weighted sums and key figure band”).

Between the band and the cases a line says how many of the template’s cases you are looking at and why not all of them — for example “5 of 16 cases · completed only · Search “ESMO””. The second number counts every case of the template you may see, regardless of tab and filter. If the view matches no case of a template with a key figure band, its frame still stays — with “0 of 16 cases”.

“Reset” in that line takes back everything except the template: tab “All cases”, no filters, no search, no favorites. A saved view stays unchanged — you only leave it.

The arrow before the name collapses a template: its name with “7 of 16 cases · …” and the total row stay, the key figures and the cases fold away. Your browser remembers which templates are collapsed, per organization and after reloading.

“Whole inventory · 16 cases”Every case of the template (when stacking by field: of the stack) you may see — with the key figure band and, when stacking by field, the sentence with the target and the bar.No
“Shown”The cases the tab and filters currently hit, with the line “… of … cases” and the total row.Yes

How to use “Template” and “Running phase” under “Filter” to see, say, every offer that is out, and save that selection as a view, is described in “Views, filters and sharing”.

Weighted sums and key figure band

If the template has a column with the aggregate “Sum weighted by …” — say “Weighted offer amount”, the offer amount weighted by the probability —, it appears in the total row, with its name and its value. Each case counts amount × weight ÷ 100, rounded to the cent; the sum is the sum of these contributions, only over the cases the tab and filters currently show.

A case without a weight counts 0, and the total row says how many (“1 case without Probability”). A click on the value in the total row opens “How “Weighted offer amount” is calculated”: per case amount × percent and its contribution, each row leads to its case, with the sum below — the same number as in the total row.

If the template has a key figure band, the template’s frame holds the box “Whole inventory” with a row of key figures, say “All offers”, “Won”, “Still out” and “Declined” — set quietly, without a box per figure; a figure’s color shows as a dot before its label. Unlike the total row, the key figures count the whole inventory of the template you may see — regardless of filter and tab.

A weighted figure such as “Weighted” carries a small ⓘ next to its label. Tapping it states the configured calculation with the names of your fields — for example “Per case “Price after discount” × “Probability” ÷ 100, added up over the open cases (all time).” — and leads to the setting in the template. Change the figure and the sentence changes with it.

Stacking by field: the stack header

Next to “Attention” and “Template”, “Stack by” also lists fields — exactly those a template carries as an overview column, that come from a dataset or a choice list and are visible to everyone (no field roles). Pick, say, “Congress” and the list shows that template’s cases, one stack per congress, each as its own card in its own frame. A saved view remembers the field.

The header shows the name and the deadline from the congress’s dataset row, but no amounts. It takes on colour when the deadline is pressing (at most 30 days away and the target not yet reached). For a field with a dataset, the stacks are ordered by deadline: the next one first, past ones after, stacks without a deadline at the end; their cases load while scrolling as usual.

Below are two boxes. “Whole inventory · 7 cases” counts every case of this congress you are allowed to see — regardless of tab, filter and search; it holds the sentence with the target, the bar and, if the template has a key figure band, the same tiles, counted only over the cases of that congress.

“Shown” shows the cases the tab and filters currently hit: on top, say, “2 of 7 cases · open only · Reset” — here “Reset” clears tab, key figure, filters, search and favourites; field and stacking stay. Below are the rows and the total row “Total of 2 cases” with the summed overview columns, over exactly these cases.

If a congress holds cases from several templates, there is one total row per template with its name. A click on a weighted sum in the total row opens its breakdown over the same cases.

The view hits no case of a congressIts frame stays, with “0 of 3 cases” and “None of the 3 cases match this view.”
A congress has no cases yetOnly “Whole inventory · 0 cases” and “No cases yet”.
Cases without a value in the field“No Congress” — the group is named after the field. It shows no sentence with a target, only the count and the tiles.
Congress collapsed (arrow in the header)The header shows the traffic-light dot (no amount) and “2 of 7 cases · open only”, the total row stays below. The browser remembers this per organization and field.
No template sets up target tracking for the fieldThe stacks show no target.

Target, traffic light and bar

The “Whole inventory” box holds one sentence: “● Weighted offer amount €155,287.85 of €250,000.00 · Gap €94,712.15” — or “Target exceeded by …”. The figure in front is the column the template has chosen in its target tracking under “Compare target with” — an overview column that sums, plainly or weighted —, and it carries that column’s name. If none is chosen, the sentence compares with “Committed”.

Committed are the cases with a committed outcome, each with its contract amount (without a contract amount, with the offer amount). A weighted column counts every case of the stack with its contribution here; without a weight it counts 0. If the target tracking compares with tiles (say “Won + Weighted”), the bar measures against their sum.

What the box counts — which dataset column gives target and deadline, the direction, offer and contract amount, which outcomes count as committed and what the target is compared with — is set by the template in one place: its target tracking (“Calculations” view). A click on target, committed, the compared column or gap shows where the figure comes from and leads there via “Set up in the template”.

The dot before the sentence is the traffic light, measured on the compared figure. You set the limits per view (see “Stack header settings”).

Redbelow 60% of the target
Yellowfrom 60% to below 90%
Greenfrom 90%
Committedstrong green
What the compared column counts beyond committedlight green
The gapin the traffic-light colour: light red or light amber, empty from green
Target exceededthe target appears as a mark in the bar

Under the bar, “Committed 48.0%” sits at the end of the committed part, “Weighted offer amount 62.1%” at the end of the compared figure and “Target” on the right. If the positions are too close, both shares appear as one text on the left.

A click on the amount of the compared column opens “How “Weighted offer amount” is calculated”: one row per case with amount × percent and its contribution (without a weight it reads “no Probability”, without an amount “no Offer amount”), with the sum below — the same number as in the sentence; each row leads to its case.

If the template compares against the sum of tiles, the same sheet lists each of these tiles with its value and its cases (won in full, open weighted), followed by the sum and the gap — again exactly the sentence’s numbers.

Reach target, stay within cap, number of cases

The direction comes from the template’s target tracking; you set the measure per view. What the figures mean is written in the box below them.

“Reach target” with measure “Sum”Target, gapSentence with gap or “Target exceeded by …”, traffic-light dot and bar as above.
“Stay within cap”The target is called “Cap”, the rest “Headroom” (cap minus the compared column, without a choice minus committed)If the compared figure goes beyond it, a red “Overrun” appears; the bar shows a mark at the cap with the excess part in red. From 90 % of the cap used, a yellow badge warns you.
Measure “Number of cases”Target and committed in pieces instead of euros (“5 of 8”); gap = target minus committedCommitted are the cases with a committed outcome. This works without an amount column too; there is no column to compare with when counting.

An overrun is never offset against another stack’s headroom — each stack stands on its own.

Stack header settings

“Save as new view …” opens a sheet; for an existing view, “Stack header settings …” in the view’s menu opens the same sheet with its values. It always asks for the name. If you are stacking by a field with a dataset, the “Stack header” section is added. It names where target, deadline and direction come from — the template’s target tracking, with “Set up in the template”; they are set there and only there.

Measure“Sum” or “Number of cases”
Warning thresholdin days, default 30
Traffic light (only with “Reach target” and “Sum”)red below / green from, in percent of the target, measured on the compared figure; default 60 and 90
Entries without cases as empty stacksEmpty stacks show dataset entries that have no case yet (not archived ones) with 0 cases, committed 0 and the full gap.

The view remembers all of it; the same settings also sit in the address and can be shared as a link.

Card fields

If a template has a group with cards — say “Offers” with congress, amount and probability per offer —, a field of a card can be an overview column too. A number is calculated across all cards of the case: the row shows the sum of its cards, the total row the sum of all cards. A text, choice or dataset field shows the values of the cards in the row (“ESMO, ASCO”), and the total row counts the cards with a value.

Weighting happens per card — by a number field on the same card (such as the probability per offer) or by a field of the case: each card counts amount × weight ÷ 100, rounded to the cent; a card without a weight counts 0.

If you stack by a card field (from a dataset or a choice list, such as “Kongress”), a case appears in every stack it has a card for — an offer with cards for ESMO and ASCO thus in both. Cards without a value sit under “No Congress”. The stack is found through the dataset: “esmo” and “ESMO” end up in the same one.

If a column belongs to the same group, the compared column, the cells of the row and “How it is calculated” count only the cards of that stack — all stacks together add up to exactly the sum of all cards. An amount or column of the case (not of the card), by contrast, counts in full in every stack of the case; so the total rows do not always add up to the overall total. To split an amount across stacks, put it on the card.

Whether a case is committed is still decided by its outcome — for the whole case, not per card. Tabs, tiles and the count per running phase keep counting cases, not cards. For this, the template’s target tracking may use a card field for “Stack by”, and “Compare target with” may be the weighted card column.

Requests with child cases

If a request creates child cases (see “Closing, child cases and payments”), the children count in the stacks and in “Action needed” as soon as there are any, and the request then no longer does — so every offer counts exactly once. As long as no child has been created yet, the request itself appears in the stacks, for example when stacking by the congress of its cards.

When stacking by a field, this only applies if the children carry that field too (it is a column of their template). If the field is a card of the request that its children do not know — say the congress of the offer cards, while the order keeps its congress in a field of its own —, the request stays in that stack even with children and counts with its commitment.

Changes to the template

The overview columns and the choice under “Compare target with” apply at once to all running cases, without publishing — including those on an older version of the template. A changed calculation of a field, by contrast, only applies to cases created after publishing; running cases keep calculating by the version they were created with.

If a stack holds cases on different versions — say before and after a changed discount scale — the box shows “2 rules”. Hovering shows the sentence saying what changed (“On 08/10/2026, the calculation of “Offer amount” was changed. Older cases still calculate with …”); a click names the affected cases with their version and leads to the “Calculations” view via “Open template”.

Action needed

When stacking by field, the key figure “Action needed” appears next to the title. Tapping it shows a short list above the stacks — per case its title, number, stack and reason, with the gap stacks on top; the stacks below stay unchanged. Follow-ups you are not allowed to see do not count.

Cases without movement for at least 10 days (open, no outcome)“No movement for N days”
Cases that are overdue themselves (own due date or an open task before today)“Overdue for N days”
Cases whose follow-up is overdue“Follow-up overdue N days”
Stacks warning “Gap · N days left”appear above the cases in the list
With “Stay within cap”: every stack that is over or at 90 %counts on its own

Export as CSV

You start the export with “Export CSV” in the “Display” panel. It includes the columns — for a weighted sum the case’s contribution, even if the column only appears in the total.

When you stack by a field, it also offers “Stacks as CSV”: one row per stack with target (or cap), deadline, committed, committed in percent, the column the target tracking compares the target with (under its name; empty without a choice), gap (or headroom) and a status — the same figures as the stack headers. If an amount is not visible to you or cannot be computed, the cell stays empty and the status names the reason.

When something is off

“3 not visible to you” in the total rowThe total row only counts what you are allowed to see; the number names the rest.—
“1 case without Probability”A case has no weight; it counts 0 in the weighted sum.“How … is calculated” lists it with “no Probability”.
“cannot be calculated” in the total rowThe amount or the weight is not visible to you. There is no value and no count.—
“—” and “not computable” in the stack headerThe sum could not be loaded, or an amount or the weight is not visible to you. Bricksta then computes neither a partial sum nor a traffic light.—
“—” when comparing with tilesPart of the tiles is hidden from you; “—” stands instead of a figure that is too small.—
“not computable” for a card column, empty cellsThe card group carries a field role you do not have. Its fields cannot be used for stacking either.—
“2 cases have no amount”Cases in the stack have no amount.A tap shows which ones.
“No target set”The dataset has no target; the amount stays.The target comes from the stack’s dataset row.
“Target tracking invalid — please set it up again in the template”The target or deadline column of target tracking no longer exists in the dataset, or its type has changed. This sentence stands instead of a number.“Set up in the template” leads there.
“View invalid — please reconfigure”The list can no longer be stacked by the view’s field.See “Views, filters and sharing”.
“2 rules”The stack holds cases on different versions of the template.Hover or click, see “Changes to the template”.
“— Action needed”Action needed could not be loaded.A tap says so in the list.