What to Set Up Before Inviting a New Worker Into Sparks Provider

You've found a new support worker and you want them rostered as soon as possible. But if you send the invitation before the record behind it is ready, you end up chasing details after they've already logged in. Here's the order that avoids that.

In Sparks Provider, adding a staff record and sending an invitation are two separate steps. You can build the record over several days, or even weeks, before anyone receives an email. That gap is useful. Use it.

1. Start the record with just a name

Go to Staff, then Add a staff member. Only the first name is required to save. This matters if you've just had a phone call with someone interested in a role and want to capture them in the system before the details are confirmed.

2. Add contact and location details as you get them

Email and mobile aren't required to save the record, but email will be needed later for a contract or an invitation. If you already know which locations this person will work across, add that too. If you don't have everything yet, that's fine. The record saves either way.

3. Leave the contract fields for later if they're not settled

Start date, award classification, date of birth, home address and emergency contact can wait. Either you add them before sending a contract, or the worker fills them in themselves when they complete it. Deciding this upfront avoids a half-finished contract sitting unsent.

4. Choose what happens next, deliberately

When you save, you'll see three options: Email a contract, Invite to the app, or Just save for now. Saving never sends anything. Whichever option you pick, the actual email still waits for its own send button on the next page. This is the point to think about sequencing. Some providers send the contract first and invite to the app only once it's signed. Others prefer to invite early so the worker can see their first rostered shift as soon as it's confirmed.

5. Come back to finish or correct the record

Open the saved record from the Staff list whenever you're ready to add what was missing, fix a typo, or update a mobile number. Nothing locks once you've saved it the first time.

6. Send the invitation only when you're ready to give access

Choose Send invitation on that record when the person should actually be able to log in. An email address is required at this step, not when the record was first saved. This is deliberate: it stops a half-built record from accidentally emailing someone before you meant to.

A fictional, anonymous example: imagine a small community support provider that's just agreed to bring on a new casual worker starting the following fortnight. The coordinator saves the worker's name and mobile the day they accept the offer, adds the award classification and start date once payroll confirms it, and only sends the invitation three days later, once the signed contract is back. The worker's first login shows a roster that's already accurate, rather than an empty account with questions attached.

Why this order holds up for small teams

• It separates record-keeping from communication, so nothing sends by accident
• It lets you capture a lead or a new starter immediately, even with incomplete details
• It keeps the contract and the app invitation as distinct, deliberate actions
• It means the worker's first login already reflects a mostly complete record, not a blank form

None of this replaces your own hiring paperwork or obligations as an employer. Sparks Provider keeps the record organised on your side; what you send, and when, is still your call.