Handing Off a Team Store: What the Next Coordinator Needs

The person who runs a team store is usually a volunteer, and volunteers rotate. A child graduates, a term ends, an officer steps down, and a program that ran smoothly for two years suddenly cannot find the artwork, the login, or the reason a decision was made.

The short answer: write down five things while you still remember them — where the accounts and access live, who approves what, where the current approved artwork is, what the calendar actually looks like, and which decisions were made deliberately and why. Hand those over through the organization rather than person to person, and do it before the last week.

Handoffs fail on undocumented decisions, not on tasks

Tasks are usually visible: someone opened the store, someone posted the announcement. What disappears is the reasoning — why the store closes on that date, why one item was dropped, why a mark is used one way and not another, which supplier question was already asked and answered.

Without that, the next coordinator either repeats work that was already done or unknowingly reverses a decision that mattered. Both are avoidable with an hour of writing.

What the document has to contain

Keep it short enough that someone will actually read it, and specific enough to be usable.

1. Access and accounts. Which systems the program uses, which organization-owned account each one sits under, and who administers it. Route every transfer through the organization's own process. Do not share passwords, do not move an account into a personal email address, and do not leave the store attached to a departing volunteer's login.

2. Approvals. Who approves identity and artwork, who approves the assortment, who approves messages to families, and who makes the final call. Names change; roles are what to write down, with the current holder noted separately.

3. Artwork and identity. Where the current approved artwork lives, which version is current, what was superseded, and which marks are authorized for which uses. Note the file that was actually used to produce items, not just the one that looks right on screen.

4. Calendar. The dates the program actually runs to — registration, season start, events, ordering periods, recognition moments — with a note of which are fixed by the organization and which were chosen. Planning a year-round store covers keeping that shape stable across seasons rather than rebuilding it annually.

5. Contacts. Who to ask at the organization, who to ask at the provider, and how support requests are routed. Record the route, not a personal phone number.

6. Decisions and their reasons. The short list of things that were settled on purpose: what was tried and did not work, what a policy prohibits, what an approver has already refused, and which questions are still open.

Handle information carefully

A handover is a moment when personal information moves, which is exactly when it is most likely to move somewhere it should not.

Do not copy purchaser lists, contact details, or size collections into a personal document to make the transition easier. Leave that information in the authorized system, transfer access through the organization, and confirm what the organization's rules require about retention and deletion. The next coordinator needs the route to the data, not a copy of it.

Close the current cycle before you hand over

An unfinished cycle is the hardest thing to inherit. Where possible, finish or clearly mark the state of:

• Any open ordering period, and what happens at its close.
• Outstanding questions from families, with where each one stands.
• Anything promised to anyone, and by whom.
• Pending approvals, and who is waiting on what.
• Any item withdrawn, corrected or under review.

Running a team store order window covers what a clean close looks like. Handing over mid-window is survivable; handing over mid-window without saying so is not.

Shadow one cycle if you can

The strongest handover is one where the incoming coordinator watches a full cycle before running one: the planning, the approval, the opening, the questions, the close. It is far more effective than any document, and it turns the document into a reference rather than a manual.

Where a full cycle is not possible, walking through a completed one — start to finish, with the document open — is a workable substitute.

Keep it a role, not a person

Programs get into trouble when a store becomes "the thing that person does". Write the role down: what it covers, what it does not, what authority it carries, and what it must escalate.

Managing a team store across multiple coaches and teams covers the same principle when several people are involved at once. A single named owner with limited, documented responsibilities is easier to replace than an undefined helper who quietly did everything.

Handover checklist

• Access sits on organization-owned accounts and is transferred through the organization.
• No credentials are shared, and nothing is moved to a personal account.
• Approval roles are written down with the current holders noted.
• Current approved artwork is identified, with superseded versions marked.
• The calendar is recorded, distinguishing fixed dates from chosen ones.
• Contacts are recorded as routes, not personal numbers.
• Deliberate decisions and their reasons are listed.
• Open questions and promises are listed with their current state.
• Personal information stays in the authorized system.
• The document is stored where the organization can find it next time.

Frequently asked questions

When should handover planning start?

Before the last week, and ideally at the point the departure is known. The useful material is written while the current cycle is still fresh, not during the rush to leave.

Can we just pass on the login?

No. Access should sit on organization-owned accounts and be transferred through the organization's process. Sharing credentials creates a security problem and leaves the program dependent on someone who has gone.

What if the previous coordinator has already left?

Rebuild from the organization's own records: approvals, minutes, published messages, and the provider relationship. Then write the document that was missing, so the next transition is not another reconstruction.

How long should the handover document be?

Short enough to be read in one sitting. A few pages covering access, approvals, artwork, calendar, contacts and decisions is more useful than a manual nobody opens.

Write it before you need it

Every program eventually hands its store to someone new. The difference between a smooth transition and a lost year is an hour of writing done while the reasons are still remembered — access, approvals, artwork, calendar, contacts and decisions, stored where the organization can find them. Treat it as part of running the store, not as an exit task.