> For the complete documentation index, see [llms.txt](https://snet-ambassadors.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snet-ambassadors.gitbook.io/home/workgroups-space/video-workgroup/roles-and-their-kpis/project-management.md).

# Project management

Use templates to create tasks.

Project management involves the following:

1. Present a weekly brief in the workgroup’s meeting whenever it’s possible.
2. Recurrent tasks:
   * Manage tasks from creation to the submission phase, communicate with assignees, and share video submissions with the quality control team for review and communicating the feedback to the assignees and upon getting approval from the quality control team, share the submission on the workgroup channel for peer review .
   * Auditing tasks based on the members' and the Quality Control team's feedback.
3. Clips tasks:
   * Creating "Making clips" tasks based on need and based on discussions in the weekly meetings.
   * Make sure the clips follow the guidelines of video projects[ here](https://snet-ambassadors.gitbook.io/home/workgroups-space/video-workgroup/acceptance-criteria-for-projects).
   * Share each submission with the Quality Control team for review and communicate the feedback to the assignees and upon getting approval from the quality control team, share the submission on the workgroup channel for peer review.
   * Auditing tasks based on the members' and the Quality Control team's feedback.
   * Post the link to the submission in the[ content sheet](https://docs.google.com/spreadsheets/d/1xqbs48KnfMBY_NgMp_Vo48dHrkEpr_bCM0KfL7x7z4k/edit?usp=sharing).
4. Video project tasks:
   * Creating "Video project" tasks based on need and based on discussions in the weekly meetings.
   * Tasks should be assigned based on approval from workgroup members and coordinated with the editor and relevant teammates before finalizing the assignments.
   * Make sure the video submission follows the guidelines of video projects[ here](https://snet-ambassadors.gitbook.io/home/workgroups-space/video-workgroup/acceptance-criteria-for-projects) by conducting the initial review.
   * Share each submission with the Quality Control team for review and communicate the feedback to the assignees and upon getting approval from the quality control team, share the submission on the workgroup channel for peer review.
   * Auditing tasks based on the members' and the Quality Control team's feedback.
   * Post the link to the clip in the[ content sheet](https://docs.google.com/spreadsheets/d/1xqbs48KnfMBY_NgMp_Vo48dHrkEpr_bCM0KfL7x7z4k/edit?usp=sharing).
   * Keep a record of your activities as subtasks on Dework.

<mark style="background-color:yellow;">NOTE: Tasks involving high-priority videos, such as Town Hall updates and monthly ecosystem updates, do not require peer review due to time constraints.</mark>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://snet-ambassadors.gitbook.io/home/workgroups-space/video-workgroup/roles-and-their-kpis/project-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.