Labelling Bare-Root Plant Batches So Every Root Bundle Keeps Its Identity

Why bare-root batches lose their identity

Bare-root plants arrive or leave a nursery as bundles of dormant crowns and roots wrapped in damp material, and that presentation erases almost everything you would normally use to tell plants apart. There is no pot to write on, no foliage, no flower and often no obvious stem character. A shipment of bare-root herbaceous perennials, roses, fruit canes or tree whips can contain several similar-looking bundles, and once wrappings are opened and roots are separated, the only remaining link to a name is whatever label you attached. That is exactly where a recurring problem starts: batch labels written in pencil, pushed into soil later reused for something else, or recorded only in your head.

The practical fix is not a single clever marker. It is a labelling system that treats each bare-root batch as a traceable unit from the moment it arrives until the plant is established and can be identified by its own growth. Good batch labels capture three things at once: what the plant is, which batch it belongs to and where or when it was handled. Build that habit and the usual failures — mislabelled divisions, duplicated names, lost provenance and a row of similar-looking trunks you cannot sort out in spring — mostly stop happening.

What a bare-root batch label should carry

A bare-root bundle is a temporary object, so its label needs to survive handling rather than a season of sun and rain. The information it holds matters more than its style.

• Plant identity: the full botanical name, plus the cultivar name if you grow named selections. Include the common name only as a secondary line.
• Batch or lot code: a short reference you assign, such as a supplier name and an arrival date, or your own propagation year and sequence number.
• Quantity: how many roots, crowns, canes or whips were in the bundle, since this is what tells you later whether all of them were planted.
• Source and date: where the batch came from and when it arrived or left storage.
• Intended destination: the bed, row, pot group or nursery area where the batch is going, so a bundle is never planted without a record of its intended place.

Give every batch a code you can read back

A code works best when it is short, structured and unambiguous. A format like two letters for the source, two digits for the year and a running number — for example a source code plus 24-07 — gives each bare-root batch a unique identity without writing a paragraph on a small tag. Write the code in two places: on the batch label attached to the bundle and in a notebook or spreadsheet line that repeats the full name, quantity and destination. If the physical tag is lost, the code still links the batch to its written record; if the written record is lost, the tag still carries the essentials.

Label bundles before you unwrap them

The most reliable moment to label bare-root plants is before roots are separated or trim work begins. Attach a durable tag to the bundle tie itself, not to the wrapping material that will be discarded. Use a waterproof pen or a pencil on a plastic or metal plant tag, and add a second copy inside the packaging if the bundle will be shared. When several bundles are opened at the same time, keep one label with each bundle rather than one label for the whole delivery table. This single habit prevents the most common mix-up: two similar bundles on the same bench, one label between them.

Choosing tags and markers that survive the job

The best labelling supplies for bare-root work are the ones that tolerate damp roots, soil contact and handling. Several product categories earn a place in a propagation or nursery kit.

• Waterproof plastic or metal plant tags: choose tags with a writing surface that does not absorb water and a tie that resists rot. Metal tags suit batches that will be heeled in outdoors for weeks; plastic tags are lighter for short transfer runs.
• Permanent markers or a pencil: permanent ink for plastic tags, a soft pencil for metal or wooden tags. Faint abbreviations defeat the purpose, so use a marker with clear contrast.
• Bundle ties or elastic bands in a distinct colour: a colour can encode a batch group at a glance, but only if the same colour is not used for a different batch in the same season.
• A batch record book or a spreadsheet: a durable notebook kept with the work or a simple digital sheet gives the batch its written identity and lets you log quantities and destinations.
• Propagation labels for the next stage: when roots go into pots or nursery beds, transfer the code to a larger, long-lasting label so that field identity matches the batch record.

Specialist nursery labelling systems with colour-coded tags and printed batch lists make sense when you handle many batches at once, but the same function is served by consistent handwritten tags and a well-kept record at small scale. Buy for the job you actually do: damp outdoor heeling-in favours metal and pencil; indoor bench work favours plastic tags and permanent marker.

Carry the batch code through every stage

Bare-root plants pass through several transitions where labels tend to fall away: unpacking, trimming, soaking, heeling in, potting and finally planting out. The recurring problem is not the first label but the gap between stages. Plan for the hand-offs.

Unpacking and temporary storage

Keep the original bundle tag attached while plants are in cold storage or heeled into damp medium. A tray label or a marker stake at the heeling-in site records the batch even if the bundle itself is divided. If you split a batch between two storage locations, copy the code to each location instead of moving the only label.

Pricking out and potting

Once bare-root plants go into individual pots, each pot needs its own label carrying the batch code plus the botanical name. At this point a reader looking at the pot can cross-check the batch record for source and origin. Use one label per pot, placed firmly in the medium, and write the code before the plant goes in so the label never depends on memory.

Planting out and beyond

When a batch reaches its final bed, record the code and destination on a bed plan or map. A map is the fallback that survives lost tags: even if the plastic label disappears, the bed record tells you which batch was planted where, and a brief note about the expected habit helps you confirm the identity when the plant grows. Update the record when a batch is moved or divided, and add the division date when you propagate again from an established plant.

Keeping records that answer real questions

A well-run batch record is not bureaucracy; it answers the questions that come up in the following seasons. It tells you whether all twelve bare-root whips in a bundle were actually planted, which supplier's batch struggled, and which bed holds last year's division. For propagation, it also links the new plant to the age and origin of the parent material, which is the real difference between a named plant and a stray label.

Record in a way you will genuinely consult. A single notebook page per batch, with columns for code, name, quantity, source, arrival date and destination, is enough. Digital records add searchability and can be updated while working, but a notebook kept in the potting area is more likely to be filled in at the bench. The practical test is simple: after a week away from the nursery, can you tell from the record alone what each batch is, where it came from and where it should be? If yes, the system is working.

Finally, make labelling part of the batch's routine rather than an extra chore. When a bare-root delivery arrives, label the bundles and enter the batch before any root is trimmed. When a batch is split, label both halves immediately. When a plant is finally planted out, transfer the code to the bed map before the tag is removed. That sequence is the whole answer to the recurring problem of mislabelled bare-root batches: a tag on every bundle, a code that follows the batch and a record that survives the season.