Module 3: Project Documents & Compliance

Core promise: By the end of this module, you can create, track, and file the paperwork that keeps a job organized, legal, and protected. You'll handle RFIs, change orders, submittals, permits, insurance certificates, lien waivers, daily logs, and meeting minutes.

Ask it → Change it → Approve it → Permit it → Insure it → Waive it → Record it

Why this module matters: This is where VAs become hard to replace. Contractors dread paperwork, and a missed document can cost real money. Your steady, accurate follow-through is the value.

In this module

1. The Paper Trail, Numbering, and Folders
2. RFIs
3. Change Orders
4. Submittals
5. Permits and Inspections
6. Insurance Certificates
7. Lien Waivers
8. Daily Logs and Meeting Minutes
9. Hands-On Exercises
10. Knowledge Check

Module learning objectives

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

• Explain why a written paper trail protects the contractor, and name the core project documents.
• Create, number, log, and track RFIs, change orders, and submittals.
• Track permits, inspections, and insurance certificates, including their dates.
• Collect and track lien waivers tied to payments.
• Turn field notes into a daily log and meeting minutes.
• File everything in a consistent folder and naming system.

Lesson 3.1: The Paper Trail, Numbering, and Folders

Construction runs on a simple rule: if it isn't written down, it didn't happen. Verbal agreements get forgotten or remembered differently. Written records settle questions about who agreed to what, when, and for how much.

Four habits for every document

Log it → Send it → Track it → File it

• Log it: give it a number and add it to the right tracker.
• Send it: deliver it to the person who needs to act, with a clear deadline.
• Track it: watch for the response and follow up.
• File it: save the final version in the right folder with a clear name.

A simple folder structure

Each project gets one main folder with the same subfolders every time, so anyone can find anything.

Hartley Kitchen Remodel
01 Contract
02 Permits and Inspections
03 Insurance Certificates
04 Subcontracts and Quotes
05 RFIs
06 Change Orders
07 Submittals
08 Daily Logs and Minutes
09 Photos
10 Billing and Lien Waivers
11 Closeout

Naming files

Use the same pattern every time: document type and number, a short description, then the date written year-month-day. For example: RFI-001 Island outlet location 2026-05-14. Dates in this order sort correctly, and the number makes each document easy to refer to. Module 5 goes deeper into building this system.

Lesson 3.2: RFIs

A request for information (RFI) is a formal written question about the drawings or specifications. It exists so that questions get a recorded answer instead of a guess. The electrician asking which side of the island an outlet goes on, in Module 1's exercise, was an RFI.

The RFI workflow

1. A sub or the contractor raises a question.
2. You give it the next RFI number and log it.
3. You send it to whoever can answer (the designer, architect, or owner), with a needed-by date.
4. You watch for the response and follow up if the date passes.
5. When the answer arrives, you record it, send it to everyone affected, and file it.

Example RFI

RFI #001
Project: Hartley kitchen remodel
Date: [date]
From: Brightline Electric, through Ridgeline Builders
To: Priya and Tom Hartley (there is no designer on this job)
Reference: Electrical drawing, island
Question: The drawings show an island outlet but don't say which side of the island it goes on. Please confirm the location.
Response needed by: [date, before rough-in]
Response: ______   Response date: ______

The RFI log

Lesson 3.3: Change Orders

A change order is a written agreement to change the scope, price, or schedule after the contract is signed. Owners change their minds, surprises appear behind walls, and the contract has to change with them. Without a change order, extra work is a dispute waiting to happen.

RFI or change order?

An RFI asks a question. A change order changes the deal. An RFI sometimes leads to a change order, such as when an answer adds work that wasn't in the contract.

The change order workflow

1. A request comes in, from the owner or because of a discovery on site. You log it.
2. The contractor prices it and decides the schedule impact. You collect any sub pricing.
3. You prepare the change order from the contractor's template.
4. The contractor reviews it.
5. The owner signs it, ideally before the work starts.
6. You update the contract total and billing, then file the signed copy.

Example change order

Change Order #1
Project: Hartley kitchen remodel
Date: [date]
Description: Change the cabinet finish from white to sage green, as requested by the owners.
Cost: +$1,150
Schedule impact: +5 days (cabinets must be reordered)

Original contract price: $48,500
Previous changes: $0
This change: +$1,150
New contract total: $49,650

Owner signature: ____________   Date: ______
Ridgeline Builders signature: ____________   Date: ______

Lesson 3.4: Submittals

A submittal is product information or a sample sent for approval before something is ordered or installed. It confirms that what's about to be bought is what the owner and designer actually want. On the Hartley job, the quartz countertop sample and the tile are submittals.

The submittal workflow

1. A sub or supplier sends product data or a sample.
2. You log it with a number and check that it's complete.
3. You send it to the person who approves it, with a needed-by date.
4. You record the decision and tell the sub or supplier.
5. Once approved, the item can be ordered.

Approval statuses

The submittal log

Submittals matter most for long-lead items. A slow approval can delay an order, and a delayed order can delay the whole schedule.

Lesson 3.5: Permits and Inspections

Most construction work needs a permit from the local building department, and most permits require inspections at set stages. Work that skips them can be ordered torn out. Tracking them is a core VA task.

What a permit application usually needs

• The completed application form.
• Drawings or a description of the work.
• The contractor's license number and proof of insurance.
• The fee.

Requirements and processes differ in every city and county. Check the building department's website or call them, and confirm with your contractor who is responsible for pulling the permit. Sometimes it's the contractor, and sometimes it's a sub.

Inspections

On a kitchen remodel, the usual inspections are a rough inspection before the walls are closed, and a final inspection at the end. You book each one, make sure the work is ready, and record the result. If an inspection fails, the inspector lists corrections. You pass these to the contractor, track the fix, and book the reinspection.

A simple permit and inspection tracker

Lesson 3.6: Insurance Certificates

You met the certificate of insurance (COI) in Module 1. It's the document that proves a sub or vendor has insurance. If an uninsured sub causes damage or gets hurt on the job, the contractor and the owner can end up responsible. That's why contractors collect a current COI from every sub before work starts.

What's on a COI

• The insured: the sub's business name.
• Policy types: commonly general liability and workers' compensation, sometimes commercial auto and umbrella.
• Policy dates: when each policy starts and expires.
• Coverage limits: the dollar amounts of coverage.
• The certificate holder: who the certificate was issued to, usually the contractor.

What you check

• The business name matches the subcontract.
• The required policy types are listed.
• The policies are active now and won't expire before the job ends.
• The certificate holder is named correctly.
• The limits meet what the contractor's contract requires.

You compare the certificate against the contractor's requirements and flag anything that doesn't match. You don't decide whether the coverage is good enough. That judgment belongs to the contractor.

Tracking expiration dates

Set a reminder about 30 days before any policy expires, so a renewed certificate arrives before the old one lapses.

Lesson 3.7: Lien Waivers

You met liens and lien waivers in Module 1. A lien is a legal claim against a property by someone who wasn't paid. A lien waiver is a signed document saying a sub or supplier has been paid and gives up that claim for the amount covered. Contractors collect waivers with each payment to keep the owner's property, and their own reputation, clear.

The four common types

A progress waiver covers work through a certain date. A final waiver covers the entire job. Always check that the amount and the through-date on the waiver match the payment.

Your role

1. When a payment is coming, request the correct waiver from the sub or supplier.
2. Check the name, amount, project, and through-date.
3. Record it in a waiver tracker.
4. File it with the billing records for that payment.

Contractors may also need to give waivers to the owner, or to the owner's lender, when they're paid. You can prepare those as well, after the contractor approves.

Lesson 3.8: Daily Logs and Meeting Minutes

A daily log records what happened on site each day. It's simple, but it can settle a dispute months later by showing who was there, what was done, and what went wrong. Meeting minutes do the same for decisions and promises made in meetings.

What a daily log includes

• The date and the weather.
• Who was on site, and for how long.
• The work performed.
• Deliveries, inspections, and visitors.
• Delays, problems, and surprises.
• Photos taken that day.

Usually the person on site sends quick notes, photos, or a voice message, and you turn them into a clean log.

Example daily log

Daily Log: Hartley kitchen remodel
Date: [date], Day 5
Weather: Cloudy, dry
On site: Delgado Plumbing, 2 people, 8:00 am to 3:30 pm
Work performed: Ran new water lines for the relocated sink. Started the gas line for the range.
Deliveries: None
Inspections and visitors: None
Issues: None
Photos: 6, saved to the Hartley photos folder
Tomorrow: Finish the gas line. Brightline Electric starts rough electrical.

Meeting minutes

Good minutes list who attended, what was decided, and who will do what by when. Send them within a day, while everyone remembers the meeting. The action items matter most.

Weekly meeting minutes: Hartley kitchen remodel
Attendees: Marcus Webb, Priya Hartley, Tom Hartley
Decision: The cabinet finish changes to sage green. Change Order #1 will follow.

Lesson 3.9: Hands-On Exercises

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

Lesson 3.10: Knowledge Check

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

1. Why should a change order be signed before the extra work starts?
2. What does "Revise and resubmit" mean on a submittal?
3. Why do you track expiration dates on insurance certificates?
4. What's the difference between a conditional and an unconditional lien waiver?
5. What belongs in a daily log?

Before you move on

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

• I can log, send, track, and file an RFI, change order, or submittal.
• I can tell an RFI, a change order, and a submittal apart.
• I can track permits, inspections, and certificate expiration dates.
• I know which lien waiver to request and what to check on it.
• I can turn field notes into a daily log and meeting minutes.