A rejected timesheet doesn’t necessarily mean your total hours are wrong.
You can have exactly 40 hours recorded, every workday filled in, and still have the timesheet returned for correction.
In a government contracting environment like CACI, the total is only one part of the record. The project, charge authorization, dates, allocation of hours, comments or supporting information, and approval path can matter just as much.
The useful question after a rejection is therefore not “How do I get it approved?”
It’s “Which part of the submitted record is incorrect?”
Start With the Rejection Reason
Don’t immediately edit numbers just because the timesheet came back.
First determine what was actually rejected.
A reviewer might be questioning:
- a charge code;
- hours assigned to the wrong project;
- an incorrect date;
- time recorded against an inactive assignment;
- missing information required for a correction;
- the way non-project activity was recorded.
Those are completely different problems.
If your 40-hour total is correct, randomly changing hours to make the timesheet “look different” can turn one error into several.
Correct Hours Can Still Be Charged Incorrectly
Suppose your week shows:
| Activity | Hours |
|---|---|
| Project Alpha | 40 |
| Total | 40 |
But on Thursday you actually spent two hours completing an authorized internal requirement rather than performing Project Alpha work.
The weekly total remains 40.
The allocation may not.
The accurate record might instead require something like:
Project Alpha — 38 hours
Authorized non-project activity — 2 hours
The exact applicable codes depend on the assignment and instructions you’ve been given, but the principle is simple: the timesheet needs to represent what happened, not merely reach the expected weekly total.
Check Whether a Project Changed During the Week
Project transitions are an easy place to create a rejection.
Imagine your new assignment became effective Wednesday.
You recorded:
Monday–Friday: New Project — 40 hours
But you were still working under the previous assignment on Monday and Tuesday.
If those first 16 hours belonged to the previous authorized work, moving the entire week to the new project because you submitted the timesheet on Friday doesn’t make the record accurate.
Look at the actual effective date.
A timesheet covers a period of work. It isn’t simply a snapshot of whatever assignment you happen to have on submission day.
Don’t “Fix” a Rejection by Moving Time Somewhere Convenient
Suppose eight hours are rejected because the expected project code wasn’t available.
You notice another active code in the system and move the hours there.
The timesheet now submits successfully.
That doesn’t mean it has been corrected.
A code being selectable doesn’t establish that it is authorized for the work you performed.
If you don’t know where the hours belong, preserve the facts:
Date
Number of hours
Work performed
Project supported
Expected assignment
Then obtain the appropriate instruction.
The objective is an accurate labor record, not simply a timesheet that passes system validation.
Corrections Should Preserve What Actually Happened
A correction is not an opportunity to reconstruct the week into something cleaner.
If you worked 7.5 hours on one activity and 0.5 on another, don’t change it to 8.0 on the first activity merely because the second entry is causing a problem.
Likewise, don’t shift Monday’s work to Tuesday just to make daily totals easier.
Correct the specific error while leaving accurate entries alone.
This matters especially when a rejected timesheet contains only one questionable line among dozens of correct ones.
A Changed Manager Can Affect the Approval Path
Sometimes the underlying hours aren’t the problem at all.
If you recently moved between CACI projects or reporting structures, your timesheet may be interacting with an outdated approval relationship.
Your operational manager may already have changed while an employee or project record still reflects the previous arrangement.
If the issue appears to be routing rather than time allocation, don’t rewrite valid work entries merely to see whether the timesheet goes somewhere else.
Identify the routing discrepancy.
For example:
“My Project B assignment became effective October 12, but the submitted timesheet is still associated with the previous approval structure.”
That is much more actionable than repeatedly resubmitting the same record.
Pay Attention to Corrections Made After Submission
Finding an error before submission is straightforward: correct it before you certify the record.
Finding it afterward can require a formal correction process.
Don’t compensate for an old error by modifying a future timesheet.
If two hours were incorrectly recorded last week, subtracting two hours from this week doesn’t repair last week’s record.
Now both weeks are inaccurate.
The correction should point back to the period containing the original mistake and follow the applicable process.
Keep the Explanation Specific
If a correction requires an explanation, describe what changed rather than writing something vague like:
“Fixed time.”
A useful explanation identifies the actual correction:
“Two hours originally recorded to Project A on October 14 were associated with the wrong authorized activity; allocation corrected.”
The exact level of detail required can depend on the applicable CACI timekeeping process, but a correction should make sense to someone reviewing it later.
Avoid unnecessary narratives. State the factual reason for the change.
Recheck the Entire Day After Making a Correction
Changing one line can accidentally create another problem.
Before resubmitting, recalculate the affected day.
Suppose Monday originally showed:
Project A — 8.0 hours
You determine that 1.5 hours belong elsewhere and add a new 1.5-hour entry.
If you forget to reduce Project A to 6.5, Monday now contains 9.5 hours.
The classification problem may be fixed, but the daily total is wrong.
After every correction, verify both dimensions:
Are the hours allocated correctly?
Does the total still represent the time actually worked?
Rejected Does Not Mean “Make It Different”
A rejection is feedback that something in the submitted record requires attention.
It is not an instruction to experiment until the system accepts the timesheet.
Read the reason, compare it with the work you actually performed, correct the specific discrepancy, and follow the applicable CACI procedure when the right charge or approval path isn’t clear.
A good correction should be explainable in one sentence:
This is what I originally recorded, this is what was wrong, and this is what the accurate record should show.
That is far more important than simply turning Rejected into Submitted.