CEDX 2026 Delivery Release: Resource capacity, sprint velocity, billable PSA timesheets, and milestone invoicing on one graph Explore the CEDX Resourcing architecture ->
CEDXSystems
EnglishTalk to sales
PROJECTS & DELIVERY CEDX Resourcing
Overview Capacity People Workflow & Tour Operators TCO Model 14-Day Sandbox Live build ↗
PROJECTS & DELIVERY CEDX Resourcing · Projects & Delivery · resourcing.cedxsystems.com

Who is on what and what it costs.

Resourcing plans people against weeks: 1,124 hours planned for W31 against 932 hours of capacity, ten people over 100%, the bench priced at $107K of idle cost. The over-allocation is on the grid before it is in the exit interview.

Open live CEDX Resourcing -> Inspect 4-screen build tour
24 people on the roster 149% avg utilisation 424h over-hours to rebalance Zero-ETL Shared Postgres Record
CEDX Resourcing Enterprise Architecture Briefing
CEDX Resourcing · 24 people on the roster

"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."

Arjun Patel · SVP of Global Operations · Keystone Logistics · 0.01s Canonical Sync
CEDX Resourcing reads and writes the exact same canonical Postgres record as CEDX Timesheets, CEDX Services, and CEDX Roadmap with zero third-party webhooks.
🔒 https://resourcing.cedxsystems.com/workspace/live
CEDX Resourcing · Overview (The week's load, scored)
resourcing.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/resourcing ↗
PEOPLE ON THE ROSTER
24
12 delivery · 4 advisory · 4 platform
AVG UTILISATION
149%
people with load, W31
OVER-HOURS TO REBALANCE
424h
across 10 over-capacity people
UNFILLED DEMAND
129h/wk
6 placeholders, P0 to P2
Program / Client Engagement Milestone & Sprint Phase Delivery Principal Budget / Billable Margin Capacity Utilization Delivery Health
Meridian Global ERP RolloutCEDX Resourcing · Record #1040 Phase 03 · Data Migration K. Vance · Principal Architect $680,000 · 44% Margin ● 88.5% Billable Util On Schedule
Q4 Core Kernel Release v4.8CEDX Resourcing · Record #1041 Sprint 22 · 64 Story Points A. Rostova · Staff Eng Lead 18 Engineers Allocated ● 92.0% Sprint Velocity Zero Blockers
Harbor Retail POS DeploymentCEDX Resourcing · Record #1042 180 Stores · Wave 2 Cutover M. Okafor · Program Dir $510,000 · 41% Margin ● 85.2% Field Capacity Milestone Billed
SOC-2 & ISO Continuous AuditCEDX Resourcing · Record #1043 Control Evidence Automation R. Lin · Security PMO $140,000 Internal Cap ● 100% Evidence Linked Audit Ready
✦ CEDX Resourcing Copilot · Meridian Global ERP Rollout
Overview Verified
Planned 1,124h against 932h of capacity, average utilisation 149% among people with load, 178 person-week conflicts scored with 20 rated high. The alerts name names: one senior consultant at 128% (52h planned on 40h) and leave colliding with a cutover, 24h confirmed plus 18h tentative while away.
CEDX Resourcing operator workspace in natural daylight
FIELD DOCUMENTARY · PROJECTS & DELIVERY

The person-by-week grid admits the collision

The grid does the thing spreadsheets hide: one consultant's W31 cell reads 320%, four jobs, one person, same week. You cannot fix what you cannot see, and this you can see from across the room.

CAMERA: CANON EOS R5 · 35MM F/1.4 · NATURAL DAYLIGHT ESTATE ROUTE: /APP/RESOURCING
CORE CAPABILITIES · CEDX RESOURCING

Three architectural jobs CEDX Resourcing gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · PROJECTS & DELIVERY FOUNDATION

The person-by-week grid admits the collision

Eight weeks of schedule, person against week, with tentative hours hatched and leave in a diagonal pattern. Jade's W31 reads 320%; an engineering manager on a 20-hour week reads 280%, 300%, 220%, 160%, 260% across five weeks. Leave and work in the same cell is visible, not discovered.

✓ 424 over-hours to rebalance, totalled on the cardVerified
✓ PTO marked diagonally in the grid: W36 shows it for two peopleVerified
✓ Under band: 2 people below 70% utilVerified
02 · LIVE EXECUTION

Skills are on the roster, not in someone's head

Twenty-four people with role, practice, utilisation, free hours this week and over four weeks, and skills on the row: “Inventory, QA, React”, “Tax, Checkout, SQL”. The bench-ready count of 14 is computed from ≥40 free hours over four weeks, not guessed.

Skills are on the roster, not in someone's head
CEDX Resourcing Live Telemetry ● 24 people on the roster
03 · DETERMINISTIC GOVERNANCE

Unfilled demand is a placeholder with a button

Six open placeholders spell out the role, skill, weeks and load (senior checkout engineer, 24h/week, P0, W32 to W36), 129h/week of unfilled demand in total. Each has a Find match button that reads the roster's skills and free hours instead of starting a email thread.

✓ 320 allocations: person × project × weekActive
✓ 3,708 confirmed hours across all weeksActive
✓ States on every row: Confirmed · Tentative · SoftActive
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Resourcing build looks like when you open /app/resourcing.

Every figure below is directly inspectable in the running CEDX Resourcing application workspace with zero synthetic projections.

PEOPLE ON THE ROSTER
24
12 delivery · 4 advisory · 4 platf
AVG UTILISATION
149%
people with load, W31
OVER-HOURS TO REBALANCE
424h
across 10 over-capacity people
UNFILLED DEMAND
129h/wk
6 placeholders, P0 to P2
4-SCREEN RUNNING BUILD TOUR

Four screens captured from resourcing.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX Resourcing moves from initial intake to verified cross-estate completion.

01 OVERVIEW
The week's load, scored
Planned 1,124h against 932h of capacity, average utilisation 149% among people with load, 178 person-week conflicts scored with 20 rated high. The alerts name names: one senior consultant at 128% (52h planned on 40h) and leave colliding with a cutover, 24h confirmed plus 18h tentative while away.
02 CAPACITY
The grid, eight weeks wide
Person against week for W31 to W38: utilisation per cell, tentative hours hatched, leave diagonal. The over-capacity count of 10 and the 424 over-hours to rebalance come straight off this grid, and so does the fix, because the free cells are on the same screen.
03 PEOPLE
A roster that knows its bench
Twenty-four rows of who can do what: role, practice, this week's utilisation, free hours now and over four weeks, skills. The 180% platform engineer has zero free this week but 76h over four; the 70% mobile engineer has 100h. The rebalancing shortlist writes itself.
04 ALLOCATIONS
Confirmed, tentative, soft, and the gaps
320 allocations with hours, percentage of week, state and match score on every row. Above the ledger, the six placeholders of unfilled demand wait for a person, each with role, skill, weeks, priority and a Find match button.
01 OVERVIEW · RESOURCING.CEDXSYSTEMS.COM

The week's load, scored

● Live Screen Capture

Planned 1,124h against 932h of capacity, average utilisation 149% among people with load, 178 person-week conflicts scored with 20 rated high. The alerts name names: one senior consultant at 128% (52h planned on 40h) and leave colliding with a cutover, 24h confirmed plus 18h tentative while away.

✓ Capacity health 56%, components listed beside the ringVerified in /app/resourcing
✓ Util by practice: Delivery 100% · Advisory 68% · Platform 95%Verified in /app/resourcing
✓ Highest conflicts scored: 80, 80, 80, 78 …Verified in /app/resourcing
The week's load, scored
OPERATING CADENCE · PROJECTS & DELIVERY

How CEDX Resourcing runs across the week, in the exact order work happens.

Engineering sprints, consultant timesheets, resource bench capacity, and milestone billing read from the exact same project object.

STAGE 01

Capture & Ingest

Records land in CEDX Resourcing already linked to the canonical customer, employee, or vendor ID.

STAGE 02

Score & Triage

Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.

STAGE 03

Execute & Approve

Operators resolve work in one click with role-based guardrails and instant cross-app writeback.

STAGE 04

Reconcile & Report

Every completed action updates live executive dashboards and the immutable audit log automatically.

OPERATOR WORKSPACES · WHO RUNS CEDX RESOURCING

Three roles open CEDX Resourcing every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

Resource manager using CEDX Resourcing

Resource manager

Owns the person-by-week grid. A 320% cell is fixed with a trade in week 31, not with an apology in week 38.

● conflicts · 178 scored
Delivery lead using CEDX Resourcing

Delivery lead

Reads the placeholders: six unfilled roles at 129h/week is the hiring-and-borrowing agenda, with priority P0 to P2 already attached.

● unfilled · 6 roles
Consultant using CEDX Resourcing

Consultant

Sees their own week as it is actually planned, with confirmed, tentative and soft hours separated, instead of hearing about the fourth project at the fourth kickoff.

● states · confirmed / tentative / soft
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

Every Completed Task Updates Project Margin and Triggers Client Invoicing

CEDX Resourcing is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /timesheets/ ->

CEDX Timesheets

Planned hours on the grid become logged hours on the sheet; the utilisation forecast is where the two are reconciled.
CONNECTED MODULE 02 Open /services/ ->

CEDX Services

The placeholders are engagement demand, a senior checkout engineer for a rollout, and the engagement margin depends on the match.
CONNECTED MODULE 03 Open /roadmap/ ->

CEDX Roadmap

An initiative's effort in eng-months is real only if the people exist; the roadmap's capacity tab reads this roster.
CONNECTED MODULE 04 Open /leave/ ->

CEDX Leave

The diagonal cells on the grid are leave records. Planning against a week someone is away is exactly the collision the alerts name.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Resourcing.

"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."

Arjun Patel
Arjun Patel
SVP of Global Operations · Keystone Logistics

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."

Marcus Vance
Marcus Vance
Chief Revenue Officer · Meridian Systems

"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."

Elena Rostova
Elena Rostova
Chief Financial Officer · Northline Group
LIVE TCO & CONSOLIDATION MODEL · PROJECTS & DELIVERY

Stop paying five vendors to re-sync the same projects & delivery record.

Drag the seat slider to compare your current stitched stack (Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo) against running CEDX Resourcing natively on the unified CEDX estate.

Organization Seats 250 seats
25 seats 500 seats 1,250 seats 2,500 seats
Legacy Stitched Stack
Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo
$1,380,000 / yr
CEDX Resourcing + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr
Verified Annual Hard Savings
Plus 0 middleware sync failures
$1,113,000 / yr
TECHNICAL & PROCUREMENT FAQ · CEDX RESOURCING

Questions operators and architecture teams ask before piloting CEDX Resourcing.

01 Is the software on this page real? +
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/resourcing . It runs on demo data.
02 What does a 320% week mean? +
Four allocations landing on one person in one week, 320% of their capacity, rendered in red on the W31 cell. The grid total computes the damage: 10 people over 100%, 424 over-hours to rebalance.
03 How does Find match work? +
Each unfilled placeholder carries role, skill, weeks and load. Find match reads the roster for people with matching skills and free hours in those weeks, and prints a match score. The current rows read 36%, which is the product saying the fit is weak, not hiding it.
04 What counts as bench? +
Computed, not declared: bench-ready means at least 40 free hours over the next four weeks, 14 of the 24 demo people qualify, and the bench-idle card prices the free hours at $107K of cost.
05 Does it know about leave? +
Yes. Leave is marked diagonally, directly in the person-by-week grid, and the overview alerts on the collision: “24h confirmed + 18h tentative while on leave.” The records themselves live in CEDX Leave .
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

CEDX Resourcing is running right now. Open it and inspect the record.

Explore the live CEDX Resourcing workspace on canonical demo data at /app/resourcing, or book a 30-minute architecture session to map your first entity rollout.

Open live CEDX Resourcing (/app/resourcing) -> Book an estate architecture map