Wrike Request Forms: Constraints for Date Questions - block out weekends

There is a very new feature in request form that allows creators to set constraints that only allow the entry of dates that are X or more days later than the form submission date. In practical terms, this means when someone fills out a form, they won't be able to pick dates (for example, a due date) that are earlier than what the form creator has designated.

HOWEVER this does not include blocking out weekends which means that if you are trying to fix a SLA say for 5 days it includes the weekend and gives the requestor the illusion that something can be delivered soon than possible.

I suggest you allow each user to set their own weekend and block out days - and add this feature to the Constraints for Date question.

Find more posts tagged with

Not planned

Status: Not planned

Comments

Kelsey Rudolph

I would love for this to be built in to the system. In the meantime, one thing I've been doing to capture weekends in the time constraint is add those numbers into the constraint. For example, I follow the following for projects that fall to be "completed" in X number of days:

1 to 5 days - Constraint as stated
6 to 10 days - I add 2 days to the constraint for the weekend
11 to 15 days - Add 4 days
16 to 20 - Add 6 days
21 to 24 days - Add 8 days

...and so on and so forth. Unfortunately ( and obviously) I can't set it up this way to account for holidays, but I do include helper text not to select weekends/holidays for finish dates as weekends/holidays are non-working days (so if the project constraint ends on a Saturday, they should not choose that Saturday/Sunday). It isn't perfect, but it does help in reflecting more realistic timelines from the start.

Julia Marber

Hey Kelsey - we have been doing the same as you have listed above but it is not an exact science and can lead to not matching submitter expectations!

Michael Kreisbuch

Also tagging in to say would be a big fan of this feature if implemented. I know that Wrike does have account-based work schedules. It would be great if the form could reference one of the account's work schedules. If not, the ability to lock off specified holidays and weekends would be huge.

I've also noticed that when populating new tasks, the forms default to the earliest available date. So, for example: I have a 3-day constraint set on the form. If the submission date was Wednesday, that would make the next available date fall on a weekend. My account's work schedule and blueprints exclude weekends, so when the task finally populates it defaults to Friday as the earliest available date - even though the constraint should prevent that date from being selected. Wondering if this behavior is change-able on forms and blueprints to have a request populate to the next available date after the constraints?

I realize that's asking for interplay between a bunch of different tools. Not sure if possible, but would be vey helpful!

Anna Giacobbe

Totally agree with this suggestion - would be great to have the ability to block out weekends!

Shona Snowden

The constraints are great, but adding this would be an advantage.

Elizaveta Bogdanova

Thanks a lot for creating a separate post here and supporting this idea! Our team is already aware of this feedback, but it's good to have it in one place. I'm sending all your thoughts here to the team 👍

Bekah Coenen

Agreed with all the comments above. It would be a great advantage to have these blocked-out dates. This would lead to better communication with requestors. I am not keen on using the work around of adding dates to the SLA timing because to reinforce Julia's point from above, it can cause miscommunication with submitters. If our SLA says 5 days, but they can not select a date that is within 5 business days it seems that our SLA is being misrepresented. I would love the ability to tie the request form to the work schedule that would pull in any blocked out dates and not allow due dates selected then.

Rohan V

Welcome to the Community Forums, @Bekah Coenen!

Thank you for taking the time to post your feedback and explain your use case. I am forwarding your comment to the responsible team now. If there are any new developments in the future, I will provide you with an update 👍

Chris Brightwell

The idea of this feature is great, but it's completely useless to me if I can't limit the dates to exclude weekends. Why is no more attention being paid to this???? I'm trying to set a limit and enforce a 5-day minimum for creative review for my team, and blocking out 5 days over a weekend only gives me 3 days. PLEASE PAY ATTENTION TO US AND FIX THIS! It's been a year since this was requested.

Elena Boughey

I would just be happy to be able to block out weekends although holidays would be a major plus! The text helper doesn't stop anyone from thinking they can get a job shipped out on a Saturday if they can get away with it.

We are just getting too large as a company to deal with this issue on a one to one basis with our customers & give them a new date when they pick a weekend drop.

Elena Boughey

Additional question. Please tell me this will also be done on a project level when a blueprint generates the project with all of it's tasks.

Rohan V

Hi everyone 👋

Thank you for your continued feedback. I checked with the responsible team, and at this time, this feature is not being planned. I understand this may be disappointing when a helpful feature isn’t available. Please know that we’re sharing all of your comments with the team, and if there are any updates or changes in the future, we’ll be sure to post them here. Thank you again for your patience!

@Elena Boughey, currently, when a request form generates a project from a blueprint, the date constraint applies to the project’s start or due date. The tasks are then scheduled according to the blueprint’s settings. However, weekends and holidays are not automatically blocked out when assigning task dates. Thank you for bringing this up. I’ll be sure to share your feedback with the Product Team. 👍

Elena Boughey

I was able to create this in less than an hour through quick programming. How is it that you won't take care of this? I'm just a beginner python programmer and was able to come up with a solution... It's not perfect since I was just looking to see if there was a logical fix. You have an entire team!

# US Federal Holidays 2025
holidays = [
datetime.date(2025, 1, 1), datetime.date(2025, 1, 20), datetime.date(2025, 2, 17),
datetime.date(2025, 5, 26), datetime.date(2025, 6, 19), datetime.date(2025, 7, 4),
datetime.date(2025, 9, 1), datetime.date(2025, 10, 13), datetime.date(2025, 11, 11),
datetime.date(2025, 11, 27), datetime.date(2025, 12, 25)
]

def is_business_day(date):
return date.weekday() < 5 and date not in holidays

def add_business_days(start_date, days_to_add):
current_date = start_date
while days_to_add > 0:
current_date += datetime.timedelta(days=1)
if is_business_day(current_date):
days_to_add -= 1
return current_date

Trish Doty

I would like to address a concern regarding the current implementation of the feature we requested when we moved to Wrike in 2017. We specifically asked for the ability to block out weekends and holidays and to set and enforce a default of business days. This feature has been highly sought after by many users.

While we appreciate the efforts to introduce a version of this feature in 2024, it still does not fully meet our needs. The current implementation does not allow us to completely block out weekends and holidays, nor does it enable us to set a strict default of business days. This shortfall means that requesters might still select dates that potentially lead to unrealistic project completion expectations.

It is crucial for us to have the ability to enforce the defaults to ensure accurate project timelines and avoid any confusion. I would appreciate it if we could address this issue and find a solution that meets our requirements, as well as those of many other teams and organizations.

Enhancing this feature to fully accommodate our initial request would significantly improve workflows and ensure smoother project management.

Basudha Sakshyarika

Hi @Elena Boughey and @Trish Doty! 😊 Thank you for your feedback. I understand your sentiment and recognize how important this feature is for your team. As Rohan mentioned above, this feature is not currently being planned. However, your comments have been shared with our Product team, and we’ll provide updates here if there’s any progress. 🙌🏽

Elena Boughey

I think it should be discussed in your next production meeting & planned. This is not an add on, it's a FIX. It's fixing a logical shortcoming of your software. I can't believe you wouldn't have made this fix already after some of the comments I've read here.

Basudha Sakshyarika

Thank you for the feedback, @Elena Boughey. I absolutely agree on how important this is, but currently, it isn’t planned to be worked on. We will be sure to keep the thread updated if this changes. 👍🏽