Project Setup

Projects are the backbone of everything in the system. They represent construction sites or jobs where workers are deployed. Every attendance record, every payment, every stoppage -- it all ties back to a project.

Creating a Project

A Company Admin creates projects with the following information:

• Name -- Something descriptive like "Highway Extension Phase 2" or "Commercial Tower Block A"
• Description -- Optional extra details about the scope of the project
• Start Date -- When work is expected to begin
• End Date -- When it is expected to wrap up
• Status -- Starts as active by default

Project Statuses

Status	What it means
Active	Work is underway; attendance is being recorded; payments are being processed
Completed	The work is done; no new attendance can go in; final payments might still need to be wrapped up
Archived	The project is fully closed out; kept around purely for historical records

Assigning Managers

After a project is created, the admin assigns one or more project managers:

• At least one manager should be marked as the primary manager
• Multiple managers can be assigned to the same project
• The same manager can handle multiple projects at the same time
• Manager assignments can be changed whenever the admin needs to
• When a manager is removed from a project, the system records the removal date rather than deleting the record, so there is always an audit trail

Assigning Workers

Workers get assigned to projects through the project management screens:

• A worker can be assigned to multiple projects at once
• Each assignment has its own status (active or inactive)
• Workers can only submit verifications for projects they are actively assigned to
• Pay rate overrides can be set up for each worker on each project

Multi-Project Considerations

When a worker is working across several projects at the same time:

• Attendance is tracked separately for each project
• Cross-project checks prevent anyone from being marked present on two projects on the same day
• Payment calculations pull everything together across all projects within a payment cycle, with a detailed breakdown showing what came from where
• Rate overrides are project-specific, so a worker might earn different rates depending on which site they are at

Project Lifecycle

Here is how a project typically flows:

1. The admin creates the project (it starts as active)
2. Managers get assigned and workers get deployed
3. Daily attendance tracking begins
4. Payment cycles run every 15 days for each worker
5. Work wraps up and the project gets marked as completed
6. Final payments are processed
7. The project gets archived for the record books