Matching method
Understand the rules, signals, limits, and review points behind matching.
2IX begins with visible rules because early matching needs trust more than mystery. More advanced scoring can come later, but the evidence should remain readable.
Rules
Start deterministic
Match obvious fields first: skills, work type, location mode, availability, cause area, verification, and screening requirements.
Evidence
Show the explanation
Every recommendation should show the positive signals, missing signals, and next action.
Learning
Improve from outcomes
Feedback from applications, completed work, and reports should tune the system without hiding the reason for a match.
1. A profile becomes signal
Volunteers publish skills, causes, availability, location preference, work samples, and a visibility setting. Private contact details are stored for follow-up, not displayed as public browsing data.
- Public: name, headline, skills, causes, broad availability.
- Limited: searchable fit signal with fewer personal details.
- Private: shared only through an application or steward workflow.
2. An organization turns a need into a scoped outcome
Organizations are asked for a concrete deliverable, steward contact, required skills, acceptance criteria, time estimate, screening notes, and project context before a post becomes useful.
- Good posts name the outcome and the first safe action.
- Weak posts are vague, unowned, or too large to start.
- Sensitive work must describe screening without exposing private records.
3. Fit is explained before commitment
The MVP score is deterministic and visible. It compares skills, availability, cause alignment, location mode, verification/readiness, and project context without pretending to be machine intelligence.
- Missing required skills are shown plainly.
- A high score is a starting point, not a guarantee.
- Color is never the only way status is communicated.
Key terms
- Scoped work
- A bounded outcome with a steward, deliverable, acceptance criteria, and estimated effort.
- Match signal
- Structured data that helps explain fit without exposing private information.
- Project readiness
- The degree to which a new contributor can understand current state and safely start.
Example deterministic match explanation
Transparent match signal
Rule-based fit estimate
79%
Skill fit
19 / 40
Matched required skills: Technical writing.
Availability fit
20 / 20
4 available hours compared with 3 requested hours.
Cause fit
15 / 15
Cause alignment: Civic technology.
Location fit
10 / 10
Volunteer prefers remote and opportunity is remote.
Trust/readiness
10 / 10
Organization verification is verified.
Project readiness
5 / 5
A project context brief is attached.
Missing required skills: Information architecture
- Matched skills: Technical writing, WordPress.
- Missing required skills: Information architecture.
- Cause alignment includes Civic technology.
- Availability meets the estimated commitment.
- The organization is verified.