All guides

When a change log is enough — and when you need project software

A solo designer may need a reliable record of decisions before they need another subscription.

Use a simple log for a small project

Record the request, estimate, decision, approval reference and actual hours. A workbook can keep those fields together without a new client account. It works best when one person owns the record and there are relatively few simultaneous changes.

Know what the workbook cannot do

A local spreadsheet will not authenticate a client's approval, collect a payment, send reminders or resolve editing conflicts between several people. Save the actual written approval in the agreed communication channel. The word “Approved” in your own log is not independent evidence.

Move to software when coordination demands it

If several people update requests, clients need a portal, or reminders are being missed, dedicated project-management or approval software may be worth the cost. Evaluate it against a real recent project rather than a long feature list.

Check export options, access controls, recurring fees and how the client sees a change. Try the approval and rejection paths, not just the attractive dashboard.

Keep the process portable

Whichever tool you choose, use stable change references and clear scope versions. Those practices make the record understandable when you change tools or revisit a project months later.