Completix

Intake Management

Every idea wants to be your next project. Few should be.

Intake is where your portfolio is really decided. Completix gives every request one front door, a complete record, a clear status, and an approval it cannot skip, so the right work proceeds and nothing slips through on a hallway yes.

Project Intake
Open 2 Pending 1 Need more info 1
ActiveCompletedAll
New Project Request
ERP System Upgrade
Feb 19, 2026
Open
Budget$520,000
TimelineFeb 4 - Jan 29
...
Customer Portal Redesign
Feb 18, 2026
Need more info
Budget$640,000
TimelineApr 1 - Sep 30
...
Data Warehouse
Feb 19, 2026
Pending
Budget$250,000
TimelineFeb 18 - May 18
...
Mobile App Refresh
Feb 11, 2026
Open
Budget$90,000
TimelineMar 3 - Jun 3
...
One path for every request

From request to approved, on one board

Whatever comes in, comes in here. Every request moves through the same states, visible to everyone, until it is approved or returned.

Open

Request created

A new request opens with its details and description.

Submitted

Submitted for approval

The requester sends it on, and policy routes it to the right approver.

Pending

With an approver

It sits with the named person to review, not in an inbox.

Approved

Cleared to proceed

An explicit decision, recorded against the request.

Need more info

Not ready? An approver returns it as Need more info, back to the requester with a reason, instead of a silent no.

Anatomy of a request

A complete record, before it can move

A request is not a one-line idea. It carries a description, attachments, and a full set of details, and it cannot proceed until someone submits it for approval.

  • Details that frame the decision: project type, priority, planned start, duration, proposed budget, customer, and sponsors.
  • Description and attachments live on the request, so the context travels with it instead of in someone's inbox.
  • Requested By is captured and a comments thread keeps the back-and-forth in one place, on the record.

Submit for Approval is the gate. Until a request is submitted, it does not advance, and the person who submits is not the person who approves.

Customer Portal RedesignMar 20, 2026
… ×
Description
Replace the legacy customer portal with a unified self-service experience. Cuts inbound support volume and supports the FY26 customer-experience objective.
Attachments 1+ Attach file
Business_Case.pdf
Comments
R. Chen 2d
Added the vendor quotes and the draft timeline.
Type a message…
Send
Details
StatusOpen
Requested ByR. Chen
Project TypeDigital Transformation
PriorityHigh
Planned Start01 Apr 2026
Duration6 months
Proposed Budget$640,000
CustomerRetail Division
SponsorsM. Adeyemi
Request Submission Required
Submit this request for approval when you're ready to proceed.
Submit for Approval
Policy-based approval

The bigger the ask, the higher the sign-off

Define your approval rules once. When a request meets a condition, like a proposed budget over a threshold, Completix routes it to the approver that rule names, so a $50k request and a $5M request never get the same level of sign-off.

Build rules on budget thresholds, project type, or priority, and point each one at the approver who should own it: a portfolio manager, an IT steering committee, or the CFO.

The rule decides who approves, not whether it is approved. The named approver still makes the call, and a default approver catches anything no rule matches, so nothing stalls.
Approval RulesAdd rule
When Proposed Budget is greater than $500,000
approval fromCFO
Matched, this $640,000 request routes to the CFO
When Project Type is Infrastructure
approval fromIT Steering Committee
When Priority is Critical
approval fromExecutive Sponsor
Otherwise, route to Intake Approvers (default)
The decision

Submitted is not the same as approved

Once a request is routed to its approver, it sits with a person, not in limbo. The decision is explicit, and so is the record behind it.

A hallway yes

No structure

  • A verbal go-ahead, no defined approver, no written reason.
  • A $5M request waved through by whoever was in the room.
  • When it fails, nobody can say how it was approved.
Decision recordNo record found.
A decision on the record

With Completix

  • The approver your policy named approves, holds, or returns it.
  • The requester, sponsors, details, and comment history travel with it.
  • The status is on the board for everyone to see, not in a side channel.
Status: Approved$640,000 request · routed to the CFO by policy · decided by the named approver

To be clear: a person approves, Completix does not. The platform routes the request to the right approver, holds the status, and keeps the record. The decision stays human.

What's included

Built for PMOs that need more than a ticketing system

Six things every request gets, designed around how a real approval decision gets made.

01

A structured request record

One description, with attachments, so context lives on the request itself.

Nothing in inboxes
02

A consistent Details panel

Project type, priority, planned start, duration, proposed budget, customer, sponsors.

Comparable requests
03

A submit-for-approval gate

A request does not advance until it is submitted, and approval is a separate step.

No hallway approvals
04

Policy-based approval routing

Rules send each request to the right approver by budget, type, or priority. People still decide.

Right approver, every time
05

One board, clear statuses

Open, Pending, and Need more info across Active, Completed, and All, with search and filters.

Visible at a glance
06

Comments and accountability

A comment thread plus Requested By and Sponsors, so the conversation stays on the record.

Always traceable
Ready when you are

Give every request a front door it cannot skip

Completix replaces informal intake with one board, one complete record per request, and approvals routed to the right people by your own rules. The right work proceeds, and every decision stays on the record.

Book a Demo
Start free. No credit card, no implementation project required.

Recommended Resources