Client Project Notes - What Every Freelancer Should Track

The project seemed clear. Then the client said "that's not what I asked for."

Without documentation, you have a he-said-she-said dispute. With documentation, you have a reference that resolves the confusion immediately.

Good project notes aren't bureaucratic overhead—they're protection and memory in one.

What to Capture for Every Client

Contact information: Names, emails, phone numbers, best communication channel, timezone, preferred contact times.

Project scope: What you agreed to deliver. As specific as possible. Reference contract language.

Timeline: Key dates, milestones, deadlines. Both client deadlines and your internal ones.

Budget and payment: Total amount, payment schedule, what's been paid, what's outstanding.

Communication preferences: How does this client like to be updated? How often? What level of detail?

Key contacts: If multiple stakeholders, who decides what? Who approves final work?

This basic information prevents simple mistakes and supports difficult conversations.

Project Scope Documentation

Scope creep kills freelance profitability. Combat it with explicit scope notes.

For each project, document:

• What deliverables are included
• What is explicitly excluded
• What assumptions are you making
• What depends on the client providing something

Example:

## Scope: Website Redesign

### Included
- Homepage design (1 revision round)
- 5 interior page templates
- Mobile responsive versions
- Design files in Figma

### Not Included
- Content writing
- Stock photography (client provides)
- Development/coding
- Ongoing maintenance

### Assumptions
- Client will provide brand guidelines
- Existing logo will be used
- Feedback consolidated from one decision-maker

### Dependencies
- Brand guidelines needed by [date] to meet timeline

When the client asks for content writing mid-project, you can reference this note: "That's not in our current scope, but I'm happy to provide a quote for that addition."

Communication Logs

Every significant communication should be noted:

• Date
• Participants
• Key points discussed
• Decisions made
• Action items (who does what by when)

You don't need transcripts. You need records of what was decided.

Example:

2024-03-15 - Call with Sarah (30 min)
- Reviewed homepage mockup
- Decision: go with blue color scheme (Sarah approved)
- Decision: reduce hero image size
- AI: [Me] Send revised mockup by Friday
- AI: [Sarah] Provide testimonial text by Monday

Email creates its own record, but calls don't. Log calls immediately after they end.

Decision Documentation

Decisions have a way of being forgotten or revised in memory.

When a significant decision is made, note:

• What was decided
• Who decided it
• When it was decided
• What it replaced (if changing course)
• Why (brief rationale)

This is especially important for decisions that might cause future problems. "Client insisted on approach X despite our recommendation of Y" is valuable when X doesn't work.

Feedback and Revision Tracking

Track all feedback received:

• Date feedback received
• Source (who provided it)
• Summary of requested changes
• How you addressed each point
• Round number (first revision, second revision, etc.)

When disputes arise about revision rounds, this log is evidence.

Example:

## Revision Log

### Round 1 - 2024-03-18
Source: Sarah via email
- Make headline larger ✓
- Change button color to green ✓
- Add phone number to footer ✓
Sent revised version: 2024-03-19

### Round 2 - 2024-03-22
Source: Sarah and Marketing Director via call
- Revert button to original blue (contradicts R1) ✓
- Add secondary CTA section ✓
Note: Secondary CTA is scope addition, documented in email

Time Tracking Integration

If you bill hourly or need to estimate future projects, track time spent:

• By task type (design, communication, revisions, admin)
• By project phase
• Including unbillable time

This data improves future estimates and identifies unprofitable patterns.

Client Preferences and Quirks

Note things that make the relationship smoother:

• How they like to receive updates
• Pet peeves (specific formatting, response times)
• Terminology they use for things
• Internal politics to navigate
• What went well in past projects

This institutional knowledge makes future projects easier.

End-of-Project Documentation

When a project concludes:

• Final deliverables provided
• Outstanding invoices and payment status
• What worked well
• What you'd do differently
• Whether you'd work with them again and why
• Referral/testimonial status

This review informs future client selection and project management.

Note Structure for Client Projects

# [Client Name]: [Project Name]

## Quick Reference
- **Contact:** [name, email, phone]
- **Project:** [one-line description]
- **Timeline:** [start] - [end]
- **Budget:** [amount] ([payment terms])

## Scope
[What's included, excluded, assumptions, dependencies]

## Communication Log
[Chronological record of significant interactions]

## Decisions
[Key decisions with date, who, and rationale]

## Revision Log
[Feedback received and how addressed]

## Files and Links
[Where deliverables, contracts, and resources are stored]

## Notes
[Anything else relevant]

Keeping Notes Current

Notes only help if maintained. Build updates into your workflow:

• After every call: spend 2 minutes logging
• After every feedback round: update revision log
• Weekly: review active project notes for currency

The overhead is minimal compared to the protection provided.

Starting Today

Your next client interaction: open a note and capture the basics. Start simple. Expand as you see what you need.

One hour of documentation now prevents one day of dispute resolution later.