Project Closer

This book serves as the complete SOP and reference guide for the Project Closer role at Upastra Digital Media. It defines the purpose, workflows, and responsibilities of the team members who ensure that every completed client project is properly finalized, documented, and delivered according to Upastra’s internal standards. 

Daily Tasks Guide - How To Do Daily Tasks

Daily Tasks Guide - How To Do Daily Tasks

How to upload a project

Note: Use the same format in the description section whenever uploading the project. As shown in the photo.

 

image.png

Changes the status of that project with the help of Order Status SOP’s.

Daily Tasks Guide - How To Do Daily Tasks

How to Start or Create a New Project | Step-by-Step SOP

Purpose

This SOP outlines the step-by-step process for uploading a new client project. It ensures that every project is properly documented, organized, and tracked from the beginning, maintaining consistency and data security across all team members.


1. Requirements Checklist

Before starting the project upload process, make sure you have collected the following items from the client:

Ensure all of these materials are complete before proceeding.


2. Project Uploading Steps

Step 1: Create a New Project in ClickUp


Step 2: Create a Folder in Google Drive


Step 3: Collect and Upload All Client Data


Step 4: Create a Subdomain for the Project


Step 5: Add Client Login Details


Step 6: Add Inspirational Website Links


Step 7: Update Discord Activity Section


Step 8: Update Project Information in ClickUp


Important Notes


Daily Tasks Guide - How To Do Daily Tasks

How to transfer a website


Subdomain

Client website

 

Daily Tasks Guide - How To Do Daily Tasks

How to close a project

Project closing steps:

Daily Tasks Guide - How To Do Daily Tasks

How To Get Review From Review Left Client & Update it Properly

Daily Tasks Guide - How To Do Daily Tasks

SOP – Handling & Uploading Client Changes (Revisions)

🎯 Objective

Ensure all client-requested changes are:

No data loss. No missed instructions. No confusion.



🧱 Scope

Applies to:



⚠️ Core Rules (Non-Negotiable)




🧭 Step-by-Step Process

🔹 Step 1: Create Changes Folder (Mandatory)

In the project Google Drive:

changes_1

changes_2

changes_3, changes_4 …

🚫 Never rename or reuse an old changes folder.


image.png




🔹 Step 2: Capture Client Messages (Proof Required)

Take screenshots of:

These screenshots must clearly show:

📸 Screenshots are mandatory even if the message is “simple”.

image.png



🔹 Step 3: Download All New Client Data

Download everything the client sent, including:

🚫 Do NOT rely on external links staying active.




🔹 Step 4: Upload Data to Changes Folder

Upload the following into the relevant changes_X folder:

Upload using the Upastra Drive And client folder only account only

(no personal accounts allowed).





🔹 Step 5: Discord Update (Carl-bot – Mandatory)

In the client’s Discord thread → Activity section:

Use the command matching the change round:

/changes1  → First round

/changes2  → Second round

/changes3  → Third round

/changes10 → Tenth round

📌 Carl-bot already contains predefined messages.

Rules:

🚫 If a change round is not logged via Carl-bot, it is not considered an official revision.


image.png




🔹 Step 6: Update ClickUp Activity

In the ClickUp task → Activity / Comments section:

Note: For First draft reply also add the positive, negative or moderate feedback from the client based on the client messages.

image.png


🔹 Step 7: Update Project Status

Finally:

- Change the task status to:

  New Changes

🚫 Do not move the status before all previous steps are completed.


🔍 Quality Check (Before Status Change)


Confirm all are done:


If even ONE item is missing → stop.

How to Manage Logins - Add or Update Logins

Fiverr Delivery Message SOP (Full-Proof)


🎯 CORE RULE (NON-NEGOTIABLE)

A delivery is COMPLETE when the agreed scope is finished and proof is shared. Revisions, transfers, logins, hosting, or silence from the client do not make a delivery incomplete.

Never imply incompletion in wording. Ever.


🚫 FORBIDDEN WORDS (AUTO-FLAG RISK)

Never use in delivery or follow-ups:


✅ APPROVED WORDING

Always use:



📦 DELIVERY SCENARIOS & EXACT MESSAGES


🟢 SCENARIO 1

Final Delivery (Client approved, no changes expected)

When to use

Delivery Message

Hello,

I’m pleased to inform you that your order has been completed as per the agreed scope. Thank you for trusting me with your project.

Here is the website link : 

Once you accept the final delivery, you’ll be prompted to leave a review. It will only take a moment, and I would truly appreciate your feedback.

If you have any questions or require any additional adjustments, please feel free to reach out through our Fiverr chat.

Best regards,
Jehan Zaib


🟡 SCENARIO 2

First Scope Delivery (Initial version, expecting revisions)

When to use

Delivery Message

The website has been completed in accordance with the agreed scope and is now ready for your review.

Website / Preview Link:
[URL]

Please review the website and let me know if there are any revisions included in your package. You may place the order in revision and share the details, and I will take care of the updates.

If everything looks good, you may proceed with accepting the delivery. Once accepted, you’ll be prompted to leave a review. It will only take a moment, and It really helps us freelancers to grow on the platform.

I’m available if you need any assistance.



🔵 SCENARIO 3

Client has NO domain / NO hosting

When to use

Delivery Message

The website has been completed as per the agreed scope in the order and is ready for review.

Since the domain and hosting are not yet available, I’ve shared a preview link.

Preview link: 

Please review the website and let me know if there are any revisions included in your order. You can submit them via the revision request, and I’ll take care of the updates.

Once you’re ready, you can also share the domain and hosting access, and I’ll transfer the website for you.



🟣 SCENARIO 4

Client has EXISTING website and doesn’t want overwrite yet

When to use

Delivery Message

The website has been completed as per the agreed scope of our order and is ready for review.

Since your domain currently has an active website, I’ve shared a preview link so you can review everything before going live.

Preview link: 

Please review and share any revisions included in your order. Once you’re satisfied, I can proceed with replacing the existing website on your domain.

Please note: once approved, the new website will replace the existing website currently live on your domain.



🟤 SCENARIO 5

Transfer didn’t happen → Backup files provided

When to use

Delivery Message

Hi {username},

Just a quick update regarding your website.

The project was completed earlier and, as there hasn’t been any recent activity, the temporary preview has been archived. A full backup has been securely saved, so the website can be deployed or transferred anytime whenever you’re ready.

If you’d like to proceed or need any assistance, feel free to reach out — I’ll be happy to help.

⚠️ Never include usernames/passwords.



⚪ SCENARIO 6

Auto-Completed Order (Client silent)

When to use

Message

Hello {username}...,

Just a quick note to let you know the order has been auto-completed by Fiverr.

If you’d like any revisions included in your order or need help with anything related to the website, feel free to reach out anytime.


🟠 SCENARIO 7

Client returns after months

Message

No problem at all — I’ve already archived the website and have a full backup ready.

Once you’re ready, I can either transfer and deploy it for you or share the backup files so you can set it up yourself. Let me know how you’d like to proceed.



🔁 REVISIONS DELIVERY RULE

Please confirm if there are any further changes needed so I can proceed accordingly.



🔒 SECURITY RULES (MANDATORY)

Never:

Always:



🧠 ADDITIONAL SCENARIOS YOU MAY FACE (Handled by SOP)

✔ Third-party tools (Fillout, Calendly, GA, Stripe)

→ Feature delivered + temporary setup = complete delivery


✔ Large sites (files too big)

→ Preview + screenshots = valid proof


✔ Client delays content

→ Extend delivery, don’t deliver


✔ Client disappears forever

→ Archive + backup = protected



🏁 GOLDEN RULE (PIN THIS)

Deliver when scope is complete.
Proof matters more than perfection.
Language matters more than intention.



Final reassurance

This SOP:

You can now operate without fear of wording-based warnings.



Just tell me what you want to lock next.