One Big Green (OBG) is designed to reduce repetitive administrative work by connecting the Back Office with the mobile app. Once your Service Sites, Services, field inventory, users, and schedules are set up, many routine updates happen as your team works.

The main benefit is that information recorded in one part of OBG can be used elsewhere without someone having to enter the same information again. Automation does not mean that OBG makes operational decisions for you, though. Your team still needs to maintain the data, set up schedules and rules, perform the work, and review exceptions.

When a Service Visit, Delivery, or Quality Inspection is scheduled, it becomes part of the operational work that the assigned field team can see in the mobile app, according to their schedule and access.

When a scheduled job is edited, reassigned, or rescheduled in the Back Office, the change is reflected in the connected field workflow. This helps the team work from the current schedule instead of relying on someone to communicate every change separately.

When technicians use the mobile app to perform Service Visits, record plant care actions, add notes, complete jobs, or log other supported activities, OBG captures that information as part of the operational record. The office team can then review the available information in the Back Office without asking the technician to recreate it in another place.

OBG also builds a history of relevant activity over time. For example, records can help your team understand what has happened to a Display, Service Site, Replacement, Issue, Assignment, or another operational item. Useful history depends on the team consistently recording meaningful actions and changes.

When a technician identifies a replacement need, raises an Issue, or creates an Assignment in the mobile app, that information can be followed through the corresponding OBG workflow. Statuses, follow-up, completion, and history remain connected to the record instead of being left only in an informal message.

Some Issues can also be created automatically.

For example, OBG can create an Issue when a Display is marked as missing during a Service Visit, or when a Display is marked as “no access” on two consecutive visits. This helps turn repeated or important field observations into follow-up work without requiring the technician to create a separate Issue manually.

This works best when the team uses the appropriate OBG workflow for the task. A message outside OBG does not automatically create or update an Issue, Assignment, or Replacement.

OBG connects working-day and field activity information so that recorded time can be reviewed in the context of the work performed. Depending on the activity, the system can distinguish Service Time, Commute Time, Other Time, breaks, and Unplanned Activities.

These records form the basis for Timesheets and comparisons between actual and budgeted time. The day's Timesheet is compiled at the end of the working day, when the user finishes their working day. OBG can also allocate commute information and support commute-cost allocation. When geofencing is enabled and configured, location information can provide additional context for timesheet review. Time records can also help with payroll preparation, but the team should still review them before using them for payroll.

The mobile app is designed to keep field work moving when a reliable mobile connection is unavailable. Relevant upcoming work can be available offline, and supported actions can be saved on the device.

When the app can connect again, saved actions synchronize back to OBG. Until synchronization happens, an offline action may not yet be visible to the office or other users. Offline mode therefore allows supported work to continue, but it does not mean every update is immediately shared.

Depending on the notification settings configured for your company and team, OBG can notify users about relevant events so they do not have to keep checking every part of the system manually.

Notifications are an extra layer of visibility; they do not replace the underlying record. The Service Visit, Issue, Assignment, Replacement, schedule change, or other item remains in OBG for review. Configure notifications around what each role needs to know, rather than enabling every notification by default.

Because Service Visit, Delivery, and Quality Inspection information is stored as operational data, the relevant reporting workflows can use the information recorded during the job. The team does not need to recreate the whole activity from scratch just to prepare its report.

For example, a completed Service Visit can contribute to a Service Visit Report, while Delivery and Quality Inspection records can feed their respective reports. The final report still depends on what the team recorded during the activity; automation cannot fill in information that was never entered.

Reports become available at different points.

Service Visit, Delivery, and Quality Inspection reports appear in the Back Office immediately after the activity is completed. Timesheets follow a different process: the day's timesheet is compiled when the user finishes their working day.

Visit reports can also be shared with customers automatically.

Depending on your company's preferences, externally shared Service Visit Reports can be generated and sent to the end customer fully automatically, or prepared automatically as a draft for a team member to review before sending.

OBG can connect actual operational activity with the budget structure you configure. Service Time, Commute Time, Other Time, replacement costs, and service revenue can help you understand performance at a Service Site and across your portfolio.

When hourly rates and overtime rules are configured, time can also contribute to job costing. This reduces the need to collect operational numbers manually from different places. The calculations depend on sensible budgets, rates, and settings: OBG can calculate and present the information, but it cannot decide whether your commercial assumptions are appropriate.

Certain job settings let your company define defaults that reduce repetitive entry and help keep records consistent. For example, default ownership or default Plants and Planters can make it easier to create and maintain operational records. The available defaults depend on how your OBG environment is configured.

Automation takes care of repetitive connections and calculations, but your team remains responsible for the quality of the data and for operational decisions. In particular:

OBG can only connect and calculate information reliably when the underlying records and settings are accurate. For example, a duplicate Service Site can create confusion in scheduling, a missing Display can leave inventory incomplete, and incorrect hourly rates can distort job-costing results.

Think of automation as “connect once, use many times.” A clear data structure and consistent field practices allow information to support scheduling, service history, reporting, timesheets, and budgets without unnecessary duplicate entry.