Skip to content

Templates

Most nonprofit paperwork is the same paperwork

A volunteer agreement goes out forty times a year to forty different people, with the same route, the same reminder cadence and the same covering note. Save that once.

Labelled file boxes and manila folders on an open wooden shelf, one pulled forward.

What this looks like today

Rebuilding the same route every time

Re-typing the same three approvers in the same order, and getting it wrong on the fortieth attempt.

The covering note drifts

Ten people write ten versions of “please sign by Friday”, and one of them forgets to say by when.

Only one person knows how it should go

When they are on leave, the process stops, or somebody guesses.

What Baton does about it

  1. 1

    Save a workflow you already trust

    Recipients, roles, routing order, reminder cadence and the message, kept as one named template.

  2. 2

    Start from it next time

    Pick the template, attach the document, change the one address that differs, send.

  3. 3

    Change it in one place

    When the approver changes, it changes for everybody who uses the template rather than in forty people’s habits.

What is true right now

Every line below describes something the product does today. Nothing on this page is a roadmap item wearing a feature’s clothes.

  • Templates belong to the organization, not to the person who made one.
  • Every field a template sets can still be changed on the individual send.
  • Reminder cadence saved with the template overrides the organization default.
  • Nothing is locked: a template is a starting point, never a rail.

The rest of the product

Send your first document today

Sign in with your email. We send a six-digit code, there is no password to invent. Name your organization, and you are on the board.

Start free

150 documents a year free for nonprofits. No credit card to start.