Persisted site plan
Keep supported planning information on the canonical site.
Site planning and milestones
Keep the simple plan beside the work used to review it.
Maintain supported site dates, plan context and milestones, then review their status from the same Site Home used for daily operations.
The planning handoff
A milestone loses meaning when it is separated from the site record.
Small teams often maintain a simple plan in one file and discuss actual work elsewhere. The plan becomes stale because the operating context is difficult to see beside it.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Open the site plan
Use the existing site record rather than creating a separate planning workspace.
- 02
Add milestones
Record the supported milestone title, dates and status context.
- 03
Review from Site Home
Keep the compact milestone summary beside current site attention.
- 04
Update responsibly
Authorised people confirm the supported plan or status change.
What site planning covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Milestone dates
Record supported milestone timing and status without a second scheduler.
Progress context
Review the plan beside current Site Home and daily operations context.
Permission-aware updates
Retain the existing site and role controls for planning changes.
Plan beside operations
Milestones remain visible where the team reviews the site.
The approved Site Home evidence includes the compact milestone summary alongside status, attention and people.
- Canonical site persistence
- Compact milestone summary
- No second planning engine
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Owner
Understand the simple plan and current site state together.
Project manager
Maintain supported milestones and review their status in context.
Supervisor
See the relevant site direction without opening a complex scheduler.
Planning boundary
A clear milestone view does not claim a full critical-path scheduler.
NIYAM records supported planning context. Baselines, sequencing, dependencies and contractual schedule decisions remain outside this Starter promise unless separately supported.
- Authorised updates only
- Supported milestone fields only
- No CPM or Gantt claim
Questions about site planning.
Straight answers about scope, review and responsibility.
Can NIYAM store site milestones?
Yes. Teams can maintain supported milestone information and use it in the existing Site Home.
Is milestone progress updated automatically?
No automatic project decision is promised. Authorised people remain responsible for supported plan and status updates.
Does this replace Primavera or full CPM software?
No. This is simple persisted site-plan and milestone context for the Starter operating workflow.