WORKED EXAMPLE · FICTIONAL DETAILS
A client follow-up tracker for freelancers
A project can be on your desk even while the next move belongs to someone else. A useful follow-up record tells you what is missing, who promised it and when you will check again. It does not require a second project-management system.
Start with the next dependency
Suppose a fictional designer has finished the first homepage draft. The client needs to supply approved copy before the next revision. Record the project, stage “Missing inputs”, the requested copy and the next contact date. A vague task called “Follow up with client” hides the dependency; “Ask for approved homepage copy” makes the next action clear.
Keep three dates separate
In this example, the agreed delivery deadline is 12 November 2026. The client promises copy on 5 November. You plan to check on 6 November if it has not arrived. The delivery deadline, promised date and your planned check-in are different facts. Do not move the deadline simply because a new promise arrives. Confirm the year and timezone whenever a message is ambiguous.
Use a small daily review
Check what is due today, then check promises that have passed. If the copy arrives, record that update and choose the next action. If it does not, send a short question yourself and record the actual contact. Keep only the context you need; do not paste a whole private conversation when one authorized excerpt is enough.
How this fits PakkaFollow
The reviewed workspace organizes owned records by stage, next date and recorded promises. CSV imports can be reviewed before saving. Public guides are available now; customer workspace access belongs to the planned paid subscription and is not opened by reading this page. There is no automatic inbox reading or client messaging.
Editable message examples
Check names, dates, amounts and permissions. Send through your usual channel only when you choose.