You can start reporting to a new manager on Monday and still find requests going to your previous manager on Friday.
That doesn’t necessarily mean your organizational change failed.
In a large environment like CACI, “manager” can exist in more than one context. Your current reporting relationship, project leadership, timekeeping approval structure, training assignments, and individual applications may not all rely on exactly the same record.
The result is a frustrating situation where everyone agrees who your manager is—but one workflow apparently doesn’t.
First Identify What Actually Changed
Suppose you move from Project Alpha to Project Bravo.
Your new manager begins assigning work immediately. Your team recognizes the change, and your new project is active.
But a request still routes to your previous manager.
Before trying to fix your entire employee profile, determine whether the problem is limited to that particular workflow.
There is a major difference between:
Your employee record still lists the previous manager
and:
Your employee information is correct, but one application still routes approvals to the previous approver.
The second problem may be application-specific.
Reporting Manager and Project Approver Can Be Different Roles
The person you report to organizationally isn’t necessarily the person responsible for every approval connected to your work.
A project can have its own authorization or approval structure.
For example, your organizational manager might handle one type of employee request while a project lead or designated approver handles another.
That means seeing two different names in different CACI applications isn’t automatically an error.
The question is whether each person is appropriate for the function being performed.
Don’t report a discrepancy solely because two screens display different managers.
Check what each field actually represents.
Effective Dates Matter
Imagine your manager change becomes effective October 15.
A request created October 13 may still belong to the previous approval structure even if you open it again after October 15.
A new request created October 16 might correctly use the new relationship.
This is why dates are important when diagnosing routing problems.
If every request created after the effective date still goes to the old manager, you have a much clearer issue than simply saying:
“I changed managers and something is wrong.”
Record when the organizational change became effective and when the affected transaction was created.
Pending Requests May Not Automatically Move
Suppose you submitted a request on Monday.
On Tuesday, your manager changes.
The request was already sitting in the previous manager’s queue when the change occurred.
Some workflows may continue using the approval route established when the transaction was submitted rather than rebuilding the route every time your organizational information changes.
That can leave an otherwise valid request waiting with someone who no longer manages you.
Don’t automatically cancel and recreate it unless that is the appropriate procedure.
First determine whether the existing request can be reassigned or otherwise handled correctly.
Project Transfers Make the Problem More Complicated
A manager change that occurs together with a project transfer can affect several records at once.
Consider this transition:
October 1 — Project Alpha / Manager A
October 7 — transfer approved
October 14 — Project Bravo effective / Manager B
After October 14, you might correctly see Project Bravo in one place while another workflow still references Manager A.
That doesn’t necessarily mean you’re still assigned to Alpha.
The project record may have updated while the approval relationship used by another application hasn’t caught up.
The reverse can happen too: Manager B appears, but project-related information still reflects the previous assignment.
Treat each mismatch separately.
Don’t Ask the Old Manager to Approve Everything Forever
If the old manager still receives requests, it can be tempting to use that as a permanent workaround.
After all, the approval goes through.
But successful approval doesn’t necessarily mean the routing is correct.
If your reporting or project relationship has officially changed, recurring requests should eventually follow the appropriate current process.
Otherwise, the problem becomes more confusing months later when the previous manager changes roles, leaves the project, or no longer has the relevant authority.
Fix persistent routing problems while the transition is still recent and easy to document.
Check Whether the Problem Affects One App or Several
This is one of the fastest ways to narrow the issue.
Suppose:
Employee information — new manager
Training assignments — new manager
Project information — new assignment
One approval workflow — old manager
That pattern suggests something very different from:
Employee information — old manager
Training — old manager
Approvals — old manager
Project information — old assignment
The first looks isolated.
The second suggests that the underlying transition may not yet be reflected broadly.
Instead of saying “CACI Apps has the wrong manager,” identify which applications or transactions actually show the outdated relationship.
Use Specific Examples When Reporting It
A useful report could look like this:
Manager change effective: October 14
Current manager: Manager B
Affected request: Request submitted October 17
Current routing: Manager A
Other employee information: Already reflects Manager B
That immediately establishes that the request was created after the change and that at least part of the employee environment already recognizes the new manager.
Compare that with:
“My approvals keep going to the wrong person.”
The second description requires someone else to discover almost every relevant detail.
Don’t Recreate Requests Repeatedly
Canceling and resubmitting can occasionally be appropriate, but it shouldn’t become a troubleshooting method.
If the underlying routing information is wrong, five new requests may simply produce five copies in the same old manager’s queue.
You also create additional records that now need to be distinguished from the request you actually want processed.
Confirm the source of the routing issue first.
Verify the Relationship After a Transfer
After a CACI project or organizational move, check the information that affects your actual work rather than expecting every screen to look identical immediately.
Your current assignment should make sense.
Your required approvals should reach the appropriate people.
Training and project responsibilities should correspond to the new role.
And applications that depend on your organizational relationship should eventually stop behaving as though the old assignment is still active.
A manager change is not just a different name displayed on a profile.
If the new reporting relationship is official but transactions created afterward consistently continue routing through the old structure, the approval path—not your request—may be what needs correction.