Before you begin
- Open the intended workspace and project, then confirm the project name and current status.
- Check that your project role includes the section and action you need.
- Prepare only the source records or evidence required for this task.
If the result is not what you expect
- A permission message means the project role or explicit section access does not allow that operation.
- A shared Sample warning is intentional: Sample records cannot be edited, cloned or converted into a real project.
- A stale or conflict message means the record changed elsewhere; reload, compare and apply the update again deliberately.
- An upload or capacity error must be resolved before the record can claim the file was saved.
Frequently asked questions
What should I verify before I work with Move a change through approval and implementation?
Use explicit transitions and approvals instead of silently changing lifecycle state. Confirm that you are in the intended real project, that your role permits this section, and that the source record, current state and required evidence agree before you make or approve any change.
How do I know Move a change through approval and implementation is complete and trustworthy?
Treat Move a change through approval and implementation as complete only after AutoNexit confirms the save or upload, the expected status and history are visible, and every required downstream link or evidence item can be opened from the same authorized project record.