There are some different things we have done related to Status to try to have more flexibility in controlling what is pulled for reports, etc. Here are the two flavors that we use/tried. 1) A workfront consultant, create an Issue Custom form for us for status reporting. We have a Queue Configuration so that when a manger creates a new Issue, they can select Project Status from the drop-down. Our custom form appears and they enter the information we need for reporting. This is good in the respect that we have a natural, historical record of Project Status Updates, each being an Issue and we can report on the last one for the current week, the last months worth, etc. Using this method does require the PM to close these Issues out before they close the project. 2) Posting an update on the Project for status updates works is you are not interested in standardizing what is given in a status. We found that it works best though, if you create a Task on your Project (we call it Project Status) and assign it to the Project Manager. This way when you run a report, you can use the Task name to ensure that the update you are getting is the Status you want and not a random comment that someone may have decided to enter on the Updates tab. This also gives us the ability on a little bigger projects to create additional Status Tasks if we want someone to report a status from testing, or affiliated with another department to provide a status ( for example: Sub-Plan Owner Status - Online Services). Admin Kelly-Wehrmann SSFCU