Back to Guides
First-time operations guide

Operations Quick Start

Organize tasks, reminders, documents, and team workflows. This page is built for the first week of internal setup: create one task flow, one reminder system, and one document home so your team is not managing operations through scattered tools.

What this guide gets you

1

One shared place for work that would otherwise disappear into messages and memory.

2

One reminder path so deadlines become visible before they become urgent.

3

One operations rhythm your team can repeat across tasks, docs, and ownership.

Before you open Operations

  • One real deadline, board date, or recurring responsibility your team needs to track.
  • A small set of files or notes you want to move into a shared operational home.
  • A clear sense of who should own the first task or reminder.

Start here

Use this order for your first operations session.

The goal is not to create a perfect operating system in one day. The goal is to move one real process out of personal memory and into a shared workspace the team can follow.

01

Open the operations workspace

Go to Operations in the top nav.

02

Create the first live task

Create your first task and assign it.

03

Set the reminder that keeps it visible

Set reminders for key deadlines.

Good day-one win

End your first session with one assigned task, one reminder tied to a real deadline, and one document or shared folder your team can return to tomorrow.

Core workflows

These are the operations motions that matter once the workspace exists.

Each workflow is here to make work visible, owned, and easy to revisit. That is what keeps operations from slipping back into inboxes and side notes.

Execution

Create and assign tasks

Start here when a real piece of work needs an owner, a due date, and a place to live outside someone’s head.

Outcome: Leave with a task flow the team can see and follow.
  1. 1
    Go to OperationsTasks.
  2. 2
    Click New Task.
  3. 3
    Assign a teammate and due date.

Timing

Set reminders

Use reminders once the task exists so deadlines stay visible early enough to act on, not just react to.

Outcome: Leave with fewer missed deadlines and less manual follow-up.
  1. 1
    Go to OperationsReminders.
  2. 2
    Add the deadline and frequency.
  3. 3
    Save to activate alerts.

Knowledge

Store key documents

This is where the team stops hunting across email, desktop folders, and shared drives for the file everyone needs.

Outcome: Leave with a clearer home for operational files and context.
  1. 1
    Go to OperationsDocuments.
  2. 2
    Upload files and organize folders.
  3. 3
    Share links with your team.

Ownership

Invite team or board members

Use this once the system is useful enough that other people should be involved, assigned, or given the right access.

Outcome: Leave with shared ownership instead of a single-person setup.
  1. 1
    Go to OperationsTeam.
  2. 2
    Click Invite and add their email.
  3. 3
    Assign the right role.

Keep momentum

The habits that keep operations from fragmenting again.

Operational drift usually comes from work living in too many places. These habits keep the shared system more useful than side channels.

FAQ

Questions teams usually ask once operations are shared.

These are the sticking points that show up after the team starts assigning real work and depending on shared reminders and files.

Good stopping point for today

If one real process is visible, assigned, and easy to revisit in the workspace, operations is already moving in the right direction.

Where can I see operations analytics?

Go to OperationsAnalytics for workload and risk insights.

Can I track budgets here?

Yes—use the Budget Builder under Operations.

How do I update team permissions?

Go to OperationsTeam and edit member roles.

Grant Guides & Resources - Expert Tips for Nonprofits | Expirely