If you’ve worked in Leidos Prism, you’ve likely seen this status:
Returned. Rejected. Sent back.
And it almost always happens at the worst moment.
You’ve already:
- filled everything out
- double-checked details
- submitted the requisition
And then it comes back.
The immediate reaction
Most users think:
- “What did I miss?”
- “I already checked everything.”
- “Why didn’t it catch this earlier?”
And that’s where frustration starts.
The key misunderstanding
People assume Prism validates everything before submission.
It doesn’t.
What actually happens
Leidos Prism performs two types of validation:
1. System validation (before submission)
- required fields
- format checks
- basic logic
2. Human validation (after submission)
- compliance
- classification accuracy
- procurement correctness
- policy alignment
And this is where most rejections happen
Not because something is missing.
Because something is not aligned.
Real rejection reasons (most common)
| Issue | Why it gets returned |
|---|---|
| Wrong commodity/category | Doesn’t match procurement rules |
| Supplier mismatch | Not aligned with approved vendor |
| Funding inconsistency | Doesn’t match allocation logic |
| Description unclear | Not sufficient for approval |
Real scenario
You create a requisition.
Everything is filled.
System accepts it.
You submit.
Then it comes back
With a comment like:
- “Please revise category”
- “Clarify supplier selection”
- “Update funding detail”
Why this feels frustrating
Because:
You weren’t told this upfront.
The hidden problem: Prism doesn’t teach you — it checks you
It doesn’t guide you through correct logic.
It waits until submission and then evaluates.
So you end up in a loop
Submit → rejected → fix → resubmit → re-check → repeat
And that wastes the most time
Not initial entry.
But rework.
Why small mistakes become big delays
Because every return means:
- re-opening request
- re-checking entire structure
- waiting again for approval
What actually reduces rejections (real approach)
1. Think like an approver
Before submitting, ask:
“Does this make sense from a compliance perspective?”
Not just:
“Did I fill all fields?”
2. Don’t rely on system validation
System checks completeness.
Approvers check correctness.
3. Be precise with classification
Categories and procurement types matter more than users expect.
4. Write clear descriptions
Approvers rely on:
- context
- clarity
- justification
5. Review dependencies, not just fields
Check how:
- supplier
- funding
- category
connect together.
Real behavior difference
| User type | Outcome |
|---|---|
| Field-focused | More rejections |
| Logic-focused | Fewer returns |
FAQ
Why was my request rejected in Leidos Prism?
Because it didn’t align with procurement or compliance rules.
But everything was filled — why rejected?
Because correctness ≠ completeness.
How do I avoid rework?
Think beyond fields — think about structure and logic.
The key insight
Prism doesn’t fail your request.
It exposes what wasn’t aligned.
Final thought
You don’t lose time because of errors.
You lose time because those errors are only visible after submission.
And the only way to fix that is to think like the system
before the system checks you.