Skip to main content

πŸ“± Using % Allocation on Mobile with CICO Time

This article explains how % allocation works ONLY on mobile when CICO is used. Desktop workflows behave differently.

Customer Support Team avatar
Written by Customer Support Team
Updated this week

🎯 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

Did this answer your question?