Hey everyone, it's Tara! Do you find it complicated to understand and implement high-level and low-level structures on monday.com? If so, check out my course "Mastering High-Level Low-Level Boards in monday.com" on Udemy. In less than an hour, you will: • Understand how a high and low-level structure can help you better manage projects • Learn how to set up this structure • Identify ways to automate a high-level low-level structure to maximize efficiency • See some concrete examples of how this structure can be used in different organizations + Get some FREE monday.com templates! ⭐ Enroll Now: www.udemy.com/course/mastering-high-level-low-level-boards-in-monday-com/
Great video! Would be awesome if you could do a more in depth one specifically addressing the issues of recurring tasks where client lists is changing or documentation may change. That's the biggest struggle I have at the moment. Do I make one master task and a subtask for each client? Do I create one individual task for each client? What if task documentation needs to be updated, how is that reflected for all clients receiving that task? Anyways, that's just some of my struggles at the moment. Thank you!
Thanks for sharing! If you do the second option of having a separate recurring task board, then you can just update the tasks there easily as they change. Did you test that out? I would use that option and then make everything a separate task for clients. Do 1 client can have 20 tasks. Can you give me more information about what you mean about task documentation?
When you follow the second method - how does the year impact the recurring feature? Is the automation looking at month/day only or does it take year into consideration?
Hi! You can actually set the time period of the automation to be whatever you want. So you could say, after the date arrives, push the due date to the next day, week, month, quarter or year. So the year itself does not affect anything. Does that make sense?
![[UA] NAVI проти G2 Esports | Blast Premier Fall Final](http://i.ytimg.com/vi/QWlIm4FGESQ/mqdefault.jpg)
Hey everyone, it's Tara! Do you find it complicated to understand and implement high-level and low-level structures on monday.com? If so, check out my course "Mastering High-Level Low-Level Boards in monday.com" on Udemy.
In less than an hour, you will:
• Understand how a high and low-level structure can help you better manage projects
• Learn how to set up this structure
• Identify ways to automate a high-level low-level structure to maximize efficiency
• See some concrete examples of how this structure can be used in different organizations
+ Get some FREE monday.com templates!
⭐ Enroll Now: www.udemy.com/course/mastering-high-level-low-level-boards-in-monday-com/
Great video! Would be awesome if you could do a more in depth one specifically addressing the issues of recurring tasks where client lists is changing or documentation may change. That's the biggest struggle I have at the moment. Do I make one master task and a subtask for each client? Do I create one individual task for each client? What if task documentation needs to be updated, how is that reflected for all clients receiving that task? Anyways, that's just some of my struggles at the moment. Thank you!
Thanks for sharing! If you do the second option of having a separate recurring task board, then you can just update the tasks there easily as they change. Did you test that out? I would use that option and then make everything a separate task for clients. Do 1 client can have 20 tasks. Can you give me more information about what you mean about task documentation?
When you follow the second method - how does the year impact the recurring feature? Is the automation looking at month/day only or does it take year into consideration?
Hi! You can actually set the time period of the automation to be whatever you want. So you could say, after the date arrives, push the due date to the next day, week, month, quarter or year. So the year itself does not affect anything. Does that make sense?