If you’ve used Leidos Prism, you’ve probably had this exact moment:
You complete a requisition.
You review everything carefully.
You click Submit.
And you expect the process to move forward immediately.
But instead, nothing seems to happen
Status changes.
But progress?
Not obvious.
The assumption most users make
“Submitted” = request is moving through approvals.
But in Prism Leidos, that’s not always true.
What “Submitted” actually means
It does NOT mean:
- approvals started
- request is actively progressing
- everything is validated
It simply means:
➡️ your request has entered the workflow system
What happens next (real internal flow)
After submission, the system does several things before approvals even begin:
- Internal validation checks
- Routing logic determination
- Assignment to approval chain
- Queue placement
Where delays actually occur
| Stage | What users think | What actually happens |
|---|---|---|
| Submitted | Process started | Pre-routing validation |
| Routed | Active review | Assigned but not opened yet |
| In approval | Immediate action | Waiting in queue |
Real scenario
You submit a requisition in Leidos Prism.
You check back later.
Status is still:
“Submitted” or “Pending”
What you assume
“It’s stuck.”
What’s actually happening
Your request is:
- waiting to be routed
- waiting in someone’s queue
- pending system-level validation
The hidden complexity: approval chains are dynamic
Approval paths in Prism are not fixed.
They depend on:
- contract type
- funding source
- dollar amount
- department rules
Which means
Two similar requests can have completely different workflows.
Example
Request A:
- low value
- standard supplier
➡️ quick approval
Request B:
- higher value
- different category
➡️ multiple approvals required
Why this creates confusion
Because the system doesn’t clearly show:
- where exactly your request is
- who has it right now
- why it hasn’t moved
So users do this
- refresh repeatedly
- open request multiple times
- assume something failed
The real issue isn’t delay
It’s lack of visibility
What actually helps (practical behavior)
1. Stop expecting instant movement
Submitted ≠ active processing.
2. Understand approval dependency
Movement depends on:
- assigned approvers
- queue priority
- workload
3. Check status intelligently
Don’t just look at label.
Look at:
- timestamps
- last activity
- routing stage
4. Avoid repeated checking loops
Checking 10 times won’t speed anything up.
The real behavior loop
Submit → check → no change → doubt → re-check → frustration
Why experienced users feel less friction
Because they:
- understand delays are normal
- don’t expect immediate updates
- check less frequently
FAQ
Why is my request stuck on “Submitted” in Leidos Prism?
It’s likely in validation or routing, not yet in active approval.
Does submitted mean someone is reviewing it?
No — not necessarily.
How long should it take?
Depends on workflow complexity and approval chain.
The key insight
Prism Leidos doesn’t show real-time progress clearly.
It shows states — not movement.
Final thought
Your request isn’t stuck.
It’s just moving through steps you can’t see.
And understanding that removes most of the frustration.