Prepare and submit a project summary or status change
Separate content changes from status transitions and follow the approval workflow when one is started.
In this article
- Choose the scope
Work on the private or shared side that is actually available.
- Prepare the draft
Edit the name, description, sector, or other proposed fields without changing status accidentally.
- Compare
Check the draft against current data and remove unconfirmed changes.
- Save
A summary change is saved directly when accepted by the service.
- Track status
A status transition can create a business workflow; use displayed feedback and notifications to learn the result.
Practical guidance
Prepare the narrative on the intended side and distinguish editing text from requesting a project status change. Review the current values before submitting and follow the returned workflow state when a transition requires processing. A saved draft is not evidence that another person approved it.
Advanced tips
Keep the proposed wording, reason for the change and supporting references together in your review process. If new evidence arrives during approval, reconcile it with the active version before submitting again rather than starting competing transitions from older drafts.