Projects

Projects help staff organize client work into clear workstreams. Use them when a client has recurring services, a one-time engagement, cleanup work, or an internal initiative that should be tracked separately from the general client record.

Where to Find Projects

• Open Projects from the employee sidebar to see the project list across the clients you are allowed to access.
• Open a Client detail page and choose the Projects tab to see only that client's projects.
• Open a task detail page to see the related project when the task has one.

The Projects page links back to the related client. The Client page Projects tab links back to the Projects page filtered to that client.

How Projects Relate to Clients and Tasks

The current relationship is:

1. Client — the business or account Bizcom serves.
2. Project — a workstream under one client, such as a recurring service, one-time job, cleanup effort, or internal tracking project.
3. Task — the specific work item. A task may be linked to a project, but existing tasks can remain unassigned.

A project always belongs to one client. Staff should not see projects for clients they are not allowed to access.

What You See in a Project List

Project lists show practical operating fields:

• project name and description
• client name, when viewing the main Projects page
• type and status
• owner, if assigned
• open, completed, overdue, and total task counts when available

Use search on the Projects page to find a project by project name, client, owner, type, status, or category.

Creating and Editing Projects

Only users who already have permission to manage clients can create or edit projects. If you have access, use the client admin/detail area and choose Create Project or Edit Project.

When creating a project:

• Use a clear name staff will recognize.
• Choose the correct project type and status.
• Assign an owner when one person is responsible for follow-up.
• Add a target end date only when it is meaningful.
• Do not create duplicate projects for the same client workstream.

Recommended Uses

Good project examples include:

• monthly accounting work for a client
• payroll processing workstream
• business permit renewal
• cleanup or catch-up work
• one-time registration or advisory engagement
• internal coordination project for a client account

What Not To Do

• Do not put private client secrets, bank data, government ID numbers, passwords, or connection strings in project names or descriptions.
• Do not create one project per small task; use projects for meaningful workstreams.
• Do not backfill all historical tasks unless a manager explicitly asks for it.
• Do not use real client names or task counts in public documentation or screenshots.
• Do not treat project assignment as required for every task; it is optional in the current MVP.

Staff QA Guidance

When checking Projects after a release, verify:

• the Projects page loads from the sidebar
• each project links to the correct client
• a Client page shows only that client's projects
• a Client page with no projects shows a useful empty state
• task detail shows the project relationship when present
• task filtering by project still works after choosing a client
• users cannot see projects for clients outside their access

If any of these fail, use Report Issue and include the page, expected behavior, actual behavior, environment, and a non-sensitive reference.

Current MVP scope

Project tracking is staff/admin-facing. Client portal project visibility, project billing/time rollups, automatic historical backfill, document migration, and project-driven recurrence rules are not part of the current MVP.