Skip to main content

SOP – Handling & Uploading Client Changes (Revisions)

🎯 Objective

Ensure all client-requested changes are:

  • Properly documented
  • Safely stored
  • Clearly communicated
  • Correctly tracked in ClickUp

No data loss. No missed instructions. No confusion.



🧱 Scope

Applies to:

  • All Fiverr website projects
  • All revision / change requests (1st, 2nd, 3rd… onwards)


⚠️ Core Rules (Non-Negotiable)

  • ❌ Never overwrite old files
  • ❌ Never rely only on chat memory
  • ❌ Never skip screenshots
  • βœ… Every change request must have its own folder




🧭 Step-by-Step Process

πŸ”Ή Step 1: Create Changes Folder (Mandatory)

In the project Google Drive:

  • For first revision:

changes_1

  • For second revision:

changes_2

  • Continue sequentially:

changes_3, changes_4 …

🚫 Never rename or reuse an old changes folder.

image.png



πŸ”Ή Step 2: Capture Client Messages (Proof Required)

Take screenshots of:

  • Fiverr Order Chat
  • Fiverr Inbox / Conversation Chat

These screenshots must clearly show:

  • Client instructions
  • Date & time
  • Any links or files mentioned

πŸ“Έ Screenshots are mandatory even if the message is β€œsimple”.




πŸ”Ή 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:

  • All downloaded files
  • All chat screenshots
  • Any notes or clarifications (if required)

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 Carl-bot quick commands only
  • Do NOT type manual messages

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:

  • Command number must match the Drive folder (changes_1, changes_2, etc.)
  • Always use the next sequential command
  • Never reuse or skip a number

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



πŸ”Ή Step 6: Update ClickUp Activity

In the ClickUp task β†’ Activity / Comments section:

  • Add a short update: Changes : 1 , Changes : 2


πŸ”Ή 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:

  • - Changes folder created βœ”
  • - Screenshots taken βœ”
  • - Data downloaded βœ”
  • - Files uploaded βœ”
  • - Discord updated βœ”
  • - ClickUp updated βœ”


If even ONE item is missing β†’ stop.