Development Time and Drop Decisions
Development time is one of the most useful but most easily misread roast controls on the Roest. This page explains how the community uses post-first-crack time, bean temperature, weight loss, color, and sensory feedback to decide when to drop a roast. It focuses on practical drop decisions rather than treating development percentage as a universal target.
What “Development” Means on Roest
Development is not simply time after first crack. It is the degree to which desirable flavors are present, off-flavors are avoided, and the coffee becomes extractable. Roast degree, by contrast, is more closely tied to color and caramelization source.
On Roest, development time is especially dependent on batch size, airflow, RPM, inlet/ET behavior, process, and how first crack is marked. A 30-second development can be fully developed in one high-energy or larger-batch context, while 50-60 seconds can still taste underdeveloped in another. Development time should therefore be treated as a starting reference, not as the final drop rule.
Why First-Crack-Based Development Is Unstable
First crack is useful, but it is not always a reliable trigger. High RPM can create false crack detections, and different coffees may crack loudly, quietly, late, early, or barely at all 2 sources. Some processed and anaerobic coffees can have weak or nearly silent cracks, making auto-detection and crack counts especially risky.
For consistency, several contributors prefer marking first crack at a repeatable bean-temperature point once the coffee’s behavior is known, rather than relying entirely on audible crack timing. Sam recommends registering crack at the same temperature every time for consistency, because it is more consistent than audible auto-detection source. Denis often goes further: he marks or ignores FC as needed, drops manually by bean temperature, and does not rely on end conditions source.
For more detail on detecting, marking, and interpreting first crack, see First Crack Management.
Starting Targets and Drop Workflow
Use these as starting points, then adjust from taste, color, weight loss, and observed bean structure. Do not apply them across machines or batch sizes without verification.
| Context | Starting development target | Drop cue | Notes |
|---|---|---|---|
| Washed filter roast | 50-60 sec | Time from consistently marked FC, or calibrated BT drop | Common starting range for washed coffees; 50-55 sec has been suggested as enough for washed filter, with 65-70 sec moving toward omni 2 sources. |
| Washed omni / more developed filter | 60-70 sec | Same as above | Useful when more body, sweetness, or easier extraction is desired; avoid assuming longer is always better. |
| Natural process | 30-45 sec | Short time after FC or BT-based drop | Naturals often need less post-FC time than washed coffees; several ranges cluster around 35-45 sec, with shorter targets for delicate or fast-developing naturals 2 sources. |
| Fermented / anaerobic / fragile process | 25-40 sec | Prefer BT or conservative time, not crack count alone | Fermented coffees can overdevelop quickly after FC; one contributor noted they often become too developed if given the usual 30-60 sec after FC source. |
| High-energy / fast sample-style profiles | 20-35 sec | Short timed drop or BT target | Short development can still be developed when the profile has high energy and large temperature gain; Luca’s 50g profile guidance was 28-34 sec, with 40 sec described as dead and lacking acidity source. |
| 100g general-purpose sample roast | 40-50 sec | Adjust to taste | A 100g sample profile was described with 6 min+ FC, 40-50 sec dev, and 10-12% weight loss source. |
| 150g light washed / Ethiopia-style references | ~55-60 sec | BT drop or timed dev from marked FC | Multiple 150g washed examples land around 5-6 min FC and ~1 min development, but style varies widely. |
| 180-190g very light style | 15-40 sec | BT drop strongly preferred | Denis often targets very short development at larger batch sizes and warns not to do 40 sec+ in some 180g profiles source. |
| 200g batches | 45-60 sec for many profiles; shorter possible in high-energy styles | BT and sensory confirmation | Sam targets about 45-60 sec development for 200g batches in one framework source. Denis reports some 200g styles can be dropped after 20-30 sec without tasting under, but not on 100-120g source. |
| Espresso / medium development | 60-90 sec or more, depending on roast style | Higher drop temp / longer post-FC time | Short filter-style development is not enough for darker, medium, or city+ targets source. |
A practical workflow is:
- Choose a starting range from the table based on process, batch size, and roast intent.
- Mark first crack consistently, preferably by a repeatable temperature or a clear audible rule.
- Drop manually for the first few trials rather than relying on an automatic end condition.
- Record drop BT, development seconds, weight loss, color if available, and sensory notes.
- If a roast tastes good, use its drop temperature and weight loss as the reference for the next batch.
- Adjust in small increments: 5-10 seconds of development, about 1-2°C drop temperature, or profile changes earlier in the roast if the problem is not actually post-FC development.
Drop by Time, Temperature, or Weight Loss
Development time is easiest to communicate, but drop temperature and weight loss often give better repeatability once a profile is close. Denis’s workflow is to run one of his process profiles, drop based on bean temperature, ignore FC/cracks when necessary, then test color, cup, brew, and adjust from there source. He also argues that after a result is liked, the roaster should pay attention to drop temperature and repeat around that temperature, with bean shape and size causing small exceptions source.
Weight loss is useful as a consistency check and a warning that a roast is far off track, but it is not sufficient by itself to determine flavor development. Denis logs weight loss to compare future batches against a liked reference roast, while also warning not to use it alone to decide whether a coffee is underdeveloped source. See Weight Loss Targets for the dedicated treatment.
Color is also useful but incomplete. Color alone can mislead because different greens take color differently, grind size affects readings, and two roasts at the same color can taste very different. For color-meter practice, see Color Reading and Measurement.
Reading Development in the Cup
Longer development tends to reduce acidity and increase bitterness or roast character. In a controlled training comparison, the same coffee/profile at 40, 50, and 60 seconds showed lower acidity with more development while bitterness crept in source.
Useful sensory mappings:
| Symptom | Likely direction | Adjustment |
|---|---|---|
| Corn water, vegetal, grassy, hay, papery, hollow tea | Underdevelopment or insufficient earlier heat | Add development time, raise drop BT slightly, or fix earlier phase heat if extra dev does not help. |
| Good acidity but thin, weak, watery, low sweetness | Often too little development or too little inner development | Add 5-10 sec, raise end BT slightly, or adjust heat/RPM/airflow earlier. |
| Bitter, burned bread, ash, roasty/toasty aftertaste | Too much development, too much late heat, or too high inlet/ET | Drop 5-15 sec earlier, lower final inlet/ET, or reduce momentum into FC. |
| Mellow, low acidity, brown sugar/caramel, heavy body | More developed / more caramelized profile | Use if desired for omni/espresso; for brighter filter, shorten dev or reduce late energy. |
| Green notes disappear after a few days but cup remains weak | Borderline underdevelopment | Push development or earlier inner development on the next roast. |
If a roast is too roasty or too dark, Denis suggests dropping earlier into development and taking away roughly 10-15 seconds from total development source. If the cup is thin and lacks intensity, Sam points to insufficient development time as a likely cause source.
When More Development Does Not Fix the Roast
Not every underdeveloped taste is fixed by staying longer after first crack. Several examples in the community point to early-phase or mid-roast energy problems where extra development only adds roastiness, bitterness, or baked notes.
A common pattern is “outside roasted, inside under.” In that case, extending development may darken the exterior without solving inner development. The corrective lever may be batch size, RPM, pressure/airflow, earlier heat application, or charge temperature rather than simply adding time. See Heat Transfer Fundamentals, Drum Speed / RPM Settings, and Pressure Management.
Another pattern is a roast with a strong crash or flat RoR into development. Some sources caution that a long flat post-FC period can taste baked, flat, or low in intensity. For detailed handling, see Rate of Rise Management.
Process-Specific Notes
Washed coffees often tolerate or need more development than naturals. Several contributors describe washed coffees, especially Kenya and Ethiopia, as needing 50-60 seconds in many filter contexts, while naturals often work better with shorter development. For process-specific profile design, see Washed Process Roasting and Natural Process Roasting.
Naturals, anaerobics, and heavily processed coffees can develop or darken quickly. They may show acceptable development with few audible cracks, and some can become oily or overdeveloped with surprisingly short post-FC time. For these coffees, drop decisions should weigh taste, aroma, bean structure, and drop temperature more than crack count alone.
Kenya and Ethiopia require special caution because they appear throughout the community with widely different outcomes. Kenya can taste excellent with relatively low weight loss and short development in one context, but vegetal or savory in another. See Kenya and Ethiopian Coffees.
Batch Size Changes the Meaning of Development Time
The same development time does not mean the same thing at 50g, 100g, 150g, 185g, and 200g. Contributors repeatedly note that small batches may have unreliable BT readings and can taste over/under at the same time, while larger batches can develop the inner bean more in less post-FC time. Denis describes 100g as lacking in BT readings, with readings improving from 120g upward and becoming more solid around 140-150g 2 sources.
This is why profile sharing must keep batch size attached to the recommendation. A 30-second development on a 185-200g high-energy profile is not equivalent to 30 seconds on a 50g or 100g sample roast. For scaling guidance, see Batch Size Scaling.
Conflicts and Open Questions
CONFLICT (Unresolved): Short BT-based development vs longer FC-based development.
One school uses short development and BT-based manual dropping, especially for light larger-batch Roest profiles. Denis reports development targets as low as 15-25 seconds for very light roasts and often ignores FC in favor of drop temperature 2 sources. Another school, represented strongly by Sam in some testing contexts, uses much longer development, such as 1:30 for washed and 1:20 for naturals, especially when translating production-roaster timing or targeting color/development balance source. Both approaches appear valid within their own roast style, batch size, and sensory target.
CONFLICT (Unresolved): Development time vs drop temperature as the primary endpoint.
Some contributors prefer manual drop by target bean temperature because FC marking is subjective and inconsistent. Others still use development time as a practical control, provided FC is marked consistently. The safest synthesis is to record both: use a repeatable FC mark for communication, but calibrate final decisions against cup quality, drop BT, weight loss, and color rather than one number alone.
CONFLICT (Unresolved): How short is too short?
Some trusted contributors report good results at 20-30 seconds development for very light or high-energy roasts, while others find sub-30 seconds underdeveloped on certain beans. The difference appears tied to process, batch size, energy at FC, roast speed, and the preferred drinking/resting window. A page-level rule such as “always 30 seconds” or “always 60 seconds” is not supported by the claims.