Coverage guide

Build across New Zealand and Australia

Keep country identifiers, source records, calendars, permissions and coverage separate when building cross-border workflows.

Country context is part of the input

A business identifier, public register and working calendar belong to a jurisdiction. Select the country intentionally and keep it attached to the result.

Reuse the workflow shape

A cross-border workflow can use a similar sequence—identify a record, retrieve source fields, prepare a summary and review—but each jurisdiction needs its own supported source and rules.

Keep the source boundary specific

  • A New Zealand identifier does not identify an Australian entity.
  • A national calendar does not automatically include regional dates or a team's roster.
  • A country pack describes the intended business context; it does not imply that all data providers or third-party systems are connected.
  • Verify source fields, freshness, licence, permissions and external transfers for the exact tool or job.

Carry jurisdiction through the result

Record the country, identifier type, date assumptions and sources used. When the source does not answer a question, keep it open for a person rather than substituting a neighbouring jurisdiction's data.

Local intelligence. Ready to build.

Start with a task you can inspect.

Connect a compatible client, choose a workflow and review the source fields that come back.