GGyess
Operations teams

Same Monday routine. Another round of reminders?

The check happens every week, along with the messages asking who’s doing it. Set up a recurring task in GGyess with an owner and written steps. Record exceptions on the task as they come up.

Inside GGyessEnlarge screenshot
A recurring task with start and end dates and four frequency choices.
The date settings let you choose a start, an end and how often the work repeats.
Step by step

Set up the next run of a recurring process

  1. Write down the usual steps and what needs checking before someone marks the work done.

  2. Assign the task to one person, set a date and include the checks they should make.

  3. Record exceptions and update the process after the review.

Inside GGyessEnlarge screenshot
Steps on a task, the control for adding another step, and its start date, due date and status.
Steps on a task, the control for adding another step, and its start date, due date and status.
Operations teams

In day-to-day work

Break down a larger task

Put quick checks on the main task. If a piece of work needs its own status, make it a subtask so people can follow its progress.

The stages your team uses

Use project statuses that match the handoff. For example, “In review” tells the team a draft is ready for someone to read.

Someone to turn to

Assign the people responsible for the task. If the plan changes, the team knows who to speak to and which assignments to revisit.

Before you start

A few good questions.

Where should we keep an exception to the usual process?

Record what happened and how it was handled on the task for that occasion. If the team adopts the change, update the written procedure too.

When should I use a recurring task instead of a reminder?

Use a recurring task when someone must complete work and report its status. A reminder suits a prompt to check or follow up.

GGyess WorkSuite

Give the next cycle a date and an owner.

Start on the free plan. Invite your team when you’re ready.

GGyess screenshot