Skip to main content

F-001 Client and Project Lifecycle Management

AttributeValue
ProjectOpen Projects Hub
Version1.3
StatusAccepted
ReadinessReady for Implementation
OwnerProduct Owner

Context​

  • Problem: Admin needs one place to manage clients and projects while enforcing MVP constraints.
  • Primary Persona: Admin (Freelancer)
  • In Scope: Client CRUD, project CRUD, 3 active project limit, discovery/planning phases only.
  • Out of Scope: Delivery and handoff phases, external collaboration workflows.

Functional Requirements​

IDRequirementSourcePriorityOwner (DRI)Decision Traceability (Q-ID)Acceptance CriteriaStatus
FR-001-01The system allows an Admin to create and manage client records and associate each project with a client.OverviewMustProduct Owner—Admin can create, view, update, and archive client records and select a client when creating or editing a project.Clarified
FR-001-02The system allows an Admin to create and manage projects with a maximum of three active projects per workspace (the freelancer's account and the Members they add).Open Questions Q-001, Q-002MustProduct OwnerQ-001, Q-002Attempting to create a fourth active project is blocked and the Admin is prompted to archive an existing project.Clarified
FR-001-03The MVP supports only discovery and planning phases for projects.Open Questions Q-003MustProduct OwnerQ-003Project status options are limited to discovery and planning; no delivery or handoff features are available in MVP UI or export.Clarified
FR-001-04Admin can archive or delete client; deletion is blocked if client has active projects.Data integrityMustProduct Owner—Archiving client preserves data; attempting to delete client with active projects shows error "Archive or reassign projects first"; deletion allowed only after projects are archived or reassigned.Clarified
FR-001-05Admin can search and filter projects by status, client, or date.UsabilityShouldProduct Owner—Project list has search input and filter dropdowns; search covers project name; filters for status (active/archived), client, date range; results update without page reload.Clarified
FR-001-06Project includes required metadata: created_at, updated_at, description, and status.Data model baselineMustProduct Owner—All projects store created_at and updated_at timestamps automatically; description is optional text field; status field supports "active" and "archived" values.Clarified
FR-001-07Reactivating archived project does not count toward 3-active-project limit until status is set to active.Lifecycle clarityMustProduct OwnerQ-001Archived project can be viewed and edited without blocking; explicitly changing status to "active" triggers project limit validation; clear UI feedback if limit would be exceeded.Clarified

Feature-Scoped Non-Functional Requirements​

IDRequirementMetric / TargetPriorityOwner (DRI)Decision Traceability (Q-ID)Status
NFR-001-01Lifecycle operations remain privacy-aligned for archival/deletion behavior.Deleted projects become inaccessible to Admin, Member, and the Client Review Portal within 24 hours; archived projects are excluded from active-project limit.MustTech LeadQ-017, Q-018Clarified
NFR-001-02Project and list views stay responsive at MVP load.Satisfies NFR-X05 performance baseline (10 concurrent Admins + 20 client reviewers, 100 requests/min, 3 projects per Admin, 200 stories total). Project list renders within 2 seconds.ShouldTech LeadQ-001Clarified
NFR-001-03Project lifecycle data scales to MVP limits without data loss.Satisfies NFR-X06 scalability baseline (3 active projects per Admin, 500 total user stories without data loss).ShouldTech LeadQ-001Clarified

Dependencies and Risks​

  • Dependencies: RBAC enforcement, project persistence model, archival policy decision implementation.
  • Risks: Active-project limit can be bypassed in edge flows; mitigation is centralized backend validation on project activation and creation.

Traceability​

Last Updated: 2026-09-08