An invitation to build and learn · practice draft 0.1

Make one useful change.
Learn with the team.

A clearer volunteer page, a simpler handover or a more visible next step. Begin with a job your team wants to improve, then inspect a proposed change before choosing what to adopt.

Prepare a case file Compare a visitor task Discuss a website preview Explore a one-workflow OS pilot

Improve the system around the work.

Follow the signals, channels, work, outcomes and feedback around one task. A volunteer page can help someone find a relevant role; a review process can clarify who decides what happens next. The proposed improvement still needs testing with the people using it.

Relief, repair, prevention, structure and source describe where work acts. Every level may be needed. This program studies mechanisms and practical friction; it does not rate charities or judge the good they do.

An inspectable starting point

From a public page to an agreed next step.

01
Choose one visitor task.
Read the charity’s current official pages and agree what matters: finding a role, understanding a program or reaching the correct contact. Record observed behavior separately from assumptions about its effects.
02
Prepare a private concept.
Use original draft copy and appropriately licensed material. Label the version, proposed changes and limitations. Keep actual donations, applications and sensitive information on the charity’s existing authorized routes.
03
Let the charity decide.
The charity chooses whether to use any change. Confirm who can approve the exact version, its hosting, rights, checks, backup and rollback before publication. A preview does not replace the official website.
04
Review what actually happened.
Record useful feedback and problems after any agreed use. A cleaner layout, completed task or favorable comment is not proof of extra donations or mission impact. Change the proposal when the evidence calls for it.

One visitor task · your local file

Keep the change and the learning together.

Write one case, inspect both working briefs and download a compatible Nonprofit Advisory backup to resume later. Nothing is saved between visits or sent to a server. Use roles, public information and fictional examples; keep private staff, donor and participant details out.

This is an untested practice guide. A file, checkbox or local status does not establish permission, a completed pilot, adoption or improved charitable outcomes. Website help can stand on its own.

Website task case

1. Choose one visitor task

Use a project alias and public information. Blank context stays unknown.

Case alias One visitor task Question the website decision should answer Current method that must be preserved

2. Record the current website

Describe a task you actually inspected. A hypothesis is separate from an observation.

Official public website URL · optional HTTPS only. Do not include private links or credentials. No page is fetched. Date actually inspected · optional YYYY-MM-DD. Leave unknown dates blank. What you actually observed, or what remains unknown Basis for the observation Access limits, missing measures and rival explanations

3. Describe the private concept

Keep donations, applications and personal records on the charity’s existing authorized routes.

Proposed change and why it might help Exact changes proposed Private preview version, file/hash or reference A reference is not evidence that a reviewer approved it. No preview is opened or hosted here. Responsible role Time budget, support and work displaced How people can disagree accessibly Data boundary, retention and stop route Proposed period and next checkpoint

4. Keep decisions separate

These are your notes about outside decisions. A local status supplies no permission, subscription or approval.

Website publication decision-maker role · optional Website publication decision, exact version and evidence/reference State unknown, withheld or the actual separately obtained decision. Keep private contacts out. Publication evidence record Separate recurring-update purpose, cadence, stop route and permission Separate permission for a public name, quotation, logo or case study

5. Review what happened

Record criticism, missing evidence and reasons to keep the current tool as well as favorable findings.

Task completion condition, unit and observation window Comparison method and its limits Aggregate feedback, disagreements and whose view is missing What is known now · negative or unknown findings are valid Continue, revise, pause, stop or keep the current tool — and why Actual or next review date · optional

6. Optional OS trial notes

Leave this separate task unknown if no OS trial was agreed. Website observations do not become OS results.

Separate OS participation decision and allowed scope Declining an OS trial does not change an agreed website contribution. Separate authorized OS owner role · optional Separate OS recurring-update purpose, cadence, stop route and permission One separate OS workflow · leave unknown if not chosen OS task completion condition and observation window OS hypothesis, baseline, setup/help time, comparison and limits OS feedback, difficulties and missing perspectives OS observations, export/recovery actually tried or unknown OS next decision and cleanup/access plan OS review date · optional

Resume an existing case file.

Choose this guide’s Nonprofit Advisory v1 JSON file, up to 8,000,000 bytes. Previewing changes nothing. Extra records in a compatible file remain in its complete backup. General Nonprofit Advisory files without this named case belong in the full local desk.

Choose native case JSON

Keep unfinished writing or the last valid file.

The writing copy retains current fields as JSON-quoted plain text, including invalid dates. It is not a restore file. The last valid native backup retains all records but excludes later unreviewed or invalid fields. Downloads do not clear the warning about leaving this page.

A shared workspace is a separate choice.

The published Charity OS home opens separately and requires sign-in and organization choice. This experimental handoff sends no file or fields and creates no account, record or invitation. Use the local Nonprofit Advisory desk for the current file workflow. Shared case-file inspection is experimental and is not offered by this guide.

I choose to reveal the existing OS home link. This does not enroll me or authorize an OS trial.

Enable JavaScript to prepare a local case.

Practice draft · Manual observations

Compare one visitor task.

Try the same task on the current page and the proposed version. Keep the starting point and success criteria consistent where possible. Record what happened and any differences in the setup.

Use general task descriptions and roles. Leave names, contact details and private links out. Entries stay on this page until you leave. Download a copy if you want to keep the handoff. Use the case guide for a larger project or a case you want to resume.

Visitor task worksheet

Visitor task Required For example, find the next volunteer orientation from the home page.

Proposed change Required Describe one change and include a short version reference if you have one.

Test setup and differences Optional Record the starting point, device and input method. Include differences that affect the comparison.

Use the same rule for counting steps and time in both runs. Leave unmeasured values blank.

Current page Completion Navigation steps Optional Elapsed seconds Optional

Proposed version Completion Navigation steps Optional Elapsed seconds Optional

Proposed next step Optional Suggest a further check, a revision or keeping the current page. Use a role if someone needs to own the work.

Enable JavaScript to prepare a local handoff.

Review the draft handoff.

Current and proposed task observations
Measure	Current page	Proposed version
Completion
Navigation steps
Elapsed seconds

Inspect the exact text of the file below.

I reviewed this draft and checked that it uses non-identifying details.

Two separate choices

Website help can stand on its own.

An OS pilot is optional. Declining it should not change an agreed website contribution. A conversation also does not establish a service engagement, delivery deadline, account, migration or institutional partnership; we agree the actual scope and capacity with each team.

One workflow · fictional records first

Try a small Charity OS pilot.

Choose a task such as a volunteer handover, a grant review or finding the source behind a decision. The following two-week sequence is an editable proposal, not a validated timetable or an already completed study.

Agree the question.

Choose a responsible role, one fictional example and what the current process does well. Keep baseline values unknown until someone observes them. Agree a stop decision and a way to disagree.

Try the actual work.

Exercise the relevant permissions, review, approval and export/recovery steps. Count setup and help time as well as task time. Keep difficulties and missing capabilities visible.

Review and revise.

Separate bugs, unclear wording, training questions and missing features. Inspect the exact changed version. A descriptive comparison from one team does not establish causal or general benefit.

Choose what comes next.

Continue, revise, pause, stop or keep the current tool. Agree cleanup and access. Publishing a name, logo, quotation or case study requires its own permission.

Discuss a pilot

Existing Projects and tasks and Resources can support an agreed example after sign-in and organization choice. These links create no record or access grant. The implementation plan explains current scope and remaining specialist/integration work.

An open invitation · volunteer coordinators

Practice one volunteer shift handoff.

Spend 25 minutes on a made-up shift with a coordinator and two adults who choose to take part. Both volunteers can read and agree to their own part of the change. The confirmed place stays where it is until staff confirm the handoff.

Keep your existing schedule. After the practice, tell us which steps were clear, where anyone needed help and whether the roster ended as expected. Share process notes without volunteer names, contact details or private screenshots.

Discuss a shift handoff pilot Read the practice steps Share with an interested coordinator

Take the working documents

Write down the scope and the learning.

These editable Markdown briefs work in a text editor or on paper. They keep missing values, publication decisions, recurring-update permission and OS participation separate.

Website preview and change-review brief ↓Editable Markdown · draft 0.1 · CC BY 4.0 One-workflow Charity OS pilot brief ↓Editable Markdown · draft 0.1 · CC BY 4.0

Automate preparation. Keep decisions explicit.

A recurring workflow can check current public sources, prepare a revised private concept, retain a change list and queue a message for review. The website owner approves publication; recipients choose whether they want recurring updates, their purpose and cadence. A published inbox or past conversation supplies no automatic permission for a sequence.

Early concepts use public information and fictional records. Keep private donor, staff and beneficiary information out of a first message. Existing forms, payments, accounts, credentials and data integrations need their own agreed scope.

Join communities by contributing.

Start with the group’s purpose, eligibility and current rules. Offer a useful answer or resource, ask organizers where a pilot invitation belongs and accept a refusal. Participation is not permission to harvest contacts or privately message members with a pitch.

Use the networks directory to find peers and share a practical question. These three starting points were checked against official sources on November 5, 2026. A listing does not establish membership, endorsement or permission to recruit.

Three places to begin · source review draft

Find the community that fits the contribution.

NTEN community

A nonprofit-technology community that welcomes staff, volunteers, funders, consultants and vendors. Its public entry page says community access needs a free account; paid membership is separate.

Ask the Community team about the right group and invitation rules before offering services or recruiting participants.

Opportunity Hack

A year-round social-good technology community. Its signup page invites developers, designers and data practitioners to a free Slack community for collaboration around nonprofit projects.

The specific rules for outside projects and pilot invitations need organizer confirmation. Start with the general inquiry form.

TechSoup community and Connect

TechSoup’s 2021 announcement describes Connect as the successor to NetSquared. Qualification for technology offers is a separate process.

Current event and forum access was limited in this review. Confirm current availability, eligibility and participation rules through the official support route.

Keep organizer replies and member information private. Ask about additional group rules; a community account does not authorize promotional messages.