Workflows
Close a project
End a project once it is delivered, cancelled, on hold or merged. Closing locks it for good, and everything in it stays readable.
- PM
Closing is how a project ends in Srishti. A closed project accepts no more changes, task completions or document uploads, but every tab and log stays open to read, so the record of what happened is kept.
Only the project's PM can close it, and closing cannot be undone. Read this page before you choose Close project.
Before you start
- You must be the project's PM. Nobody else sees Close project, and the server refuses anyone else.
- The project must be live. A draft, or a project waiting for creation approval, cannot be closed; an approver's decision settles those.
- It does not have to be finished. You can close a project at any time while it is live, for example when it is cancelled or put on hold.
- Tell the people on it first. Closing sends no notification to the project's members.
When to close
When every mandatory activity is complete, the project's status becomes Completed and the Overall status card on the Overview says All mandatory activities complete — ready to close. with its own Close project button. Closing is the next step: a project stays Completed until you close it.
You can also close a project that will not finish. Pick the reason that fits, so anyone reading it later knows why it stopped.
| Reason for closing | Use it when |
|---|---|
| All mandatory activities complete — project delivered | The product launched and the work is done. |
| Project cancelled — business decision | The business stopped the project. |
| Project on hold indefinitely | Work has stopped with no date to restart. |
| Merged with another project | The work continues as part of another project. |
| Other | None of these fit. Explain in the comment. |
Close the project
The PM's menu. It is not shown to anyone else, or on a closed project.
Opens the closing window. Nothing is closed until you confirm there.
After closing, it shows Project closed — Reason: … with your comment.
- Open the project and choose Actions, then Close project. On a completed project you can use the Close project button on the Overview instead.
- Read the warning. The window, titled Close … ? with the project's name, says that closing locks the project and cannot be undone.
- Pick a Reason for closing. It is required: the Close project button stays off until you choose one.
- Add a Comment if it helps. It is optional, up to 2,000 characters, and shown on the project afterwards.
- Choose Close project. A message confirms Project closed and that the project is now read-only.
What happens next
- The status becomes Closed. On Projects it counts under Completed / Closed.
- The project is read-only. No plan changes, task completions or document uploads are accepted. Every tab stays readable.
- The Overview shows how it ended: the reason, your comment and when it was closed.
- The Actions menu goes away, so no new baseline can be started.
- A re-baseline waiting for approval can no longer be approved.
- Reminders and escalations stop. Only running projects are checked for due and overdue work.
- It is recorded in the project's Activity log, with who closed it.
What can go wrong
| Problem | Why | What to do |
|---|---|---|
| No Actions menu or no Close project | You are not the project's PM, the project is already closed, or a re-baseline draft is open for editing. | Ask the PM. Inside a draft, choose Save & exit on its banner first. |
| Only the project's PM can close it. | Closing is the PM's decision alone. | Ask the PM to close it. |
| A project waiting for creation approval cannot be closed | It is not a live project yet. | Its approvers decide it. A second rejection cancels it. |
| Closed by mistake | Closing cannot be reversed. | Create a new project for the remaining work. |