🇬🇧 Purpose
Defines how tasks must be created, structured, named, and operated in ProSys. Ensures consistent workflow, clean audit trail, predictable automation, zero ambiguity in responsibility.
🇻🇳 Mục đích
Định nghĩa cách tạo, tổ chức, đặt tên và vận hành task trong ProSys.
1. Parent vs Sub-task: Parent = Service (one service/procurement item; owns workflow, approval, audit). Sub-task = Evidence only (Quote, Invoice; OPEN → DONE; never participates in approval or workflow).
2. When to create Parent: When any money will be spent, any vendor is involved, any approval is required, any invoice will exist.
3. When to create sub-tasks: When you receive a quote → create Quote sub-task. When you receive an invoice → create Invoice sub-task. One sub-task per document (recommended). Attach file to sub-task. Mark sub-task DONE when document is final.
4. Naming: Parent: [Service] <clear business description>. Sub-task: [Quote] / [Invoice] <vendor name>.
5. Assignment: Parent assignee = service owner. Sub-task assignee = person who uploads/manages the document.
6. Labels: Must follow phase-x, cohort-xxxx, loc-xxx.
7. Do NOT: Create sub-task without parent; use sub-task to request approval; put invoice directly on parent without sub-task; use ProSys for non-procurement work.
8. Audit: If it is not in ProSys → it does not exist. If it is not attached → it is not auditable. If it is not approved in workflow → it is not valid.