Coffee Education8 min read

Coffee Roast Log Template (Free) — Plus a Better Way to Track Roasts

A roast log is how you turn one good roast into a repeatable one. Here's a free template with the fields that matter, a filled-in example, and an easier option for Kaffelogic owners.

BrewedLate Coffee

Coffee Expert

#coffee roast log #roast log template #coffee roasting #home roasting #kaffelogic nano 7

A roast log is the difference between "that one great batch I can't recreate" and a profile you can dial in on demand. This guide gives you a free template with the fields that actually matter, a worked example from a real home roasting setup, and — if you're roasting on a Kaffelogic Nano — a way to skip the manual logging entirely.

What worked for other roasters

Most-used community Kaffelogic profiles, ranked by real downloads and rated roast outcomes.

  • 1
    Adap. Raost NCC
    10% success · 18 roasts
    859
    47 likes
  • 2
    JRoast v7
    Washed

    FC 203.7°C is very close to expected 205°C, weight loss 13.2% is ideal, and ~101s post-FC development is well-executed for a light roast.

    755
    24 likes
  • 3
    JLightEtiopia
    Natural
    532
    23 likes
  • 4
    April Fools!
    667
    5 likes
  • 5
    JLightColumbia
    Washed
    9% success · 13 roasts
    473
    18 likes

Community roast data via kl-profiles.com · 71 profiles · 8,634 downloads

Why Bother Logging Roasts?

Home roasting has one brutal property: every variable interacts. Change the profile and the first crack time moves. Change the green weight and the development time ratio shifts. Without a log, you're re-deriving cause and effect from memory every time — and memory is optimistic.

A log turns each roast into a data point you can compare against the next one. Three roasts on the same bean at slightly different levels, logged properly, will teach you more than thirty roasts from memory.

The Free Coffee Roast Log Template

Copy this table into Google Sheets, Notion, or a notebook. The first nine columns are recorded during (or immediately after) the roast; the last four you fill in after resting and cupping.

FieldExampleWhy it matters
Date2026-07-12Tracks rest time and bean age
CoffeeEthiopia Guji, naturalOrigin + process drive profile choice
Green weight (g)120Batch size changes roast dynamics
ProfileF-NAT-1500-2200Your heat/fan recipe
Roast level2.0Where on the curve you ended
Total time7:08Baseline for comparisons
First crack6:35Start of development phase
DTR (%)7.7%(Total − FC) ÷ total — your development ratio
Post-roast weight (g)105.6Yield; pairs with green weight
Roast loss (%)12.0%Moisture loss; a proxy for development
Rest days7When you actually evaluated it
Cup notesFruity, slight earthinessThe whole point of the exercise
Next adjustmentTry level 2.5Closes the loop into the next roast

That last column is the one most templates omit, and it's the most valuable: every roast should end with a hypothesis for the next one.

A Worked Example: Bracketing a New Bean

Say you land a natural Ethiopia Guji and you're roasting on a Kaffelogic Nano 7 at 120 g batches. A sensible first pass is bracketing — three roasts at three levels so you can taste the spread:

#ProfileLevelTotalFCDTRLossNotes
1F-NAT-1500-22001.06:475:3118.6%11.1%Fruity but earthy — likely too light
2F-NAT-1500-22002.07:086:357.7%12.0%Less earth, still a hint
3F-NAT-1500-22003.07:196:2113.2%12.2%(cup after 7 days)

With the log filled in, the pattern is visible at a glance: roast 1's earthiness tracks with its short total time, and roast 2 confirms the direction. Your next session starts with a decision instead of a guess.

Where Spreadsheets Break Down

A template like this earns its keep for your first dozen roasts. Past that, the cracks show:

  • Manual entry drifts. Miss one first-crack time and your DTR column lies to you forever.
  • No curves. A total time can't show you where the roast stalled — the curve can.
  • No search. "Which roasts of washed Kenyans above 1,700 m landed under 14% loss?" is three clicks in software and a lost afternoon in Sheets.
  • Nothing compounds. The spreadsheet never turns your history into a recommendation for next time.

The Better Way for Kaffelogic Owners: Upload the Log File

If you roast on a Kaffelogic Nano, the machine already writes a complete .klog log of every roast — bean temperature, fan, and power curves with exact timestamps. Instead of transcribing, you can upload the file to BrewedLate Roasting and let it fill in the roast automatically:

  • Times, curves, and profile parsed straight from the .klog — no manual entry
  • Green coffee inventory and cellar tracking alongside each batch
  • AI suggestions for your next roast, based on your history and tasting comments
  • A plan-before-you-roast checklist, so the "next adjustment" column becomes tomorrow's to-do list

You only add what the machine can't know: how it tasted and what you'd change. Demo mode works without signup if you want to see it with sample data first.

Either way, keep logging. The template above is free and works today — the app just removes the parts nobody enjoys.

Related Reading

Frequently Asked Questions

What should I record in a coffee roast log?
At minimum: the date, coffee (origin and process), green weight, roast profile or heat settings, total roast time, first crack time, post-roast weight, and cupping notes after resting. From those basics you can calculate roast loss and development time ratio (DTR), which are the two numbers that make roasts repeatable.
What is development time ratio (DTR) in coffee roasting?
Development time ratio is the time from first crack to the end of the roast, divided by total roast time, expressed as a percentage. Most filter roasts land between 10% and 20%. If a roast tastes flat or baked, your DTR was likely too long; if it tastes grassy or sour, it was likely too short.
Is a spreadsheet good enough for logging coffee roasts?
A spreadsheet works for your first dozen roasts and is better than memory. It breaks down when you want to compare curves, search across roasts, or convert notes into a plan for the next batch. Purpose-built roast tracking software automates the calculations and keeps every roast searchable.
Do Kaffelogic Nano owners need a manual roast log at all?
Not really. The Nano records a complete .klog log file for every roast — bean temperature, fan, and power curves with timestamps. Uploading that file to roast tracking software fills in times, temperatures, and curves automatically, so you only add the things the machine can't know: how the coffee tasted and what you'd change.
How long should I wait before cupping a roast?
Rest washed coffees 7–10 days and naturals 5–7 days before judging them seriously, and record the rest days in your log. Tasting too early is the most common reason roasters 'fix' profiles that were actually fine.
Roasting

Track your roasts with BrewedLate

Plan roast batches, upload Kaffelogic logs, and get AI roast suggestions for your next roast — free.