In FCCS, when defining tasks for repeatable operations across close cycles, which approach is recommended?

• A. when the tasks require consistent definition across close schedules
• B. when the tasks are repeatable over multiple close cycles
• C. when the tasks are often late in completion and they need to be monitored more closely
• D. when the tasks require multiple levels of approvers

Answer: (B)

When close cycles involve the same steps over and over, the best approach is to create a repeatable task definition that can be reused across multiple cycles. This means you set up a single task template that covers the standard sequence, timing, and responsibilities, and then apply it to each close cycle.

Using a repeatable task definition ensures consistency across cycles because every cycle follows the same exact steps, in the same order, with the same owners and deadlines. It also saves time and reduces the chance of omissions, since you don’t recreate tasks from scratch for every cycle. Maintenance becomes easier too—update the task once, and the change propagates to all cycles, helping you stay aligned and auditable across the board.

The other options touch on related concerns but don’t capture the efficiency and reuse gained from a repeatable task approach. Consistent definitions across schedules describe the outcome but not the mechanism; monitoring for late completions or handling multiple approvers are important, yet they don’t address the core benefit of reuse across repeated cycles.