Status update is stale
The project may look healthy because the latest facts never reached the management view.
Open the project, request the missing update, and retain the new forecast or escalation.Connect projects, milestones, actions, blockers, status updates, and decisions so every management signal opens the record that needs attention.
The useful view is not a percentage-complete chart. It is the shortest path from a warning to the owner, date, blocker, decision, and source evidence behind it.
Each signal is useful only when it identifies the accountable record and next response.
The project may look healthy because the latest facts never reached the management view.
Open the project, request the missing update, and retain the new forecast or escalation.A delivery commitment moved beyond its due date while the reason and recovery path remain unclear.
Open the milestone, assign recovery work, and request a decision when the forecast changes.The work owner cannot remove the constraint and the sponsor does not see an explicit decision request.
Route the blocker to one decision owner with a due date and retain the outcome.The headline health and the detailed action records disagree.
Review the open work, update health, and record why the forecast is still protected or at risk.Separate records preserve ownership without breaking the links a project manager needs.
Sponsor, owner, phase, status, health, forecast, current milestone, latest update, and next decision.
The current delivery position and the records behind it.Commitment, owner, priority, due date, progress, evidence, and completion.
Late work, due-soon work, and the next delivery commitment.Impact, current state, decision request, decision owner, due date, response, and closeout.
The constraint or choice that must change before delivery can move.Reporting period, health, changed facts, milestone movement, risks, decisions, and next actions.
The approved narrative sent to sponsors and stakeholders.A project manager should not need a meeting to discover which record is overdue or blocked.
| Queue | What belongs here | Manager response |
|---|---|---|
| Due in five days | Milestones and actions with an owner and near-term due date | Confirm evidence, owner capacity, and whether the forecast still holds |
| Overdue | Open work whose due date has passed | Replan, reassign, escalate, or close with evidence |
| Blocked | Work that cannot continue without a dependency or decision | Name the decision owner and response due date |
| Stale updates | Active projects without a recent update | Request current facts before using the dashboard signal |
| Waiting decisions | Explicit project choices without a recorded response | Escalate the question, impact, options, and deadline |
For a focused update such as a new health rule, milestone type, owner view, reminder, or dashboard filter, the administration path is materially different.
Requirements, development or vendor scheduling, testing, deployment, and follow-up commonly stretch a focused change across 5–20 business days.
A trained Jodoo administrator can typically configure and test one field, choice, rule, role view, reminder, or dashboard update in about 30 minutes–4 hours.
Keep specialist planning or financial systems in place when their scheduling, costing, or governance controls define the job.
Your team needs linked business records, intake, approval, reminders, exception queues, dashboards, permissions, and frequent business-owned changes.
Native critical-path scheduling, resource leveling, earned value, advanced portfolio planning, or project accounting is central.
Construction, software development, professional services, or another industry needs specialist field, code, billing, or compliance depth.
Yes. Map stable columns such as project, owner, phase, status, health, dates, milestones, and next decision first. Split repeating actions, issues, and updates into related records when teams need separate owners, dates, reminders, or history.
Update the project, milestone, action, blocker, or decision as soon as a commitment, forecast, due date, or owner changes. Use a regular reporting cadence for sponsors, but do not wait for the weekly report to correct live delivery data.
Jodoo forms and task views are mobile-ready. Keep mobile updates focused on assigned work, status, evidence, blockers, due dates, and completion rather than compressing the full management dashboard onto a phone.
Not when the project depends on native critical-path scheduling, resource leveling, earned value, advanced portfolio optimization, or project accounting. Jodoo can coordinate the operational records and decisions around those systems.
Keep each blocker and decision as its own record with a project reference, owner, status, due date, impact, response, and closeout. Managers can then open the exact exception behind a dashboard signal instead of searching meeting notes.
A trained administrator can usually add a focused field, status, role view, reminder, or dashboard measure in the same working session. Test the change in a copy first when formulas, permissions, or integrations depend on it.
Follow an at-risk project into its overdue action, blocker, decision request, and next status update before adapting the model to your team.