Completing a Project 

This article provides a clear guide for when and how to mark a project complete, ensuring timely payments and avoiding support escalations.

1. When to Mark a Project Complete

Before marking a project complete, all three of the following conditions must be met:

1. Work Completion and QA – Verify that all project work has been completed and fully quality-checked.

2. Client Review – Give the client sufficient time to review the work, ask questions, and request final revisions.

3. Final Revisions Completed – Complete any requested revisions and obtain the client’s approval.

Important: Only mark a project complete once these criteria are satisfied. Premature completion is the most common cause of escalated support tickets.

2. How to Mark a Project Complete

Once the work is done and the client has reviewed it:

1. Navigate to the project card in your conversation with the client.

2. Click “Mark Complete.”

3. A notification is sent to your client indicating the project is ready for review.

4. The client has 72 business hours to request changes before the project automatically approves.

If the client requests revisions during this review period:

• Complete the revisions and ensure the client approves the updates.

• Re-mark the project complete once the client has reviewed and confirmed satisfaction.

Payment: Funds are released to your wallet after client approval.

3. Support Issues Related to Marking Complete

Marking a project complete prematurely can escalate support tickets.

Resolution Steps:

1. Move the project back to “In Progress.”

2. Address client concerns and complete any necessary revisions.

3. Once resolved, re-mark the project complete.

Support Intervention:

• The Support team may ask you to move a project back to “In Progress” if they have not received a response.

• In urgent situations, Support may move the project themselves to begin de-escalation.

Typical scenarios for Support intervention:

• You have not responded after Support requests you move the project back.

• The situation is escalating quickly and immediate status adjustment is required.

Key Takeaways

• Only mark a project complete when work is done, revisions are addressed, and client approval is obtained.

• Premature completion is the leading cause of escalated support tickets.

• Always follow up promptly if revisions are requested.

• Communicate with Support immediately if issues arise.