NIYAM · Repeatable workflows

Agree the process. Then make it repeatable.

Use published workflows with known inputs, visible run status and a clear person for exceptions.

Explore the example Plan your setup

Start with one workflow. Use your own access. Review the result.

1Read

2Prepare

3Review

4Verify

Example prompt

Show the published workflows I can run, their required inputs and approval steps. Do not start one yet.

01 / 04

Begin with a source record.

The same project records—tasks, materials, bills and approved reports—provide context. A workflow must already be defined and published.

02 / 04

Make the next step specific.

Show the selected workflow, version and input mapping before preparing a run.

03 / 04

Keep the decision with the team.

Check its scope and approval steps. Agree the system and data direction before any new integration is built.

04 / 04

Check what was actually saved.

Inspect the saved run, its progress and any failed step. Review cancellation or retry according to the available controls.

Plan a repeatable workflow

Actual NIYAM approved DPR, with named reviewer, retained submission and linked daily work. — Actual NIYAM screen · Fictional demo data Open full screenshot (new tab)

This is the NIYAM source view. The steps illustrate a supported review pattern; they do not run an assistant or change a record.

Keep the handoff clear.

An example prompt does not create an arbitrary integration. New systems and workflow changes are reviewed and scoped with your team.

Owner agrees the process
Administrator manages access
Team handles exceptions

Choose where you work

One project record. More than one way to use it.

Assisted setup

ChatGPT

Questions, summaries and reviewed follow-ups.

Explore ChatGPT

Assisted setup

Codex

Scoped tasks, technical workflows and integration work.

Explore Codex

In the product

NIYAM assistance

Configured bill extraction and report drafts, with the original record close by.

See the built-in help

Provider setup, available tools and costs depend on your NIYAM agreement and the provider’s plan and workspace policy.

Already alongside your records

Use the help inside NIYAM.

Keep the manual workflow and its evidence available at every step.

Review a bill

Configured extraction prepares fields for review. Check the source and correct uncertain details before posting.

Bill review

Prepare a report

Use recorded activity to prepare a report, then check the content and sharing choice.

Daily reporting

Agree an integration

Bring the system, data direction and job you want to simplify. The team reviews scope and access first.

Discuss your workflow

A general in-product agent is not part of this demonstration. Availability of extraction and summaries depends on the enabled configuration.

Choose a job

Start with a familiar part of the day.

Daily work

Ask for the priorities, check the source record, then prepare one useful follow-up.

See the workflow 02

Project setup

Organise the brief into a site, a lead and a starting plan. Check the missing details together.

See the workflow 03

Bills and documents

Keep the document, extracted details and review together before they become costs or stock.

See the workflow 04

Client updates

Prepare an update from reviewed work, then check its audience and contents before sharing.

See the workflow 05

Client money

Keep client bills and receipts distinct from supplier costs, payments and reimbursements.

See the workflow

Clear before you connect

Access, approval and cost stay visible.

Your access

Use an active NIYAM membership with AI Assistance enabled and a small grant for the agreed tools.

Access and controls

Your decision

Review the exact site, values and effect of each sensitive proposal. Check the saved result before moving on.

How MCP works

Your agreement

Confirm MCP inclusion in your NIYAM agreement and the provider plan separately. API usage and custom integration work can carry separate charges.

Review plans

A few useful answers

Know what to expect.

Will the assistant change records without me?

Reads use the permitted records. Sensitive actions use a prepared proposal and confirmation. Review the exact site, values and downstream effect before you approve.

Does everyone share one connection?

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.

What happens if I cancel or lose the connection?

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.

Is the AI subscription included in NIYAM?

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.

Can I still do the work directly in NIYAM?

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.

Is this a recording of ChatGPT or Codex?

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.

A manageable first step

Pick one project. Try one useful request.

Agree the workflow and access, connect with support, then check the result together.

Plan your setup Explore the demo project