Alternating-week planning: how to organize A/B weeks

Some teams' work does not fit into a single week: rotating shifts, part-time schedules, clients that alternate or two-week sprints. In all those cases the same need appears: planning A and B weeks, also called odd and even weeks.

Syncro does not have a "every two weeks" recurrence rule. What it does have is a weekly planner and time tracking that let you apply the alternation explicitly and review it. This guide explains how to do it without pretending the product does something it does not.

What alternating-week planning is

A/B planning splits work into two repeating cycles:

• Week A (even): the tasks that belong to this week.
• Week B (odd): the ones that belong to the next.

It is not the same as a two-week sprint. A sprint has a goal and a closing date; A/B describes when each block of work happens. They can be combined: a two-week sprint with the first week in A mode and the second in B mode.

When it makes sense

If your team works the same every week, you do not need A/B: an ordered backlog and a weekly review are enough.

The limitation to accept

Syncro does not create recurring tasks every two weeks. If you need a task to appear automatically in the even week, you will have to plan it by hand or keep a template outside the product.

This is not an accidental defect: the planner stores concrete time blocks, not calendar rules. Accepting it from the start avoids false expectations and lets you design a flow that actually works.

How to set it up in Syncro

1. Mark A and B tasks

Before planning, make the alternation visible. You have two options:

• Labels: create a Week A label and a Week B label in the project. They are visible on the card and can be filtered on the board and in the backlog.
• Title prefix: start the title with [A] or [B]. It is simpler, but it clutters the task name.

For small teams, the prefix is enough. For projects with many labels, labels avoid confusion and let you filter without searching text.

2. Decide what is fixed and what alternates

Not every task needs alternation. Separate:

• Weekly fixed: meetings, review, support.
• A/B alternating: the work that changes week.
• No cycle: one-off tasks planned when needed.

If you turn everything into A/B, the label loses value. Alternation should reduce mental load, not add another classification.

3. Plan the specific week, not the whole cycle

The weekly planner works with the visible week. Every Friday or Monday:

1. Open the calendar's weekly view.
2. Filter by the Week A or Week B label, as appropriate.
3. Drag tasks to the days you will work on them.
4. Adjust the load: if the week is already full, move tasks to the backlog before adding more.

Planning the whole cycle at once usually produces a plan that does not survive the first surprise. Planning the specific week keeps the decision close to reality.

4. Review on Friday and prepare the switch

Alternation fails when Monday starts without knowing which week it is. Spend five minutes on Friday:

• Close what was completed.
• Move what did not fit back to the backlog.
• Check which label belongs to the next week.
• Leave the two or three main tasks planned.

That small ritual avoids the chaotic Monday and makes alternation a decision, not a surprise.

5. Compare planned with dedicated hours

At the end of the week, look at estimated and dedicated hours in Reports. If a Week A task has appeared for three weeks and never gets done, the problem is not the alternation: the plan does not fit. The time tracking guide explains how to log hours without mixing planned and actual time.

A concrete example

A two-person team serves two clients and alternates focus:

• Week A: North client. Tasks labelled Week A.
• Week B: South client. Tasks labelled Week B.

On the previous Friday, each person filters by the next week's label and reserves blocks in the planner. On Monday there is no meeting to decide the focus: it is already decided. Urgent requests from the other client go into the backlog and are reviewed in their week, unless they are genuinely urgent.

Common mistakes

• Duplicating tasks for A and B. You create two almost identical tasks that drift apart. Better one task with a label or prefix.
• Not closing the week. If Friday is not reviewed, alternation becomes a rule nobody remembers.
• Planning the whole cycle in January. The two-week plan breaks with the first change; plan the week and review.
• Confusing alternation with priority. A task belonging to week B is not less important; it only says when you work on it.

Frequently asked questions

Can Syncro repeat a task automatically every two weeks? No. The planner stores concrete blocks, not recurrence rules. Alternation is applied by planning each week.

Is a label or a title prefix better? For a few tasks, the prefix is fast. For large projects, the label lets you filter and keeps the title clean.

Does this replace a two-week sprint? No. The sprint defines a goal and a close; A/B defines which week each block runs in. They can be used together.

What about urgent work in the other week? Handle it if it is genuinely urgent and note it in the backlog for review in its week. If you handle everything, alternation stops existing.

---

Takeaway: A/B alternation does not need a magic feature; it needs a label, a weekly view and five minutes of review on Friday.