ChatGPT
Questions, summaries and reviewed follow-ups.
Explore ChatGPTOrganise the brief into a site, a lead and a starting plan. Check the missing details together.
Start with one workflow. Use your own access. Review the result.
Actual NIYAM screens
Fictional project · Example prompts
Supplying a drawing does not automatically create an accurate estimate, takeoff or engineering plan.
Questions, summaries and reviewed follow-ups.
Explore ChatGPTScoped tasks, technical workflows and integration work.
Explore CodexConfigured bill extraction and report drafts, with the original record close by.
See the built-in helpProvider setup, available tools and costs depend on your NIYAM agreement and the provider’s plan and workspace policy.
Keep the manual workflow and its evidence available at every step.
Configured extraction prepares fields for review. Check the source and correct uncertain details before posting.
Bill reviewUse recorded activity to prepare a report, then check the content and sharing choice.
Daily reportingBring the system, data direction and job you want to simplify. The team reviews scope and access first.
Discuss your workflowA general in-product agent is not part of this demonstration. Availability of extraction and summaries depends on the enabled configuration.
Ask for the priorities, check the source record, then prepare one useful follow-up.
See the workflow 02Keep the document, extracted details and review together before they become costs or stock.
See the workflow 03Prepare an update from reviewed work, then check its audience and contents before sharing.
See the workflow 04Keep client bills and receipts distinct from supplier costs, payments and reimbursements.
See the workflow 05Use published workflows with known inputs, visible run status and a clear person for exceptions.
See the workflowUse an active NIYAM membership with AI Assistance enabled and a small grant for the agreed tools.
Access and controlsReview the exact site, values and effect of each sensitive proposal. Check the saved result before moving on.
How MCP worksConfirm MCP inclusion in your NIYAM agreement and the provider plan separately. API usage and custom integration work can carry separate charges.
Review plansReads use the permitted records. Sensitive actions use a prepared proposal and confirmation. Review the exact site, values and downstream effect before you approve.
Each person connects with their own identity. NIYAM checks membership, role, site access and the connection’s tool grant. Team rollout and provider availability depend on your workspace policy.
Leaving a proposal unconfirmed does not save the proposed operational change. If a save response is uncertain, check the record or recover the existing request before creating another one. Reconnect expired or revoked access as appropriate.
Check your NIYAM agreement for MCP access and your provider’s plan for the assistant. A ChatGPT or Codex subscription and separately billed API usage are different products. New integrations are scoped separately.
Yes. Sites, tasks, materials, money and reviewed reports have their own NIYAM screens. Connected assistance is an additional way to use supported work, subject to setup and permissions.
The screenshots are actual NIYAM screens with fictional project data. Example prompts explain the intended workflow. They are not recordings of a provider conversation or proof that every provider supports every action.
Agree the workflow and access, connect with support, then check the result together.