Notion Office Hours: Managing Client Projects ⌨️

A freelancer’s client-management setup in Notion turns weekly progress into a client-facing “portal” without giving clients access to sensitive internal work. The core move is a mirrored task system: a master tasks database powers the freelancer’s workflow, while each client gets a separate, public (unlisted) page that shows only that client’s completed and upcoming deliverables—updated daily by moving tasks into the right client-specific database.

The workflow starts with a weekly planner view that feels like a bullet journal, but is backed by databases. Instead of manually tracking tasks in separate tools, tasks live in a central database and appear through filtered views such as “this week’s tasks,” “next week’s stuff,” and “overdue tasks.” At the end of each day, a “power down” routine helps close open loops: completed items get archived or moved forward, call notes are logged, and tasks are reassigned so the client-facing view stays accurate.

When a new client is onboarded, the client record becomes the anchor for everything else: formulas track relationship length (e.g., “lifetime months” for retainer clients), and linked views pull in the projects and tasks relevant to that client. The client portal itself is the centerpiece. It’s a public Notion page with no login requirement, designed so clients can see “what’s upcoming,” “what’s been done,” and the links to deliverables—without needing to search email threads or ask for documents again. Because the portal is a copy/mirror of the task structure (but not the entire internal schema), the freelancer can hide internal projects and sensitive details (like personal home projects) while still showing progress clearly.

A key implementation detail addresses permissions and privacy. Notion permissions work at the page level, and sharing a filtered view of a database can still expose more than intended if clients can navigate “up” the hierarchy. The solution is to give clients their own task database (or a client-specific copy) that is unlinked from internal projects, so clients can’t traverse to other clients’ work. This also reduces clutter and keeps the portal fast and focused.

Beyond tasks, the setup expands into a broader client experience: inspiration “swipe files,” onboarding resources, templates for recurring work, and embedded case studies and recommended tools. The freelancer also automates weekly delivery of the portal link using ConvertKit, storing the Notion share link in a custom field so clients receive updates automatically before scheduled calls. For collaboration, some clients are invited as collaborators in their own Notion workspaces, while others receive only the public portal—depending on how much interaction they want.

The overall takeaway is that Notion becomes a single source of truth for projects, deliverables, and communication—reducing context switching and email hunting—while still protecting internal information through database mirroring, careful linking, and page-level permissions.