QuickBooks Workforce App Setup Snags and the Settings That Fix Them
New QuickBooks Workforce users report missing iPad listings and blocked GPS punches; the fix lives in battery, location, and refresh settings.
Getting the employee time tracking app onto a phone sounds like a two-minute job: download it, sign in, clock in. We keep seeing the same sticking points surface in user reports, though. The app hides from iPad searches, battery savers quietly strangle location tracking, and permission screens sit in different places on every platform. Here is where setup breaks down, and the device settings that get time punches recording.
One app, two names
QuickBooks Workforce is the current name for the employee time tracking app, but the rebrand is incomplete. On iPhone, the notification permission prompt still names QuickBooks Time. On Android, the app’s info page can list the older label too. That mismatch sends plenty of people hunting for an app they already have. If a store search for Workforce comes up empty, search the Time name before deciding the app is unavailable. Both labels point to the same tool, and settings screens may use either one.
The iPad store filter hides it
Workforce ships as an iPhone app, and the App Store on iPad can default to iPad software only. When that filter is active, the app simply does not appear in results. The fix takes seconds. Open the App Store, switch the filter along the top from iPad only to iPhone only, then search again and download. The app then runs on the iPad in iPhone format. Android has no equivalent trap; Google Play lists the app for any compatible device.
Check compatibility and storage first
The store listing answers two questions before you install anything. On iPhone, the Information section carries a compatibility line that confirms the device qualifies, plus a size entry showing how much storage the download needs. On Android, About this app holds the same compatibility note, and the App info page shows the download size.
Installation itself is uneventful. Tap Get and then Open on iOS, or Install and then Open on Android. A prompt asks about notifications, and either answer is fine; the setting can be changed later. Expect a somewhat higher battery and data draw once background tracking starts, which is a byproduct of location, not a fault.
Battery optimization is the usual culprit
Most trouble starts after sign-in. Tracking that depends on GPS needs the app to keep working in the background, and phones treat exactly that behavior as a battery threat. Low Power Mode on iPhone suspends it, and battery saver apps on Android can do the same. The result is the complaint that shows up most often: the clock-in records, but location never appears, or tracking stops partway through a shift.
On iPhone, open Settings, tap Battery, and turn off Low Power Mode. If a battery saver app is installed, check its permissions and exclude the Workforce app from its controls.
On Android, go to Settings, then Apps, then App Management, and open the app’s info page. Tap Battery, choose Unrestricted, and back out to save the change. That single setting stops the system from suspending tracking mid-shift.
Location needs the widest permission
Employers who require location tracking should set the app’s location permission to Always; that is the level the tracked-shift setup calls for. On iPhone, open Settings, select the Workforce entry, tap Location, choose Always, and switch on Precise Location. Then confirm Background App Refresh is enabled, because throttled refresh produces the same stalled symptoms.
There is a master switch to check as well. Under Settings, then Privacy & Security, Location Services has to be on. With it off, no app on the phone can read location at all, and the per-app choices are moot.
On Android, the App info page handles it: Permissions, then Location, then Allow all the time, along with the precise location toggle. Notifications live on the same page and are optional, though turning them on helps with clock-in reminders.
The settings that resolve it
Across these reports, the working fix is consistent and unglamorous. Reinstalling rarely changes anything, because the blockers live in the phone rather than in the app. Four changes end most stalled setups: Low Power Mode off, location set to Always with precise coordinates, Background App Refresh on, and Android battery set to Unrestricted.
The name confusion takes care of itself once you know both labels describe one app, and the iPad app was never missing at all; the store filter was pointed at the wrong device class. Work through the settings in order and the first punch should record without a fight.