Use case example: We have a request form to send emails. Email subject lines and preview text can be no more than 150 characters, but our requestors fail to read the help text.

Thanks, Richard. Fusion is not in scope unfortunately. I agree that your two options would require a lot of training and oversight—so it's helpful in ruling out approaches.I'm starting to think that, if we have a consistent lineup of second-level requestors, I might add them as approvers. If they ap...

I'm curious to hear if others have tried to solve this problem:I have been tasked with creating a request queue in which a requestor provides the first batch of information, but then another role type has to fill in a bunch of additional custom form data. In other words, this is a request that needs...

I also use milestones to plot publish dates on an editorial calendar. So far people love it!

I pin a dashboard to the Projects area that includes a bunch of reports that filter to the user viewing it, including most of what you list above plus:My projects 100% complete but not in closed status (Yes, we're working toward defaulting all projects to autocomplete.)My projects not updated in ove...

Yessss, when I found the tips from @RandyRoberts it made my quarter(ly audit).

My creative thinking: Create a queue for each visibility profile. You can aggregate intake by either routing requests to a central project or building a report/dashboard to report on the issues across the queues.

Theoretically, sure. I, however, have project owners who push back if there is any amount of redundancy. Those redundancies also mess with our reporting, which sends leadership in a tailspin.

That's my question, too. It sounds messy having to maintain two projects. I'd rather use a task conversion process. Cross-project predecessors, however—I'm trying to find the secret to recalculating schedules more automatically. I definitely support the concept of one deliverable per project for all...

I presume there is custom form data you're trying to carry over? If your custom form is applicable to tasks, you could add that custom data to a parent task and move the group of tasks to the monster project. I think. I hope. You might test it in the sandbox first.