Prefer to look around first? Live demo at app.databoardapp.com. Demo workspaces expire after 24 hours. Questions? Write us.
Tasks · GanttFrom the live demo
Proof
See the load. Act on the queue. Measure the slip.
From the live demo — schedule, capacity, and the queue that waits on you.
Workload · LevelFrom the live demo
1
1 · Was→now preview
Every slipped date before you accept the batch.
2
2 · Nothing mutates yet
Accept is one batch + undo.
3
3 · Overload as a number
Who is over the line — not a vibe in someone’s head.
What to notice
1
Was→now preview
Every slipped date before you accept the batch.
2
Nothing mutates yet
Accept is one batch + undo.
3
Overload as a number
Who is over the line — not a vibe in someone’s head.
Workload · Level
See overload. Preview the move.
Who is over the line is a number. Level opens a was→now preview of every slipped date. Nothing is saved until you accept.
Needs youFrom the live demo
1
1 · Three counts, one inbox
Overdue, pending review, and requests — totaled at the top.
2
2 · Days late as a number
22d overdue. Not “we should look at that.”
3
3 · Why it waits on you
Overdue task, pending review, or an open request — labeled on the row.
What to notice
1
Three counts, one inbox
Overdue, pending review, and requests — totaled at the top.
2
Days late as a number
22d overdue. Not “we should look at that.”
3
Why it waits on you
Overdue task, pending review, or an open request — labeled on the row.
Needs you
One queue for what waits on you
Overdue work, pending reviews, and open requests in one place — not three inboxes and a chat thread.
Tasks · KanbanFrom the live demo
1
1 · Over the line is 4/3
Review is past its cap. The badge is the number, not a color mood.
2
2 · The jam is visible
An over-limit column gets a border the floor can see.
3
3 · Limits stay honest
In progress 1/5 is a cap — not a decoration on the header.
What to notice
1
Over the line is 4/3
Review is past its cap. The badge is the number, not a color mood.
2
The jam is visible
An over-limit column gets a border the floor can see.
3
Limits stay honest
In progress 1/5 is a cap — not a decoration on the header.
Tasks · Kanban
Execute with WIP limits that stay honest
Limits are counted, not decorative. When Review goes 4/3, the column says so — the floor can see the jam.
Projects · TreeFrom the live demo
1
1 · Nested jobs, one tree
Concept through fabrication without exporting a second list.
2
2 · Lifecycle on the row
Fabrication, testing, concept — a badge on the job, not a slide status.
3
3 · Defended target end
Target end stays on the project you opened.
What to notice
1
Nested jobs, one tree
Concept through fabrication without exporting a second list.
2
Lifecycle on the row
Fabrication, testing, concept — a badge on the job, not a slide status.
3
Defended target end
Target end stays on the project you opened.
Projects · Tree
Portfolio health without a second spreadsheet
Nested jobs, lifecycle badges, and a defended target end. One tree for the plant — concept through fabrication — not a slide deck.
Tasks · GanttFrom the live demo
1
1 · Bars on working weeks
The scale is a working calendar — not a pretty date picker.
2
2 · Status on the same list
Done, Review, To do — the same tasks as the bars.
3
3 · Critical path, on demand
Typed links plus a critical-path toggle. Baseline when you set one.
What to notice
1
Bars on working weeks
The scale is a working calendar — not a pretty date picker.
2
Status on the same list
Done, Review, To do — the same tasks as the bars.
3
Critical path, on demand
Typed links plus a critical-path toggle. Baseline when you set one.
Tasks · Gantt
Plan on a working calendar
Dependencies and status sit on one timeline. Working days, typed links, and a critical path — not a pretty date picker.
Was → now, then writeLevel or Smooth opens an overload preview. Accept is one batch — nothing mutates on the first click.
Needs youOverdue, review, and open requests sit in one queue. Not three inboxes.
Late / On plan / AheadPlan vs actual is computed from the baseline you set. Not a status someone typed.
What the product shows on a live workspace — not a customer case study.
Capabilities
Plan. Execute. Capacity. Control.
The same workspace from WBS to workload — not four disconnected tools.
01
Plan
Table, Gantt, and calendar on the same tasks. Typed FS / SS / FF / SF links, WBS contain, milestones, and a critical-path highlight on working days.
Baseline dates vs the live schedule
Working calendars per org, group, and person
Projects nest; progress is effort-weighted
02
Execute
Board views that stay honest on the plant floor: Kanban with WIP limits, requests as tickets, versioned files on the parent task or project.
Needs you: overdue, review, open requests
Time and non-labor costs on the work
Discussion, history, and last-action undo
03
Capacity
Shared people across parallel jobs. Workload shows who is over the line. Level or Smooth opens a was/now preview — it never mutates on the first click.
Leveling may slip the portfolio end
Smoothing spends float only
Accept is one batch, with undo
04
Control
Fixed roles — admin, manager, technician, viewer — plus a lock on the board when you need read-first. Plan vs actual stays visible: Late, On plan, Ahead.
Late / On plan / Ahead against baseline
Group scope without a second tenant
Trash, archive, and retention — not silent delete
Built for engineering
Delivery and capacity, not generic PM SaaS.
Data Board is for engineering and ops teams of about 10–80 — industrial, plant, mechatronics — where the same people sit on too many parallel jobs and dates slip because nobody sees the load.
Shared specialistsControls, mechanical, commissioning. One person is not a swimlane you can clone.
Working time, not calendar theaterOrg, group, and member calendars, holidays, and hours. Links push on working days.
Baseline you can defendSet schedule and cost baselines separately. Late / On plan / Ahead is computed, not a status someone typed.
Roles that match the floorAdmin, manager, technician, viewer. Technicians edit what they own or are assigned — not the whole org.
Compared to
Workbook chaos or a heavy PMO suite.
Engineering and ops already have tools. Shared specialists still go over the line because nobody sees working time, baselines, and parallel plant jobs in one place.
vs Excel + Teams
Chat around a workbook.
The schedule lives in a sheet. Load lives in someone’s head. Dates slip in a thread that is not the plan.
No shared working calendar, no live baseline
Overload shows up as overtime, not a number
The same specialist on three jobs, three file versions
vs MS Project
Heavy PM, thin on the floor.
Fine for a single program office. Awkward when controls, mechanical, and commissioning are shared across the plant.
Desktop gravity; the rest of the team still lives in chat
Leveling exists — the was/now decision usually does not
Roles and requests are not how a technician actually works
vs ticket PM
Swimlanes are not people.
Boards assume you can clone a column. A commissioning lead is one person on too many parallel jobs.
WIP limits on cards, not hours on a working calendar
No Late / On plan / Ahead against a defended baseline
Generic SaaS grain — not industrial, plant, or mechatronics
Security
Tenant isolation, then Postgres RLS.
Every organization is its own tenant. Work rows carry organization_id. The API checks membership and role; PostgreSQL row-level security is the second layer — not a slideshow policy.
Sessions use an HttpOnly cookie. Roles stay fixed: admin, manager, technician, viewer. The marketing site has no account, no backend, and no tracking scripts.
Next step
Join the free beta.
For engineering and ops teams of about 10–80 who need delivery and capacity in one workspace. Join free during beta — pricing later. The live demo is there if you want to look around first. Questions? Write us.