Where do I start as solo IT with almost no documentation?

November 16, 2026 5 answers
Asked by JEXLIN!4b

I recently started a solo IT role at a nonprofit. The documentation is mostly missing or outdated, the previous IT person has not been available for a handover, and my boss is leaving soon.

There is no ticketing system or clear vendor list, and I am still figuring out the network and user access. With a limited budget, what should I tackle first?

Answers

_x34~paperwrench.7

Start with the things that could stop the organization from operating. Check what is being backed up, where the backups live, who can access them, and whether a restore can actually be performed. Document any gaps rather than assuming a successful backup notification means recovery will work.

Before your boss leaves, ask who owns the key accounts and contracts, who approves access, and who will make those decisions after the transition. Then put the major risks and unfinished work on one list and ask leadership to rank them with you. That gives you something concrete to point to when urgent requests compete for your time.

m.638!drainbadge:

Also make sure the backup information is accessible somewhere other than the system you might need to recover.

Reply to this answer
u.258+fusebasket

Go talk to finance. Bills and payment records can reveal phone providers, support contracts, software renewals, internet service and other vendors nobody has mentioned. Ask for contact details and renewal dates while you are there.

That may be the quickest route to finding out who handles the fax line and who repairs the machine. Those could easily be different companies.

Reply to this answer
6a!corkwicket_428

Do a basic discovery pass before worrying about a perfect diagram. Find where the internet connection enters each building, trace what you reasonably can, and note the switches, firewalls, access points and servers you find. Compare that with the admin portals and the old files. Mark anything uncertain as unverified.

Your private SharePoint site is a perfectly usable starting place for notes. Keep an inventory, a rough network map, vendor contacts and a record of recurring tasks there. A network inventory tool might help later, but you do not need to buy a whole stack of tools before writing down what you know.

JEXLIN!4b:

Would you document user access at the same time?

Reply to this answer
6e!mosscompass_419

Get clear expectations from the incoming leadership. One person can make progress here, but routine support, discovery and rebuilding documentation will compete for the same hours. Show them the prioritized list and what will have to wait.

Ask about budget for temporary help as well as another staff member. A local managed service provider or nonprofit technology consultant might be able to help survey the environment. Nonprofit technology communities and discount programs are also worth checking for affordable resources.

Reply to this answer
_juno-fork.73

Automation can wait a bit. First learn which processes are actually supposed to happen, especially account creation and removal. Write down the steps and who approves them, then automate the stable, repetitive parts once you can check the results.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions