Contractor site teams
Submit dated progress, quantities and supporting evidence within the correct development.
Explore this roleGive leadership a consistent project view across developments while each contractor update, approval and cost keeps its responsible source.
Pune · Two residential developments
Demonstration project · Work in progress
Prompt ideas require a connected assistant and permitted access. Review proposed changes before saving.
Screens captured from NIYAM on 9 September 2026. Names, amounts and projects are fictional. Site photos inside the demo are AI illustrations.
For developers, project directors and management teams reviewing multiple sites, contractor packages and stakeholder commitments.
Submit dated progress, quantities and supporting evidence within the correct development.
Explore this roleReviews exceptions, contractor records, bills and approvals across the portfolio.
Explore this roleReceive a consistent reviewed view for decisions and selected communication.
Explore this roleSelected progress and reports keep your client informed. Supplier bills and internal expenses stay with your team.
How sharing works
Connect assistance to your site context. Check the records, review the proposal and confirm the work you want saved.
Explore connecting ChatGPT to permitted NIYAM workflows through MCP.
ChatGPT connection guideConnect supported NIYAM tools for scoped work. Check the source, review the action and verify its result.
Codex connection guideConfigured bill extraction and report drafts support review. General internal-agent actions are not yet qualified.
See bill reviewCore site work has a complete manual path. New integrations are agreed by scope.
How MCP connects the toolsNIYAM organises project operations and review. It is not a property-sales CRM, statutory certification system or replacement for engineering, accounting and authorised approvals.
Review access and controlsYes. Orchard Homes uses two separate active sites in one fictional workspace. Each site keeps its own plan, people and records while the owner can review the portfolio.
Use consistent milestones, tasks, evidence and dated DPR records. NIYAM organises the source; the project team still checks completeness, measurements and acceptance.
Use site and portfolio views to review current stages, open actions and supported approvals without rebuilding the status from separate messages.
No. Internal costs, company payments and reimbursements remain distinct from client invoices and receipts, even when reviewed for the same development.
No. NIYAM retains the submitted record, evidence and review trail. Authorised engineers, consultants and developer representatives make certification and acceptance decisions.
Yes. Start with one active site and a clear opening date. Add the current milestones, team and balances, review them, then extend the same operating pattern to the next development.
Add the current plan, bring in your team and record the next day’s work. For an existing project, agree opening stock and balances before you carry them forward.
Plan your first site