Gusto

Your assistant can pull the whole roster, employees and contractors, along with each person's job and current rate, and lay it out in one place. Gusto splits that across the employee record, the job record and the compensation record, which is why answering it by hand means three screens per person. Reading it changes nothing in the account.

What you end up with. A current roster with job titles and pay rates in one table, without opening Gusto.

Start with it bringing you the information and you deciding.

Never without. Pay rates are among the most sensitive records you hold. Do not let the result land in a shared doc or a team channel.

Built on: List Employees / List Contractors / Get employee / List job compensations

Gusto refuses a pay run for specific reasons and it records them: blockers held against the company, outstanding information requests, and open notifications with due dates. An assistant can read all three at once and give you the real list rather than the one error message you happened to see.

What you end up with. A plain list of what is holding up this pay run and what each item is waiting on.

Start with it bringing you the information and you deciding.

Never without. Confirm each blocker inside Gusto before the filing deadline. The list reflects the moment it was read, not the moment you act on it.

Built on: List Payroll Blockers / List Information Requests / List Notifications / Get company onboarding status

The answer lives in three places: the policy the person sits on, their history of accruals and usage, and the hours accruing from the pay period in progress. An assistant can read all three and write the reply for you. You read it and send it.

What you end up with. A drafted reply carrying the balance, the policy it came from, and the date it was calculated.

Start with it doing the work and checking with you.

Never without. Read the number yourself before it reaches the employee. A balance quoted in writing gets treated as a promise.

Built on: List Time Off Policies / Get Time Off Policy / List Time Off Activities / Calculate Accruing Time Off Hours

The employee record, the job and the compensation are three separate actions in Gusto, and an assistant can do all three from the offer details you already have. You then read the record back and correct anything wrong before the person is invited to onboard.

What you end up with. A new employee record with job and rate attached, waiting for you to check it line by line.

Start with it doing the work and checking with you.

Never without. Check start date, work location and rate against the signed offer. Work location decides which state's taxes apply, so a wrong one is a filing problem, not a typo.

Built on: Create Employee / Create Job / Create job compensation / Get employee / List employee onboarding status

It can create the contractor, individual or business, at the rate you name, and then tell you where every existing contractor stands in onboarding. Gusto asks for different fields depending on which type it is, and an hourly contractor needs a rate, so the assistant comes back to you when the details are short rather than guessing.

What you end up with. The contractor created, plus a list of everyone still missing something before they can be paid.

Start with it doing the work and checking with you.

Never without. Decide the contractor versus employee classification yourself first. That is a tax question, not an admin one, and the record you create is the evidence of your answer.

Built on: Create Contractor / Get Contractor / List Contractors / List contractor onboarding status

It can create the deduction as a fixed amount or a percentage against the employee, read back what is already in place so you do not stack two of them, and pull the receiving agency's requirements. That lookup covers child support agencies specifically, with the FIPS codes and payment requirements each state sets, which is the part that is easiest to get wrong by hand. For other kinds of order there is no equivalent lookup and you supply the agency details yourself.

What you end up with. The deduction entered against the right person, with that state's agency requirements shown next to it.

Start with it doing the work and checking with you.

Never without. Compare amount, start date and receiving agency against the order itself before the next pay run. A wrong deduction reaches somebody's bank account before anyone notices it.

Built on: Create Garnishment / Get Garnishment / Update Garnishment / List Child Support Agencies

The reading and the staging, and not the last step. An assistant can list the policies, show who is assigned to each, surface the outstanding requests, and move people onto the replacement policy. Gusto refuses to deactivate a policy while any request against it is still pending, which makes the pending queue the real work.

What you end up with. Everyone moved onto the replacement policy and the old one queued up for you to switch off.

Start with it doing the work and checking with you.

Never without. Gusto refuses to deactivate a policy while any request against it is still pending, and the connector exposes no action that switches a deactivated policy back on. Confirm every assigned employee already sits on the replacement and the pending queue is empty before you approve it.

Built on: List Time Off Policies / Get Time Off Policy / List Companies Time Off Requests / Add Employees to Time Off Policy / Deactivate Time Off Policy

It can list the earning types the company has, default and custom, and read the pay stubs that used them, so you can see whether anything current depends on one. Deactivating an earning type is also available, and it is the kind of change that quietly alters how future pay is categorized.

What you end up with. A list of earning types with evidence of which ones are still in use on recent pay stubs.

Start with it doing the work and checking with you.

Never without. Deactivating an earning type is not quite a delete: the connector's create action reactivates an inactive type of the same name rather than making a second one, so that name is the only handle you have on it afterward. Check the last two pay periods for stubs that used it and decide where that pay goes instead before you approve the change.

Built on: Get Company Earning Types / List Pay Stubs / List Pay Periods / Deactivate Earning Type