---
# System prepended metadata

title: Cleric SOP Outline
tags: [Clerics, SOP]

---

# Cleric Standard Operating Procedure (SOP) for RaidGuild

![](https://hackmd.io/_uploads/SJJZ5Uhbp.png)


### Introduction:
The Cleric plays a vital role in the RaidGuild ecosystem, acting as the point of contact for clients and ensuring smooth operation of the project from start to finish. This SOP details the responsibilities and actions required of a Cleric.

### 1. New Client Submissions:
   1. Monitor the *Raid Guild Discord server, new client submissions channel*.
   2. Signal interest in handling a client's request by marking with the *Raid Guild crossed swords emoji*.
   3. Discuss with fellow clerics to ensure work distribution is even.

### 2. Client Communication:
   1. Using the details from the initial submission, contact the client.
   2. Understand and evaluate the client's requirements.
   3. Schedule a consultation meeting.

### 3. Consultation Meeting:
   1. Prepare a checklist to gather essential information, which includes:
      - Problem description.
      - Proposed solution (if available).
      - Required skill set.
      - Budget and timeline (both should be as concrete as possible).

### 4. Post-Consultation Steps:
   1. Attend the *Tuesday Raider Round-up meeting* and convey the project details.
   2. Mark the raid as `recruiting` if proceeding.
   3. Post the specifications in the *#who-is-available* channel on Discord.
   4. Create a new instance in the *Dungeon Master* platform, detailing specific roles needed. This action will auto-generate two communication channels (internal and external).

### 5. Setting Up Communication:
   1. Transition all communications to the public channels on the RaidGuild server.
   2. Onboard the client onto the RaidGuild server: provide instructions (these need to be created).
   3. Post initial project specifications in the internal server for clarity.

### 6. Assembling the Raid Team:
   1. Once a team with the required skill sets is in place, schedule a follow-up meeting with the client.
   2. Draft a proposal detailing the problem, hypothesis, and proposed solution.
   3. Set up an escrow for the client to fund the scoping or design sprint by [following these steps.](https://handbook.raidguild.org/docs/how-does-it-work)

### 7. Formal Proposal:
   1. Post the scoping sprint, the team collaborates to create a formal proposal. This should follow the linked standard format, detailing:
      - Problem space.
      - Methodology.
      - Milestone-based work outline with corresponding budgets corresponding to the escrow.
   2. Send the proposal to the client along with instructions regarding fund deposition.

### 8. Begin Work Phase:
   1. If the client proceeds, commence work post fund confirmation.
   2. If the client declines, understand their reasons, update the guild, and mark the raid as lost in the *Dungeon Master* tool.

### 9. During Work Phase:
   1. Provide updates in the *Dungeon Master* tool.
   2. Ensure client satisfaction. Address any questions or concerns and relay them to the team.
   3. Update the client upon completion of milestones and handle fund release/distribution by setting up the txns.

### 10. Project Completion:
   1. Confirm that the client's expectations have been met.
   2. Collect feedback.
   3. Instruct the client on releasing the final milestone payment.
   4. Distribute the payment to project contributors.
   5. Mark the raid as `shipped` in the *Dungeon Master* tool.
   6. Archive the communication channels on Discord using the `/to-valhalla` command.
   7. Participate in the retrospective led by the Monk.

### 11. Documentation:
   1. Assist in formatting the retrospective learnings into the portfolio case study template.
   2. Submit the completed study to the (????) channel for portfolio inclusion. **This step is unclear.**

---

**Additional Topics for Consideration:**
1. **Cleric Availability:** Exploring ways to transparently view each cleric's availability upon a new client submission.
2. **Shared Cleric Resources:** 
   - Possibility of a shared email (e.g., clerics@raidguild.com) for initial client contact and decentralized management of this shared resource.
3. **Tool Improvements:** Discuss ways Discord and Dungeon Master can be further optimized for transparency, member protection, and client experience improvement.