Workflow
Coordinate Nonprofit Board Recruitment in Finta
Coordinate nonprofit board recruitment with a role brief, permissioned candidate stages and an Aurora preparation workflow. Keep selection with authorized leaders.

- Audience
- Authorized nonprofit recruitment coordinators and board leaders
- Products
- Aurora, CRM, Documents
- Prerequisites
- Approved source context, Named workflow owner, Review of outgoing actions
- Expected outcome
- A permissioned candidate board, reviewed role expectations and an owned next conversation.
- Approval boundary
- The workflow owner confirms facts, recipients, permissions and final external actions.
Keep nonprofit board recruitment moving with a permissioned candidate list, a clear statement of board needs and a next action for every conversation. Use Finta for relationship context and Aurora for preparation, while the board's authorized people make selection and governance decisions.
This workflow handles the relationship and preparation work, not candidate selection. Follow your organization's bylaws and authorized review process. BoardSource's recruitment guidance is a useful starting point for role expectations and governance responsibilities.
1. Define the board need
Prepare a role brief covering the organization's mission, responsibilities, expected time commitment, current board priorities and recruitment owner. State which questions candidates should be able to answer before considering the opportunity.
Avoid collecting an extensive personal profile because a CRM can hold one. Retain only the information relevant to a permitted recruitment conversation, with appropriate access and permission.
2. Build the relationship stages
In Finta CRM, create stages or categories that match your process. Add only the candidates and connectors you are authorized to record. Use tags or approved custom fields for role interests, relevant experience and next-step ownership.
| Stage | Entry evidence | Next action |
|---|---|---|
| Potential introduction | A relevant, permissioned connection | Ask the connector whether an introduction is appropriate |
| Introduction agreed | Connector and candidate agree to the conversation | Arrange the first discussion |
| Exploring the role | Candidate has the accurate role brief | Discuss responsibilities and questions |
| Authorized review | Required materials are ready for the proper reviewers | Follow the board's process |
| Closed or deferred | Decision or preference recorded | Respect the agreed follow-through |
A connector mentioning someone is not consent to a bulk invitation. Keep an offered introduction separate from a completed one.
3. Ask Aurora for a preparation brief
Use the approved role brief and these permitted conversation notes. Prepare questions about responsibilities, candidate interests and unresolved expectations. Link factual points to the supplied sources. Do not infer sensitive personal characteristics, rank suitability, make a selection decision or send an invitation.
Aurora works from available workspace context and supported connections. If a source is missing, supply an approved summary rather than assuming an external board portal is connected.
4. Make the first conversation useful
Illustrative invitation:
Hi [Name],
[Connector] confirmed that an introductory conversation would be welcome. Our board is exploring [accurate role need]. I would be glad to share the responsibilities and hear your questions before either side considers next steps.
Would a short conversation be useful?
Review the message and send it through your approved channel. Record the actual response, not the outcome you hoped for.
5. Close the loop after review
Keep the board decision, communication owner and next action visible. A suggestion from one member is not a board appointment. Preserve the organization's formal approval record outside a casual AI summary.
| Final receipt | Check |
|---|---|
| Accurate role brief | Responsibilities and expectations reviewed |
| Candidate communication preference | Actual consent or preference documented |
| Authorized review status | Proper decision-makers and process identified |
| Next action | One owner and a real date or stopping point |
If permission is missing, stop outreach. If requirements conflict, resolve them with the appropriate board leader. If Aurora introduces unsupported details, correct the source record before reusing the brief.
For the wider relationship program, explore nonprofit development in Finta. For permissioned introductions, continue with our warm-introduction workflow.