Skip to content

Product tour

One worksheet, and everything it unlocks

Fieldcurve is built around a single idea: the tracker your program already trusts — Milestones, Activities, Tasks, weighted percent complete — made live, multi-user, auditable, and still fluent in Excel.

The worksheet

A worksheet, not a website

The whole MAT tree in one virtualized, editable grid. It reads like the spreadsheet it replaces — dotted numbers, level shading, sticky ancestors — and edits faster than one.

  • Inline status, percent, owner, weight, and date edits — commit from the keyboard, stay in the row
  • Smooth at 1,000+ tasks: virtualized rendering keeps roughly thirty rows in the DOM
  • A full treegrid keyboard model: arrows walk and fold the tree, Enter opens, Tab cycles a row's cells
  • Per-level expand presets and filtered views that prune to matches plus their ancestors — editing stays live
  • Compact, dense, and glove-friendly field density modes

Weighted rollups

Numbers that explain themselves

Only leaf tasks carry a manual percent. Every level above is a weighted average, recomputed in the same transaction as the edit — and every computed number will show you its work.

  • Weights are relative shares among siblings — set them where work isn’t equal, rebalance with a live preview
  • The contribution breakdown behind every computed percent: weight × percent, child by child
  • A calibration editor for the daily judgment call: type it, step it in fives, or slide against the projection
  • The rollup cascade is visible: one leaf edit, and activity, milestone, phase, and project tick together
Why is Mechanical Completion at 46.7%?

Dashboard & reporting

Every number is a doorway

The 7 a.m. question is never “what is the percent” — it’s “what needs attention”. The dashboard answers, and every count clicks through to exactly those tasks, filtered.

  • Blocked, overdue, at-risk, due-soon, and phase progress at a glance
  • Two clicks from any tile to the live, editable tasks behind it — no export, no second system
  • Scope by project, group, or due window; deep links carry the filter, so a URL is a report
  • Status and progress read in one shared color language across dashboard, worksheet, and editor
This morning, at a glance

Excel round-trip

Excel stays in the loop

Your program has owners, contractors, and steering decks that live in Excel. Fieldcurve treats that as a fact, not a failure — import what exists, export what they expect.

  • Import your current tracker: structure, weights, percents, and owners arrive intact
  • A full dry-run diff — creates, updates, conflicts, warnings — before a single row commits
  • Commit happens in one transaction under the same permission checks as any edit
  • Exports are board-clean workbooks matching your template, so nobody downstream re-formats
Import tracker — dry run

Built for the field

Works where the work is

Progress happens at the workface, not at a desk. Fieldcurve is designed so recording it there is the easy path — not the thing the night shift retypes.

  • Field density mode: 44px glove-friendly touch targets, larger type, phone-first layouts
  • My Tasks puts each crew member's day in one list — update percent and status in place
  • Append-only notes and comments merge cleanly — field observations never overwrite each other
  • Offline field use with transparent sync is on the near-term roadmap, and the data model was built for it from day one

Templates

Stop rebuilding the same program

Turnarounds rhyme. Capture the structure your best planner would build — phases, milestones, activities, tasks, weights — and instantiate it as a ready project.

  • Author templates in the same worksheet idiom, with the same keyboard manners
  • A phase catalog for the standard blocks: CSU, operational readiness, handover
  • Instantiate with names, weights, and structure intact — then tailor to the specific plant
Templates · Gas plant turnaround v3

Security & trust

Isolation your IT team can verify

Multi-tenant is a promise about what cannot happen. Fieldcurve keeps it at the database layer, beneath the application — and proves it with an automated isolation gate.

  • A hard per-organization boundary enforced with PostgreSQL row-level security
  • Deny-by-default roles scoped to org, group, or project; assignment never grants access
  • An append-only audit trail: who, what, before, after, when
  • Soft deletes with Undo instead of destructive “are you sure?” dialogs
The boundary, as your IT team will test it

See it on your own tracker

The fastest evaluation is your real spreadsheet imported live — structure, weights, and numbers, in about thirty minutes.