My Pay in the Tech App (1:05 video). Open on its own page
Pay the way your shop actually pays
Everything about pay lives under Pay in the sidebar, in five tabs: Pay runs (what each technician is owed for each pay period, to check, approve and enter in payroll), Team pay (how each technician is paid), Bonuses (extra pay that comes on its own: incentives, the quality bonus among them, and contests), Chemical budgets and Pay settings (how often you pay, overtime, mileage and where approved pay goes). All five need payroll access, and none of them need the team tools turned on.
Pool Founder works out pay and sends you the payroll file; it does not send money to technicians, withhold or calculate taxes, or file W-2s or 1099s. It also doesn't check pay against minimum wage or overtime law (for example a per-stop tech's pay for a week falling below minimum wage); your payroll provider or accountant handles that. Enter each approved pay run in Gusto, QuickBooks Payroll, ADP or however you pay today.
Pay periods and pay runs
Your pay schedule (Pay → Pay settings) splits time into pay periods: Every week, Every 2 weeks, or Twice a month (by default the 1st to the 15th, and the 16th to the end of the month; Pay periods start on the picks any two start days from the 1st to the 28th, so the 12th and the 28th give the 12th to the 27th, and the 28th to the 11th of the next month). Each pay period gets its own pay run, listed on Pay → Pay runs with its status, total and number of techs.
- In progress: the period running now. Its pay run is worked out every night once anyone has worked in it, and the header says when ("Updated Nov 9, 2:04 AM (every night until Nov 15)"). A period nobody has worked in yet shows Work out pay now.
- Draft: the morning after a period ends, its pay run is worked out one last time and waits for you. From then on it stays current by itself: when something changed since it was worked out, opening the pay run (or one tech on it) works it out again on its own, and the banner says Updating the pay with these changes… for a moment. It doesn’t while the Approve confirmation is open, so the total you approve is the one you read. You can still click Refresh any time (in the ⋯ menu, or in the banner below). Refresh says what it did: worked out again, with incentive lines arriving a moment later, or Already working it out… if they’re still coming in from the last click. If you turned on Tell me when a pay period’s pay is ready to check, you get a text and a push with the link.
- Approved: locked. Nothing about it changes again.
- Paid: you marked it as entered in payroll.
- Ready to start: a period that ended before its pay run was made. Click it and Work out pay now.
When something changes after a draft was worked out (a stop synced late, route hours changed, a bonus or a tip came in, or someone’s pay rate or your pay settings changed), a blue banner says Changed since this was worked out and lists each technician and what changed, for example "Mike: 1 more stop" or "Ana: pay rates or settings changed". An open draft works itself out again right away (at most every 30 seconds while you keep it open); the banner stays only if something still differs afterwards, and Refresh works the pay out again by hand. Approved and paid pay runs never change this way. Refresh also brings incentives up to date for the pay run’s dates, so you don’t wait for the nightly run: Working it out… shows while their lines come in, usually within a minute.
Pay periods follow your company’s time zone: a stop finished at 7 pm on the last day of a period belongs to that period, not the next. Changing the pay schedule redoes the unapproved pay runs for the current and the last pay period on the new dates (switching from every week to twice a month on Nov 11 turns a Nov 9 to 15 draft into Nov 1 to 15). Approved and paid pay runs keep their dates, and no day is ever on two pay runs. A draft made before a schedule change says so at the top and has a Use button with the new dates (for example Use Nov 1 – 15).
Check a pay run
Opening a pay run shows its total (pay plus tips), the three steps Check pay → Approve → Mark as paid, and a table with one row per technician: Tech (with W-2 or 1099 contractor under the name), Hours (overtime underneath), Stops, Hourly or salary, Stop pay, Bonuses (the quality bonus, automatic bonuses and ones you added), Time off (only when someone has paid time off), Mileage, Tips and Total, with a totals row.
An amber banner above the table names anything to fix before you approve: stops with no pay rate, stops but no pay (no rate set), a route that was never ended (its hours count only up to the last stop finished that day, so check it), a technician not marked W-2 or 1099, or a total below $0. Each comes with a Fix Mike’s pay link to that technician on Team pay.
Click a technician to open their page: How it adds up lists every line with its math ("32.5 h × $18.00", "14 stops × $22.00", "30% of $1,200.00 (labor)" for a work order paid as a percent, overtime, the quality bonus, mileage, each bonus and the tips owed), then Total to pay. An incentive paid for every pool shows as one line for the pay period, for example "Pool add-on: 70 stops × $0.45"; click Show each to list (and on a draft, remove) the stops one by one. The technician’s statement email and My Pay group it the same way. Below it, Every stop lists each visit (date, customer, type and pay) with Download stops for a CSV, then their scorecard.
- 1To add a one-off bonus or take money back, open the technician on a draft pay run and use Add a bonus or take money back.
- 2Pick the Type: Bonus, or Take money back / fix a mistake.
- 3Enter the Amount ($) and What the tech reads (for example "Extra pools this week"), then click Add bonus or Take it off their pay. It shows on their pay right away. Only that line is added: the rest of their pay stays as it was worked out.
- 4Changed your mind? Click Remove next to it while the pay run is still a draft.
Approve, then mark it paid
Once the period has ended, click Approve pay and confirm. If the draft changed since it was worked out, the confirmation says so and offers Refresh first or Approve anyway. Approving:
- Locks the pay run. Bonuses and fixes from then on go on the next pay run, including any bonus dated in the period that wasn’t on it yet.
- Emails each 1099 contractor their statement, line by line, so they know what to invoice (when Email 1099 contractors their statement when I approve is on in Pay settings).
- Emails the payroll file (the CSV) to the owner, or to the address in Send the payroll file to.
- Marks the tips on it as paid out. Tips a technician is owed are paid out with their pay, not separately.
After you enter it in your payroll provider, click Mark as paid. Clicked it too early? Use Undo in the message that pops up, or Not paid yet later. Download CSV is there at every step. Its columns: Employee, Worker type, Period start, Period end, Regular hours, Overtime hours, Stops, Hourly pay, Overtime pay, Stop pay, Commission (only for older commission setups), Quality bonus, Bonuses and incentives, Paid time off, Mileage reimbursement, Gross pay, Tips and Total to pay.
An approved pay run doesn’t change on its own, not even when you change someone’s rate later. If a stop from that period syncs after you approved it, the next pay run says so ("Nov 2 – 8 was approved, then 1 stop was added for Mike: +$22.00") with Add to this run or Ignore, even for a technician who wasn’t on the approved run at all. The amount is priced with the rates the approved run paid (per stop, hourly, overtime, mileage and the quality bonus), so a raise since then is never back-paid by accident. A bonus earned during an approved period also lands on the next pay run.
Found a mistake after approving?
- Approved, not marked paid yet: click Reopen to edit and confirm. The pay run goes back to a draft with the same numbers, and its tips and bonuses are owed again. Change what you need and approve again: the statements and payroll file go out again marked corrected.
- Marked paid (the money already went out): click the technician and use Fix a mistake. Pick Paid too little: pay more or Paid too much: take back, enter the amount and What happened (the tech reads this), and click Add the fix. It goes on the next pay run as its own line, and the locked pay run lists it under Fixed after it was locked. This also works on an approved run you’d rather not reopen. If it really wasn’t entered in payroll yet, click Not paid yet first, then reopen it.
A technician who was archived (or stopped being a technician) during a period is still on that period’s pay run for the stops they finished and the bonuses they earned.
To throw a draft away, use Delete draft in the ⋯ menu. Bonuses stay on their dates, and you can start the pay run for that period again from the list.
Extra pay runs
For pay outside the schedule, like a holiday bonus or a missed check, click Extra pay run at the top of Pay runs, give it a Name and a Pay date, and click Create pay run. Then Add a tech for each person with what they get. An extra pay run pays only what you add to it, never hours or stops. Approve it and mark it paid like any other.
Team pay: how each technician is paid
Every technician is paid one of four ways (the Pay type):
- Hourly: tracked hours × hourly rate, plus overtime when it's turned on in Pay settings. This is the default. Paused time is unpaid: Pause route on the Today tab (for lunch or a personal errand) is left out of tracked hours. A bathroom break stays paid when the technician doesn't tap it; Pause stop keeps the clock running.
- Per stop: a flat amount for each completed stop, per maintenance stop, and work orders paid by each service’s pay (with an amount for services without their own pay). A service, a customer or a work order can pay its own rate; see the sections below for the order.
- Hourly + per stop: hourly wages (with overtime when it’s on), plus the per-stop amount on top.
- Salary: a Salary typed a year, a week or a pay period (a week is stored as × 52 and a pay period as × your pay periods a year, so $500 a week pays exactly $500 every weekly pay run; under the box it shows the year and what each pay run pays), paid evenly each pay period whatever the hours or stops: ÷ 52 every week, ÷ 26 every 2 weeks, ÷ 24 twice a month ($52,000 a year is $1,000 a week). No overtime, and stops pay nothing extra (incentives still pay on top). A pay run that covers only part of a period (after a pay schedule change) pays its days at the salary ÷ 364 a day. Pool Founder has no hire or end dates, so a technician who starts or leaves mid-period is paid the whole period: change it on the draft with Take money back / fix a mistake. Paid time off keeps the salary paying and adds only the Extra per paid day off, if set. Profitability counts a salaried technician’s time at the salary ÷ 2,080 hours (shown under the salary).
Work orders (on Per stop or Hourly + per stop) are paid one of two ways. Each service’s pay (the default) lists every work order service with what that technician gets for one stop of it: their own tech rate on the service (marked with their name, for example "Jake’s rate"), else the service’s Pay per stop. Click a service to change its pay or add a tech rate. Services with no pay of their own pay the amount in Services without their own pay get (blank: the same as a maintenance stop). The other way is Percent of the work order. In Pay → Pay settings you pick what the percent is taken from, for the whole company: the work order total before tax, labor only (lines that aren’t a part or chemical), or the total less what its parts cost you (a part with no cost set counts at its price). Discounts come off first. The percent is paid once per work order, in the pay period its first visit was finished; any later visits on the same work order show "already paid". A rate set on the work order itself (Tech pay per stop) still wins over the percent.
Commission on every stop is being retired: technicians already set up on it keep being paid that way, but new setups use per-stop rates per service and a percent on work orders instead.
Pay → Team pay lists every technician with their Position, Pay type, Rates, W-2 / 1099 and what they cost A week. Click a technician (or Edit) to change their pay:
- 1Pick a Position, or No position.
- 2Each rate shows the position’s in grey: type one to set the technician’s own, or click Use position rate. Without a position, every rate is simply theirs.
- 3Set Worker type: W-2 employee or 1099 contractor.
- 4Check Last 4 weeks at these rates (what recent weeks would pay) and click Save pay. Pay runs not approved yet pick it up when you refresh them.
The same page lists Services that pay Mike a different per-stop rate (with a link to change them on Services) and, when positions have requirements, his checklist To move up to Lead Tech with a Move to Lead Tech button. The Pay card on a technician’s employee page shows the same summary, and its Edit pay button opens this page. Changing the hourly rate on the employee edit form still works and shows up here too.
Positions
A position (Tech I, Tech II, Lead Tech) holds one set of pay, so you change it once instead of tech by tech. Positions are optional: with none, each technician just has their own rates. They replace the old percent levels; there are no percent raises on top of pay any more. A rate the position leaves blank keeps each technician’s own (a per-stop position doesn’t wipe a tech’s hourly rate).
- 1On Pay → Team pay, in the Positions section, click Add position.
- 2Enter a Name, pick the Pay type, and fill in the rates it needs: Salary (a year), Hourly rate, Per maintenance stop, and for work orders either Each service’s pay (the list shows each work order service’s Pay per stop, with Services without their own pay get for the rest; blank means same as per stop) or Percent of the work order. Per-position rates on a service don’t exist: a service pays everyone in the position the same, unless a technician has their own tech rate on it.
- 3Running more than one ladder (W-2 service techs and 1099 contractors, say)? Click Put it on a separate ladder and name it (for example "1099"); once there are several, pick its Ladder. On the ladder sets where it sits on its own ladder.
- 4Optionally fill in To move up into this position: days in the position below, a stop rating, on-time starts, inspections in the last 90 days and their average. Techs see how close they are in the app.
- 5Click Add position.
Editing a position’s pay changes it for everyone in it, except rates that are a technician’s own; its page names who it changes before you save. Move higher on the ladder / Move lower on the ladder set the order of the ladder (lowest first). A position can only be removed once nobody holds it.
With more than one ladder, Team pay shows each one with its own steps and an Add a step link. Moving up stays on a ladder: a 1099 Level 1’s next position is Level 2 on the 1099 ladder, its requirements count days as Level 1, and "Ready to move up" and the app’s progress card follow the same ladder. A company with one ladder sees none of this.
Paid time off
Time off marked paid (Team → Time off, or Pay these days in the list of who was off at the top of a pay run) adds a Paid time off line: each of the technician's scheduled workdays in it pays that day's scheduled hours × their hourly rate (hourly technicians) plus their Extra per paid day off, a rate on Team pay and on positions like the others (per-stop technicians get only the day rate). It never counts as overtime and gets no quality bonus. See time off.
W-2 employees and 1099 contractors
Payroll providers usually pay contractors in a separate run from employees. Mark each technician as a W-2 employee or a 1099 contractor on Team pay (or the Pay card on their employee page). It does not change any pay math. The pay run shows it under each name and flags anyone not marked, the CSV has a Worker type column so you can split it, and approving a pay run emails 1099 contractors their statement.
Paying W-2 employees on a different schedule (for example every 2 weeks, 26 times a year, while 1099 contractors are paid every week)? On Pay → Pay settings, set W-2 employees are paid to Every week, Every 2 weeks or Twice a month (1st and 16th); Same as everyone puts them back on the main schedule. For every 2 weeks, W-2 current pay period started on picks which weeks pair up. W-2 employees then get their own pay runs, labelled (W-2) on Pay runs, and 1099 contractors (and anyone not marked W-2 or 1099) get pay runs labelled (1099) on the main Pay schedule. Each is approved, sent and marked paid on its own. Days already on an approved pay run from before the change are never paid again. Overtime is still counted per work week, and per-pay-period bonuses still follow the main pay schedule.
Pool Founder does not withhold taxes, calculate payroll taxes, or file W-2s or 1099s. Your payroll provider does that.
Pay per stop on a service
When some visit types are worth more to a technician than others (a filter clean versus a quick weekly service, say), put the rate on the service instead of on the person. Every service, recurring service or work order, has a Pay per stop ($) field: "What a technician on per-stop pay earns for one visit of this type. Blank = their default rate." It only appears for roles with payroll access, and saving it needs payroll access too.
- 1In the sidebar, open Services, then the Services tab.
- 2Click a card to edit it (or click New service and pick how it runs).
- 3On a recurring service the field is in the Pricing & frequency card, under the rate. On a work order it is in the Basics card, under Time at stop (minutes).
- 4Enter dollars (for example 22) and save. Clear the field and save to go back to the technician's default.
The service's card on the Services page shows a muted "Pays $22/stop" line when a rate is set. Jobs created from the service remember it, so every completed visit of that job pays the service's rate to a technician on Per stop or Hourly + per stop. Hourly and commission technicians are not affected.
When technicians earn different amounts for the same work (your longest-serving tech gets $32 for a shaft seal, a newer one $25), keep one service and give it Tech rates instead of making a "Nick shaft seal" service. Under Pay per stop, click Add a tech rate, pick the technician, and enter their dollars per stop. Add a row for each technician who earns something different; everyone else gets the service's Pay per stop (or their own rate when that is blank). The × next to a row removes it. The service's card then reads, for example, "Pays $25/stop + 2 tech rates". Technicians never see each other's rates.
For each completed stop, payroll resolves the rate in this order: the job's own tech rate for that technician → the job's own Tech pay per stop (the customer's recurring service or the work order; see the next sections) → the service's tech rate for that technician → the service's Pay per stop → (work orders only) the technician's Services without their own pay get amount (under Work orders on their pay page) → the technician's Per-stop rate → nothing. A stop that reaches "nothing" pays $0.00 and the pay run flags it in an amber banner ("Mike: 2 stops have no pay rate") with a Fix Mike's pay link that opens his pay on Pay → Team pay. Team pay also lists, for each technician, the services that pay them a different per-stop rate.
On a pay run, click a technician to see How it adds up: one line per service (plus "Recurring stops" or "Work order stops" for jobs not built from a service) with the stop count and rate, for example "14 stops × $22.00". Below it, Every stop lists each visit with what it paid; a visit paid at the technician's own tech rate on the service carries a blue Tech rate badge.
Custom tech pay for one customer's pool
When a few customers pay a technician differently from the rest of their service (an odd or oversized pool, say), set it on that customer's recurring service instead of making a separate service for each one. Its Tech pay per stop ($) beats both the service's Pay per stop and the technician's own Per-stop rate, for technicians on Per stop or Hourly + per stop. Hourly and commission technicians are not affected, and it does not change what the customer is charged. Like every pay field it only appears for roles with payroll access, and only they can set or clear it; other people's edits leave it alone.
- 1Open the customer's maintenance service from their page and go to its Billing tab.
- 2Under the price, click Set tech pay (or the green Custom tech pay badge if one is already set).
- 3Enter dollars in Tech pay per stop ($) (for example 45) and click Save tech pay. The hint under the field says what applies when it is blank: the service's pay, or the technician's own per-stop rate.
- 4To go back to the normal rate, open it again, clear the field, and save.
You can also fill it in up front: the Technician Pay section of the new maintenance form has the same Tech pay per stop ($) field. $0 is allowed and pays nothing for those visits (it is not flagged as unpaid).
On a pay run, visits with custom pay get their own line, named after the service and the customer (for example "Weekly Service · Jane Smith"), and a green Custom pay badge in Every stop. Like every rate, a change reaches the pay period running now that night and a draft pay run when you next open it (or click Refresh); it never changes a pay run you already approved.
Tech pay on a work order
One-time jobs rarely pay the same: pulling a motor is worth more to a technician than a quick valve fix, and a deck cleanup after a grind can take hours. Give each work order its own Tech pay per stop ($). It beats the work order service's Pay per stop and the technician's own work order pay for every visit of that work order, for technicians on Per stop or Hourly + per stop. It does not change what the customer is charged.
- 1On the web: open the work order and go to its Billing tab. Next to the total, click Set tech pay (or the green Custom tech pay badge), enter dollars, and click Save tech pay. The same Tech pay fields (Tech pay per stop and Tech rates) are in the work order form itself, under Notes, when you create or edit a work order.
- 2In the technician app: open the work order from the route. Below the parts, tap Tech pay, enter the amount (for example 45), and tap Save. Remove custom pay goes back to the usual rate.
Tech rates work here too: with payroll access, the same dialog has Tech rates below the amount, listing the service's tech rates ("From Shaft seal: Nick $32/stop") and letting you set a different one for a technician on this work order only. In the technician app, the Tech pay row shows each technician what the stop pays them, for example "You earn $32.00 per stop (your Shaft seal rate)", so nobody has to type their rate in.
Who can set it: roles with payroll access, on any work order. To let technicians enter their own pay (you tell them "add $45 for this one" and they do it on the spot), turn on Set tech pay on work orders for their role on the Roles & Permissions page. It is off for the Technician role until you turn it on. With it, a technician can set the pay only while the work order is open; once it is completed, only someone with payroll access can change it. They can see a work order's tech pay but never a recurring service's or anyone's payroll. Every change is recorded with who made it.
On a pay run, those visits get their own line, named after the work order and the customer (for example "Replace pump motor · Jane Smith"), with the green Custom pay badge in Every stop.
Incentives: extra pay techs earn on their own
On Pay → Bonuses, Incentives pay techs extra for what they do, onto the pay run for the period it counts in. You build each one: click Add an incentive, give it a Name techs see and pick What kind: Pay per item ($10 a 5-star Google review, $3 an issue a tech reports, or a percent of each sale), Hit a target ($25 for a month with no thumbs down), Prizes for top techs ($75 for the most reviews, every month, where a contest runs once; tied techs split the prizes, or each get one) or Same amount every period (to every tech who meets its conditions).
Then fill in the blanks of its sentence: what counts (stops done, recurring stops (stops done without repairs), tasks on a stop, route days, stops not done on their day, stops covered, Google reviews, thumbs up or down, issues reported, repair sales, new customers sold, leads converted, callbacks, chemical budget months, cancellations, days off, inspections, daily scorecards, something you log, or a photo or note a tech sends in), + narrow it down, who gets the credit (a sale can go to who sold it or the tech who found the problem), when it counts (a sale when accepted or when paid, optionally only if it still holds some days later), how it’s approved (automatically, by a person, or for claims also by AI) and how often it pays. Tried on your data shows what it would have paid each tech last period before you save. Beside it, the page says when it starts counting: an amount for each item counts from the start of today (what a tech already did today counts, and its lines show on the pay run within a moment of saving); a new incentive paid by the week, pay period or month counts the one it’s added in; a change to one counts from the next period, or tick Count this week too. If another incentive that counts the same thing was removed and already paid some of these on pay not approved yet, it says so: the new one won’t pay those again.
Below it, up to three Conditions: only pay when these are true, or leave it empty to always pay. Add a condition lists the common ones by group (On the route: route started on time that day, didn’t miss a route day that week, at least 10 stops that day, every stop done on its planned day that week; From customers: no thumbs down, no callbacks, no customers cancelled; Paperwork and checks: no checklist tasks skipped, inspections averaging 80 or more, every scorecard target hit; What you log: one item for each kind you log, like a ride-along, read as “a “Ride-along” logged that month”, checked over the incentive’s own period unless you pick every week or every day, with an optional lowest score; Sent in by techs: an approved photo or note from one of your claim incentives that day, like a clean truck photo, or new photo check… to set one up right there (techs send it from the app, a person approves it, and it pays nothing by itself; on Bonuses it shows as Photo check · techs send it in the app); On file: one item for each thing techs have on file, like insurance or their own vehicle), with Build your own… last. Each reads as a sentence with what missing it costs under it: an amount for each item loses only that day’s (or week’s) pay, any other kind loses the whole period’s. Conditions are checked at the end of a period, so adding one to an incentive paid as it happens makes it pay each week (you can pick the period right there, or Keep paying as it happens). An approved photo condition counts only claims a person (or the AI) approved: one still waiting doesn’t count until it’s approved, and one approved or rejected after the period was paid corrects that pay on the next pay run. Every stop done on its planned day misses a stop the tech skipped, left undone or moved to another day once the day started; office skips, stops a teammate took that day and excused days don’t count against them. An On file condition picks from what techs have on file, so the names always match; an older one whose name no tech has on file says so on the incentive, with the name it likely meant. Under Fine-tuning: A different amount for a position, pay only above a number a week, a cap, Who it’s for, per-customer Limits and Dates. Each incentive has a switch, Results (where techs stand and what past periods paid, or each item paid), Edit and, in its ⋯ menu, Remove (with Undo). If it has earned money on pay runs not approved yet, Remove asks first: Keep it (the default: techs still get it) or Take it off (those lines come off the drafts; Undo puts them back). Approved pay never changes. A new incentive counts the period it’s added in. A change pays from the next period (one paid as it happens, from today), and past pay never changes; to change how often it pays, Save as new: the old one finishes its periods and the new one starts after, so nothing pays twice. Turned off, nothing that happens while it’s off pays; what was earned before still pays. Pay for something that later goes away (say an invoice back to unpaid) is taken back. Your earlier automatic bonuses moved over and pay the same.
Leads converted (in the Sales group) counts each lead that became a new customer, however it was converted: at the door during a lead visit or from the Leads page. A lead linked to an existing customer isn't counted, and each lead counts once. The credit goes to The tech who did the visit (whoever finished the visit stop, else that route's technician) or Who booked the visit (the office person who booked it; a visit booked by a lead provider or the AI Front Desk has nobody here). It counts Converted, First visit done, or Still with us 4, 8 or 13 weeks after service started (recurring service). Narrow it down by Lead source (your lead sources, for example to pay only for leads from one provider), Kind (Recurring service or One-time job), or Price ($). A lead who signed an accepted recurring service can also count in New customers sold, so pay new customers with one of the two.
Try your plan runs incentives, on or off, over the last 4, 8 or 13 weeks: what each tech would have earned, a weekly average and a yearly estimate, with a floor and a ceiling for conditions nothing records yet. Count history imported from another system includes visits from your old software, which never pay. Some incentives count what the app can’t see. Logs are one-off things you record for a tech (a referral, a new client sold, a ride-along score): an incentive whose “what counts” is something you log, or that has a What you log condition, has a Log one button on its row and on its Results page (pick the tech, the date, a number if it uses one, and a note). Its Results page lists what it counted, each with Remove (anything it paid is taken back, with Undo). On file is something lasting about a tech with a since date (insurance that names you, their own truck with your wrap): open Pay → Team pay → the tech, and under On file use Add (what it is and since when, today by default) or End (its last day, with Undo). An incentive with an On file condition pays only while it’s on file; the tech’s page also says which incentives need what they’re missing, and lists what you logged for them in the last 6 months. There is no list of every tech’s On file items in one place: each tech’s pay page has their own.
Which tech gets a Google review
When an incentive pays for Google reviews (Pay → Bonuses), each review is credited to one technician, automatically, after every sync:
- The review names one tech (full name, or a first name only one tech has): that tech.
- It names several techs ("Mia and Jake were great"): the one who runs that customer's regular route, else the one who visited most recently, else the first one named. The review is marked Names Mia and Jake so you can check it. A review is never split between techs.
- It names nobody: the customer's regular route tech, if they visited within the days set under Which tech gets a Google review on Pay → Bonuses (14 by default). Otherwise whoever visited that customer last in that window. When more than one tech visited, it's marked Mia and Jake visited. This needs the review linked to a customer (by name, or with Link to customer).
- Nothing to go on (no tech named, and no linked customer or no visit in the window): nobody gets it and it is marked No tech found. Link it to the customer and the tech is picked again.
With the "Access payroll" permission, each review shows who got it and why, for example Tech: Mia Torres · named in the review, · regular route tech, · last visit Nov 3 or · set by Sam. Change picks another tech or Nobody, and the toast has Undo. The new tech gets the review bonus and an unpaid bonus is taken back from the old one (a bonus already on an approved pay run stays). A tech you pick is never changed by a sync; Let Pool Founder pick in the same menu hands it back. The Needs a look filter shows only the marked reviews, and See who got each review on Pay → Bonuses opens it with a count. Team members without "Access payroll" don't see the tech line.
Claims, approvals and AI photo checks
An incentive counting Photo or note a tech sends in says What should techs send? (and Needs a photo). Techs use My Pay → Claim a bonus: a photo from the app’s camera (not saved photos, never the same photo twice), then Send, offline too. Your claims shows Waiting for approval, Approved or Not approved with the reason, and Ask for a second look once.
Pay → Approvals (permission Approve what technicians’ incentives count, included with payroll access): Approve, Reject with a reason, Approve 2 for the selected (with their total), Take it back on Approved and Approve after all on Rejected; approving pays, rejecting takes the pay back (a prize period already finished keeps its places, so a period waits up to two weeks for approvals). Nobody approves their own.
An AI judge (for claims) checks the photo against What the photo must show, one check per line: by default it approves at 85% sure every check is met, rejects at 20% or less, and sends the rest (and any claim without a photo) to a person (How the AI decides). AI, then a person only suggests. AI (unsure ones go to a person) decides, with a share sent to Approvals as a Spot check: Agree, or Take it back (or Approve after all) if the AI got it wrong. How the judges are doing shows overturns per incentive; past 1 in 10, the AI pauses on that incentive until Turn AI back on.
The quality bonus
The quality bonus is an incentive on Pay → Bonuses: + a percent of the technician’s stop and work order pay (their commission, for commission techs) each pay period. Hourly pay and mileage never get it, so a technician on plain Hourly is unaffected. It pays one of two ways:
- One percent: for everyone who hits every scorecard goal ("+10% on their stop and work order pay each pay period for techs who hit every scorecard goal").
- By stop rating level: only the average stop rating counts, one row per level ("Average stop rating 90 or higher: +10%", "80 or higher: +5%"), with + Add a level (up to 6). The highest level they reach pays; below the lowest level, nothing.
To add one: Add an incentive → Pay per item → in the sentence, change what counts to Stop and work order pay, then pick One percent or By stop rating level and set the numbers. Tried on your data on the right shows what it would have paid. Companies that had the old Quality bonus card already have it as an incentive named Quality bonus.
A goal is judged on the number everyone sees: a stop rating shown as 80 against a goal of 80 is a hit. The bonus uses the technician’s scorecard on the last day of the pay period and shows as its own line on the pay run the morning after the period ends ("Quality bonus (Nov 9 – Nov 15): +10% on $682 stop pay"). A technician with no score yet (fewer than 5 rated stops) gets no bonus.
Contests
Also on Bonuses: Start a contest to put a leaderboard in the technician app (most 5-star Google reviews, Customer thumbs up, Stops completed, On-time starts or Average stop rating between a start and end date) with prizes for 1st, 2nd and 3rd. Prizes go on the winners’ pay when the contest ends. Cancel contest takes the leaderboard down and pays no prizes.
Pay settings: schedule, overtime and mileage
- Pay schedule: Every week, Every 2 weeks or Twice a month. For every 2 weeks, Your current pay period started on picks which weeks pair up. For twice a month, Pay periods start on the picks the two days of the month the periods start on (1st to 28th, at least 7 days apart). A preview shows the current and next period. Changing it redoes the unapproved pay runs for this period and the last one on the new dates; approved and paid runs keep theirs.
- Work weeks start on: the day each work week (and each weekly or every-2-weeks period) starts.
- Pay overtime, off to start. Turn it on to set Overtime after (hours a week, 40 to start) and Overtime pays (1.5 is time and a half). Overtime is counted per work week, even when a twice-a-month period splits a week: the hours from the part of the week in the other period count toward the 40, so overtime is paid once, in the period where it happens.
- Work order percent is taken from: for technicians paid a percent of work orders, the work order total before tax, labor only, or the total less part costs.
- Mileage paid back per mile. It starts at $0, which pays nothing for miles; set a rate to pay techs back.
- Pay run messages: Tell me when a pay period’s pay is ready to check, Email 1099 contractors their statement when I approve, and Send the payroll file to (empty sends it to the owner).
- Techs see their pay in the app: shows each technician their own pay (see below).
Payroll taxes and benefits (labor burden) and monthly overhead are profit settings, not pay: they are under Settings → Pricing, in Costs for profitability.
What technicians see: My Pay in the mobile app
When Techs see their pay in the app is on (Pay → Pay settings), technicians get My Pay under the Account tab. It is off until you turn it on, and a tech only ever sees their own pay.
- This pay period so far: a total that goes up live as they finish stops, with today’s pay and stops, tips owed, and when the period ends.
- Still to earn today: the stops left on today’s route at their rates plus any incentive that pays a set amount for each stop ("up to $84 more", naming the incentives in it), and for hourly techs how far they are from overtime (when overtime is on).
- Quality bonus: something to aim for, with each goal hit or missed and about what it could add. It is not counted in today’s pay.
- More ways to earn: every incentive that applies to them, with what they earned from it this period and where they stand now (for example which day a condition was missed).
- Claim a bonus and Your claims, when you have incentives techs claim from the app (see Claims, approvals and AI photo checks).
- Contests with their rank, How it adds up (every line with its math), Your position with what it takes to move up, and Last paychecks (older pay stubs are with your payroll provider).
Anything that isn’t certain yet is labelled as an estimate ("up to", "about"). The final pay is what you approve on the pay run.
What the scorecard measures
The score is the technician's average stop rating over the last 30 days: every rated stop in that window, averaged. So the scorecard and the day-by-day stop ratings always agree, and you change what counts toward the score (where they start and finish, tasks, required photos, time on site, callbacks, customer thumbs up / down) under Performance → Stop Ratings, not here. A thumbs-up can push a stop past 100, but the score itself tops out at 100.
Next to the score you set goals (targets). Open Performance → Stop Ratings. The Scorecard goals card at the bottom always starts with "Average stop rating of at least 80 out of 100", followed by the goals you added, each written as a sentence with its number in a box (for example "Skips no more than 2 % of their stops"). Use Add a goal to add one, or the × on a row to remove it; the average stop rating can't be removed. Click Save goals (or Discard; Undo in the message that pops up takes a save back); the next nightly scoring run uses the new goals. Right now beside the goals shows each technician’s latest scorecard and which goals they miss. A goal is judged on the number everyone sees, so a rating of 80 against a goal of 80 is a hit. The goals you can add, for what a stop rating can't see:
- Skip rate (on by default): stops the tech skipped, as a share of completed plus counted skips. Skipped stops have no rating, so this is the only place they count. Office skips are not counted against the tech, and neither are skips with a reason your company excuses (by default Customer asked to skip, Pool covered or closed, Gate locked, Dog in yard, Customer not home and Weather; change it under Settings → Technician App → Skipped stops) or that the office marked Excuse it on Missed Pools. A stop the office Dismissed on Missed Pools is left out entirely. Ran out of time, Other and any skip the office marked Count it still count. Older skips, from before the Skipped stops setting, use the default for their reason. The line says how many skips were left out, for example "2 excused, not counted". Lower is better; the default target is 2% or less.
- Showed up: route days the tech showed up for. Default target 100%.
- On-time starts: work days where the route started before its scheduled start time. Default target 90%.
- Issues reported: equipment or site issues the tech flagged from the field during the window. Default target 1.
- Stops completed: visits completed during the window. Default target 100.
Target lines show hit or miss under the score and can decide a quality bonus that pays for hitting every goal, but they never change the score: a tech who skips too much keeps their average stop rating and misses the skip-rate target. There are no weights. Task completion, photos on required tasks, time on site and positive customer feedback are no longer separate scorecard lines, because every stop rating already checks them.
A line with too little to measure shows "Not enough data" and is left out rather than counted against the tech: the average stop rating needs at least 5 rated stops in the 30 days, skip rate 5 scheduled stops, on-time starts 3 work days. Until a technician has 5 rated stops they have no score.
Stop ratings: how every stop went
Every completed stop gets its own rating out of 100, so a technician sees how each visit went the same day; the scorecard's score is the 30-day average of these ratings. Once an owner or admin turns them on for technicians (see below), technicians see their own under the mobile app's Account tab → How My Stops Went. Their route screen also shows Today's score in a bar along the bottom: today's average stop rating so far, with how many of today's rated stops were Great. It updates after every completed stop (before the first one it reads "Shows after your first stop"), and tapping it opens How My Stops Went. This is today's average, not the 30-day scorecard score, which only changes at the nightly update. Stop ratings are off for technicians until you turn them on: until then techs don't see the How My Stops Went row or any rating, while owners and managers already see them on employee pages and in Settings, so you can tune the numbers on your past weeks before your team sees anything. Managers see any technician's on their employee page (Team → Employees → click the technician) in the Stop ratings card, next to the Scorecard card.
Out of the box each stop is checked on these things, worth these points (each company can change them, see below):
- Started at the pool (20): the phone's GPS when they tapped Start Job was within 500 ft of the pool's location on the map.
- Finished at the pool (20): they marked the stop done at the pool, not after driving away (a stop completed more than 2 minutes after GPS saw them leave counts as a miss).
- Tasks checked off (25): partial credit for each task checked.
- Required photos (20): photos on every photo-required task.
- Time on site (15): pools only. Full credit at 60% or more of the time that pool usually takes, none at 30% or less. Going long is never marked down, and repairs (work orders) are not timed.
- No callback (10): no water-quality request from the customer (customer portal or text, category Water quality) and no courtesy-visit unplanned stop to that pool in the 7 days after the stop (a return visit booked to redo this visit counts whenever it happens; see Callbacks and return visits below). Until those 7 days pass it shows as not counted yet.
- Chlorine held until next visit (15, off by default): free chlorine at the pool's next reading, 3 to 10 days later, was at or above the low end of the company's Free Chlorine range (Technician Alerts → More → Alert settings → Water chemistry ranges; 0.5 ppm if not set). Pools whose sanitizer is bromine or none are skipped, as are repairs. Turn it on only if your techs record real readings: a tech who logs 0 as a placeholder would miss it every week.
Points are relative: the rating is always out of 100, so a check worth 40 when the rest add up to 60 counts for 40% of it. A check that can't be judged is left out instead of counted as a miss: no GPS reading, a pool with no location on the map, a visit with no photo-required tasks, or a pool whose usual time isn't learned yet. By default a customer thumbs up on the service report adds 10 points of extra credit on top (so a perfect stop with a thumbs up counts as 110), and a thumbs down shows on the stop without lowering the rating. A rating a manager marked Not the tech's fault on the Job Feedback page earns or costs no points at all. The two after-the-visit checks fill in on their own: a complaint or return visit days later lowers that visit's rating on the day it happened, not the day it was noticed. Ratings read 90+ Great, 75+ Good, 50+ Fair, under 50 Poor.
Both screens show a strip of the last 7 days with each day's average, the selected day's average and how many stops were rated great, and every stop on the route. Tap or click a stop to see each check with what happened ("Started the job 0.4 mi from the pool", "3 of 4 tasks checked off") and the points it earned. Skipped stops and stops not done yet are listed without a rating; a stop skipped by the office says so and never counts. Under the stops, the app spells out the company's current rules in one sentence.
Turn ratings on for technicians. At the top of Performance → Stop Ratings, the Technicians see their ratings switch is off by default. Turning it on shows each technician their own stops in the app right away; turning it off hides them again. It saves on its own (no Save changes needed) and needs the employees:update permission. Change how stops are rated. Go to Settings (sidebar) → Team access → Stop Ratings (or search "Stop Ratings" with ⌘K). It needs the employees:update permission (owners and admins by default). You can:
- Turn any check on or off with its switch, and set its points (1 to 100). Each row shows its share of the score. At least one check must stay on.
- Set the "At the pool" distance (100 to 5,280 ft, default 500) for big lots, gated communities or rural properties.
- Set Rushed visits: Full credit at (default 60%) and No credit at (default 30%) of the time that pool usually takes. No credit must be lower than full credit.
- Set Thumbs up adds extra credit (0 to 50 points, default 10) and Thumbs down takes off (0 to 50 points, default 0). 0 turns either off. A rating never goes below 0.
Changes are a draft until you click Save changes (Discard changes and Use the defaults are next to it). While you edit, the Rated your way panel re-rates your real stops from the last 1 week, 2 weeks or 4 weeks (pick with the buttons at its top) both ways: the overall average saved vs. with your changes, Where points are lost, per stop (how many points each check costs the average stop under your changes), and the stops whose rating would change the most. Below the settings, Day by day shows every technician's average for each day in that range, with how many stops they did and the check they lose the most points on. Switch it between With changes, Saved and Change (how many points each day moves, green up, red down) to see who a setting helps or hurts before you save. Days nobody worked show as thin gaps, and the grid opens on the most recent days (scroll left for older ones). Click a day to open that technician's page on that day in the Stop ratings card. Ratings are worked out when someone looks at them, so saving re-rates every day, past ones included. For a week afterwards technicians see a note in the app: "Your company changed how stops are rated on Oct 6." George can change these settings too ("stop counting where they start the job"), with the usual approval card.
Stop ratings show no pay. They only affect pay through a quality bonus incentive, when you have one (by rating level, or as one of the goals). There is no way yet for a technician to dispute a rating or for a manager to override one; if the pool shows in the wrong place on the map, fix the service location's address so future visits rate correctly.
Callbacks and return visits (redos)
A callback is a customer water complaint (a Water quality request from the customer portal or a text) or a return visit to the pool after a visit. It counts against the technician who did that visit: their stop rating for it loses the No callback points, so it shows on their scorecard and a quality bonus.
Schedule a return visit. Open the complaint (sidebar → Messages → Portal messages, then the request) or the completed visit (sidebar → Completed Stops, or from the customer's page), and click Schedule return visit. The window says which visit it redoes ("Redo of the Mon, Nov 10 visit by Mike (Weekly Service)"; for a complaint, the last visit to that pool in the week before it), and preselects that technician on their next route day that doesn't already have the pool. Under Who goes back, and when pick another technician or day if you like, change the Note for the tech (it starts as "Return visit: " plus the request's subject), then click Schedule return visit. The toast has Undo.
- It is another visit of the same service, added to that technician's route for that day only (straight onto their phone if the route is running). The note shows at the stop as a note for the next visit until the end of that day.
- When it is done it is never billed to the customer (not on an invoice, not counted in visit-count or per-visit billing), and it pays the technician $0 per stop: it shows on their pay run under Return visits at $0. Technicians paid hourly still get paid for their time, and it earns no per-visit incentive.
- Its time, chemicals and job costs count against that job's profit, with no revenue, so the job's margin on Profitability drops by what the redo cost.
- It is the redone visit's callback, even when it happens more than 7 days later. A complaint and the return visit booked for it count as one callback, not two.
- Once one is booked, the button turns into where it stands ("Return visit Sat, Nov 14 · Mike"). When it is done it reads Went back Sat, Nov 14 (click it to open that visit), and Another return visit books a second one.
- Recurring service visits only. A work order visit says "Return visits work on recurring service visits. For a work order, add another visit to the work order." It can't go on a day the pool is already serviced or scheduled, or on a technician's day without a route.
- To cancel one nobody has started, use Undo on the toast, or ask George ("cancel the return visit for the Smiths"). It needs the "Add stops to other techs' routes" permission (Owner, Administrator and Office Manager have it by default). George can schedule one too: "schedule a return visit for the Smiths with Mike on Thursday".
See every callback. Performance → Scorecards has a Callbacks, last 30 days card under the table, one row per callback: the visit (customer, date, technician), what happened (the complaint and its subject, a return visit, or a Courtesy stop a technician added), and the return visit (date, technician, and Scheduled, On site or Done), with a count per technician at the top. Return visits booked for the next two weeks are listed too.
To bill the customer for going back, create a work order instead: a work order is billed and paid as usual and is not counted as a callback. Courtesy unplanned stops a technician adds in the field still count as callbacks against the visit before them (within 7 days), but they are not visits of the job.
What technicians see: My Scorecard in the mobile app
Technicians can see their own scorecard in the mobile app under the Account tab → My Scorecard. It shows their Average stop rating with the change vs 7 and 30 days ago, "Ranked N of M on the team" (when the team has more than one rated tech), and a See how each stop went link; a What you're measured on card with the same lines an admin sees (actual vs. target, hit or missed, or "Not enough data yet"); a This period card counting stops this pay period (Stops, Recurring, Work orders); and How to improve tips, so a tech always knows exactly which target they are missing. Before there are enough rated visits it reads No score yet ("Complete a few more visits and your score will show up here after the next nightly update."). Until you turn on Technicians see their ratings (Settings → Stop Ratings), My Scorecard shows no score or stop rating, only "Your score isn't on yet" and the other target lines such as skip rate.
My Scorecard shows no pay amounts. Pay is on its own My Pay screen (Account tab → My Pay), which only appears when Techs see their pay in the app is on in Pay settings (see below).
Frequently asked questions
Does Pool Founder pay my technicians or run payroll?
No. Pool Founder works out each technician's pay for every pay period on Pay → Pay runs and emails you the payroll file when you approve it. It does not send money to technicians, withhold taxes, or file W-2s or 1099s. Enter the approved pay run in your payroll provider (Gusto, QuickBooks Payroll, ADP), then click Mark as paid.
Can I pay my techs every two weeks or twice a month?
Yes. On Pay → Pay settings, set Pay schedule to Every week, Every 2 weeks (pick which week the current period started) or Twice a month (the 1st to the 15th and the 16th to the end of the month, or any two start days you pick under Pay periods start on the, such as the 12th and the 28th). Each pay period gets its own pay run. Overtime is still counted per work week, even when a twice-a-month period splits a week. Unapproved pay runs for this period and the last one are redone on the new dates; approved and paid runs keep theirs. A draft made before the change shows a Use button with its new dates.
Can I pay my techs per pool instead of hourly?
Yes. On Pay → Team pay, click the technician and set Pay type to Per stop with a rate per maintenance stop (work orders pay each service’s Pay per stop, or the amount you set for services without their own pay), or Hourly + per stop for both. Each technician can be paid differently. Pool Founder works out what each one earned on every pay run; you pay them through your payroll provider or however you pay today.
How do I give several techs the same pay, or a raise to all of them?
Make a position. On Pay → Team pay, click Add position (for example Lead Tech), set its pay type and rates, and put the technicians in it. Changing the position's pay changes everyone in it, except rates you set as a technician's own. Positions can also have requirements to move up, which techs see in the app, and can sit on separate ladders (W-2 and 1099, say) that each move up on their own. Positions replaced the old percent levels.
Can I pay a technician a salary?
Yes. On Pay → Team pay, open the technician (or a position) and set Pay type to Salary with the yearly amount. It is paid evenly each pay period whatever the hours or stops: ÷ 52 every week, ÷ 26 every 2 weeks, ÷ 24 twice a month. There is no overtime on a salary, and incentives still pay on top. Someone who starts or leaves mid-period is paid the whole period (Pool Founder has no hire dates), so adjust that pay run with Take money back.
How do I approve pay and get it into Gusto?
Open Pay → Pay runs. The morning after a pay period ends, its pay run is waiting as a Draft. Check each tech (click one to see every line and stop), fix anything the amber banner flags, then click Approve pay. Approving locks it, emails 1099 contractors their statement, and emails you the payroll CSV (or downloads it with Download CSV). Enter it in Gusto, QuickBooks or ADP, then click Mark as paid.
What happens if a stop syncs after I approved the pay run?
The approved pay run doesn't change on its own. The next pay run shows it ("Nov 2 – 8 was approved, then 1 stop was added for Mike: +$22.00") with Add to this run or Ignore, even for a tech who wasn't on the approved run. The amount uses the rates the approved run paid, so a raise since then isn't back-paid.
Can I change a pay run after I approved it?
If it isn't marked paid yet, click Reopen to edit: it goes back to a draft, you fix it and approve again, and the statements and payroll file go out again marked corrected. If it is marked paid, click the tech and use Fix a mistake (Paid too little: pay more, or Paid too much: take back): the correction goes on the next pay run with the reason you give, and the paid run lists it.
Can I pay techs a percent of a work order?
Yes. On Pay → Team pay (or in a position), set Work orders to Percent of the work order instead of Each service’s pay. In Pay → Pay settings, pick what the percent is taken from: the total before tax, labor only, or the total less what the parts cost you. It is paid once per work order, in the period its first visit was finished. A rate set on the work order itself still wins. Commission on every stop is being retired; per-stop rates per service cover recurring work.
Can I run payroll for any date range I want?
No. Pay runs follow your pay schedule (every week, every 2 weeks or twice a month), plus extra pay runs for one-off pay. You can’t type in custom start and end dates for one pay run: the dates come from the pay schedule. If your periods don’t run 1st to 15th, pick Twice a month and set Pay periods start on the to your two start days (for example the 12th and the 28th). There is no custom-date-range payroll page any more. To see every stop a tech did over some other range, use Completed Stops.
Can I pay a holiday bonus outside the normal schedule?
Yes. On Pay → Pay runs, click Extra pay run, name it and pick the pay date, then add each tech and what they get. It pays only what you add. To add a bonus to a regular pay period instead, open its pay run, click the tech, and use Add a bonus or take money back.
Can I mark techs as 1099 contractors vs W-2 employees?
Yes. On Pay → Team pay (or the Pay card on their employee page), set Worker type to W-2 employee or 1099 contractor. Pay runs show it by each name and flag anyone not set, the CSV has a Worker type column, and approving emails 1099 contractors their statement. Pool Founder does not withhold taxes or file W-2s or 1099s; your payroll provider does.
Can I pay W-2 employees every 2 weeks and 1099 contractors every week?
Yes. On Pay → Pay settings, set Pay schedule to Every week (for 1099 contractors and anyone not marked W-2) and W-2 employees are paid to Every 2 weeks, then pick which week the W-2 period started. W-2 employees and 1099 contractors then get separate pay runs on Pay runs, labelled (W-2) and (1099), each approved and marked paid on its own. Mark each tech W-2 or 1099 on Team pay.
Does the quality bonus change hourly pay?
No. It is a percentage on stop and work order pay only. Hourly pay, overtime and mileage never get it, so a technician on Hourly is unaffected even when the bonus is on.
What is the difference between the two quality bonus rules?
One percent pays one percentage (for example +10%) when the technician hits every goal on their scorecard, and nothing otherwise. By stop rating level looks only at the average stop rating and pays the level it reaches (for example 90 or higher: +10%, 80 or higher: +5%). It’s an incentive on Pay → Bonuses; Tried on your data shows what it would have paid.
Can I pay techs a percent of the work they find, once the customer pays?
Yes. Add an incentive (Pay per item), count repair sales, switch the amount to a percent, credit the tech who found the problem, and count it when the invoice is paid. The percent is of the total before tax.
Can a bonus reward each new customer a technician signs up?
Yes. Add an incentive (Pay per item) and count New customers sold: each new recurring-service customer, credited to the tech in Sold by on the accepted recurring service they signed, once their first visit is done. To reward keeping them, count it when they are still with us 4, 8 or 13 weeks after service started (a visit that many weeks after the first; leaving later doesn’t undo it). Wrong tech? Change Sold by and the money moves to the right one. Customers added another way aren’t counted there: to pay for every lead that becomes a customer (converted at a lead visit or from the Leads page), count Leads converted instead, credited to the tech who did the visit or who booked it.
Can I pay a per-pool bonus only on days a tech sends in an approved photo, like a clean truck?
Yes. First add the photo incentive techs claim (Photo or note a tech sends in). Then on the per-pool incentive, Add a condition → Sent in by techs → An approved “Clean truck” that day. Only approved photos count; one approved later pays the difference on the next pay run.
Can I see what a new incentive would have paid before I turn it on?
Yes. While you build it, Tried on your data shows what it would have paid each tech last period, and Try your plan runs several incentives over the last 4, 8 or 13 weeks.
Can a bonus apply to only some technicians?
Yes. When you add or edit an incentive on Pay → Bonuses, go to Fine-tuning → Who it’s for and pick positions, certain techs, or W-2 or 1099 only. A different amount for a position pays techs in that position a different amount from the same incentive.
Can different kinds of visits pay a technician different amounts?
Yes. Open Services → Services, edit the service, and fill in Pay per stop ($) (Pricing & frequency card on a recurring service; Basics card on a work order). Completed visits of jobs made from that service pay that amount to per-stop technicians; services without one fall back to the technician's work order or per-stop rate. If neither exists the stop pays $0.00 and the pay run flags it.
Can two technicians earn different pay for the same service?
Yes. Open Services → Services, edit the service, and under Pay per stop ($) click Add a tech rate, pick the technician and enter their amount (for example Nick $32, Alex $25). Technicians without a tech rate get the service's Pay per stop, or their own rate when it is blank. Team pay lists, for each tech, the services that pay them differently. Needs payroll access.
Can I set a different tech pay for one customer without making a new service?
Yes. Open that customer's recurring service, go to its Billing tab, click Set tech pay, enter the Tech pay per stop ($), and click Save tech pay. It overrides the service's Pay per stop and the technician's own per-stop rate for that job's visits. You need payroll access to see or change it.
Can my technicians enter their own pay on a work order, like a motor swap?
Yes. Turn on Set tech pay on work orders for their role on the Roles & Permissions page (it is off for Technician until you do). Then a technician opens the work order in the app, taps Tech pay, enters the amount, and taps Save. It works only while the work order is open. It applies to technicians on Per stop or Hourly + per stop and does not change the customer's price.
Can I see pay for a custom date range?
Pay is worked out per pay period on Pay runs; there is no custom-date payroll page any more. Click a technician on a pay run for every stop in that period (Download stops for a CSV). For any other date range, use Completed Stops.
Can I pay my techs a bonus for 5 star Google reviews?
Yes. On Pay → Bonuses click Add an incentive, keep Pay per item and Google reviews, and set the amount (for example $10 for each 5-star review). Each review goes to the tech it names, else that customer’s regular route tech; the Google Reviews page shows who got each one, with Change to fix it.
A review names two of my techs. Which one gets credit?
One of them, never both. Pool Founder picks the named tech who runs that customer's regular route, else the one who visited most recently, else the first one named, and marks the review "Names Mia and Jake" on the Google Reviews page. To give it to the other tech, click Change on the review and pick them (needs the "Access payroll" permission); the bonus moves with it and Undo puts it back. A review that names nobody goes to the regular route tech if they visited recently, else the last tech to visit.
Can I change what the tech scorecard measures?
The scorecard measures the tech's average stop rating over 30 days; change what a stop rating checks under Performance → Stop Ratings. The goals (the stop rating's target, plus skip rate, showed up, on-time starts, issues reported and stops completed) are set on Performance → Stop Ratings in the Scorecard goals card, then Save goals: that's where you change what the tech scorecard measures. Goals show hit or miss and can decide a quality bonus for hitting every goal; they don't change the score.
Why does a goal say "Not enough data"?
The technician has not had enough rated stops, scheduled stops, or work days in the last 30 days for that goal to mean anything (5 rated stops for the average stop rating, 5 scheduled stops for skip rate, 3 work days for on-time starts). It is left out rather than counted as a miss, and without 5 rated stops there is no score.
Can technicians see how much they are paid in the app?
Only if you turn it on: Pay → Pay settings → Techs see their pay in the app. Then each technician gets My Pay under the Account tab with their own pay for this pay period, line by line, and past paychecks. My Scorecard never shows pay.
How is each stop rated?
Every completed stop gets a rating out of 100. By default: started at the pool (20 points), finished at the pool without driving off first (20), tasks checked off (25), required photos (20), time on site for pools (15; repairs are not timed), and no callback (10: no water-quality request or courtesy visit to that pool in the 7 days after). An optional check, off by default, looks at whether chlorine held until the next visit to that pool. Checks that cannot be judged are left out. A customer thumbs up adds 10 extra points. Each company can change the checks, their points and thresholds under Performance → Stop Ratings. Technicians see their ratings under Account → How My Stops Went only after an owner or admin turns on Technicians see their ratings (off by default).