Planning and delivery
- Projects
- Tasks
- Milestones
- Dependencies
Assets And Delivery
Projects
Project management for planning, tasks, milestones, resources, time, budget, governance, delivery, billing, and export evidence.
Implemented
Evidence-first module page
Primary users
Project manager
Delivery lead
Resource manager
Finance reviewer
App-derived visual
Project delivery workspace
Delivery
Milestone tracked
Budget
Approval aware
Governance
Evidence
| Area | Status | Evidence |
|---|---|---|
| Tasks | Dependency aware | Timeline proof |
| Budget | Variance tracked | Cost history |
| Deliverables | Acceptance flow | Approval trail |
Core workflows
What the module helps operators complete.
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Step 1
Plan projects, tasks, milestones, dependencies, and resources
Step 2
Track time, costs, budget lines, and change requests
Step 3
Govern issues, deliverables, acceptance, and project close
Step 4
Review project billing, reports, exports, and AI-assisted delivery
Feature checklist
Capabilities grouped the way operators look for them.
Financial control
- Resources
- Time logs
- Budget lines
- Costs
Governance
- Change requests
- Issues
- Deliverables
- Billing milestones
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | Relationship |
|---|---|
| Accounting | Cost recognition, posting, and billing evidence |
| HR / Payroll | Resource and time-log context |
| Documents | Deliverable and governance evidence |
| BI | Project profitability, workload, and delivery analytics |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
Governance
- Approval override controls
- Change request workflow
- Deliverable acceptance evidence
- Export run checksums
Reports
- Project status
- Budget vs actual
- Resource workload
- Billing readiness
AI coverage policy
What ERPStack can honestly claim for this module today.
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI L2 ready| Coverage claim | Current AI coverage: Projects L2/L2 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 2 registered tools, 2 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: not in the current proactive-agent monitor wave. |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
Module pages explain value, workflow, control, and proof in one place.
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Feature clarity
Buyers can see concrete function groups instead of vague capability claims.
Operational fit
Workflows, users, and connected modules show where the module belongs.
Governance proof
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Review path
Public pages link back to app routes so reviewers can compare page claims to product surfaces.