Setup help for a local-first planner.

First run

1. Open Effort Plan and go to Settings.
2. Set your normal workday capacity and buffer in General settings.
3. Add one integration or create a manual task.
4. Plan a task to a day and choose the hours for that allocation.

Azure DevOps setup

Azure DevOps imports are read-only in the current release. Configure the organization/project, choose import rules, then sync assigned daily work such as tasks and bugs.

• Use default daily-work rules for normal planning.
• Use custom work item types, states, area, iteration, and tags when needed.
• Effort values are treated as hours when imported from common Azure DevOps scheduling fields.

Outlook local sources on macOS

Due to Microsoft restrictions, Effort Plan reads Outlook schedules and tasks from macOS Calendar and Reminders instead of connecting directly to Microsoft 365.

1. Open macOS System Settings and add the Microsoft work account.
2. Enable Calendars for meetings and Reminders for tasks when available.
3. In Effort Plan, open Settings, then Integration, then Add new for Outlook Calendar or Outlook Tasks.
4. Effort Plan shows a short notice first. Close it to continue.
5. When the permission request appears, choose Allow, then select the local account.

Export and import local data

Use Settings, Local Storage to export local planner data. The export is designed for moving to another computer or keeping a backup.

• Included: tasks, allocations, work-done notes, dismissed items, integration metadata, and app settings.
• Excluded: passwords, OAuth tokens, Azure DevOps personal access tokens, and other secrets.

Known limits

• Outlook Email import is not supported in this release.
• Current imports are read-only and do not push updates back to source systems.
• Current installers are unsigned preview builds.
• Windows local Outlook support will evolve separately from macOS EventKit support.