Home Roasting8 min read

How to Roast Colombia ASOSPAC: Bright Filter for Fruit + Chocolate

Data-backed case study for Colombia ASOSPAC COL03: profile experiments toward a fruity-bright goal with real klog metrics.

BrewedLate Coffee

#Colombia ASOSPAC#Tolima coffee#washed Colombian coffee#home coffee roasting#Kaffelogic#Bright Filter#9minFilter

The short answer: for washed Colombia ASOSPAC (Tolima, Fair Trade Organic), the best recent home recipe is Bright Filter at level 2.4 / 100g — chocolate and fruit, ~12% DTR. 9minFilter ~1.8 first unlocked fruit; early Raost runs at high DTR were dark and dead for fruit.

Colombia · Tolima · Washed · 1550-2,030 MASL · Excelso EP · John Burton

Colombia ASOSPAC COL03

Goal: fruity bright18 roasts logged

Aroma of chocolate, molasses and spices. Flavours of dark chocolate, cranberry and raw sugar with a long caramelized almond aftertaste. Medium-high crisp acidity and medium coating body. Score: 83.75+

Best so far: Bright Filter at level 2.1, 120 g — tasted good 1 of 1 time.

The journey

  • Tasted good
  • Had a fault
  • Not tasted yet

What the roasts show

  1. Roast 1: Raost at level 2.2, 100 g. 1 with a fault (roasty).
  2. Then level 2.2 → 1.7, load 100 g → 110 g: roast 2. 1 with a fault (grassy).
  3. Then level 1.7 → 2.5, profile Raost → F-WSH 1000-1700: roast 3. 1 with a fault (grassy).
  4. Then level 2.5 → 1.8, profile F-WSH 1000-1700 → 9minFilter: roast 4. 1 good.
  5. Then level 1.8 → 1.7, load 110 g → 120 g: roasts 5–6. 1 good, 1 with a fault (grassy).
  6. Then level 1.7 → 2.5, profile 9minFilter → F-WSH 1500-2200: roast 7. 1 good.
  7. Then profile F-WSH 1500-2200 → Gentle Filter, load 120 g → 100 g: roast 8. 1 with a fault (roasty).
  8. Then level 2.5 → 2.0, profile Gentle Filter → Rich Filter: roast 9. 1 with a fault (roasty).
  9. Then level 2.0 → 2.6, profile Rich Filter → F-WSH 1500-2200, load 100 g → 120 g: roast 10. 1 with a fault (grassy).
  10. Then level 2.6 → 2.4, profile F-WSH 1500-2200 → Bright Filter, load 120 g → 100 g: roast 11. 1 good.
  11. Then level 2.4 → 2.2: roast 12. 1 good.
  12. Then level 2.2 → 2.0: roast 13. 1 not tasted.
  13. Then level 2.0 → 1.9: roast 14. 1 with a fault (grassy).
  14. Then level 1.9 → 2.1: roast 15. 1 not tasted.
  15. Then load 100 g → 120 g: roast 16. 1 good.
  16. Then load 120 g → 135 g: roast 17. 1 not tasted.
  17. Then load 135 g → 130 g: roast 18. 1 not tasted.
  • Weight lost: good roasts 14.2%–16.0%, roasts with a fault 14.3%–16.7%.
  • Time in the hot zone: good roasts 2:04–2:44, roasts with a fault 2:04–3:02.
  • End temperature: good roasts 212 °C–224 °C, roasts with a fault 214 °C–224 °C.
  • Good cups were tasted after 8–16 days of rest (6 tastings).
  • The first good cup on Bright Filter at level 2.4, 100 g was roast 11 of 18.

This shows what differed in the roast. It does not say why the cup tasted different.

Recipes tried

  • Bright Filter

    Still dialling in · 8 roasts · 2:37–2:44

    • 1.9 · 100 g · 1 roast, Had a fault
    • 2.0 · 100 g · 1 roast, Not tasted yet
    • 2.1 · 100 g · 1 roast, Not tasted yet
    • 2.1 · 120 g · 1 roast, Tasted good
    • 2.1 · 130 g · 1 roast, Not tasted yet
    • 2.1 · 135 g · 1 roast, Not tasted yet
    • 2.2 · 100 g · 1 roast, Tasted good
    • 2.4 · 100 g · 1 roast, Tasted good

  • F-WSH 1500-2200

    Moved on · 2 roasts · 2:04–2:07

    • 2.5 · 120 g · 1 roast, Tasted good
    • 2.6 · 120 g · 1 roast, Had a fault

  • Rich Filter

    Moved on · 1 roast · 3:02

    • 2.0 · 100 g · 1 roast, Had a fault

  • Gentle Filter

    Moved on · 1 roast · 2:30

    • 2.5 · 100 g · 1 roast, Had a fault

  • 9minFilter

    Moved on · 3 roasts · 2:10–2:21

    • 1.7 · 120 g · 2 roasts, Mixed results
    • 1.8 · 110 g · 1 roast, Tasted good

  • F-WSH 1000-1700

    Moved on · 1 roast · 2:04

    • 2.5 · 110 g · 1 roast, Had a fault

  • Raost

    Moved on · 2 roasts · 2:42

    • 1.7 · 110 g · 1 roast, Had a fault
    • 2.2 · 100 g · 1 roast, Had a fault

The recipe that stuck

Profile
Bright Filter
Level
2.4
Batch
100g
16%
2:43
End temperature
224°C
Winning batch
R-092 · 2026-07-09
nice and different. i've got a chocolaty note but also some fruit.

Compare two recipes

Comparewith
  • 1.9 points less weight lost (13.3% vs 15.2%)

No usable roast log for Bright Filter at level 2.1, 130 g, so hot zone and end temperature are not compared.

This shows what differed in the roast. It does not say why the cup tasted different.

What the roasts taught

  • Early Raost runs at high DTR tasted dark/roasty with no fruit — wrong family for a bright Colombian goal.
  • 9minFilter around level 1.7–1.8 / ~110–120g first unlocked clear fruit (R-034).
  • Latest sweet spot: Bright Filter at 2.4 / 100g — chocolate plus fruit; a tick lighter (2.2) is the current fine-tune.
  • Washed F-Series still sometimes brought green notes even when fruit showed — Bright Filter was cleaner for this lot.

Where the good cups live

Roast level against batch size. Colour is the profile; a larger dot is a roast that tasted good.

Roast mechanics across the roasts

Roast loss, hot zone and end temperature for each logged roast. Each line has its own scale, so compare shapes, not heights.

Roast goal

Roast to just before or at first crack completion to maximize the high-altitude fruit expression. Push the cranberry and red berry brightness to the forefront while retaining enough development to keep the caramel sweetness supportive rather than dominant. Accept a slightly lighter body in exchange for the vibrant, juicy acidity that defines the fruity character. The chocolate notes will shift toward cocoa powder rather than dark chocolate bar—lighter and more complementary to the fruit.

Start your own roast log

The counts in this guide are from when it was written. Roasts added since then are in the Colombia ASOSPAC roast log, which lists every attempt and how it tasted.

About ASOSPAC

ASOSPAC is a smallholder association in Santiago Pérez, Tolima — high-altitude washed lots with dark chocolate, cranberry, raw sugar, caramelized almond, and crisp acidity (~83.75+). Roast goal here: fruity-bright, keep berry brightness with supportive caramel, not a heavy chocolate bomb.

Journey

Raost: wrong gear for fruit

Early Raost @ 2.2 / 100g hit ~33% DTR and tasted dark and roasted with no fruit. Lighter Raost still fought green then flattened into chocolate without the cranberry lift.

9minFilter: first real fruit

9minFilter ~1.8 / 110g finally produced “fruit with acidity” and a second brew that was sweet and fruity. That unlocked the goal — even if later rest comparisons to commercial coffee stayed demanding.

Bright Filter: chocolate + fruit

Bright Filter @ 2.4 / 100g was “nice and different… chocolaty note but also some fruit,” with a note that bloom looked a little dark (hence a 2.2 follow-up). Washed F-Series still occasionally reintroduced green notes even when fruit appeared.

Dialed-in recipe

SettingValue
ProfileBright Filter
Level2.4 (fine-tune 2.2)
Batch100g
DTR~12.2%
Loss~16%
Rest7–10 days

Charts and full log: ASOSPAC case study →

Related reading

Track every roast, improve every batch

BrewedLate helps home roasters log green coffee inventory, roast batches, Kaffelogic curves, and get AI recommendations — all in one web-based tool.

Try the Free Roast TrackerBrowse Kaffelogic Profiles

How to roast Colombia ASOSPAC on a Kaffelogic Nano

Dialed-in recipe from a 12-roast log for washed Tolima ASOSPAC

1

Load 100g green

A 100g batch.

2

Select Bright Filter at level 2.4

A brightness/fruit-oriented profile; drop toward 2.2 if bloom looks dark.

3

Target ~12% DTR and ~16% loss corridor

Match the winning batch when conditions allow.

4

Rest at least 7–10 days

Re-brew after rest before changing family.

5

Taste for cranberry fruit plus cocoa/chocolate

Fruit and chocolate together — not pure roast or pure green.

Frequently Asked Questions

What is the best Kaffelogic profile for Colombia ASOSPAC?
In this log, Bright Filter at level 2.4 / 100g delivered chocolate notes plus fruit — the best balance for a fruity-bright goal. A tick lighter (2.2) is the ongoing fine-tune.
Why did Raost taste dark and roasty on this Colombian?
Early Raost runs hit very high DTR (26–33%) and tasted dark/roasted with no sweetness or fruit. Wrong family and over-development for a high-altitude washed fruit goal.
Did 9minFilter work for ASOSPAC?
Yes as a breakthrough: 9minFilter around 1.7–1.8 / 110–120g first unlocked clear fruit and sweetness. Later Bright Filter kept fruit and added a chocolaty note the cup profile promised.
What batch size should I use?
Winning Bright Filter batches used 100g. Successful 9minFilter fruit cups used ~110–120g. Avoid tiny loads if your standard profiles expect 100g+.
How long should washed Colombia rest?
Often a full week-plus. One note after 10 days still compared poorly to commercial rest expectations — judge after adequate rest before abandoning a profile.

Related Articles

How to Roast Kenya Gatugi Peaberry: 17 Roasts to a Dialed-In Cup

A data-backed case study of dialing in washed Kenya Gatugi peaberry: batch size as the hidden variable, profile experiments, and the final roast metrics that stuck.

Home RoastingRead more →

How to Roast Ethiopia Yirgacheffe at Home: Gentle Filter After 14 Roasts

A data-backed case study of dialing in washed Ethiopia Yirgacheffe: batch size, failed dark F-WSH runs, and the Gentle Filter corridor that worked.

Home RoastingRead more →

How to Roast Ethiopia Sidamo at Home: Gentle Filter Dialed-In Recipe

Data-backed home roast case study for Ethiopia Sidamo ETH04: profiles tried, rest lessons, and the Gentle Filter corridor.

Home RoastingRead more →

How to Roast Swiss Water Decaf Brazil: F-NAT 0-1200 at 3.4

Data-backed case study for natural-process Swiss Water Decaf Brazil: medium chocolate-nutty goal and the F-NAT corridor that stuck.

Home RoastingRead more →