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.


Revision #2
Created 25 December 2025 11:12:18 by Jehanzaib
Updated 25 December 2025 11:36:12 by Jehanzaib