Team Store Decision Log: Writing Down Why the Store Is the Way It Is

6 min read
An open notebook of simple log entries beside a laptop, fabric swatches and a folded blank navy t-shirt.

Most team store questions that arrive mid-season are not really about the store. They are about a decision someone made weeks earlier: why the youth sizes stop where they do, why the secondary color is the one on the hoodie, why the window closes on a Friday. If that decision lives only in one organizer's memory or in a message thread, it has to be re-made every time it is questioned. A decision log is the small habit that prevents that.

The short answer: keep one dated list, owned by the organization, where each entry records what was decided, who decided it, what it was based on, and what would change it. Write entries as decisions happen rather than at the end. Keep the log free of personal information about families and students. When the season closes, the log is the core of what you hand on, because the advice to keep the small number of things that make next season easier, delete the personal information you no longer need, and leave one findable note saying where everything is depends on those things having been written down in the first place.

What belongs in an entry

An adult writes a short entry in a ruled notebook with an orange fabric swatch clipped to the page.

A decision log works when entries are short and consistent. For each decision, record:

  • The date the decision was made, not the date it was written up.
  • The decision itself in one plain sentence. "The store will carry youth and adult sizes in the two approved colors only."
  • Who made it. Use the role, such as the booster treasurer or the athletic director, and the name only where the organization's own records already use names for that role.
  • What it was based on. The approved identity record, the artwork permission, a school policy, a prior season's note, or a confirmed product detail from the approved source for that exact item.
  • What would change it. A new policy, a changed roster of responsible adults, a confirmed detail that turns out to differ.

Entries that lack a basis are the ones to revisit. A decision made because "that is what we did last year" is still a decision, but the log should say so, so that the next organizer knows it was inherited rather than confirmed.

Which decisions to log

Not everything needs an entry. The decisions that tend to be questioned later, and therefore belong in the log, are the ones that shape what families see:

  • Identity decisions: which logo, which colors, which name forms, and who approved them.
  • Assortment decisions: which items are in, which were considered and left out, and why.
  • Structure decisions: one store or several, one window or ongoing, and how the choice was reached when more than one coach or group was involved.
  • Communication decisions: who announces, through which channel, and what wording was agreed.
  • Change decisions: anything altered after the store opened, with the reason.

If a decision was made jointly by several coaches or a board, record the agreed outcome and the forum where it was agreed, not the individual positions.

Who writes it and where it lives

One person owns the log, usually the organizer, and a named backup can add to it. It lives in a place the organization controls, such as a shared folder the school or club administers, so that it does not disappear when a volunteer steps back. A single document is easier to keep current than a set of scattered notes, and a dated list is easier to read than a free-form narrative.

Keep the log separate from order information and from any list of families. The log explains the store; it is not a record of who bought what.

Keep personal information out of it

The log should describe decisions, not people. Do not record student names, family contact details, sizes tied to individuals, or any detail that identifies a child. If a decision was prompted by a family's question, record the question in general terms: "a parent asked whether a larger youth size would be added" rather than who asked. This keeps the log safe to hand on and safe to share with the responsible organization without further review.

Use the log during the season

The log earns its keep when questions arrive. An organizer who can point to a dated entry with its basis answers consistently and quickly, and can explain what would need to happen for the answer to change. It also supports approvals: when someone asks whether a change was authorized, the entry says who approved it and when.

Use the log at close-out and handoff

At the end of the season, read the log once from top to bottom. Mark the entries that should carry forward, add a short note where a decision turned out to need revisiting, and confirm that no personal information crept in. The log then becomes the center of the close-out note, and the next organizer inherits reasons rather than only results.

Frequently asked questions

How detailed should each entry be?

One to three sentences. If an entry needs more, attach or link the supporting record, such as the artwork permission, rather than copying it in.

What if a decision was never formally made?

Write it down as inherited practice with the date you noticed it, and note who should confirm it. That turns an assumption into something the organization can decide.

Can the log be shared with families?

It is an internal record. Share the decisions through the usual announcements, and keep the log itself with the organization.

Who should be able to edit it?

The organizer and a named backup. Others can suggest entries, but one owner keeps the format consistent.

Before the season's first decision

  • The log exists in a place the organization controls, with a named owner and backup.
  • The entry format is agreed: date, decision, role, basis, and what would change it.
  • The list of decision types to log is written at the top.
  • A note at the top says that no student or family personal information belongs in the log.
  • Close-out is planned as a read-through of the log, with carry-forward entries marked.