Integrations · Last updated 1 June 2026 · 4 min read

BigChange integration

BigChange (JobWatch) is a field-service and job-management platform widely used by UK field-service businesses.

BigChange
BigChangeField-service & job management · UK field service

BigChange (JobWatch) is a field-service and job-management platform widely used by UK field-service businesses. Connect it to TrainAR to import jobs as tasks and post training-completion notes back to the BigChange job.

What syncs

Into TrainAR (15-minute polling + on-demand):

  • BigChange jobs become tasks in TrainAR.
  • Status mapping: completedOk and completedWithIssues map to completed; cancelled maps to archived; all other statuses (new, scheduled, started, and so on) map to open.
  • Incremental sync pulls only the jobs whose status changed since the last poll.
  • BigChange users are matched to TrainAR users by email for assignment.
  • Your BigChange Customer ID and the job ID are stored on each task so writeback routes back to the correct job.

Back to BigChange (when Sync direction = Import + Writeback):

When a training session is completed against a BigChange-sourced task, TrainAR posts a note onto the job with the task title, completed-by name and email, score, duration, and a session link.

What you will need

  • A BigChange (JobWatch) account.
  • Your BigChange Customer ID - the numeric account identifier, found in your BigChange API / developer area.
  • Your BigChange site authorised to connect to TrainAR - a one-time request to BigChange (see Requesting access below).
  • At least one Note Type in BigChange (Settings - Notes - Note Types) if you want writeback, because BigChange notes must reference a note type.
  • Admin access to TrainAR.

Requesting access from BigChange

BigChange links partner apps to customer sites on their side, so there is a one-time access request before you can connect. It only takes a couple of minutes.

  1. Contact BigChange. Reach out to BigChange's partnerships or support team - through your usual BigChange support channel or your account contact - and ask them to authorise your site to connect to the TrainAR partner application.

  2. Include these details so they can make the link:

    • Your consent to connect your BigChange account to TrainAR.
    • Your BigChange site ID (if you know it).
    • Your BigChange user ID (if you know it).

    If you do not have the site ID or user ID to hand, BigChange's support team can look them up for you.

  3. BigChange links it. Their team manually connects your site to the TrainAR partner application and confirms to both you and TrainAR once it is done.

A short message is all it takes, for example:

"Please authorise our BigChange site to connect to the TrainAR partner application. This email is our consent to enable the integration. Our site ID is [your site ID] and user ID is [your user ID] - or please look these up for us if needed."

Setup

BigChange uses OAuth 2.0 client-credentials with a per-account Customer ID.

  1. Complete the one-time access request above and wait for BigChange to confirm your site is linked to TrainAR.
  2. Dashboard - Integrations - BigChange card - Connect.
  3. In the connect modal, enter your Customer ID (numeric).
  4. Click Connect. Once BigChange has authorised your site, the connection validates and an initial job sync runs.
  5. (Optional) Open settings to enable Import + Writeback.

Sync model

BigChange does not push webhooks to TrainAR, so TrainAR polls BigChange every 15 minutes for new and changed jobs. There is up to a 15-minute delay between a change in BigChange and the matching update in TrainAR. Click Re-sync on the card for an immediate pull.

A full re-sync pulls up to 12 months of history, because BigChange caps date-range queries at 12 months per request.

Troubleshooting

Connection fails or shows a 401 after entering the Customer ID. Your site has not been authorised to the TrainAR partner app yet, or the Customer ID is wrong. Complete the Requesting access steps with BigChange, and double-check the numeric Customer ID.

Jobs are not syncing in. Check the card sync history and confirm the Customer ID matches the account whose jobs you expect. Polling runs every 15 minutes; use Re-sync to force a pull.

Writeback note is not appearing on the BigChange job. BigChange notes must reference a Note Type. If your account has none, create one in BigChange (Settings - Notes - Note Types) and reconnect; until then writeback is skipped rather than failing. Also confirm Sync direction = Import + Writeback.

An engineer is not assigned on a synced task. Assignment matches the BigChange user to a TrainAR user by email. Make sure the engineer exists in both systems with the same email address.

Privacy

TrainAR receives the job-related fields needed for syncing - title, description, status, contact, dates, and the assigned resource or user. Financial and unrelated BigChange records are not pulled. BigChange receives only the writeback notes that training completion produces.

You can disconnect at any time. Existing tasks remain in TrainAR; polling and writeback stop immediately.