Weekend Sourdough Baking Log: Perfect Your Loaf, One Bake at a Time

1. Bake Session Overview

Use this log during and after your weekend bake. There are no right or wrong answers — the goal is to capture what actually happened in your kitchen so you can compare bakes later and spot which conditions produce your favourite crust and crumb.


Baker name or nickname

Bake date

Which day of the week did this bake fall on?


Number of loaves produced in this bake

What shape were the loaves?


Is this a repeat of a formula you have baked before?


Recipe source or reference used (if any)

2. Flour Mix — Percentages of White, Whole Wheat and Rye

Enter your flour blend as percentages of the total flour weight. Bakers often use baker's percentages, where all flour adds up to 100 percent and every other ingredient is measured against that total. The table below estimates the weight of each flour from the percentages you enter.


Total flour weight used (g)

Flour Mix Breakdown

Flour Type

Percentage of Total Flour (%)

Total Flour Weight (g)

Weight of This Flour (g)

White bread flour
70.0
1000
700
Whole wheat flour
20.0
1000
200
Stoneground rye flour
10.0
1000
100
 
 
 
0
 
 
 
0
 
 
 
0
 
 
 
0
 
 
 
0
 
 
 
0
 
 
 
0

Do your flour percentages add up to 100 percent?


What characteristics were you aiming for with this flour blend?


Did you add any seeds, grains, or other dry add-ins to the flour mix?


Flour brand, mill, or source (optional)

Any notes about the flours themselves (protein level, freshness, how they felt)?

3. Starter and Levain

The condition of your starter or levain often shapes the whole bake. Recording how it looked, smelled and behaved before mixing gives you a useful reference point when comparing weekends.


Did you build a separate levain (pre-ferment) the day before this bake?


Starter feeding ratio used

Hours since the starter or levain was last fed

How active did the starter or levain look before use? (1 = sluggish, 5 = very active and domed)

Did the starter pass a float test in water?


How would you describe the aroma of the levain at use?


4. Hydration and Dough Formula

Hydration is the water weight divided by the total flour weight, expressed as a percentage. Higher hydration often gives a more open crumb but can be harder to handle, especially in a warm or humid kitchen.


Hydration formula

Hydration (%)=Water weight (g)Total flour weight (g)×100\text{Hydration (\%)} = \frac{\text{Water weight (g)}}{\text{Total flour weight (g)}} \times 100


Water weight used (g)

Calculated hydration (%)


Salt weight used (g)

What type of salt did you use?


How was the dough mixed and developed?


Describe your fold or knead schedule during the first hour or two:

Did you hold back any water during mixing and add it later?


5. Step-by-Step Progress Log

Fill in each stage as the bake unfolds. Note the start time, the room temperature at that moment, and what the dough actually looked like. Comparing these rows across weekends is one of the clearest ways to see how kitchen temperature affects your results.


Stage-by-Stage Progress

Stage

Start Time

Room Temperature (°C)

Visual Observations

Autolyse
8:30 AM
21.5
Shaggy, rough dough at first; smooth and extensible after resting, no dry patches left.
Bulk Fermentation
9:15 AM
22.0
Bubbly surface with bubbles at the edges; roughly doubled in size by the end of the window.
Proofing
1:30 PM
21.0
Loaf held its shape in the basket, puffy surface with a few visible bubbles, slight wobble when shaken.
Bake
4:00 PM
22.0
Strong oven spring in the first 12 minutes, score opened well, crust turned deep golden after the lid came off.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Approximate total time from mixing to the loaf coming out of the oven (hours)

How did you judge the end of bulk fermentation?


Did you notice any uneven fermentation (for example a warmer spot in the bowl)?


How manageable was the dough during shaping? (1 = very sticky and difficult, 5 = smooth and easy)

Any stage that felt off-schedule or surprising?

6. Shaping, Proofing and Bake Details

These details help you connect oven setup and proofing choices with the final crust and crumb. Adjust temperatures and times to suit your own oven and equipment.


How was the final proof carried out?


Scoring pattern used

Depth of score (mm), if you know it

What baking vessel or surface did you use?


Oven preheat temperature (°C)

Minutes the oven was preheated before loading

Bake temperature with the lid on (°C)

Bake temperature with the lid off (°C)


Total bake time (minutes)

Did you add steam during the first part of the bake?


Internal crumb temperature if measured (°C)

Anything unusual about the oven or kitchen this weekend (weather, humidity, other cooking)?

7. Results — Final Crust and Crumb

Once the loaf has cooled, take a moment to score the result honestly. Over time, this single rating alongside your room temperature readings will show you which kitchen conditions give you the texture you like best.


Final Crust & Crumb

Please rate each aspect of the finished loaf

Crust colour

Crust thickness and crunch

Crumb openness and evenness

Crumb moisture and softness

Flavour balance and sourness

Shape and oven spring

How would you describe the crumb when sliced?


Did the loaf have a noticeable sour tang?


How do you feel about this bake overall?

Upload a photo of the finished crust

Choose a file or drop it here

Upload a photo of the sliced crumb

Choose a file or drop it here

Estimated ingredient cost for this bake (optional)

What worked best in this bake?

8. Reflection and Plan for the Next Bake

Small, deliberate changes are easier to learn from than many changes at once. Choose one or two adjustments to try next weekend and note them here.


Which factors do you think most influenced this result?


Rank these areas by how much you want to adjust them next time (most important first)

Flour mix percentages

Hydration level

Levain ripeness and quantity

Bulk fermentation time

Final proof time

Oven temperature and steam

Will you repeat this formula on another weekend?


Notes and reminders for the next bake

I have recorded every stage and the final result for this bake

Baker's sign-off

Analysis for Weekend Sourdough Baking Log — Track Flour Mix, Fermentation and Crumb Results

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.



Overall Form Summary

This Weekend Sourdough Baking Log is a thoughtfully structured, multi-section form designed to help home bakers systematically record every variable of a sourdough bake — from flour blend percentages and starter condition through to fermentation timing, oven setup and a final crust and crumb rating. The form's greatest strength lies in its progressive, chronological flow: it mirrors the actual baking process from session overview through mixing, fermentation, shaping, baking and reflection. This makes the form intuitive to fill in during or immediately after a bake, reducing recall errors. The inclusion of a step-by-step progress table with room temperature and visual observations is particularly effective, as it directly supports the stated goal of correlating kitchen conditions with final texture. The use of conditional follow-up questions throughout keeps the form concise for straightforward bakes while still allowing detailed capture when unusual circumstances arise. Areas for improvement are minor: the form is quite long overall, which could feel daunting for quick weekend bakes; some optional fields (such as flour brand, estimated cost and image uploads) could be grouped or clearly marked as optional to reduce perceived effort. Additionally, the calculated hydration field is present but does not appear to have an automatic formula attached in the definition, which could lead to inconsistent manual entries.


Bake Session Overview

Baker name or nickname — This field establishes a simple identifier for each bake record. In a personal or small-group context, this supports straightforward record-keeping and lets the baker sort or compare entries over time. The placeholder encourages informal names, which is appropriate for a hobby-oriented log.


Bake date — Capturing the date anchors each log entry chronologically. This is essential for the form's core purpose of comparing conditions across multiple weekend bakes and identifying trends over time.


Which day of the week did this bake fall on? — This single-choice question with conditional follow-ups adds useful scheduling context. The follow-up fields for mid-week or multi-day bakes capture how the process was spread out, which can help explain timing variations when reviewing records later.


Number of loaves produced in this bake — Recording loaf count helps contextualise ingredient quantities and total bake time. A batch size of one versus several loaves can affect oven loading and fermentation behaviour.


What shape were the loaves? — Shape affects scoring, baking time and crumb structure. The conditional follow-up for tin dimensions is a practical touch that captures relevant detail without burdening bakers who use other shapes.


Is this a repeat of a formula you have baked before? — This yes/no question with branching follow-ups helps distinguish between iterative refinement and first-time experiments. Knowing how many times a formula has been attempted adds valuable context when interpreting results.


Recipe source or reference used (if any) — This optional field supports traceability and helps the baker recall where a formula originated when reviewing past bakes.


Flour Mix — Percentages of White, Whole Wheat and Rye

Total flour weight used (g) — This is the foundational measurement for baker's percentage calculations. It anchors the entire flour mix table and allows derived weights to be computed accurately.


Flour Mix Breakdown — The table structure is well designed, with columns for flour type, percentage of total, total flour weight and a calculated weight per flour using the formula ROUND(column2/100*column3,0). This automation reduces arithmetic errors and encourages consistent data entry. The pre-populated example rows (white, whole wheat, rye) serve as clear guidance.


Do your flour percentages add up to 100 percent? — This self-check question is a smart data-quality safeguard. The conditional follow-up for discrepancies captures legitimate reasons for totals below 100 percent (such as seed soakers), preventing confusion during later review.


What characteristics were you aiming for with this flour blend? — This multiple-choice question with follow-ups captures the baker's intent, which is important for interpreting whether results met expectations. The conditional fields for sour tang and other characteristics add useful depth.


Did you add any seeds, grains, or other dry add-ins to the flour mix? — Add-ins can significantly affect hydration, crumb and flavour. The conditional follow-up requesting quantities supports accurate record-keeping.


Flour brand, mill, or source (optional) — This optional field provides provenance context. Flour characteristics can vary between sources, so this can help explain differences between bakes.


Any notes about the flours themselves — This free-text field captures qualitative observations (freshness, texture, aroma) that quantitative fields cannot, adding richness to the log.


Starter and Levain

Did you build a separate levain (pre-ferment) the day before this bake? — This branching question distinguishes between levain-based and direct-starter methods. The follow-ups capture levain weight or how the starter was added, providing essential context for fermentation behaviour.


Starter feeding ratio used — Feeding ratio influences levain maturity and acidity. Recording it helps the baker correlate feeding practices with flavour and rise outcomes.


Hours since the starter or levain was last fed — This numeric field with decimal precision captures a key timing variable. Ripeness at use is one of the most influential factors in sourdough outcomes.


How active did the starter or levain look before use? — The 1-to-5 rating scale provides a quick, consistent measure of starter vitality that can be compared across bakes.


Did the starter pass a float test in water? — This yes/no field with a follow-up for observations captures a common practical check. The follow-up acknowledges that a failed float test does not necessarily mean the starter is unusable.


How would you describe the aroma of the levain at use? — Aroma is a useful qualitative indicator of fermentation state. The conditional follow-up for sharp aromas tracks whether that character carried into the finished loaf.


Hydration and Dough Formula

Water weight used (g) — Water weight is the numerator in the hydration calculation and is fundamental to dough behaviour. Capturing it precisely supports consistent comparison between bakes.


Calculated hydration (%) — This field is intended to hold the computed hydration percentage. The form includes a KaTeX equation displaying the formula, which is helpful for clarity. However, no automatic formula appears to be attached to this field in the definition, so the baker would need to calculate it manually or the form creator may wish to add an automated calculation.


Salt weight used (g) — Salt affects fermentation rate, flavour and dough strength. Recording it with decimal precision supports accurate formula tracking.


What type of salt did you use? — Different salt types can affect flavour and dissolution behaviour. The conditional follow-up for other salt types captures specifics.


How was the dough mixed and developed? — Mixing method influences gluten development and dough temperature. The multiple-choice format with a follow-up for other methods captures this variable efficiently.


Describe your fold or knead schedule during the first hour or two — This free-text field captures the mechanical development approach, which directly affects dough structure and fermentation.


Did you hold back any water during mixing and add it later? — Bassinage (delayed water addition) is a technique that affects dough handling. The conditional follow-up captures how much and when, which is useful for replication.


Step-by-Step Progress Log

Stage-by-Stage Progress — This is the form's centrepiece table, with columns for Stage, Start Time, Room Temperature (°C) and Visual Observations. The four pre-populated rows (Autolyse, Bulk Fermentation, Proofing, Bake) guide the baker through the key phases. This structure directly supports the form's stated goal of correlating kitchen temperature with results. The example observations in the rows serve as helpful prompts.


Approximate total time from mixing to the loaf coming out of the oven — This summary metric gives a quick overview of the bake's total duration, useful for comparing efficiency across sessions.


How did you judge the end of bulk fermentation? — This question captures the baker's decision-making method. The conditional follow-up for the sample jar method adds precision, while the other follow-up captures alternative approaches.


Did you notice any uneven fermentation? — Uneven fermentation can indicate temperature gradients in the kitchen. The follow-up captures details about the bowl's location, which is practical for troubleshooting.


How manageable was the dough during shaping? — The 1-to-5 rating provides a quick measure of dough handling characteristics, which correlates with hydration, fermentation and flour choice.


Any stage that felt off-schedule or surprising? — This open-ended field captures unexpected events that structured fields might miss, adding narrative context to the log.


Shaping, Proofing and Bake Details

How was the final proof carried out? — Proofing method (room temperature, cold retard, or a mix) significantly affects flavour and crumb. The conditional follow-ups capture duration details for cold retard and mixed approaches.


Scoring pattern used — Scoring affects oven spring and crust appearance. This free-text field captures the baker's technique.


Depth of score (mm) — Score depth influences how the loaf opens during baking. The optional nature of this field is appropriate, as not all bakers measure precisely.


What baking vessel or surface did you use? — The vessel affects heat transfer, steam retention and crust development. The conditional follow-up for other vessels captures specifics.


Oven preheat temperature (°C) — Preheat temperature is a key variable in oven spring and crust colour. Recording it supports meaningful comparison between bakes.


Minutes the oven was preheated before loading — Preheat duration affects how thoroughly the vessel and oven are heated, which can impact the initial bake.


Bake temperature with the lid on/lid off — These two fields capture the two-phase baking approach common in covered-pot baking. The split is practical and mirrors real-world practice.


Total bake time (minutes) — Total bake time is essential for correlating with crust colour, crumb moisture and internal temperature.


Did you add steam during the first part of the bake? — Steam affects crust formation and oven spring. The branching follow-ups capture how steam was created or how the absence of steam affected the crust.


Internal crumb temperature if measured — This optional field captures doneness data for bakers who use a thermometer, supporting more precise comparisons.


Anything unusual about the oven or kitchen this weekend — Environmental factors like humidity or other cooking can affect results. This free-text field captures context that structured fields cannot.


Results — Final Crust and Crumb

Final Crust & Crumb — This 1-to-5 star rating is the form's primary outcome measure. It is the key metric the baker will track against room temperature readings to identify optimal kitchen conditions. Its simplicity makes it easy to record consistently.


Please rate each aspect of the finished loaf — The matrix star rating breaks the result into six sub-questions (crust colour, crust thickness, crumb openness, crumb moisture, flavour balance, shape and oven spring). This granular breakdown provides much richer data than a single rating alone and helps pinpoint specific areas for improvement.


How would you describe the crumb when sliced? — This descriptive field with conditional follow-ups captures crumb characteristics qualitatively. The follow-up for dense or gummy textures prompts the baker to reflect on possible causes.


Did the loaf have a noticeable sour tang? — Sourness is a key flavour dimension in sourdough. The branching follow-ups capture either the strength of sourness or an alternative flavour description.


How do you feel about this bake overall? — The emotion rating adds a subjective, personal dimension to the log that complements the structured ratings.


Upload a photo of the finished crust/sliced crumb — Image uploads provide visual records that are invaluable for comparing bakes over time. Visual documentation often reveals details that text descriptions miss.


Estimated ingredient cost for this bake (optional) — This optional currency field adds an economic dimension for bakers who want to track costs. Its optional status is appropriate.


What worked best in this bake? — This reflective field helps the baker identify successful practices worth repeating.


Reflection and Plan for the Next Bake

Which factors do you think most influenced this result? — This multiple-choice question encourages analytical thinking about cause and effect. The follow-up for other factors captures additional insights.


Rank these areas by how much you want to adjust them next time — The ranking question forces prioritisation, which aligns with the form's guidance to make small, deliberate changes rather than many at once.


Will you repeat this formula on another weekend? — This branching question captures the baker's intention and what they plan to change (or try instead), supporting iterative improvement.


Notes and reminders for the next bake — This free-text field serves as a practical to-do list for the next session.


I have recorded every stage and the final result for this bake — The checkbox acts as a self-confirmation step, encouraging thoroughness before sign-off.


Baker's sign-off — The signature field provides a sense of completion and personal ownership of the record.


Overall Assessment

This form is exceptionally well designed for its purpose. Its chronological structure mirrors the baking process, making it intuitive to complete. The combination of structured fields (ratings, numeric inputs, choice questions) with free-text observations captures both quantitative and qualitative data effectively. The use of conditional follow-ups throughout keeps the form efficient while allowing depth when needed. The step-by-step progress table with room temperature tracking is a standout feature that directly enables the form's core analytical goal. Minor areas for potential improvement include: (1) adding an automatic calculation formula to the Calculated hydration (%) field to match the formula displayed in the equation element, (2) clearly marking optional fields (such as flour brand, estimated cost and image uploads) to reduce perceived form length, and (3) considering whether the full form could be split into a shorter core log and an optional extended section for bakers who want to capture every detail. Overall, the form balances depth and usability well and is well suited to helping home bakers systematically improve their sourdough results over time.


Mandatory Question Analysis for Weekend Sourdough Baking Log — Track Flour Mix, Fermentation and Crumb Results

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.


Mandatory Question Analysis

Baker name or nickname
Requiring this field helps ensure each bake record can be associated with a specific baker, which is particularly useful in shared or household contexts where multiple people may log their bakes. It supports basic record organisation and prevents anonymous entries that would be difficult to attribute later. The form creator should confirm whether informal nicknames or more formal identifiers best serve their intended record-keeping needs.


Bake date
Marking the bake date as mandatory supports chronological record-keeping and enables meaningful comparison across multiple baking sessions. Without a date, it would be difficult to track trends over time or correlate results with seasonal or environmental changes. This is a reasonable requirement given the form's purpose of building a comparative baking log.


Number of loaves produced in this bake
Requiring loaf count helps contextualise ingredient quantities, total bake time and oven loading conditions. A single loaf versus a multi-loaf batch can affect fermentation timing and baking outcomes. This requirement supports accurate interpretation of the data captured in other fields, though the form creator may wish to consider whether a default value of 1 could reduce friction for the most common single-loaf scenario.


Total flour weight used (g)
This field is foundational to the flour mix table and the hydration calculation. Requiring it ensures that the baker's percentage breakdown and derived weights in the table are meaningful and comparable across bakes. Without this value, much of the quantitative data in the form would lack context. This is a reasonable mandatory requirement for the form's analytical purpose.


Water weight used (g)
Water weight is essential for calculating hydration, which is one of the key variables the form aims to track. Requiring this field supports the core objective of correlating formula variables with final crust and crumb results. The form creator should note that the Calculated hydration (%) field does not appear to have an automatic formula attached, so bakers may need to compute this manually.


Salt weight used (g)
Requiring salt weight supports complete formula documentation. Salt influences fermentation rate, flavour and dough strength, so its inclusion in the mandatory set helps ensure the formula record is comprehensive enough for meaningful comparison between bakes. This requirement is proportionate to the form's purpose of building a detailed, replicable baking log.


Oven preheat temperature (°C)
Requiring oven preheat temperature captures a key variable that affects oven spring and crust development. Including it in the mandatory set supports the form's goal of identifying which conditions produce the best results. This is a reasonable requirement, though the form creator may wish to consider whether a typical default value could be offered as a starting point to reduce entry effort.


Total bake time (minutes)
Total bake time is essential for correlating baking duration with crust colour, crumb moisture and overall results. Requiring this field ensures that the bake record includes enough detail for meaningful comparison across sessions. This requirement supports the form's stated purpose of helping bakers identify optimal conditions.


Final Crust & Crumb
This 1-to-5 star rating is the form's primary outcome measure and the key metric the baker will track against room temperature and other variables. Requiring it ensures that every log entry includes a result assessment, which is essential for the form's analytical purpose. Without this rating, the log would capture process data but lack the outcome data needed to identify which conditions produce the best texture. This is a well-justified mandatory requirement.


Overall Mandatory Field Strategy Recommendation

The form currently designates 9 fields as mandatory, distributed across the session overview, flour mix, hydration formula, bake details and results sections. This is a reasonable and well-balanced selection: the mandatory fields capture the core quantitative variables (flour weight, water weight, salt weight, oven temperature, bake time) and essential identifiers (baker name, bake date, loaf count) alongside the primary outcome measure (final crust and crumb rating). The placement of mandatory fields throughout the form — rather than concentrated at the beginning — means the baker encounters requirements at the natural point in the process where the information is most relevant, which can feel less burdensome than a front-loaded set of required fields.


  • Balancing depth against completion rates: The form is quite comprehensive overall, with many optional fields alongside the mandatory core. This is a sensible approach — it allows enthusiastic bakers to capture extensive detail without forcing casual users to fill in every field. Consider clearly marking optional fields (such as flour brand, estimated cost and image uploads) with a visual indicator to reduce perceived form length and lower the barrier to completion.

  • Conditional logic: The form already makes effective use of conditional follow-ups throughout, which is excellent. This keeps the form concise for straightforward bakes while capturing detail when relevant. Consider whether any currently unconditional optional fields could benefit from being triggered by a preceding question to further streamline the experience.

  • Mandatory field placement and selection: The mandatory fields are well chosen — they represent the minimum data set needed for the form to deliver its stated value (comparing kitchen conditions with final texture). The Final Crust & Crumb rating as mandatory is particularly well justified, as it is the outcome variable the entire log is designed to support. The numeric fields (flour weight, water weight, salt weight, oven temperature, bake time) are also reasonable requirements given the form's analytical purpose.

  • Overarching observations: With 9 mandatory fields spread across a long form, the overall required-field burden is moderate. The form creator may wish to consider whether Number of loaves produced in this bake could default to 1 and be made optional, as single-loaf bakes are likely the most common scenario. Similarly, Calculated hydration (%) is not marked mandatory but is listed as a key field — if an automatic formula were added to compute it from water and flour weights, it could be populated automatically and would not need to be a required manual entry. Periodically reviewing the mandatory set based on user feedback and actual completion patterns can help ensure the requirements remain proportionate to the form's intended use.


Let’s tile this form so fly it’ll be floor-less! 🦋🧱 Edit this Weekend Sourdough Baking Log — Track Flour Mix, Fermentation and Crumb Results
Ready to build a form that's sharper than a brand-new set of steak knives? Zapof's got your back with conditional logic and question branching – it's like giving your users the VIP treatment, every single time!
This form is protected by Google reCAPTCHA. Privacy - Terms.
 
Powered by Zapof