Weekly Nudges
Weekly nudges remind the account owner when an enabled project has gone at least seven days without an update. They are owner reminders, not client messages. A nudge contains a link back to the update form for each due project.
When weekly nudges become due
Nudges are enabled by default when a project is created. The service measures age from the latest posted update. If a project has no updates, it measures from the project's creation time instead.
A project becomes eligible when at least seven days have passed. The rule uses elapsed time rather than a named day of the week. A project created on Tuesday can become due the following Tuesday, and a project updated on Saturday can become due the following Saturday.
Weekly nudges are not tied to a named weekday. The delivery process checks eligible projects on its operating schedule, so the message may arrive after the exact seven day point. Use your calendar if you need a reminder at a fixed local time or on a fixed weekday.
Posting an update resets the age used for future nudges. The next eligibility point is at least seven days after that post. A project does not become due because a client added a reply, because the latest owner update remains the relevant date.
How nudge emails are grouped
The service groups all eligible projects for one owner into one email. A single project email names that project and says how many days have passed. An email for several projects gives the count in its subject and lists each due project in the body with a direct link to its update form.
The queue handles one owner per processing tick. You receive at most one owner reminder per day, and each included project has a weekly cap based on its last successful nudge. A different project can become due on a later day without waiting for the first project's week to end. These controls prevent a due project from producing a message on every processing run.
The exact arrival time can vary because owners are processed in turn and mail can fail temporarily. Treat the nudge as a backup prompt rather than a time guarantee.
Turn nudges off or on
Open the project and find Email me a weekly nudge when this project needs an update. Clear the checkbox to opt out for that project, or select it to enable reminders again.
With JavaScript available, changing the checkbox submits the setting automatically. The page reloads and restores focus to the checkbox when browser session storage is available. The setting still saves if browser storage is blocked.
Without JavaScript, changing a checkbox does not submit by itself. Select the Save button shown beside the setting. Check the final checkbox state after the page reloads.
The setting belongs to one project. Turning off one project does not turn off reminders for other projects in the same account. Review each project if you want to stop all project nudges.
What happens to a queued nudge
The service checks the selected projects again before delivery. If you disable the nudge or post a new update after the reminder was queued, the project is removed from that reminder before it is sent. If no queued projects remain due, the message is cancelled.
Several due projects can change between queueing and delivery. The sent email contains only the queued projects that are still enabled, still at least seven days old, and still within their reminder timing limits at the final check.
This final check reduces stale reminders, but mail delivery still has timing boundaries. A post made after the mail server accepts a reminder cannot recall the message. You can ignore that reminder because the new update has already reset the project age.
Delivery failures and retry limits
Nudge delivery uses the same outbound email system as updates and reply notifications. A failed nudge is not retried repeatedly during the same week. Its retry timing keeps the weekly reminder cap, including cases where the mail server result was uncertain.
The owner project page does not show a nudge delivery status beside updates. If you expected a reminder and did not receive one, check these conditions:
- Confirm that the project's nudge checkbox is selected.
- Confirm that at least seven full days have passed since the latest update or project creation.
- Check spam, junk, quarantine, and mail rules for the configured service sender.
- Confirm that you are checking the account owner's inbox, not the client's inbox.
- Open the project directly and post the update without waiting for email.
If the conditions are met and reminders remain absent, use the Support link in the site footer.
Use nudges as a practical prompt
A nudge means the project record is old. It does not decide whether the project is late, healthy, active, or complete. There is no project done or archive control, so disable nudges on a project that no longer needs regular updates.
The product also has no fixed schedule builder, per project reminder day, time zone setting, or custom reminder interval. Use another calendar or task tool for those needs. You can still keep the resulting client communication in the project history.
Use weekly nudges as backup reminders, and use your calendar when an update must happen at a fixed time. Read Managing Projects for project lifecycle limits and Email Delivery for outbound mail behavior. The Friday afternoon update habit offers a writing routine, but nudges themselves are not tied to any particular weekday.