Request Form Organization

Yes please! We would also benefit from this. (I think anyone with a reasonably sized Wrike instance would as well.)

Yes, absolutely yes! Upvoted!! Soraya Noel

Some ways that we've managed our large volume of request forms:

• We have an internal Wiki page where we use headers and a table of contents separated by team so you can click and be brought to a table for that team's forms (includes likes, descriptions, who owns the form, etc.) - they only downside to this is that it takes extra maintenance especially when we are not alerted necessarily if a new request form has been created or if one was edited 
• We prefix most of our internal request forms with a team acronym (that we collectively agreed upon) so that the forms on the backend are sorted alphabetically - i.e. all graphics request forms start with [CS], all digital request forms start with [DG], all content request forms start with [CO], etc. 

I agree.  We have many account wide forms, and the list is a pain to scroll through.

I agree too...
in this moment I've created a Folder where a CIT Task is used to organize data.
Maybe can help  =)

Hi folks, thank you for this feedback! 

Our team is aware of this need. Please consider upvoting this similar post too 👍

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover