Handing a new person a pile of passwords on their first morning is a common way to start — and a poor one. Knowing what to set up before hiring remote IT staff will protect your systems, shorten the first week, and make it possible to review their work. This article is a day-zero checklist for a small US firm. For how to choose the person, see how to hire remote IT support staff. For a wider view of hiring models, see IT staff augmentation vs project outsourcing vs freelancers.
The setups below are ordinary and enough for most firms. They are not a full security audit, and they do not replace advice from your own IT or legal counsel when your work has special duties.
Key takeaways
- Before the start date, have named accounts, multi-factor sign-in, a company password manager, a ticket tool, a written access list, and an off-boarding note.
- If some of this is missing, you can still hire, but finish the list before you grant admin rights.
- A ticket tool lets you see what came in, what was done, and what is still open. Chat is a poor official record.
- Make a one-page access list with three columns: system, access on day one, and who can approve a change.
- The estimate is about 58% savings per professional at the default setting. The homepage also describes savings of up to 70%. Saving money does not mean skipping named accounts or multi-factor sign-in.
On this page
- What to set up before hiring remote IT staff: the short list
- Accounts, sign-in, and the password manager
- Tickets, records, and how work will be seen
- Access that matches the first month, not every possible future job
- The trial month and a calm first week
- A day-before checklist
- Frequently asked questions
What to set up before hiring remote IT staff: the short list
Before the start date, have these in place:
- A named account for the person in every system they will use (no shared logins)
- Multi-factor sign-in on those accounts
- A company password manager, with only the vaults they need
- A ticket tool or a dedicated inbox, so work is not lost in private chat
- A written access list: what they can open on day one, and what stays closed
- A way to join a staff member’s machine only with permission and a record of the session
- An off-boarding note: who removes access, and on the same day the work ends
If some of this is missing, you can still hire, but finish the list before you grant admin rights. A person can start on a narrow set of tickets with limited access while you finish the rest.
Accounts, sign-in, and the password manager
Create the accounts yourself, or have a current admin do it, before the first day. Use the person’s name. Do not reuse a leftover “intern” login. Turn on multi-factor sign-in and confirm they have completed it before they touch a live system.
A password manager is how you share needed credentials without sending them in email. Give them a vault for support tools, not a vault that also holds banking and payroll. If they must request a new secret, have a simple rule for who approves it.
When a device is lost, or when someone leaves, you should be able to close the account and revoke the password-manager access without hunting through spreadsheets. If you cannot do that today, fix it as part of this setup.
Tickets, records, and how work will be seen
What to set up before hiring remote IT staff also includes a place where the work lives. A ticket tool (even a simple one) lets you see what came in, what was done, and what is still open. Chat is fine for a quick question. It is a poor official record.
Write two or three sample tickets so the new person can see how you like them written: short problem, steps taken, and how the user was told it was fixed. You will train them in this process. RemoteProz monitors delivery; it does not design your ticket rules for you.
If they will join a user’s machine, use a tool that asks the user to accept the session and that can keep a log. Agree that surprise, unannounced access is not allowed.
Access that matches the first month, not every possible future job
Make a one-page access list with three columns: system, access on day one, and who can approve a change. Start with email admin or device management only if the first tickets need it. Leave payroll, banking, and owner documents out unless there is a clear reason and a second person in your firm signs off.
For shared drives, share only the support folders, not the whole company drive. For cloud apps, prefer a support role over a global admin role until the person has been with you through the trial.
Write the off-boarding steps now, while you are calm. List every system on the access list, plus the password manager, the ticket tool, and any group chats. Name the person who will run that list. When someone leaves in a hurry, you will be glad it already exists.
How to manage remote staff in a small firm covers the weekly review habits that sit on top of this setup.
The trial month and a calm first week
You can try remote staff in month one, and billing starts in month two only for the people you keep. Spend the first days confirming that access works, that tickets have a home, and that the person knows who to call in an emergency. Then give them real but limited work.
Do not skip the setup because the queue is long. A messy start creates more tickets than it closes.
Based on the RemoteProz savings calculator on the homepage, the estimate is about 58% savings per professional at the default setting, compared with a traditional in-house hire. The in-house side includes salary, benefits, office, and training; the RemoteProz side is an all-inclusive service. The homepage also describes savings of up to 70%. The exact price depends on the role and your needs. Prices are customised, and they are more affordable and efficient than typical market options. Use the calculator for an estimate, not a quote. Saving money does not mean skipping named accounts or multi-factor sign-in.
Want a price for a specific role?
Tell us the role you have in mind and we’ll talk you through your options.
A day-before checklist
The afternoon before they start, tick these items:
- Accounts exist, and a welcome note has been sent through a firm channel
- Multi-factor sign-in has been tested on at least one system
- The password-manager invite has been accepted
- The ticket tool login works
- The access list is saved where both of you can see it
- An emergency contact in your firm is named
- You have a first set of tickets or a first-week plan
If more than two of those are still open, move the start by a day rather than improvising.
Frequently asked questions
Do we need a full-time security team before we hire?
No. You need named accounts, multi-factor sign-in, limited access, a ticket record, and a way to remove access quickly. Add more controls as your risk and size grow.
Can they use their own laptop?
Many firms allow it if you set basic rules: screen lock, updates, and no copy of company files onto personal storage. Some firms issue a company device instead. Pick one approach and write it down.
What if we already shared a single admin password with a vendor?
Change it before the new person starts, and stop using shared passwords going forward. Invite each person into the password manager with their own login.
Who should own this setup if I am not technical?
Name one person in the firm, even a manager who is not an engineer, to own the checklist. They can work with your current vendor or with the new hire to finish the items, but one name should be responsible.
If you want help hiring once the setup is ready, contact RemoteProz. You train the person on your process, and we monitor delivery through a month-one trial.
Next step
Tell us the role you have in mind and we’ll talk you through your options.