Project Updates
I would love to know if there is a best practice for creating project updates. I work for a home builder and we have several blueprints for each of our processes as all vary in steps. I would like to standardize a way to create project updates so that I don't have to create multiple update blueprints. Currently, we don't have a consistent way the team goes about their updates. We have updates for flyers where the copy may change or UX may have to add in different code for a web banner or email. Does this exist anywhere or does the community team have any suggestions on how one would go about this?
If I'm understanding the question correctly (which it is very possible I am not, lol), wouldn't custom workflows be a good use case for understanding where a project exists for a specific use case? That is how we track where we are at, and we have dozens of custom workflows that are uniquely setup for a very specific need.
Tracey Perry could you perhaps give some more info what you mean with project update? What do you want to achieve with a blueprint? We are using blueprints for new projects only, and I can not see the point where to use a blueprint during an ongoing project.
I use some blueprints during a project to add a phase or something and not to have my original project having too much tasks, but like Sven said, we might need more info to help you better,,,