Prepare for a useful visit

A consistent visit makes it easier to listen, agree on actions, and close the loop.

Before travelling, open Frontline Execution and check the location, visit details, and any configured tasks or prior follow-up you can access. Confirm the visit’s purpose with the appropriate Northstar contact if it is unclear.

This is a practical example, not a Northstar visit standard. Confirm approved visit expectations, location scope, and required records before publishing or using it as operational guidance.

A practical visit sequence

Adapt this example to Northstar’s approved process.

  1. 1

    Prepare

    Review the location and available visit details in Frontline Execution. Note the questions you need answered and any follow-up already recorded.

  2. 2

    Observe and listen

    Talk with the team and observe the work relevant to the visit’s purpose. Separate what you observed from what you were told.

  3. 3

    Agree on actions

    Summarize the issue or opportunity, name the next action and responsible role, and confirm when the team will check progress.

  4. 4

    Record follow-up

    Enter the agreed follow-up in the configured Frontline Execution workflow. If the workflow is unavailable, use Northstar’s confirmed fallback process.

Record visit work in Frontline Execution

The app—not this page—is the working record when the relevant workflow is configured.

Confirm your app access and location permissions.

Use the configured visit task or follow-up workflow.

Ask the designated Northstar app support route if the location or workflow is missing.

Northstar must confirm app access, location views, workflows, and the support route before this guidance is published.