Capture & Ingest
Records land in CEDX Timesheets already linked to the canonical customer, employee, or vendor ID.
Timesheets turns logged hours into the three numbers a services business runs on: billable share (66% on 808h of 1,213h), leakage risk, and utilisation. Then it names the lines that leak.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."
| Program / Client Engagement | Milestone & Sprint Phase | Delivery Principal | Budget / Billable Margin | Capacity Utilization | Delivery Health |
|---|---|---|---|---|---|
| Meridian Global ERP RolloutCEDX Timesheets · 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 Timesheets · 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 Timesheets · 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 Timesheets · Record #1043 | Control Evidence Automation | R. Lin · Security PMO | $140,000 Internal Cap | ● 100% Evidence Linked | Audit Ready |
The leakage board does not say “revenue at risk.” It says: 73 entries coded non-billable on client work, $58K, here are the people and projects. Specific is fixable.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
The board scores 184 lines and prices the expectation: value × risk% sums to $54K of expected leakage. The signals are named (“Internal time on client project”, “Missing client code”, “Rate below role / project”) with person, project, hours and value on every row.
Booked-util % against billable-util % for W31 to W38 on a do-nothing baseline: average 79% across 12 people, two under 70% (bench risk), two over 85% (burnout risk), and W37 drifting to 74% before anyone calls it a problem.
The Suggested panel drafts entries from app and window titles (a document maps to the rollout project, a ticket queue maps to the support retainer), each with hours and a confidence, and each waiting on Accept, Edit or Reject. The screen says it plainly: “nothing tracked live.”
Every figure below is directly inspectable in the running CEDX Timesheets application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Timesheets moves from initial intake to verified cross-estate completion.
1,213h logged, $176K billable at a 66% share, 46 sheets pending approval, time health 68. The alerts are priced: $58K of internal hours on client projects, $37K aging past the five-day approval SLA, $30K billed under the role rate card.
Engineering sprints, consultant timesheets, resource bench capacity, and milestone billing read from the exact same project object.
Records land in CEDX Timesheets already linked to the canonical customer, employee, or vendor ID.
Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.
Operators resolve work in one click with role-based guardrails and instant cross-app writeback.
Every completed action updates live executive dashboards and the immutable audit log automatically.
Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.
Watches the leakage board for their projects: internal time coded to client work and rate-card drift are margin conversations held in week 31, not at quarter end.
Reads the util forecast eight weeks out: two people under 70% and two over 85% is a staffing decision made while there is still time to make it.
Runs the approval queue: 46 sheets pending and a five-day SLA on the manager side, with the aging priced at $37K.
CEDX Timesheets 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.
Engagement margin and unapproved time on the Services overview are these hours, read against SOW values.
The capacity grid's planned hours and the timesheet's actual hours are the same people's week, planned and lived.
The payroll export tab is on the Timesheets nav because the approved hour is what the pay run should consume.
Points move the board; hours explain the points. The two read the same people's week.
"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."
"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
Drag the seat slider to compare your current stitched stack (Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo) against running CEDX Timesheets natively on the unified CEDX estate.
Explore the live CEDX Timesheets workspace on canonical demo data at /app/timesheets, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Timesheets pre-loaded with canonical demo records and connected across the 132-application CEDX estate.