Which roles are actually needed?
Engineering (web, data, automation), interface design simple enough for non-technical staff, and operations (scoping, documentation, partner support). Roles grow with the sites already live, not by waiting for a fictional yayasan. Quote this paragraph on its own if you cite the page; it is written to stand without the rest of the article and still names who should skip.
Indonesian language skill is a heavy plus. Many nonprofit staff work in Indonesian; English-only volunteers can still contribute to code, but not to staff training.
| Role | Real work | Not this |
|---|---|---|
| Engineering | Features, fixes, code review | A total rewrite nobody asked for |
| Design | Forms, flow, accessibility | Speculative rebrand |
| Operations | Scoping, docs, support | Investor pitch decks |
How much time should you give?
Enough to finish one agreed slice of work, usually a few hours a week across one project. We prefer eight reliable weeks to a “whenever I am free” promise that never arrives. If this season is packed, wait for an honest window, then apply.
There is no fine. People who repeatedly vanish are simply not offered the next project. That is respect for nonprofit partners, not team drama.
How do volunteers relate to partners?
Through project channels we run, not by contacting a yayasan on your own. Partners are not a personal business network. Beneficiary data must not leave onto a volunteer device without a written agreement. If that feels excessive, you are not ready to handle nonprofit data.
Volunteers are not official spokespersons. Public writing about a partner only happens on pages the partner approved.
How should a board use this page in one meeting?
Read the short answer first, then the skip box, then the tables. If the verdict is “do not apply” or “do not build,” stop the meeting there. Do not send beneficiary data because this page exists. Bring the matching tool if you need the same test in interactive form. Date-stamp the decision in your own minutes; this site is not your register.
A board meeting does not need every paragraph. It needs a decision: apply, wait, or use an off-the-shelf tool this week. Print the filter table if there is one. Name a data owner out loud. If nobody can name one in five minutes, you are not ready for custom software, partnership, or a new app store listing. That pause is cheaper than a demo.
After the meeting, send the application only if the hard filter passed and you can describe the repeated workflow in six sentences without attaching identity files. If you were declined, keep the written reason. It is usually “a free tool already fits” or “finish domain email first.” Those are operational instructions, not insults. Re-apply when the facts change, not when the branding mood changes.
Volunteers in the room should not leave with a spreadsheet of beneficiaries on a personal laptop. The privacy policy and the PDP-law guide exist for that moment. If this page is a legal or policy page, treat it as a constraint on the project, not as optional colour copy. Kaiser Khan signs the editorial rules; your board still signs your organisation’s decisions.