Completix

Contact
Project intake management

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

Give every project idea one front door, the same information to judge it by, and a recorded decision from the people your policy names.

Book a demo Follow one request
Project Intake
Open 2Pending 1Need more info 1
ActiveCompletedAll
New Project Request
Customer Portal Redesign
Mar 2, 2026
Need more info
Budget$640,000
TimelineApr 1 - Sep 30
...
ERP System Upgrade
Feb 19, 2026
Open
Budget$520,000
TimelineMay 4 - Jan 29
...
Data Warehouse
Feb 26, 2026
Pending
Budget$250,000
TimelineApr 6 - Jul 31
...
Mobile App Refresh
Feb 11, 2026
Open
Budget$90,000
TimelineMar 16 - Jun 12
...
Need more infoMar 5, 2026
Customer Portal Redesign
Returned by D. Okafor, CFO

“Please attach the vendor quotes before I review.”

Back with R. Chen to update and submit again

One project intake path, from first idea to a recorded decision.

Every request moves through the same statuses, with a named person responsible at each step. Nothing advances on a hallway conversation.

Open

Request created

The requester completes the intake fields and adds a description and attachments.

Submit for Approval

Submitted

Nothing enters approval until someone submits it. Submitting starts the policy routing.

Pending

With the named approvers

Your approval policy picks the approvers from the request's intake fields. Several approvers review in parallel, and all must approve.

Decision

A person makes the call

ApprovedCleared to proceed
RejectedClosed, on the record
Need more infoBack to the requester

Every step is logged on the request. Who submitted it, who approved it, rejected it, or asked for more information, and when, all viewable from the request itself.

When it arrives

The idea arrives as a complete request, not an email thread.

R. Chen in the Retail Division wants to replace the customer portal. Without a front door, that idea shows up as a few emails and a hallway chat, with no budget, no sponsor, and nothing anyone can compare. In Completix it arrives as one request, with the same fields as every other request.

Inbox3 unread
RC
R. ChenMon
Portal idea, can we talk this week?
Thinking we replace the customer portal before Q3...
MA
M. AdeyemiTue
RE: RE: Portal idea
Budget? No idea yet, maybe ask Finance.
RC
R. ChenWed
Fwd: vendor deck
Attached. Not sure who needs to sign off.
No budget captured No sponsor confirmed No decision recorded
Today: the idea lives in inboxes.
Customer Portal RedesignMar 2, 2026
… ×
Description
Replace the legacy customer portal with a unified self-service experience, to cut inbound support volume for the Retail Division.
Attachments 1+ Attach file
Business_Case.pdf
Comments
R. ChenMar 2
Added the business case and a 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
In Completix: one record, ready to submit.
  • Details that frame the decisionProject type, priority, planned start, duration, proposed budget, customer, and sponsors, the same on every request.
  • Context on the recordThe description, attachments, and comment thread stay on the request instead of in someone's inbox.
  • A deliberate submit stepNothing enters approval until someone selects Submit for Approval, which starts the policy routing.
Project Intake ApprovalRoute project requests to the right approvers based on request attributes
Add ruleActive
Default Approvers1
Rule 12
Conditions
BudgetGreater than$500,000
And
TypeIsDigital Transformation
Add condition
Approval required from
Members2DOLM
Groups
Delete rule
Rule 23
Rule 31
Last modified: Feb 20, 2026 at 04:04 PM by K. Walsh
When it is submitted

A $640,000 request lands. Your policy decides who signs off.

R. Chen submits the request. Completix checks it against your approval rules and sends it to the approvers the matching rule names. This one is a Digital Transformation request over $500,000, so it goes to both the CFO and the CIO. They review in parallel, and it is approved only when both approve.

A policy holds as many rules as you need. Each rule combines intake fields, such as budget, project type, priority, or customer, with AND and OR conditions, and names the members or groups whose approval is required. That is how organizations with tightly delegated authority, such as those working to public-sector approval thresholds, keep every sign-off at the right level.

The rule picks the approvers, never the outcome. If your policy names the person who submitted the request, they approve it like any other named approver, and the log shows exactly that.

When someone asks later

Months later, someone asks how it was approved. The answer is on the request.

An auditor, a new finance lead, or a sponsor who was not in the room opens Customer Portal Redesign and sees its full history: who submitted it, who asked for more information, and each approver who signed off, with dates. It is the same record that supports your portfolio governance.

Customer Portal RedesignHistory
Approved
Mar 12, 2026
ApprovedD. Okafor, CFO, second of two approvals
Mar 11, 2026
ApprovedL. Moreau, CIO
Mar 9, 2026
Submitted for approvalR. Chen
Mar 5, 2026
Need more infoD. Okafor, CFO
Mar 3, 2026
Submitted for approvalR. Chen
Mar 2, 2026
Request createdR. Chen
Logged as each step happens

Without a front door

  • A verbal yes, with no named approver and no written reason.
  • A $5M request waved through by whoever was in the room.
  • A year later, nobody can show how it was approved.

With Completix

  • The approvers your policy names each approve, reject, or ask for more information.
  • The details, attachments, and comments stay on the request.
  • Each step is logged with who and when, viewable from the request.

What every intake request gets

Intake is part of the Completix PPM platform, built for PMO teams that need more than a ticketing system.

A structured request record

The description and attachments live on the request, not in inboxes.

Context stays attached

The same intake fields every time

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

Comparable requests

A deliberate submit step

Nothing enters approval until someone submits it for approval.

No hallway approvals

Approval rules on intake fields

Combine budget, project type, priority, customer, and other fields with AND and OR, and name one approver or several.

The right approvers

One intake board

Open, Pending, and Need more info at a glance, across Active, Completed, and All.

Visible at a glance

A complete decision history

Every submission, approval, rejection, and request for more information, with who and when.

Always traceable

Project intake, common questions

What counts as a project request in Completix?

Any new project idea, whether it comes from a business unit, IT, or an executive sponsor. Each one is captured with the same intake fields, including description, proposed budget, timeline, and sponsors, so every request is judged on the same basis.

The approvers your approval policy names for that request. A rule can name one approver or several; when it names several, they review in parallel and the request is approved only when all of them approve. Completix routes the request when it is submitted, and every decision is made by a person.

The request's intake fields, combined with AND and OR conditions. Proposed budget is one of them, alongside fields such as project type, priority, and customer, so routing reflects how your organization actually delegates authority.

Then they approve it like any other named approver. Your policy decides who approves, and the log records who submitted and who decided, so the situation is visible to anyone who reviews the request later.

Yes. Submissions, approvals, rejections, and requests for more information are logged with who acted and when, and the history is viewable from the request itself.

No. Every approval, rejection, or request for more information is made by a person. Completix routes the request, holds its status, and records the decision.

Turn incoming demand into governed decisions.

Give your PMO one structured process for capturing, routing, and deciding on new work, with every decision on the record.

Book a demo Talk to us

Recommended Resources

excel portfolio

Why Excel Fails at Portfolio Management

Spreadsheets are how almost every PMO starts, and how a portfolio quietly loses visibility, accountability, and trust as it grows. Here’s where the breakdown happens.

critical decisions

Structured Project Management: Pillars & Pitfalls

Structured project management means consistent, auditable decisions across intake, prioritization, governance, and delivery, not more paperwork. See where ad hoc tools break down and what holds up under real deadlines, funding limits, and audits.