# Everyday workflows

Put projects, tasks, notes, sources, and checks together in practical routines.

## Start the day

1. Find the project from the sidebar or **⌘ K**.
2. Open **Overview** and check unfinished tasks and any inbox items.
3. Review dependency or folder warnings that need attention.
4. Open the brief or setup document and the linked source folder.
5. Move the card you are starting into the appropriate Tasks list.

Saved provider data is useful context, but refresh it when you need the latest remote state. Local folder scans and provider refreshes are separate.

## Capture a meeting or planning session

Write rough notes in the scratchpad and wait for autosave. Move a lasting decision into a document. Add useful URLs as links, and upload a screenshot or reference file to Assets.

For a plain task checklist, use **Tasks → Paste tasks**. If you have [scratchpad AI](/guide/integrations/scratchpad-ai/) connected, choose **Generate actions** to suggest cards, documents, links, and project changes from mixed notes. Review the suggestions before saving. Your original notes stay in the scratchpad.

## Work on a monorepo

A monorepo keeps several apps or packages in one repository. Link its local folder under **Sources**, then add a [package location](/guide/sources/dependency-checks/) for each part you want to check, such as `apps/web` and `services/api`.

Check the package locations and filter findings by folder. Give a location a runtime override only when it needs a different tool path from the workspace defaults.

## Prepare a release

Review unfinished cards, document release decisions, and check current dependency results. Refresh repository activity for build status and open pull or merge requests. Open an item on GitHub or GitLab to act on it; Orbit displays that activity for reference.

Record deployment links with useful names and notes. Keep production credentials in the correct Secrets environment. If your release process needs an .env export, include only the required values.

## Finish or hand over a project

Save a current document with setup instructions and decisions, then archive finished work to retain its context.

For a handover, share the project's required documents and files, provide access to its source repository, and transfer necessary credentials through a suitable secure channel. A workspace export includes **every project**, so only share one when the recipient should receive your entire workspace.

If you are moving your own workspace to another Mac, follow [export and import](/guide/settings/export-import/). After importing, relink folders, reconnect accounts, and run fresh checks. The archive does not contain source code, vault secrets, or provider credentials.