Work together
Open the shared Charity OS to create an organization and invite your team. Its 26 modules connect programs, projects, grant seeking and delivery, budgets, contacts, volunteers, events, evidence, governance and documents. Roles and optional program assignments control access. Record ownership names responsibility; it does not grant permission.
Keep working drafts, comments and decisions together. Another authorized reviewer must approve a revision before it can become an approved snapshot. Board and external readers see permitted approved snapshots. Frozen reports retain the source revisions and a checksum so later edits do not quietly rewrite a past report.
The shared service also has a grant-period report workflow. Select one agreement, one program and a period; prepare approved sources, save their versions for separate approval, then preview and freeze an immutable report. Awards, external receipts, spending references and planning remain distinct. Unknown amounts stay unknown, and observations retain their units and limits without becoming causal claims. An eligible board reader receives a separate approved projection rather than private source records. This does not certify accounts, submit a funder report or establish actual human review of test records.
Read-only CiviCRM, OpenProject, Kobo and CSV connections have an explicit preview before import. Configure your own credentials; a connection is not automatic two-way synchronization. Files, revision checks, recoverable trash and private JSON backups support handover and recovery. Original import archives can be downloaded separately. Personal reminders run in the daily dispatch after their due time.
Accounting records hold external references and reconciliation controls. The OS does not post a ledger, run payroll, move money or issue tax receipts. Casework and safeguarding hold opaque codes and specialist-system references rather than private case narratives.
The shared service also supports public operational requests. Approved, version-bound forms can collect minimal contact, event-interest and volunteer-interest requests with explicit consent. A private receipt checks status or withdraws the request; an administrator separately reviews it before preparing unapproved drafts. Sending a request does not book a place, assign a volunteer or subscribe to a newsletter. Answer erasure is separate from withdrawal and cannot remove earlier backups or separately prepared contacts. Restored forms and receipts remain inactive. Controlled checks used synthetic requests; real participant use and actual human review are not implied. Your requests provides separate account access to requests you explicitly link. Both a matching verified email and the saved private receipt are required. Review your own submitted answers, correct eligible pending answers with fresh consent, withdraw, erase answers or permanently unlink account access. Signing in alone searches no requests and grants no team role. Backup imports restore no participant access.
The Participation console adds explicit confirmation and waitlists for individual places at event sessions or volunteer shifts. A reviewed interest request reserves no capacity. Staff must enable the occurrence, associate the typed candidate and obtain specific consent before confirming a place. Promotion is manual. Confirmed capacity stays reserved through later review edits, and cancellation releases it once. Your linked request can show your own participation and let you cancel it; withdrawing the original request alone does not cancel a confirmed place. Operational email requires a separate fresh choice from the verified participant. An administrator reviews current confirmations before activating delivery; old preferences and paused history are never mailed automatically. The fixed notice links to the signed-in portal without putting occurrence details or receipts in email. Delivery runs in a bounded daily dispatch, so it is not an urgent or exact-time alert. Turning updates off, erasing answers or unlinking access stops unsent updates; a message already attempted may still arrive. Broader workflows and operational acceptance remain in the implementation plan.
Manage shifts, attendance and renewals
- Site orientation. Review a requirement for one eligible volunteer shift. Record completion from the organization’s own register. New confirmations and waitlist promotions require current evidence for the whole shift. Training eligibility guide
- Offline attendance. Download a worksheet for an approved Events session. Enter totals offline, then reconnect to review and save an attendance draft. Offline attendance guide
- Membership renewal. Members can start from a linked contact request. If a member prefers to renew in person, one staff member records their choice and another reviews the same approved term. Online renewal guide · In-person renewal guide
Review two contact records
Use the contact-review workspace. It is for an organization owner or administrator with unrestricted Contacts access. It does not decide that matching names or emails belong to one person.
Choose two person-reference records deliberately. Read the Left and Right values and IDs; Unknown means no value is recorded. You can keep both records and explain whether they describe different people, a household, separate roles or an unresolved comparison. That decision creates no household access or account relationship.
For an eligible merge, both records must be unapproved local drafts. Choose the ID to keep, the title to use and the source of each display label and email. Choosing Unknown clears that selected field. Organization, role, contact preference, purpose and review date must already agree. Source-owned records or private and historical links can prevent a merge; this first version does not move their references.
Review the proposed result and acknowledge it before Commit. The surviving ID stays; the other record goes to trash with its history retained. No consent, participant link, account permission or external identity is transferred. If the result is interrupted, use deliberate Retry for that exact command. Do not start another decision merely because its response is missing.
An undo needs its own review and the original saved command. Later edits or new dependencies can block it. Historical reports restored from a backup do not restore a live command or permission to undo. Keep the original backup; restored history is not an instruction to repeat a merge.
Some existing workspaces are outside this first version, including those with unsupported legacy, Learning or grant report packets. Keep their history and use ordinary Contacts editing while that coverage remains unavailable. Do not delete history to make a merge eligible. Read the contract and the software checks and limits.
Coordinate a group booking
Staff can group 2–10 existing requests for the same event session or volunteer shift. Each person’s consent and approval checks remain separate, and each admitted person holds their own place. Review all members or deliberately select a smaller subset. Capacity and overlap are checked together; if any selected person cannot be admitted, that selection reserves no places. Cancellations name the confirmed members whose places should be released.
In the shared OS, open the occurrence in Participation, then choose Open staff group tools. Grouping requests grants no household access or authority for a coordinator to consent or act for others. Read the software checks and their limits. Real participant use and charity pilots remain separate from those checks.
Bring a plan into shared learning
Start a Theory of Change in the Impact Measurement Toolkit, or prepare a learning row in Nonprofit Advisory. In the shared OS, deliberately choose the saved file, inspect the selected material and review the proposed Learning drafts. This copies a version for review; it does not keep the browser tool and team workspace synchronized.
Connect the plan to observations with their units, sources and limits. Write a review of what the team learned, including uncertainty, missing evidence and what to change next. Another authorized reviewer must approve eligible revisions through the ordinary review process. A frozen report keeps the chosen source versions and authored interpretation together. Access follows organization, program and role permissions. Importing a plan, recording attendance or approving a draft does not establish that an activity caused an outcome.
Import aggregate visits as observation drafts
In the shared OS, choose Aggregate field responses. Download the empty JSON template and prepare a file in its declared visits format. Choose a current program, its matching visits indicator and a CSV source identity configured by an administrator. Read the whole-file transmission notice before inspection, then deliberately select the rows to retain.
Unknown counts and denominators stay unknown; supplied zeroes remain zeroes. Selected exclusions keep their reasons without creating observations. Review every proposed draft and its selected source manifest before committing. A source hash identifies the retained values; collection quality and causal interpretation still need review.
The import creates ordinary unapproved observations with unknown evidence. Later edits stay separate from the original manifest. Interrupted saves retain one exact command for deliberate Retry. Complete workspace backups preserve historical manifests and restore observations as unapproved drafts. Connections return unconfigured; accepted commands and credentials stay outside the restored workspace. Read the format and boundaries.
Record a whole-occurrence attendance count
For an eligible ended event or volunteer shift, staff can load the current occurrence and enter the observed attendance total for the whole occurrence. Confirmed places provide context; they are neither the default count nor a cap. Keep registrations and walk-ins unknown unless the corresponding facts are known. This draft leaves volunteer minutes unknown. Attendance does not by itself establish hours worked or a service outcome.
Review the exact proposed record, acknowledge its whole-occurrence scope and create an unapproved draft. Open that ordinary record for corrections and separate review. This is staff reporting, not participant check-in or a partial-shift booking workflow.
Draft the next recurring task
In the shared OS, open a saved weekly, monthly or quarterly task and preview its next occurrence. Review the exact local time, time zone, UTC instant and copied fields before generating one planned, unapproved draft. Monthly dates retain the original anchor, so a January 31 schedule returns to March 31 after February. Repeated local times need an explicit instant choice; nonexistent local times refuse generation.
Each source has one next task across retries. End the series before changing its kind, program or schedule. A separately confirmed End stops future drafts and keeps existing tasks. Recovered history stays inactive. This is a manual planning workflow; it sends no reminder, assigns no participant place and makes no claim that the work happened.
Start with the local workspace
Write down your mission and the community’s role in shaping it. Add each program or project with its intended change, owner, budget, spending and target date. Depth is an optional working description, from relief to source. It does not grade the work, and unknown can stay unknown.
The grant pipeline keeps opportunities, stages, amounts, deadlines and next steps together. Link a grant to a project, assign an owner, then turn the next step into a task. The dashboard separates pending requests, awards and project budgets so the same money is not quietly counted twice.
Keep the feedback loop visible
The evidence log records what was observed, when, in what units and with what support. It can hold outputs, outcomes, no change and harms. Leave the value blank when it is unknown; zero means an observed zero. Use the notes and source link to explain the method and its limits. A change after a program is not by itself proof that the program caused it. The Impact Measurement Toolkit helps make that distinction.
Every record can be edited or deleted. Deleting a project keeps its grants, tasks and observations without a project link. Undo restores the previous workspace until the next change or reload. Search, project filters and status filters help find what needs attention.
Keep a copy of your local work
The smaller workspace on this page saves only in this browser. Owners are labels for organizing the work, not invitations or notifications. It does not send reminders or submit grant applications.
Export JSON to keep all fields and restore the local workspace on this or another device. The shared OS can also preview this local file and convert its records into drafts in an empty organization. It preserves the original file privately; owner labels do not become accounts, and observations do not become verified measurements. Import validates the whole file and shows a preview before replacing anything. CSV gives you the records for a spreadsheet; use JSON for a full restore. The fictional example is clearly marked and replaces your current workspace only after confirmation when there is existing work.
If browser storage is blocked or full, the workspace keeps working on the open page and shows a notice to export before leaving. Clearing browser data removes the saved copy. Use program-level records, and keep private case files in the systems your organization uses for them.