Module 5: Tools & Systems

Core promise: By the end of this module, you can set up and run a contractor's digital office. You'll organize files, build a template library, evaluate project management software, protect client information, and document your work so it runs smoothly.

Organize it → Template it → Connect it → Secure it → Track it → Document it

Why this module matters: Most small contractors run on text messages, paper, and memory. A VA who can bring order to that, without overwhelming the client, becomes the person the business depends on.

In this module

1. The Contractor's Tech Stack
2. Cloud Storage and Folder Systems
3. Building a Template Library
4. Project Management Software
5. E-Signatures, Calendars, and Communication Habits
6. Security, Access, and Confidentiality
7. Tracking Sheets and Simple Automations
8. Writing SOPs and Your First 30 Days
9. Hands-On Exercises
10. Knowledge Check

Module learning objectives

By the end of this module, you will be able to:

• Describe the tools a small contractor typically uses and your role with each.
• Build a company-wide folder system and naming convention.
• Create a template library for the documents from Modules 2 to 4.
• Compare project management platforms and research which one fits a client.
• Use e-signatures, calendars, and communication habits that leave a clear record.
• Protect client information with good access and security habits.
• Write an SOP and run a 30-day onboarding with a new contractor client.

Lesson 5.1: The Contractor's Tech Stack

"Tech stack" just means the set of tools a business uses. A small contractor's stack is usually simple, and often messy. Before you change anything, learn what's already there.

Lesson 5.2: Cloud Storage and Folder Systems

In Module 3, you built a folder structure for one project. Now zoom out to the whole company, so every project, template, and license has a home.

A company-level structure

Ridgeline Builders
00 Company
    Licenses and Insurance
    Templates
    Logos and Brand
    Contact List
01 Bids
    Active, Won, Lost
02 Active Projects
    Hartley Kitchen Remodel (the 11 subfolders from Module 3)
03 Completed Projects
04 Subs and Vendors
05 Accounting Documents

Rules that keep it clean

• One source of truth. Each document lives in one place. Share a link instead of emailing copies, so nobody works from an old version.
• Clear versions. Use v1, v2, and v3, and add SIGNED to the name of a signed copy. Avoid names like "final FINAL."
• Share narrowly. Owners see only their own project folder. Subs see only what they need. Use view-only access unless someone needs to edit.
• Archive at closeout. Move finished projects to Completed Projects and keep them. Records may matter years later.
• Back up. Confirm that the storage service keeps versions, and ask the contractor how files are backed up.

Lesson 5.3: Building a Template Library

You've written proposals, change orders, RFIs, booking messages, and owner updates. Each time, you started from something. A template library means starting from a polished, approved version every time. It saves hours and keeps everything consistent.

What goes in the library

How to build a good template

1. Start from a real document that worked well.
2. Replace anything that changes with a clear placeholder in brackets, like [Owner names] or [Job site address].
3. Leave the legal wording and standard terms locked. Only the contractor changes those.
4. Have the contractor approve it, then save it in 00 Company / Templates.
5. Always use "Save As" for a new project, so the original template stays clean.

Lesson 5.4: Project Management Software

Project management software brings many things into one place: schedules, documents, RFIs, change orders, daily logs, photos, budgets, and sometimes a portal where owners can see their project. Everything you've learned in Modules 2 to 4 can live inside one of these tools.

Platforms you'll meet

These products change often, and so do their features and pricing. When a client asks about a tool, check the company's current website and demo instead of relying on what you remember, including this table.

Questions that help a contractor choose

• Who will use it: the office, the crews in the field, the owners?
• Will crews actually use it from their phones?
• Does it handle the documents in Modules 2 to 4, such as RFIs, change orders, and daily logs?
• Does it connect to the contractor's accounting software?
• Can owners see only their own project?
• Is there a trial or demo, and what happens to the data if they leave?

You research and compare, and the contractor decides. In most cases your real job is to learn the tool your client already uses, quickly.

Learning a new tool fast

1. Watch the vendor's official training videos and read their help center.
2. Create a test project with fake data and practice every task you'll handle.
3. Write a one-page cheat sheet of the steps as you learn them.
4. Ask the client for a short screen-share to see how they use it day to day.

Lesson 5.5: E-Signatures, Calendars, and Communication Habits

E-signatures

• Send the document, then watch for the signature and send a friendly reminder if needed.
• When it's signed, save the completed PDF in the right folder and add SIGNED to the name.
• Keep the signing record that the tool provides, since it shows who signed and when.

Calendars

A shared calendar is the contractor's single view of the week. Add subs' start dates, inspections, deliveries, and meetings, and use a separate color for each type. Include the address and a contact in each event, so anyone who opens it has what they need.

Communication habits that leave a record

• Pick the right channel. Texts are fine for quick field questions. Anything that needs a record, such as a decision, a date change, or an approval, goes in email or the project software.
• Confirm calls in writing. After a call, send a short note: "Per our call, Delgado will start Wednesday."
• Use a clear subject line. Start with the project name and a document number so messages are easy to find, like [Hartley Kitchen] RFI-002 Pipe behind sink wall: answer needed by Friday.
• Reply promptly. A quick "Got it, I'll have this to you by Thursday" builds trust.

Lesson 5.6: Security, Access, and Confidentiality

You'll handle contracts, owners' addresses and phone numbers, pricing, and sometimes financial records. Protecting that information is part of your professionalism, and contractors notice.

Habits to build from day one

• Use a password manager to share logins instead of texting or emailing passwords.
• Turn on two-factor authentication for email, storage, and any system with client data.
• Use unique passwords for each account.
• Ask for the minimum access you need, and don't share it with others.
• Keep client files in the client's cloud storage, not on your personal desktop or phone.
• Never share a whole folder when a single project folder will do.
• Sign a confidentiality agreement if the contractor asks, and keep what you see private.

When an engagement ends

Offboarding matters too. Return or delete any files you hold, hand over all logins and documents, remove your access, and make sure the contractor has copies of everything, such as templates and trackers.

Lesson 5.7: Tracking Sheets and Simple Automations

The logs and trackers from Modules 2 to 4 can all live in one spreadsheet workbook with a tab for each. It becomes the contractor's control center.

A control-center workbook

Tabs: Bid log, RFI log, Change orders, Submittals, Permits and inspections, Insurance certificates, Lien waivers, Materials and deliveries, Contacts

Simple automations

Automation means letting a tool do repetitive work for you. Start small, and only automate things that already work by hand.

Later, no-code tools such as Zapier can connect apps to each other, for example adding a form response to a spreadsheet. Learn the basics once your manual workflow is steady.

Lesson 5.8: Writing SOPs and Your First 30 Days

A standard operating procedure (SOP) is a short written guide to a recurring task. It lets you do the task the same way every time, and lets someone else cover for you if you're out.

An SOP template

SOP: [Task name]
Purpose: why this task matters
When: how often, or what triggers it
Tools and templates: what you use
Steps: numbered, in order
Who approves: who checks it before it goes out
Notes: common problems and how to handle them

Your first 30 days with a new contractor client

Onboarding checklist

• I have access to email, calendar, and storage, with two-factor authentication on.
• I know the three biggest pain points the contractor wants solved first.
• The company folder structure is in place.
• The template library is built and approved.
• The trackers are set up and the first recurring tasks are scheduled.
• We've agreed on how and when we communicate.

Lesson 5.9: Hands-On Exercises

Try each exercise on your own first. Then open the self-check answers to compare.

Lesson 5.10: Knowledge Check

Answer each question in your own words, then check yourself.

1. Why shouldn't you push a contractor to buy new software right away?
2. Why share a link to a document instead of emailing copies?
3. In a template, what should be a placeholder and what should stay fixed?
4. Name two security habits you should follow with client information.
5. How can you learn a new project management tool quickly?

Before you move on

You're ready for Module 6 when you can say yes to each of these:

• I can build a company folder system with clear file names.
• I can turn a real document into an approved template.
• I can compare project management tools and explain my research.
• I follow good security habits with client information.
• I can write an SOP and plan a 30-day onboarding.