Quick answer
- Create a database with properties for task name, frequency, due date, status, owner, and task type
- Add formula and rollup properties to calculate next due dates automatically
- Build filtered views for daily, weekly, and monthly tasks
- Create linked SOP documentation with step-by-step instructions
- Set up templates for common task types to speed up entry
Recurring tasks slip through the cracks when they live in your head or scattered across email reminders. You forget to invoice clients on time, skip weekly backups, or miss monthly compliance checks until they become urgent.
A Notion recurring tasks template solves this by putting every repeated task—from daily admin to quarterly reviews—in one database with automatic due dates, clear ownership, and linked SOPs. You’ll see what’s due today, who owns what, and exactly how to do it.
Why Use Notion for Recurring Tasks and SOPs
Notion combines task tracking with documentation in one place. Unlike standalone task managers, you can link each recurring task to its full standard operating procedure, making it easy for anyone on your team to pick up a task without asking for instructions.

The database structure lets you filter tasks by frequency (daily, weekly, monthly), owner, or category. You can create custom views that show only what’s due this week, or build a master checklist for month-end close procedures.
For teams already using Notion, this keeps everything centralised. If you’re tracking project work in a Kanban board or running sprint boards, your recurring admin tasks can live alongside them without switching tools.
What to Include in Your Recurring Tasks Database
Before you build, decide what information each task needs. A good recurring tasks database tracks the task itself, when it repeats, who’s responsible, and where to find the detailed instructions.
Start with these core properties:
- Task Name (title) – Keep it action-oriented: “Send monthly invoices” not just “Invoicing”
- Status (select) – Not Started, In Progress, Complete, Blocked
- Owner (person) – Who’s responsible for this task
- Frequency (select) – Daily, Weekly, Biweekly, Monthly, Quarterly, Yearly
- Due Date (date) – When the next instance is due
- Last Completed (date) – Track when it was last done
- Category (select) – Admin, Finance, Marketing, Operations, HR, etc.
- Priority (select) – High, Medium, Low
- SOP Link (relation or URL) – Link to the full procedure documentation
You can add more later, but these nine properties give you enough structure to track and organise recurring work without overcomplicating the system.
Step 1: Create Your Recurring Tasks Database
Open Notion and create a new page. Give it a clear name like “Recurring Tasks & SOPs” or “Operations Checklist”.

Type /database and select “Table – Inline”. This creates a database directly on the page. If you want to reference this database from multiple pages, use a full-page database instead.
Add the core properties listed above. Click the + icon in the table header to add each property. Choose the correct property type—select for Status and Frequency, person for Owner, date for Due Date and Last Completed.
For the SOP Link property, you have two options. Use a URL property if your SOPs are external documents or web pages. Use a relation property if you’re building SOP pages inside Notion (we’ll cover this in step 4).
Step 2: Add Formula Properties for Next Due Date
Manually updating due dates after each completion is tedious and error-prone. A formula property can calculate the next due date automatically based on when you last completed the task and its frequency.
Create a new property and choose “Formula”. Name it “Next Due Date”.
Use this formula to calculate next due dates:
if(empty(prop("Last Completed")), prop("Due Date"),
if(prop("Frequency") == "Daily", dateAdd(prop("Last Completed"), 1, "days"),
if(prop("Frequency") == "Weekly", dateAdd(prop("Last Completed"), 1, "weeks"),
if(prop("Frequency") == "Biweekly", dateAdd(prop("Last Completed"), 2, "weeks"),
if(prop("Frequency") == "Monthly", dateAdd(prop("Last Completed"), 1, "months"),
if(prop("Frequency") == "Quarterly", dateAdd(prop("Last Completed"), 3, "months"),
if(prop("Frequency") == "Yearly", dateAdd(prop("Last Completed"), 1, "years"),
prop("Due Date"))))))))
This formula checks if you’ve completed the task. If Last Completed is empty, it shows the original Due Date. Once you mark it complete and add a Last Completed date, it automatically calculates the next occurrence based on frequency.
Add a “Days Until Due” formula to see urgency at a glance. Create another formula property with this code:
dateBetween(prop("Next Due Date"), now(), "days")
Negative numbers mean overdue, positive numbers show days remaining. This makes it easy to spot what needs immediate attention.
Step 3: Build Filtered Views for Different Frequencies
One long list of every recurring task quickly becomes overwhelming. Create separate views that filter tasks by frequency or due date, so you only see what’s relevant right now.
Click “Add a view” at the top of your database. Choose Table, Board, or Calendar view depending on how you prefer to see tasks.
Create a “This Week” view. Add a filter: Next Due Date is within the next 7 days. Sort by Next Due Date ascending. This shows only what’s coming up soon.
Build frequency-specific views:
- Daily Tasks – Filter: Frequency is Daily
- Weekly Tasks – Filter: Frequency is Weekly
- Monthly Tasks – Filter: Frequency is Monthly
- Overdue – Filter: Days Until Due is less than 0 and Status is not Complete
Add a Board view grouped by Owner if you’re managing tasks across a team. Each person sees their own column of recurring responsibilities, similar to how you’d organise a Kanban board.
For calendar lovers, create a Calendar view with Next Due Date as the date property. This gives you a visual month-at-a-glance of when everything comes due.
Step 4: Link Tasks to SOP Documentation
The real power of tracking recurring tasks in Notion is linking each task to its full procedure. When someone new picks up “Monthly financial close,” they shouldn’t need to hunt for instructions—the SOP should be one click away.
Create a separate database for SOPs. Make a new page called “Standard Operating Procedures” and add a full-page database. Give it properties for SOP Name (title), Category, Owner, Last Updated, and Status (Draft, Active, Needs Review).
Write each SOP as a page inside this database. Open a new entry and document the step-by-step process. Use headings, numbered lists, and screenshots. The more detail, the better—assume the reader has never done this before.
Link the two databases together. Go back to your Recurring Tasks database. Add a new property, choose “Relation,” and select your SOPs database. Name it “Related SOP”.
Now you can link each task to its procedure. When someone opens “Send quarterly tax estimates,” the related SOP appears in the task properties. Click through to see the full instructions.
This structure mirrors how you might organise documentation in a Notion wiki for remote teams, where knowledge lives in linked databases rather than scattered documents.
Step 5: Create Task Templates for Faster Entry
If you’re adding many similar tasks, templates speed things up and keep data consistent. Notion’s database templates pre-fill property values so you don’t type the same information repeatedly.
Click the dropdown arrow next to “New” in your database. Select “+ New template”.
Create templates for common task patterns. For example, a “Monthly Finance Task” template might pre-set:
- Frequency: Monthly
- Category: Finance
- Owner: [your finance person]
- Priority: High
Make templates for Daily Operations Tasks, Weekly Marketing Tasks, or Quarterly Review Tasks. When you need to add a new recurring task, pick the relevant template instead of starting from scratch.
Use templates to include checklist content too. Inside each template, add a bulleted or numbered list of sub-tasks. For a “Weekly Team Meeting” template, you might include “Prepare agenda,” “Send calendar invite,” “Record notes,” and “Share action items.”
If you’re already using meeting agenda templates in Notion, this approach will feel familiar—templates ensure consistency across repeated activities.
Step 6: Set Up Reminder and Completion Workflows
Notion doesn’t send email reminders for upcoming tasks automatically, but you can create manual workflows that make it easy to see what needs attention and mark tasks complete.
Use the “Overdue” and “This Week” views as your daily dashboard. Add these views to your Notion homepage or pin them in your sidebar. Check them each morning to see what’s due.
Create a “Mark Complete” workflow. When you finish a task, update these two properties:
- Set Status to Complete
- Fill in Last Completed with today’s date
The Next Due Date formula automatically updates to show when you need to do it again. Then change Status back to Not Started so the task reappears in your active views.
Consider using Notion’s reminders feature for critical tasks. Open a task page and type @remind to add a one-time reminder. Notion will send you a notification on that date. This works best for high-stakes tasks like “Submit quarterly taxes” or “Renew business license.”
For more complex workflows with external notifications, you might integrate Notion with Zapier or Make. But for most small businesses and freelancers, checking a dedicated view each morning is simple and reliable.
Advanced: Add Rollups for Team Capacity
If you’re managing recurring tasks across a team, rollup properties help you see workload at a glance. You can count how many tasks each person owns or identify bottlenecks.
Create a People database if you don’t have one already. Add team members as entries.
Add a relation from People to your Recurring Tasks database. Name it “Assigned Tasks”.
Add a rollup property in the People database. Set it to count the number of related tasks. Now you see how many recurring responsibilities each person has.
Add another rollup to count overdue tasks per person. Use “Show original” and apply a filter: Days Until Due is less than 0. This highlights who’s falling behind and might need help.
This capacity view works well alongside other Notion project tools. If you’re also running sprint planning in Notion, you can balance recurring operational work against new project tasks.
Ready-made Notion template
Scrum Board PRO
A complete agile project-management system in Notion: sprint board, backlog with MoSCoW priorities, bug tracker, sprint planner with burndown, meeting notes and reports. Set up in 10 minutes, no monthly subscription.
Example: Monthly Finance Tasks Setup
Here’s a practical example of how to structure a set of monthly finance recurring tasks using this system.
Create these tasks in your database:
- Reconcile bank accounts – Monthly, due 5th of each month, owner: Finance Manager, linked to “Bank Reconciliation SOP”
- Send client invoices – Monthly, due 1st of each month, owner: Finance Manager, linked to “Invoicing Process SOP”
- Process expense reports – Monthly, due 10th of each month, owner: Finance Manager, linked to “Expense Reimbursement SOP”
- Review cash flow – Monthly, due 15th of each month, owner: CEO, linked to “Cash Flow Review SOP”
- Pay contractor invoices – Monthly, due 20th of each month, owner: Finance Manager, linked to “Contractor Payment SOP”
Write detailed SOPs for each task. The “Send client invoices” SOP might include steps like: review time tracking records, generate invoices in accounting software, attach project summaries, email invoices with payment terms, and update status in CRM.
If you’re also tracking income and expenses in Notion, you might link this to a finance tracker template for complete visibility.
Add sub-tasks or checklist items inside each SOP page. When the Finance Manager opens “Bank Reconciliation SOP,” they see a numbered list: download bank statement, match transactions, flag discrepancies, document variances, get approval from CEO.
When to Use a Pre-Built Template
Building a recurring tasks database from scratch takes time, especially if you want advanced formulas, multiple linked databases, and polished views. Sometimes a pre-built solution gets you running faster.
If you’re managing more than just recurring tasks—say you’re running full agile sprints with backlog management, bug tracking, and retrospectives—consider a complete system like Scrum Board PRO. It includes a sprint board, backlog with MoSCoW prioritisation, and meeting notes templates, all set up in 10 minutes without a monthly subscription.
For simpler needs, the database you’ve built in this guide gives you everything you need. You can always expand it later by adding more properties, automations, or integrations as your processes mature.
If you’re deciding whether to build or buy, check out what you actually get with free vs paid Notion templates to weigh the tradeoffs.
Common Mistakes to Avoid
Don’t overcomplicate the database at the start. Begin with core properties and add more only when you feel friction. Too many fields make data entry tedious and people stop using the system.
Don’t skip the SOPs. A task list without instructions only works if everyone already knows how to do the tasks. Linking procedures makes the database useful for onboarding, delegation, and backup coverage.
Don’t forget to actually mark tasks complete. The Next Due Date formula only works if you update Last Completed. Build this into your routine—Friday afternoon or Monday morning are good times to review the week and mark what you finished.
Don’t create too many views. Three to five views are usually enough. If you have 15 views, no one knows which one to use. Stick to This Week, Overdue, and one view per major frequency or category.
How to Maintain Your Recurring Tasks System
A recurring tasks database only stays useful if you keep it current. Old tasks clutter the views, incomplete SOPs confuse people, and outdated frequencies mean things fall through the cracks.
Schedule a monthly review of the database itself. Add a recurring task called “Review recurring tasks database” that happens the first Monday of each month. During this review:
- Archive tasks that are no longer needed
- Update frequencies if they’ve changed
- Check that SOPs are still accurate
- Add new recurring tasks you’ve been doing manually
Assign clear ownership. Every task should have an owner, even if that person delegates the actual work. The owner is responsible for ensuring it gets done and updating the database.
Use the system as your single source of truth. If recurring tasks also live in email reminders, your calendar, and sticky notes, the Notion database becomes just another place to check. Consolidate everything here and trust it.
If you’re managing a remote team, this becomes even more critical. A centralised system in Notion for remote teams keeps everyone aligned without constant meetings.
Combining Recurring Tasks with Other Notion Systems
Your recurring tasks database doesn’t exist in isolation. It connects to projects, goals, and daily work. Here’s how to integrate it with other Notion systems you might be using.
Link recurring tasks to goals. If you’re tracking quarterly goals in Notion, add a relation from recurring tasks to your goals database. This shows which operational tasks support which strategic objectives.
Reference recurring tasks from project pages. When you’re planning a project, check your recurring tasks database to see what operational work might conflict with project deadlines. If your designer has 15 hours of recurring weekly tasks, don’t assume they have 40 hours for project work.
Include recurring tasks in your daily standups. If you’re running daily standups in Notion, create a template that pulls in today’s recurring tasks alongside project work. This ensures routine responsibilities don’t get forgotten during busy project phases.
Add recurring tasks to your client onboarding. If you have a client onboarding checklist in Notion, link it to recurring tasks like “Send monthly status report” or “Schedule quarterly review call” so these get added automatically when you onboard a new client.
Using Notion AI to Draft SOPs Faster
Writing SOPs from scratch is time-consuming. If you have Notion AI, you can speed up the drafting process and fill in gaps faster.
Start with a rough outline of the process. Type out the major steps in bullet points. Then select the text, open Notion AI, and ask it to “Expand this into a detailed step-by-step procedure.”
Use AI to identify missing steps. After you’ve drafted an SOP, ask Notion AI to “Review this procedure and suggest any missing steps or edge cases.” It might catch things like “What happens if the payment fails?” or “Who to notify if there’s an error.”
Generate checklists from prose. If someone wrote up how they do a task in paragraph form, paste it into a Notion page. Use AI to “Convert this description into a numbered checklist.” This gives you a cleaner format for your SOP.
This approach works well if you’re already using AI for other Notion workflows. For example, if you’re using AI to draft OKRs in Notion, the same tool helps document the recurring tasks that support those objectives.
Just remember that AI-generated SOPs need human review. Check for accuracy, add company-specific details, and test the procedure with someone who hasn’t done it before.
Tracking Changes and Improvements to Procedures
SOPs aren’t static. As your business grows and processes improve, you’ll need to update procedures. Your Notion setup should make it easy to track what changed and when.
Add a “Last Updated” date property to your SOPs database. Update it manually each time you revise a procedure. This helps everyone know if they’re looking at current information.
Add a “Version” text property if you need detailed change tracking. Label versions as 1.0, 1.1, 1.2, etc. In the SOP page itself, maintain a “Change Log” section at the bottom listing what changed in each version.
Create a “Needs Review” status for SOPs. When someone discovers a procedure is outdated or incomplete, they change the status to flag it. The SOP owner then knows to update it.
Schedule quarterly SOP reviews as a recurring task in your system. During these reviews, read through each procedure, test it, and update anything that’s changed. This keeps documentation trustworthy.
Scaling the System as Your Team Grows
A database that works for three people might not work for 30. Here’s how to scale your recurring tasks system as you add team members and complexity.
Add team or department properties. Beyond individual owners, tag tasks with Team (Sales, Marketing, Operations, Finance) so you can filter by department. Create department-specific views that each team uses as their hub.
Introduce approval workflows. Add a “Reviewed By” person property and a “Review Status” select property. Some tasks might require sign-off before they’re considered complete—useful for financial tasks, compliance, or anything that affects customers.
Split recurring tasks by type. Instead of one massive database, consider separate databases for operational tasks, customer tasks, and compliance tasks. Link them together with relations but maintain focus in each area.
Delegate database maintenance. Assign someone to be the “system owner” who ensures the database stays clean, SOPs stay current, and people are using it correctly. This might be an operations manager or chief of staff role.
As you grow, you might also expand into more structured project management. Tools like a product backlog or MoSCoW prioritisation system complement your recurring tasks by managing one-time project work alongside ongoing operations.
Troubleshooting Common Issues
Formula showing wrong dates? Check that your Last Completed field is actually filled in. If it’s empty, the formula falls back to Due Date. Also verify that your Frequency values exactly match the text in the formula (case-sensitive).
Tasks not showing in filtered views? Open the view, click Filter, and review the conditions. A common issue is filtering by Status = Not Started but forgetting to include In Progress. Use “Status is not Complete” instead to capture all active tasks.
Team not updating Last Completed? People forget this step. Add a checklist inside each task template that includes “Update Last Completed date” as the final step. Or create a separate “Completion Log” database where people log each time they complete a task, then use a rollup to pull the latest date.
Too many tasks, feeling overwhelmed? Your database might be revealing that you’re trying to do too much. Review the list and ask: Can this task be eliminated, automated outside Notion, reduced in frequency, or delegated? Sometimes the problem isn’t the system—it’s the workload.
Frequently asked questions
Can Notion automatically reset recurring tasks?
Notion doesn't have built-in recurring task automation, but you can use a formula property to calculate the next due date based on when you last completed a task. After marking a task complete and filling in the Last Completed date, the formula automatically shows when it's due next. You then manually reset the Status to Not Started so it reappears in your active task views.
How do I track recurring tasks for multiple clients in Notion?
Add a Client property (relation or select) to your recurring tasks database. Create filtered views for each client that show only their tasks, or use a Board view grouped by Client so each client has their own column. You can also link your recurring tasks database to a CRM database to see all client-related work in one place.
What's the best way to handle tasks with irregular schedules?
For tasks that don't follow a strict daily/weekly/monthly pattern, add a Frequency option called 'Custom' or 'As Needed'. Don't rely on the automatic formula for these—instead, manually set the Due Date each time. You can also add a Notes property to document the trigger conditions, like 'Run this task when inventory drops below 50 units'.
Should I use a separate database for SOPs or keep them in the same table?
Use a separate database if your SOPs are detailed multi-step procedures that apply to multiple recurring tasks or need their own review cycle and ownership. This keeps your recurring tasks table clean and lets you link one SOP to many tasks. Keep SOPs in the same table only if they're simple one-paragraph instructions unique to each task.
How do I prevent overdue tasks from piling up in Notion?
Create a dedicated Overdue view and check it daily. Add a reminder task in your database called 'Review overdue tasks' that recurs weekly. When tasks pile up, investigate why—it might mean the frequency is wrong, the owner has too much work, or the task is no longer necessary. Archive or adjust tasks that repeatedly go overdue.
Can I use Notion recurring tasks for habit tracking?
Yes, though a recurring tasks database focuses on work responsibilities rather than personal habits. For habit tracking, consider a dedicated system with daily checkboxes and streak counters. If you want to track business habits like 'Review financials' or 'Post on LinkedIn', the recurring tasks database works well, especially if you link habits to business goals.