> For the complete documentation index, see [llms.txt](https://engyon.gitbook.io/engyon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engyon.gitbook.io/engyon/en/reference/sources/life-cycle-management.md).

# Life cycle management

On this screen, file requests go through statuses from draft to approved client delivery. Clients deliver documents at the request of the auditor. These documents must be assigned to the client, added by the client and eventually approved by the auditor.

When you click on <kbd>Status</kbd> in the sources screen, you get the following option: <kbd>close specification</kbd>. Click on this. The status <kbd>draft</kbd> disappears. The request now receives the status <kbd>unassigned</kbd>.

Click on the initials behind the file request. Assign the request to the client. The status changes to <kbd>Assigned</kbd>. You can also assign or bulk unassign multiple file requests at once; see [Assigning file requests](/engyon/en/how-to-guides/sources/manage-and-create-file-requests.md#assigning-file-requests) and [Unassigning file requests](/engyon/en/how-to-guides/sources/manage-and-create-file-requests.md#unassigning-file-requests).

The client now sees the file request appear and can assign it to other colleagues if necessary.

An upload leaves the status on <kbd>Assigned</kbd>. When the files are complete, the client clicks <kbd>Status</kbd> and chooses <kbd>For review</kbd>. After that, the client cannot set that status back. If the team needs more, they choose <kbd>Request clarification</kbd>.

After the client has uploaded a document, it must first be approved by an auditor before it can be used in a procedure. During approval, the auditor determines that the uploaded file meets what was requested. If necessary, the auditor can place a comment on the file, which is visible to the client.\
Files uploaded by an auditor are immediately marked as approved by the auditor in question.
