Recurring Task Checklist Template for Client Work

A recurring task checklist is a reusable set of steps for work you perform on a schedule. For client work, give each cycle its own record, define what counts as done, and turn any unresolved issue into a separate action with an owner and a date.

This works for weekly account reviews, monthly reporting, routine content checks, and ongoing client administration.

The checklist repeats. The outcome belongs to that particular day or period.

Below is a free template, a worked example, and a practical way to manage the routine in SelfManager.ai.

Free recurring task checklist template

Copy this setup into a document, spreadsheet, or task manager.

Routine: [Name]
Client / project: [Name]
Frequency: [Weekly, monthly, or another agreed schedule]
Responsible person: [Name]
Period covered: [Dates]
Inputs needed: [Files, access, figures, or approval]
Definition of a completed cycle: [Expected result]
Procedure last updated: [Date]

Suggested step statuses: Not started, In progress, Done, Blocked, Not applicable.

Use “Not applicable” with a reason. It should mean the step did not apply, rather than that it was skipped without checking.

Copy-paste cycle summary

Period covered: [Dates]

Work completed: [Short summary]

Exceptions found: [Issues or none]

Inputs still missing: [Details or none]

Follow-up actions: [Action, owner, date]

Client update: [Sent / not required / awaiting review]

Next cycle: [Date]

Keep the reusable instructions separate from this cycle’s results.

Worked example: a weekly website review

This fictional example is for a freelancer who has agreed to perform a weekly website review for a client.

It is a workflow example, not a complete technical maintenance procedure. Adapt the actual checks to the platform, contract, and access available.

Routine: Weekly website review
Client: Harbor Studio
Frequency: Friday
Responsible person: Alex
Period covered: October 12–16, 2026
Completed cycle: Agreed checks performed, findings recorded, and required follow-ups created

The enquiry-flow check remains blocked even though the summary has been sent.

That is a useful record. Marking every row complete would hide the unresolved verification.

The next weekly review should check the follow-up, but the follow-up also needs attention on its own scheduled date.

Choose what should actually repeat

A recurring checklist works best for a stable process.

Good candidates include:

• Reviewing open client requests each week.
• Preparing an agreed monthly activity report.
• Checking a defined set of published content.
• Reviewing tracked work before invoicing.
• Verifying that recurring deliverables have been sent.

Be careful with work that happens only when a condition is met.

“Publish the client’s new article” should not become a weekly promise if the client supplies articles irregularly. A recurring task to check for approved content may be more accurate.

Separate the repeatable check from the work it may uncover.

Match the checklist to one schedule

Put steps together when they share a useful frequency and purpose.

A weekly client review might include checking open questions and preparing a short update. A monthly reporting cycle may require different figures, comparisons, and approval.

Keep them separate if combining them creates steps you repeatedly mark “not applicable.”

Also define the period being reviewed.

A Friday review might cover Monday through Friday. A monthly report might cover the previous calendar month. The day you perform the task and the period it describes are different things.

Define done before repeating the task

Vague instructions become more expensive when they repeat.

“Check analytics” could mean anything from opening a dashboard to preparing a client recommendation.

A clearer instruction is:

Review the agreed indicators for the previous calendar month, record material changes, and identify questions that need investigation.

Likewise:

• “Review requests” becomes “Check each open request and record the next action.”
• “Prepare report” becomes “Draft the agreed sections using the confirmed reporting period.”
• “Check invoices” becomes “Compare the invoice draft with the agreed scope and recorded work.”

The definition of done should match the service you actually provide.

Keep each cycle’s history

Avoid using one checklist that you repeatedly clear and overwrite.

A separate dated record helps you answer:

• Was the check performed?
• What did it find?
• What remained unresolved?
• What did the client receive?
• Did the same issue appear again?

Keep the stable procedure as the template. Record findings in that cycle’s notes, comments, or results fields.

This also prevents stale context from being mistaken for a current result. Last month’s “all figures confirmed” should not appear as evidence for this month’s report.

Use repeating tables in SelfManager

SelfManager repeats whole tables, rather than individual tasks inside a non-repeating table.

For a recurring checklist:

1. Create a table containing the stable steps.
2. Put reusable instructions in the notes.
3. Set Repeat to the appropriate schedule.
4. Check the preview of upcoming dates.
5. Record results on each day’s instance.

Supported schedules include daily, selected weekdays, every few days, and a date each month. Each occurrence gets unchecked tasks and the template notes when you first open that day.

You can manage routines under All › Repeats.

Deadlines and reminders are not copied to repeated days. Comments and images remain with the date where they were added.

For one recurring action, use a small table containing that task.

Start with one client routine in SelfManager. Repeat the stable checklist, then keep each cycle’s findings in its own comments or notes.

Handle missed and blocked work explicitly

A fresh checklist does not resolve the previous cycle.

If Friday’s review is incomplete when the next Friday arrives, decide what happens to the unfinished work.

Complete the earlier cycle

Use this when the original period still needs its own result, such as an outstanding monthly report.

Keep the period clear even if the work happens late.

Carry forward a specific action

Use this when an issue needs attention independently of the routine.

For example:

Confirm enquiry test receipt with client on Monday.

Keep the reference to the original finding so the context stays available.

Record why the cycle was skipped or cancelled

Use this when there is no longer useful work to perform.

For example:

Review cancelled because the site was decommissioned. No further cycles required.

Do not mark skipped work as completed.

Track exceptions separately from the routine

A recurring review can identify work that is outside its own scope.

Finding a broken form and fixing it are different actions. Finding a request for a new feature does not automatically authorize implementation.

For each exception, record:

• What happened.
• Its effect on the client or project.
• Whether action is within scope.
• Who needs to decide or act.
• The next review or working date.

This keeps the routine manageable while making the resulting work visible.

If the same exception returns, investigate the cause or revise the procedure.

Use AI to improve a checklist

AI can help draft a routine from your process or review the records you have kept.

For example:

Turn the process below into a recurring checklist.

Separate stable instructions from results that need to be recorded each cycle.

For every step, suggest a clear definition of done.

Identify missing inputs and approval points.

Keep optional recommendations separate from agreed work.

Process: [Paste your notes]

For a review:

Review these recurring client-work records.

Identify repeated blockers, missing outcomes, and follow-up actions with no clear date.

Use only the recorded information. Do not assume that an unchecked task was completed.

Suggest one practical change to the checklist.

SelfManager’s AI can work with tasks and selected supporting context, including comments. Verify suggestions against your agreement and the source records.

If you only need a simple reusable checklist, a document may be enough. SelfManager becomes more useful when the routine belongs alongside daily client work and you want a dated history to review.

Review the routine when the work changes

A checklist should reflect the service you provide now.

Revisit it when:

• The client changes the agreed scope.
• A new platform changes the procedure.
• A step repeatedly produces no useful result.
• A recurring issue needs a stronger check.
• Reporting or approval requirements change.

Keep the earlier records as they were. Update the reusable procedure for future work.

Use SelfManager to keep the routine on the right days, preserve each cycle’s outcome, and turn exceptions into clear next actions.

Frequently asked questions

What is a recurring task checklist?

It is a reusable set of steps performed on a schedule. Each cycle should have a record showing what was completed, what was found, and what still needs action.

What client work should use a recurring checklist?

Use one for repeatable services such as weekly reviews, monthly reporting, routine content checks, and recurring administration. Match the steps to your agreed scope and the inputs available.

Should every client have the same checklist?

A shared base template can help, but adapt it to each client’s scope, platform, schedule, and approval requirements. Remove irrelevant steps and add the checks the service actually requires.

What should happen when a recurring task is missed?

Keep the missed cycle visible. Decide whether to complete it late, carry forward a specific action, or record why it was cancelled. A new cycle should not erase the previous outcome.

Does SelfManager repeat individual tasks?

SelfManager’s recurring feature repeats whole tables. To repeat one task, place it in its own small table and set that table to repeat. Each occurrence has its own unchecked task.