Why plan rather than react
Reactive feeding - noticing a colony is short and feeding it there and then - is sometimes unavoidable, but a standing feeding plan drawn up for the season ahead generally produces better outcomes and less last-minute scrambling. A plan sets out, in advance, roughly what each colony is likely to need and when: spring stimulative feeding timed to precede the main flow, protein supplementation to bridge the early-spring pollen gap if it's a known issue at that site, and autumn feeding to bring every colony up to a safe winter weight well before the weather turns.
Tailoring the plan to the colony
A single feeding schedule rarely suits every colony in an apiary. Newly hived nucs and swarms generally need more sustained, frequent feeding to draw comb and build up numbers than an established, overwintered colony starting the season with full stores. Colonies that have come through winter light, or that were re-queened late and are playing catch-up, may need a more intensive spring programme than their neighbours. Building the plan around colony-by-colony assessment - rather than a single blanket schedule for the whole apiary - avoids both overfeeding strong colonies (which can trigger premature swarming or congestion) and underfeeding weak ones.
Putting a schedule together
A workable schedule sets out, for each stage of the season: what's being fed (thin syrup, thick syrup, fondant, pollen patty), roughly how much and how often, and the trigger for stopping (a nectar flow starting, or stores reaching a safe target weight). It doesn't need to be rigid - weather and forage vary year to year - but having a default plan to adjust from is far easier than deciding from scratch at every apiary visit whether a given colony needs feeding.
Monitoring and adjusting
A feeding plan is only as good as the monitoring behind it. At each visit, check what's actually happening rather than assuming the plan is working: feeder or fondant consumption, hive weight (by hefting or, for a more precise picture, a hive scale), brood pattern, and general colony temperament and activity. Keeping simple records - what was fed, when, and what was observed at the next visit - makes it much easier to spot a colony that isn't responding as expected, and builds up a useful picture of what that particular apiary actually needs from one year to the next, rather than relying on generic seasonal rules alone.
Be ready to deviate from the plan when the colony tells you to: a colony taking syrup unusually fast may be building comb or making up for a shortfall faster than expected and could need topping up sooner; one that isn't touching the feeder at all despite apparently needing it is worth investigating further, since untouched syrup can point to a problem (queenlessness, disease, or simply syrup placed somewhere the cluster can't reach) rather than a lack of need.
Frequently asked questions
Should every colony in an apiary get the same feeding schedule?
No - needs vary by colony strength, history and time of year, so schedules are best set colony-by-colony rather than applied as one blanket plan.
What should a feeding plan actually record?
For each season stage: what's being fed, roughly how much and how often, and the condition (flow starting, target weight reached) that signals it's time to stop.
How do I know if my feeding plan is working?
Check consumption, hive weight, and brood pattern at each visit, and keep simple records so you can compare what actually happened against what the plan expected.
What does it mean if a colony won't touch syrup I've provided?
It's worth investigating rather than assuming the colony doesn't need it - untouched syrup can indicate queenlessness, disease, or a feeder placed where the cluster can't easily reach it.
Try it live
See these dynamics unfold yourself in Beehive Colony: Agent-Based Model — a free, interactive 3D simulation that runs entirely in your browser.
▶ Open Beehive Colony: Agent-Based Model