One issue we’ve come across is we’re not being notified or seeing the changes on our end when clients make “edits” or “amendments” to a project request custom form.

I literally had this happen yesterday. How to train the numerous external requesters to do an @ update after they change a form seems overwhelming and ineffective, there's no way people who use Workfront twice a year are going to remember or refer to documentation. This would be something to add to the Idea Exchange if it isn't already in there.

One idea is to add instructions to the top of your form on what to do if you change the form after the request has been submitted.

I have not tested this out but there is a field level setting in custom forms that lets you indicate "Display Field Changes in Update Feed". This is found near the bottom under Additional settings that affect this form only.

We put it in our Requester documentation: once you submit, don't add to the request! Each project manager is in constant email/phone contact with their requester, so it hasn't been an issue that I know of.

We also created a requester dashboard that moves submitted requests to a separate report that does not have links to the original request. Unless the requester held onto a direct URL, this effectively blocks them from their own request once it's submitted since our requesters have very limited access.

For example, our Requesters have no access to the project/task resulting from a request.

A bit draconian, but seemingly effective.

(The alternative in our mind was to delete the request once it's convert to a project/task, which was almost how we launched. The dashboard "lockout" was the work-around.)

As Dave said, you can set it up so that when info is changed there is something that is put in the Update stream. We have been using that for years. The one thing that does suck is that if you wanted to do a Notes report to capture all these changes, you can't. While in the update stream, it doesn't appear to create a "note" that you can report on. :(