Intake
REQ-0312
Approved under policy
ApprovedPrograms that answer to a customer, an auditor, and a contract.
Defense programs are judged on evidence. Who approved the design review, what the program actually cost against its approved value, which specialist was committed where, and whether the subcontractor deliverable arrived when the schedule said it would. Completix keeps that record as the program runs, not after somebody asks for it.
Ground Sensor Refresh Program
Increment 2 of 4, review scheduled 16 Oct 2026, chair: Program Director
A. Reyes
Engineering authority
ApprovedM. Halstead
Program finance
ApprovedJ. Okafor
Quality and compliance
PendingOutcomes: Approve, Reject, or Need more info.
Reviewers decide under the program's governance policy. Completix records the decision, it does not make it.
Every approval, review, decision, and status report stays attached to the program that produced it, so the answer to a hard question is a lookup, not a reconstruction.
Intake
REQ-0312
Approved under policy
ApprovedBudget
4,850,000
Approved value
EAC 5,142,000Gate
Critical Design Review
Review 16 Oct 2026
AwaitingDecision
D-014
Revised antenna housing
18 Sep 2026Reporting
Aug 2026
Period report
Posted, lockedCapacity
A. Reyes
October allocation
135%Defense and aerospace portfolios carry a kind of scrutiny most industries never see. A program runs for years, is often funded in increments, depends on a supply chain you do not fully control, and has to be explainable to a customer, a prime, and an auditor long after the people who ran it have moved on. Spreadsheets and disconnected scheduling tools survive that for a while, then fail when somebody asks a question nobody kept the evidence for.
Completix is project portfolio management software built for that reality. Demand enters through structured intake and is approved under a policy you define. Approved work moves through governance gate reviews. Cost against approved value, capacity by named person, and the risks, decisions, and status that prove how the program was run all stay attached to the program, in one platform.
It is configured directly by the team that builds it, with no system integrator or reseller in the middle. If you are comparing against heavier legacy platforms, our Planview alternative page covers where each approach fits.
Traceability. Every approval, change, and decision explainable years later, with the evidence still attached.
Cost control against approved value. Forecast and estimate at completion measured against what was approved while there is still time to act.
Scarce technical capacity. Qualified specialists committed across production, qualification, and sustainment at the same time.
Supply chain exposure. Long lead items, single source components, and subcontract deliverables that move the critical path.
Controlled information. Need to know access across primes, partners, and internal teams working the same program.
Defensible reporting. A status record that reflects what was known at the time, not what was reconstructed afterwards.
It is eleven months after the fact. The engineer who raised it has rolled onto another program. The approval lives in an email chain, a meeting minute, and somebody's memory. Reconstructing it costs a week and still leaves gaps.
The program team assembles the trail backwards from whatever survived: inbox archives, minutes on a shared drive, a schedule nobody kept a copy of. The answer eventually arrives, but it is a reconstruction, and reconstructions do not hold up well under questioning.
Decisions are recorded where they are made. The RAID decision log captures the decision, the owner, and the date when the program agrees it, not at audit time.
Gate reviews leave a record. Each gate review holds its criteria, its reviewers, and the outcome, Approve, Reject, or Need more info, decided by people under the program's own governance policy.
Reports become snapshots. Posting a reporting period locks that period's report permanently, so what leadership saw at the time stays exactly as it was.
Evidence sits with the record. Specifications, review packs, and correspondence attach to the project they belong to, and artifact files are versioned, so the review pack from that week is still the review pack.
| ID | Decision | Owner | Date |
|---|---|---|---|
| D-014 | Adopt revised antenna housingApproved at PDR, supersedes baseline rev C | A. Reyes Engineering authority | 18 Sep 2026 |
| D-013 | Defer thermal rework to increment 3Moves out of increment 2 scope | M. Halstead Program finance | 03 Sep 2026 |
| D-012 | Single source long lead connectorsAlternate supplier assessed and declined | P. Ndiaye Supply chain | 20 Aug 2026 |
| D-011 | Extend qualification test windowSchedule rebaselined for increment 2 only | S. Vukovic Program director | 06 Aug 2026 |
| D-010 | Move integration rig booking to NovemberRig shared with a second program | L. Brandt Test and qualification | 22 Jul 2026 |
| Resource | Oct | Nov | Dec | Jan |
|---|---|---|---|---|
ARA. ReyesSystems engineering | 135% | 120% | 88% | 70% |
LBL. BrandtTest and qualification | 80% | 98% | 112% | 92% |
PNP. NdiayeSupply chain | 60% | 65% | 55% | 50% |
JOJ. OkaforQuality and compliance | 90% | 108% | 96% | 75% |
RMR. MarchettiSoftware integration | 70% | 72% | 94% | 118% |
Push qualification start by 3 weeks
Shown hatched on the grid until someone applies the scenario.
Defense portfolios draw on a small population of qualified specialists. The same systems engineer sits on a qualification campaign, a production program, and a sustainment effort at once, and nobody sees the collision until a milestone moves.
Completix tracks allocation per individual, not by role type, so the conflict shows against the person in the month it is created, and the Warning Center can flag over-allocation against triggers you configure. What if modeling lets you test a reshuffle first, shown as modeled until someone applies it.
Allocation is a management view, not an automatic reassignment. Completix shows the contention. People resolve it.
Defense work runs on need to know. A subcontractor needs their workstream, finance needs the money, and a partner on one program has no business in another. Access has to be a structural decision, not a matter of trust.
Subcontractors and partners are added the same way as your own staff, by email address. There is no separate class of outside user to manage.
A person's role controls which projects they can open and what they can do in them, so what someone sees follows from their assignment, not from local convention.
Files attached to a project inherit that project's permissions, so controlled material is governed by the same rule as the record itself.
If your program carries specific handling, hosting, or accreditation obligations, raise them early. We will tell you plainly what we can and cannot support, before a procurement decision rather than after it.
Nobody approved an overrun. It accumulated. A test slip here, a long lead price increase there, two weeks of unplanned integration support. On defense programs the variance is rarely dramatic on the day it appears, which is exactly why it is missed.
The variance is visible while it is still small. Approved value, forecast, EAC, and variance sit on one card, and EAC is calculated automatically.
Actuals move the position as they are entered. The budget updates as actuals go in, so the picture reflects what has been booked, not last quarter's snapshot.
Vendor invoices sit beside the quote. In vendor management, a side by side view with flags makes matching quick. A cost marked to count toward budget flows in automatically, and invoice approval stays in your financial system.
Drift is surfaced, not buried. The Warning Center checks your budget and schedule triggers on every data change and raises breaches for review. It flags the condition, people decide the response.
Funding is decided at approval. Projects start from an approved intake request. Approval follows a policy you define, can route on any field including budget, names its approvers, and logs every action. Nothing releases funds automatically.
Approved (BAC)
4,850,000
Forecast
5,090,000
EAC
5,142,000
Variance
-292,000
Monthly forecast vs actuals
One platform for the portfolio, configured directly by the team that builds it.
Risks, assumptions, issues, and decisions kept as four separate logs, each with owners, dates, and a change history.
Live status until you post a period. Posting locks that report as a permanent snapshot of what was reported.
Quotes and invoices tracked per vendor with a side by side view for matching. Invoice approval stays in your financial system.
Portfolio health, spend, and schedule position read from the live project records instead of collected by email every Friday.
Budget, schedule, and resource over-allocation triggers you configure are checked on every data change. Breaches are surfaced for people to review.
Critical path calculated automatically, schedule history with restore points, and MPP import and export for existing program schedules.
The governance problem looks different in every industry. These pages cover how the same platform is applied elsewhere.
Government and Public Sector
Procurement defensibility, audit trails, and multi year budget cycles.
Manufacturing
Capital project contention and plant resourcing constraints.
Engineering
Multi discipline programs and capital intensive delivery.
IT
Application portfolios, transformation programs, and IT demand.
Banking and Financial Services
Regulatory change portfolios and risk posture reporting.
Professional Services
Client delivery, utilization, and billable capacity planning.
Education
Grant funded portfolios and term based delivery cycles.
Marketing
Campaign portfolios, creative capacity, and spend visibility.
It is software that manages a defense organization's programs as a portfolio rather than as isolated projects. One platform holds intake and approval, cost and forecast, resource capacity, risks and decisions, and reporting. For defense the value is less about task tracking and more about traceability: being able to show what was approved, by whom, against what evidence, at any point in a multi year program.
Traceability comes from recording decisions where they happen. RAID logs hold risks, assumptions, issues, and decisions as four separate logs with owners, dates, and a change history of who changed what and when. Gate reviews hold their criteria, reviewers, and outcome, and artifact files are versioned. Posting a status report period locks a permanent snapshot of what was reported. Approvals are human decisions under your own policy: Completix records the decision and the evidence behind it, and does not make the decision or escalate automatically.
Yes. Resource allocation is held against named individuals across every project they are committed to, so contention shows against the person in the month it is created. The Warning Center can flag over-allocation based on triggers you configure, and scenario planning lets you model a reallocation, shown as modeled, before anyone applies it. Completix surfaces the conflict and the options. The reassignment stays a management decision.
Completix tracks budgets by fiscal year, at portfolio level and line of business level, with approved value, forecast, EAC, and variance for each project. You select a fiscal year and see that year's numbers, so a program funded in increments can be reviewed one year at a time. Funding is decided at intake approval under a policy you define, and Completix never releases funds automatically.
Vendor tracking holds quotes and invoices per vendor, with a side by side view and flags to speed up matching. Marking a cost to count toward budget is a manual action, and once recorded it flows into the budget automatically. Invoice approval itself stays in your own financial system. Subcontractor staff are added as users by email, and their role controls which projects they can open. Supply chain risks and decisions live in the same RAID logs as the rest of the program.
No, and we say so plainly. Completix is a cloud service, and it is not offered as accredited for classified processing. What it does provide is need to know separation: people, including partners and subcontractors, are added by email with a role that decides which projects they can open, and documents follow the access of the project they are attached to. If your program has specific handling, hosting, residency, or accreditation obligations, raise them at the start of the evaluation and we will tell you directly what we can and cannot support.
Completix supports MPP file import and export, so existing program schedules can be brought in and shared back out. This is a file level exchange, not a continuous two way sync. For programs managed directly in Completix, project scheduling calculates the critical path automatically and keeps schedule history with restore points.
Typical enterprise PPM platforms are capable and can suit the largest primes with dedicated tool administrators. The commonly reported trade off is cost, configuration depth, and implementation through a partner or integrator. Completix is configured directly by the team that builds it and is aimed at organizations that want portfolio governance without a heavy implementation program. Our nine platform comparison goes through where each approach fits, including where the incumbents are stronger.
Not a generic feature tour. Walk us through one of your programs, its gates, its subcontractors, and its people constraints, and we will show you the record it would leave behind. If you share your own project data, we can build the demo around it.