Freelance projects: keep scope, feedback and delivery aligned

1. Choose the space and the outcome

Feedback arrives in pieces and quietly changes the scope. Keep the agreed brief visible and convert accepted changes into explicit delivery tasks.

Open the app and use the space selector to choose your personal space or an authorized shared space. You can name a shared space “Client project”. The manual workflow works in a free personal space; AI and shared work require an eligible plan and allowance. Before inviting a member, check whether they should see the information in this case.

2. Keep the context in Notebook

Open Notebook, choose New note and enter “Client brief — agreed scope”. Replace the example below with your own information. Choose the appropriate folder, or create one from the folder row. After saving, reopen the note to confirm the content was stored.

Keep the client’s requested change beside your acceptance decision. Use a separate shared space only when the client should see the work. A completed task is an internal tracking record, not a signed acceptance or invoice.

Deliverable: one landing-page draft.
Included: copy layout and mobile structure.
Not included: payment integration.
Review: one feedback round.
Change requests: confirm before adding to delivery.

3. Turn the next steps into tasks

In Tasks, choose New task and name the first action “Confirm the project brief”. Add a short description and the case name. Set a due date for a real commitment. Enable a reminder separately if you need a notification: a due time alone is not a reminder. In a shared space, choose an actual member as assignee before saving.

The other two actions in this example are “Prepare the first draft” and “Check delivery against the brief”. These are separate outcomes; completing one does not complete the others.

4. Ask Doneh for help when useful

Return to Home in the same space and keep the approval shield enabled. Send the relevant note text with the prompt below rather than relying on a note title alone. Review proposed titles, dates, assignees and any deletions, then approve only the changes you intend.

This step is optional and requires AI access. If using voice input, check the transcription. Do not assume Gmail, Drive or Calendar is connected; this workflow also works without those integrations.

5. Review the result and close the loop

Find “Confirm the project brief” using task search. Use List or Kanban when reviewing several cases. Start a task when work begins and mark it done only after the outcome is reached. Add new facts or decisions back to “Client brief — agreed scope” so the next reader understands what changed.

Final check: one findable note, three non-duplicate tasks, confirmed owners and dates for commitments, and a clear next step. If saving fails, check the list before creating a second copy. Replace all fictional example data before using the workflow for real work.

Sources & further reading

1. Open the app
2. Plans and access