A toolkit in Equip is a predefined set of content types used to generate content for a specific church event or ministry workflow. Toolkits help teams consistently create the right kinds of content by grouping related content generation tools around a shared purpose.
Once a toolkit is run, the generated content is created inside a project, where it can be reviewed, edited, and published alongside any source content uploaded to that project.
How Toolkits Work
Each toolkit is built around an event type, such as a staff meeting, worship service, or communication cycle. That event type determines which content types are included in the toolkit.
When you run a toolkit:
- Equip uses AI to generate content based on:
- The content types defined in the toolkit
- The source content uploaded to the project
- Generated content is created within the selected project
- Outputs reflect the specific context, messaging, and materials provided
The toolkit defines what types of content can be created—the project and its source content determine what the AI generates.
Toolkit Types in Equip
Equip includes several default toolkit types, each designed for a common church activity or workflow. These toolkits provide a consistent structure for generating content related to that event type.
Default toolkit types include:
- Mission Report
- Event Debrief
- Pastoral Visit
- Small Group Season
- Worship Service
- Weekly Comms
- Staff Meeting
- Kids Sunday
- Media Production
- Weekly Sermon
Each toolkit includes a specific combination of content types relevant to its event.
Content Types in a Toolkit
A toolkit consists of content types that define the kinds of content Equip can generate for that event.
Examples of content types include:
- Plans or agendas
- Written summaries or reports
- Email or communication drafts
- Media-related outputs such as captions, descriptions, or graphics
- Follow‑up or recap content
The exact content generated depends on:
- The toolkit’s configured content types
- The source content available in the project
Toolkits do not generate content in isolation—they rely on project context to produce relevant results.