Organize, close, and delete projects

Organize projects when creating them

Use a consistent project name and select the correct client. Add a description, keywords, contacts, contract, coding sets, and guidelines where required by your workflow.

Avoid creating a second project merely because the first is missing from a dropdown. Verify the active company, client relationship, and integration mapping first.

Filter and sort the project list

Open Org > Projects. Use search, client, and status controls to narrow the list. Projects have Open and Closed statuses, and the project view provides separate Open and Closed navigation.

Sort by the available columns, including name, client, status, or task count, to find projects that need attention.

Close completed work

Edit the project and change its status to Closed when the engagement is complete but its history must remain available. Closing is preferable to deletion for completed client work.

Before closing, review open tasks, unsubmitted time, pending approvals, expenses, invoices, staffing allocations, and connected-system activity.

Reopen a project

Find the project in the Closed view, edit it, and change its status back to Open. Confirm that its client, team, contract, and integration mappings are still current before recording new work.

Delete only when appropriate

The project table provides individual and bulk delete actions. Deletion is destructive and can affect linked projects, contacts, contracts, time, tasks, external identifiers, and downstream company relationships.

Use deletion for erroneous or unused projects, not ordinary completed engagements. Read the confirmation carefully and avoid bulk deletion unless every selected project has been reviewed.

Imported projects

For projects managed by an external practice-management system, correct mapping or lifecycle state in the authoritative system when appropriate. Deleting a project in only one system can cause it to be recreated or leave disconnected records during the next sync.