Moving to another project inside CACI can look deceptively simple. Same employer, same employee record, maybe even the same office—just a different team.
Operationally, it can be a much bigger change.
A new assignment can affect your manager, charge codes, labor category, work location, schedule, required training, and the systems you’re authorized to use. The most important piece is the effective transition date, because that separates work belonging to the old assignment from work belonging to the new one.
Helping Another Team Is Not Automatically a Transfer
There’s an important difference between temporarily supporting another project and actually moving to it.
Suppose your current project needs less support this week, so you spend six hours helping another CACI team.
That doesn’t necessarily mean your primary assignment has changed.
You may simply have work that needs to be recorded against a different authorized activity while your existing project remains your normal assignment.
A formal move is different. It establishes that the new project becomes your assignment from a particular date.
Don’t infer a transfer solely from the fact that another manager started giving you work.
Get the Effective Date Straight
Consider a transition effective October 14.
You work:
October 12 — old project
October 13 — old project
October 14 — new project
October 15 — new project
October 16 — new project
The fact that all five days fall within one workweek doesn’t mean they belong under the same project information.
This becomes especially important for timekeeping.
If the new assignment begins Wednesday, don’t move Monday and Tuesday’s hours to the new project simply because you’re completing the timesheet after the transition.
The work should reflect where it actually occurred.
Your Charge Authorization May Change
A project transition frequently means the charge structure relevant to your work changes as well.
Old charge codes shouldn’t be reused automatically because they remain familiar or visible.
Likewise, don’t assume the new project’s code applies before its authorized effective period.
Suppose you worked:
Old assignment — 16 hours
New assignment — 22 hours
Required internal activity — 2 hours
The weekly total is 40 hours, but those hours may need three different authorized classifications.
Putting everything against the new project gives you the right total and the wrong allocation.
If the new code isn’t available when authorized work begins, raise the issue rather than substituting another convenient code.
Labor Category Is Not Just Your Job Title
Government contracting adds another distinction that can be easy to overlook.
Your internal CACI title and the labor category associated with a particular contract aren’t necessarily the same thing.
A contract can define labor categories around specific qualifications, experience, education, or contractual requirements.
Moving to another project therefore doesn’t always mean every classification from the previous contract follows you unchanged.
If the new assignment has specific requirements, make sure the administrative transition reflects the arrangement you were actually offered.
Don’t assume that because both teams casually call the role “Systems Engineer,” every underlying project designation must be identical.
System Permissions Don’t Automatically Follow You
You had access to Project A’s applications yesterday.
Today you officially move to Project B.
That doesn’t mean every Project A permission should remain indefinitely, nor does it mean every Project B permission appears instantly.
Application access can depend on the assignment itself, authorization, account provisioning, training, and need-to-know requirements.
This creates a common transition period where your employment move is complete but one of the required systems still isn’t ready.
Report the missing application specifically.
“Nothing works” isn’t useful.
“My Project B assignment became effective October 14, but I still don’t have the application required for task X” gives support and management something concrete to investigate.
Training Can Change With the Assignment
A new project may bring requirements that weren’t relevant to the previous one.
That can include customer-specific procedures, information-security requirements, project training, or other mandatory material.
Previously completed company-wide training doesn’t necessarily satisfy every requirement associated with a new assignment.
At the same time, you shouldn’t automatically repeat every course you’ve ever taken just because you changed projects.
Check what is actually assigned and whether an existing valid completion is recognized.
If a course suddenly appears overdue immediately after the transfer, verify the requirement and completion record before blindly taking the same training again.
Manager and Administrative Records Can Update at Different Times
Your operational reality can change before every employee-facing record catches up.
You may already report to the new project manager while an older manager still appears somewhere in the employee environment.
A short synchronization delay isn’t automatically evidence that the transfer failed.
But outdated reporting information becomes a real problem if approvals, time records, training, or other workflows continue routing to the wrong person.
That’s when the discrepancy needs correction.
Be precise about the field and effective date rather than simply reporting that your profile “still looks old.”
Don’t Abandon the Old Assignment Early
A new project manager may want you immediately.
That doesn’t automatically erase existing responsibilities.
If the official transition is Friday, work assigned through Thursday still belongs to the previous arrangement unless management establishes something different.
This is particularly important when both projects are trying to schedule the same employee during the transition.
You shouldn’t personally solve that conflict by deciding which manager’s work seems more important.
Get a clear transition decision.
Check the New Assignment After the Move
Once the transition is effective, several things should make sense together:
Current project or organizational assignment
Manager/reporting relationship
Authorized charge information
Applicable labor classification
Required applications
Required training
Work schedule and location, where relevant
They don’t necessarily live in one CACI Apps screen, and they may not update simultaneously.
That’s exactly why the effective date is so useful. It gives you a reference point for deciding whether a record reflects the old arrangement or the new one.
Moving between CACI projects isn’t simply changing the name of the customer on your profile.
The old work has to end correctly, the new work has to begin under the right authorization, and your time, systems, and project requirements need to follow the assignment you’re actually performing.