π― Overview
When workers clock in using the mobile Kiosk (CICO), all of their time is assigned to the project they clocked into. Rhumbix treats that time as a project bucket, and all % allocations must stay inside that bucket.
If you add cost codes from another project, you can still assign time to them β but not using % allocation. You will need to type the hours manually for those.
π¨ How Percentage Allocation Works on Mobile
Action | What Happens |
Worker clocks in on Project A | β All time goes into Project A's bucket |
Foreman adds cost codes from Project A | β Can use % OR manually type hours |
Foreman adds cost codes from Project B | β % will NOT apply because there is no CICO time in Project B |
Foreman wants time on Project B | β Must enter hours manually β % does not move time to another project |
π§ Key Rule to Communicate to Crews
If you clock in on Project A, you only have time in Project Aβs bucket.
So all % splits must stay on Project A β
thereβs no time in Project B to apply a percentage to.
To give time to Project B, type the hours in manually.
You do not have to use percentage on the CICO project β entering hours is always allowed.
π· Mobile Example
Your worker clocked in on the Kiosk and Rhumbix recorded 8 hours on Project A.
You open the Rhumbix app to create the timecard and add:
β Cost Code 1 (Project A)
β Cost Code 2 (Project A)
β Cost Code 3 (Project B)
What You Want To Do | What Works |
Split time on Project A | β % or manual entry both work |
Give some time to Project B | β Manual hours only β % wonβt apply |
Try % allocation on Project B | π« Nothing happens β no time exists in that project bucket |
π‘ Best Practice Recommendation
Scenario | Best Action |
All work was on one project with one CICO | β Use % OR manual β both are fine |
Work was split between two projects | π§ Consider separate CICO clock-ins OR use manual hour entry for the second project |
Crew wants quick split between codes on one CICO project | π % is a fast option |
Crew needs precise control | β Manual entry gives full control β even on the CICO project |
β Common Misunderstanding to Avoid
βI put 50% on Project B, but it didnβt move any time.β
β Thatβs expected β you didnβt clock in on Project B, so Rhumbix has no time there to split.
π Solution: Enter the time manually or clock in on that project separately.
π§ Quick Reminder for Foremen to Share with Crews
% = Split time where you clocked in
βManual hours = Move time anywhere you need
β Summary
Method | Works on CICO Project | Works on Other Projects |
% Allocation | β Yes | π« No |
Manual Hour Entry | β Yes | β Yes |