A Stage-Based Blueberry Greenhouse Management Plan

By Coraline Liao, CEO, CFGET | Reviewed by CFGET Project Planning Team | Updated: July 24, 2026

A January pruning instruction is useless if January means deep dormancy at one farm and active fruit development at another. Greenhouse cover can move crop timing again. The operating calendar needs to start with what the plant is doing, then attach local dates.

This guide builds that calendar around visible stages. It helps the team decide:

• what to observe before acting;
• which records need to sit together;
• where pruning, pollination, irrigation and climate decisions interact;
• what must be confirmed locally before a task enters the standard procedure.

Use it beside the blueberry greenhouse planning guide. The pillar explains the whole production system; this page assigns work through the crop cycle.

Start with phenology, then add dates

Phenology is the timing of plant-development events such as bud swell, bloom and ripening. It is more reliable than a copied monthly calendar because it shows which biological stage the team is managing.

UGA Extension’s guide to recognizing flower and vegetative buds helps distinguish the structures before pruning and bud counts. Its photos and regional context should be checked against the cultivars on the farm.

Build one local record for each cultivar block:

After two or more seasons, this record becomes useful for labour, pollination, packing and climate planning. The dates may shift, but the sequence exposes what changed.

Winter state: Verify the intended biology

Some projects maintain deciduous dormancy. Others use evergreen systems with selected southern highbush cultivars in suitable climates. Neither is an equipment setting that can be chosen at the last minute.

At this stage, record:

• cultivar and intended winter state;
• chill accumulation with the chosen model;
• leaf retention and plant condition;
• dormant flower-bud load;
• root-zone moisture and drainage;
• protected and outdoor temperature history;
• heater, vent and freeze-protection readiness.

Do not warm the house because the crop “looks asleep.” Confirm chill and market-timing decisions from the cultivar and chill guide.

Beginner takeaway

The calendar begins before leaves return. Winter conditions influence bud break, bloom timing and the amount of fruiting wood available for the season.

Pruning: Decide what the cut is meant to change

Pruning can influence plant structure, flower-bud load, renewal growth, light distribution and harvest labour. The correct severity depends on plant age, cultivar, vigour and production goal.

Before cutting, sample plants and record:

• healthy and weak cane count;
• flower and vegetative bud distribution;
• dead, damaged or diseased wood;
• canopy crowding and worker access;
• previous yield and fruit-size pattern;
• replacement growth for future seasons.

UGA Extension’s pruning techniques explain the reasoning behind establishment pruning, flower-bud load and cane renewal. Commercial blueberry timing and severity still need cultivar and regional advice.

Mark several reference plants before pruning. Photograph them, count selected attributes and follow their crop response. A team learns more from those records than from changing pruning style across the whole block without a comparison.

Bud break and pre-bloom: Prepare the system before flowers open

Once buds advance, cold sensitivity, pollinator preparation and disease risk can change quickly.

Complete these tasks before meaningful bloom:

1. verify cultivar labels and the bloom-overlap map;

2. inspect vents, screens and pollinator access routes;

3. calibrate flower-height climate sensors;

4. check irrigation uniformity and root condition;

5. review the local crop-protection plan for bloom;

6. confirm labour responsibility for daily flower-stage records;

7. test alarms for cold, heat, humidity and equipment failure.

A late scramble around open flowers usually means the preparation stage was skipped.

Bloom: Treat pollination as daily fieldwork

During bloom, record flower stage by cultivar, pollinator visits, condensation, weather and spray events on the same sheet.

The blueberry greenhouse pollination guide provides the full method. The crop calendar only needs to show:

• who checks colony or pollinator condition;
• where fixed observation points are located;
• when weak distribution triggers a call to the pollination supplier;
• which climate or spray change requires team approval;
• how flower damage is separated from pollination failure.

Avoid judging fruit set while bloom is still moving through the block. Keep the observations, then compare them with later set.

Fruit set and expansion: Confirm the crop before feeding the estimate

UGA Extension describes blueberry fruit set, development and ripening as a sequence affected by pollination, seed development and environment. See Blueberry Fruit Set, Development and Ripening.

For greenhouse management, map:

• initial set by cultivar and zone;
• fruit drop and damaged clusters;
• new shoot growth and canopy density;
• root-zone water balance;
• leaf and fruit temperature during high radiation;
• pH and EC trends from fixed samples;
• early pest or disease patterns.

Do not increase water or fertilizer solely because fruit is visible. Use measured plant and root-zone demand. The irrigation and fertigation guide explains the input-output check.

Professional grower note

Compare fruit set with the earlier bloom map. Good set near pollinator entry and weak set in distant rows points to a different problem from uniform weak set in one cultivar.

Ripening and harvest: Protect fruit condition and the picking system

The crop is commercially unfinished until suitable fruit reaches the buyer.

Track:

• maturity and picking criteria agreed with the buyer;
• fruit temperature at harvest;
• wetness or condensation before picking;
• firmness, visible defects and rejected fruit;
• pick rate and labour availability;
• time from picking to cooling;
• pack and cold-chain performance;
• marketable volume by cultivar and date.

Harvest records should separate total picked weight from saleable pack-out. A greenhouse that shifts timing but increases rejects has not delivered the intended business result.

The user-identified CFGET protected blueberry video shows a large container block but does not identify crop stage. The local Chengdu video separately shows fruit at mixed ripening stages and a worker carrying a harvest basket. Those images confirm harvest activity, not yield, pack-out or fruit quality.

Postharvest: The next crop has already started

After the main harvest, review plant recovery and the structure of next season’s crop.

Record:

• cane and shoot growth;
• leaf condition;
• root health and irrigation response;
• tissue or substrate tests justified by the program;
• pest and disease history;
• damaged equipment and emitter replacement;
• pruning observations for the next cycle;
• actual labour, utility and pack-out figures.

Use the quieter period to compare planned and actual dates. Update standard procedures while the reason for each change is still clear.

One page for the operating room

Create a live dashboard with these columns:

The threshold can be a local technical limit, a visual trigger or a call for specialist review. It must tell staff what happens next.

For example, “check humidity” is not an operating instruction. “Inspect flower wetness at the three marked zones before pollinator release; call the crop lead if any remains wet” is testable.

A regional calendar is a reference, not your schedule

UF/IFAS publishes a detailed southern highbush blueberry management calendar for Florida. It shows how tasks can be organized around a regional crop cycle. Its months, cultivars, pests and production assumptions belong to Florida.

Use regional calendars to find missing task categories. Put your own dates beside observed phenology, greenhouse conditions and local registrations.

About this review

Coraline Liao, CEO of CFGET, reviewed this page with attention to turning visible crop stages into an operating calendar. Her public LinkedIn profile describes her as a Greenhouse Technical Director with more than 15 years in the greenhouse industry.

The CFGET Project Planning Team completed the technical review. Cited research, direct observations from CFGET’s Chengdu footage and professional interpretation are kept separate. Local crop advisers, laboratories, engineers and authorities must confirm decisions that depend on cultivar, site or regulation.

Project video: greenhouse project reference

This field video gives a quick project visual to read beside the specifications and RFQ checklist.

Frequently asked questions

When should greenhouse blueberries be pruned?

Timing depends on production system, cultivar, plant age, climate and the purpose of the cut. Identify buds and define the intended crop-load or renewal effect before choosing the date.

Can one calendar cover every cultivar?

Use one farm framework, then keep stage dates and cultivar-specific tasks by block. Bloom, harvest and pruning response can differ enough to require separate entries.

What is the most important bloom record?

Record cultivar flower stage, pollinator activity, flower condition and climate together. Any one of those alone can mislead the diagnosis.

When should the calendar be updated?

Update observations during the stage and review the full calendar after harvest. Record why a procedure changed, not merely the new date.

Your next action

Make the first version from this season’s crop:

1. label cultivar blocks and reference plants;

2. define visible stages that all scouts can recognize;

3. enter actual dates from farm records;

4. assign one owner to each observation and decision;

5. connect climate, irrigation, pollination, IPM and labour records;

6. add buyer and pack-house milestones;

7. review the completed cycle before the next pruning decision.

The resulting calendar belongs in the blueberry greenhouse requirements and start-up checklist. It tells a system designer when the crop needs each function and tells the operating team what to verify.