Project Stoppages
Project stoppages happen when work on a construction project has to be put on hold because of something outside anyone's control. The system has its own approval workflow and payment rules for dealing with these situations.
What Causes a Stoppage?
The usual suspects include:
- Rain or severe weather
- Equipment breaking down
- Material delivery delays
- Safety concerns
- Government inspections or orders
- Really anything that prevents normal work from happening
Stoppage Workflow
Step 1: Manager Declares the Stoppage
The project manager reports that work has stopped on a project for a specific date. They provide:
- Date of the stoppage
- Reason for the stoppage
- Payment terms (optional):
- A fixed amount per worker (for example, 500 LKR per worker)
- OR a percentage of each worker's daily base advance (for example, 50% of their daily advance)
- If neither is specified, workers get nothing for the stoppage day
The stoppage is created and sent to the admin for approval.
Step 2: Admin Approves or Rejects
The company admin reviews the stoppage declaration:
Approve:
- The stoppage takes effect
- The system updates existing attendance records for workers who were on site that day to "project stopped" status
- If payment terms were specified, each worker's stoppage attendance record includes their payment amount
Reject:
- The stoppage does not take effect
- The admin has to provide a reason for the rejection
- The manager can re-declare the stoppage with different terms if they want to try again
Step 3: Stoppage Takes Effect
Once the admin approves:
- Every active worker on the project gets a "project stopped" attendance record for the stoppage date
- Each worker's record tracks their individual payment amount based on the stoppage terms
- These records get included in payment cycle calculations
Stoppage Statuses
| Status | Description |
|---|---|
| Pending Admin | The manager declared it; waiting for the admin to decide |
| Approved | The admin approved it; attendance records have been created |
| Rejected | The admin turned it down; the manager can re-declare if needed |
Payment During Stoppages
Option 1: Fixed Amount
Every affected worker gets the same flat amount regardless of their worker type or daily rate.
Example: All workers receive 500 LKR for the stoppage day.
Option 2: Percentage of Daily Advance
Each worker gets a percentage of their own daily base advance amount.
Example: At 50%, a worker whose daily advance is 1,500 LKR would receive 750 LKR, while a worker whose daily advance is 2,000 LKR would receive 1,000 LKR.
Option 3: No Payment
If no payment terms are set, workers are recorded as stopped but they do not receive any compensation for that day.
Admin Override
After a stoppage is approved, the admin can override the payment amount for individual workers. This allows for exceptions:
- A foreman who did supervisory work during the stoppage might get their full pay
- A worker who was already absent might get nothing
- Custom amounts for any other special circumstances
Per-Worker Tracking
Each worker's relationship to a stoppage is tracked individually:
- Affected start date -- when the worker started being affected
- Affected end date -- when the worker stopped being affected (left open if ongoing)
- Payment amount -- the actual amount paid to this specific worker
- Payment percentage -- the percentage used for the calculation
Impact on Payment Cycles
Stoppage payments get folded into the payment cycle calculation:
- They show up in the per-project breakdown
- They contribute to the gross earnings for the cycle
- Daily advances are not given on stoppage days (since the worker did not actually work)
- The stoppage payment takes the place of the normal earnings calculation for that day
Restarting After a Stoppage
An admin can restart a stopped project, which signals that normal operations are back up and running. This does not retroactively change any of the stoppage records -- it just means new attendance can be recorded normally going forward.