Cadence LLC

Site Metrics

Cadence Dashboard Connecting Data as of 2026-08-25 Test Build
Tasks/Work Plan
0
Confirmed On Site Tentative Complete Conflict Critical Path Baseline Milestone Drag a bar to move it · drag its right edge to resize · linked activities cascade automatically

Task List

Every task, Cadence crew and subcontractors together — pulled from the live EmployeeName/CustomerVendor lists in Project Transaction Details, employee rates enriched from Labor & SG&A. Resource Type distinguishes Labor from Nonlabor/Subcontract. Click a column header to sort, or click a status pill to advance it.
ID ▾ Name ▾ Company ▾ Code ▾ Project ▾ Dates ▾ Duration ▾ Crew / Rate ▾ Status ▾

Resources

Raw source lists from Raw Data → Project Transactions, enriched with real FY-to-date labor cost from Labor & SG&A → Labour by Employee/Project. Vendor trade tags are auto-suggested from the company name — verify before dispatch. Click a row to expand it. This is the full company roster — it isn't scoped by the Project selector above, so you can always find someone to add to any job.

Internal Employees ()

Vendors & Subcontractors ()

Labor Cost by Job — FY-to-Date

Real Acumatica project-code totals from Labor & SG&A → Labour by Project. Shown by code; only a verified subset maps to a display name.
Project Code ▾Likely Project ▾Hours (FYTD) ▾Labor Cost (FYTD) ▾

Site Metrics vs Daily Logs

By subcontractor and project

Site = who clocked in (site metrics). Log = what the sub reported in the Procore daily log, pending logs included. Scheduled hours are shown for context only.
SubcontractorProject Heads S / LSite hLog hLog − Site Site, no logLog, no siteSched hStatus
Feeding this page from the field clock-in (site metrics) system
Have the clock-in system POST /api/subrec (up to 400 records per call) with {"kind":"hours","records":[…]}. Each record:
{ "id": "clock-<stable id, so a re-send updates instead of duplicating>",
  "source": "clock", "basis": "worked",
  "date": "2026-10-05", "vendor": "<sub name exactly as in Acumatica>",
  "project": "<project name exactly as in Site Metrics>",
  "employee": "Jane Doe", "hours": 9.5,
  "clockIn": "2026-10-05T06:58:00", "clockOut": "2026-10-05T17:03:00" }
Both pages pick these up immediately — per sub, per day and per employee — with no change to the page. Any hours record whose source is not procore_log and whose basis is not billed counts as site metrics.
About this test build. Employee, vendor and project lists are live-pulled from Project Transaction Details (Raw Data → Project Transactions) on the Cadence Financial & Project Operations Dashboard — 69 employees, 252 vendors/subcontractors and 34 projects with real Acumatica project IDs. Only the 14 currently Active projects are offered for new scheduling (real project status, not inferred) — the other 20 Completed jobs stay fully viewable for any booking that already references them. As of 2026-08-25. Employee rates are real too: direct hourly rate + overhead rate for the most recent fully-closed period (07-2026), falling back to the Jan–Jul FY-to-date blend when nothing posted last period, plus real rate-by-project where Acumatica shows a difference (see each employee's Directory card). Low-hour-sample rates are flagged, not hidden. Scheduling entries now save to a shared Cloudflare KV store (a Pages Function at /api/schedule) — everyone on this link sees the same bookings, live. Nothing is written back to Acumatica or Procore, and this endpoint is not yet gated behind Cloudflare Access the way the main dashboard is, so treat it as internal-link-only for now, not public. If your connection drops, changes fall back to this browser's local cache and re-sync once it's back — the pill in the top-right shows sync status. Sub Reconciliation (Main Menu → Site Metrics) keeps its own shared store at /api/subrec: subcontractor invoices pulled server-side from Acumatica AP bills (with attached backup file names) and Procore subcontractor invoices, Procore daily-log manpower (headcount, hours, work done), and — when it is connected — the field clock-in system. The pullers run on a computer with Acumatica/Procore credentials (scheduling-site\pullers); the page itself only reads the store, and nothing is written back to Acumatica or Procore.