search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Sector content and pathways

    Nonprofit: explain activities and participation

    An association must distinguish between discovering an action, joining, making a donation and volunteering. These intentions sometimes use the same pages, but require different explanations and confirmations.

    These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.

    All sectoral files
    Chairs and screen in an empty meeting room
    AI-generated illustration

    Explore all 28 review cases — An old campaign remains active

    Linking mission and concrete actions

    Present the mission with identifiable activities and their period. Distinguish Planned Action, Current Action and Balance Sheet. The numbers should indicate what they measure and their internal source validated. A photograph requires appropriate authorization; An illustration image does not prove the realization of an action.

    Preparing for the membership course

    Explain who the membership, its period and the steps of treatment is for. A form must ask what is needed at this step, then announce who resumes the request. When payment is delegated to a platform, check the link, displayed identity and confirmation before sending visitors.

    describe volunteering as a commitment

    Detail the missions, the place or the mode of participation, the expected time and the support offered. A simple invitation to help does not allow you to project yourself. Specify whether applications are open or if the page describes only the possible types of actions.

    Keep donations understandable

    Present the announced use of the funds and the operation of the payment. Promises concerning a tax receipt or benefit must be validated by the person competent for the situation of the association. Do not deduce these conditions by the simple fact that an organization presents itself as an associative.

    Ensure continuity with volunteers

    Prepare an update sheet: Responsible, Alternate, Events to be withdrawn and accounts belonging to the organization. Keep a publishing history. At each team renewal, test forms and recipients to prevent requests from reaching a person who no longer intervenes.

    Information to gather before writing

    • Mission and dated actions
    • Membership conditions and period
    • Detailed volunteer missions
    • Application processing circuit
    • Sources of balance sheets and image rights

    For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.

    A case for preparing the content

    Publish the approved version, not the latest draft

    Fictional case: meeting note v1 is approved and public. A newer v2 is still under review.

    Fictional teaching exercise: these texts and values describe no real business, course or product.

    Path to check

    1. Draft
    2. Review
    3. Approve
    4. Publish

    Compare the wording

    Avoid in this example

    The latest edit is our official version.

    More precise wording

    Approved note: v1. Draft v2 is under review; publication will change after approval.

    Scroll the table horizontally if needed. With a keyboard, focus the table and use the arrow keys.

    Three checks based on the supplied information
    Starting informationWhat it establishesWhat still needs checking
    v2 edited yesterdayNewer draftWho still needs to approve it?
    v1 approvedValidated version in this scenarioAre its date and owner stated?
    Public page v1Content currently offered to readersDo links and summaries identify this same version?

    Editing and approval dates describe different stages.

    Read three participation rates

    Fictional case: 24 people contacted, 18 confirmations and 12 participants. The group is closed; each person is counted once and every participant had confirmed.

    Confirmations represent 75% of contacts. Attendance is about 66.7% of confirmations, but 50% of contacts. Always state the reference group and snapshot date. For a real contact file, explain how personal data is used and protect it.

    This workshop uses its own fictional snapshot. Do not combine its figures with those of another example on the page.

    Two reference groups: 24 contacts, then 18 confirmations. These numbers are invented.

    The diagram values are listed below with their labels.

    Find the values behind the diagram
    MeasureValue
    People contacted24
    Confirmations18
    Participants12
    No confirmation6
    Confirmed but did not participate6
    Confirmations / contacts75%
    Participants / confirmations66.7%
    Participants / contacts50%

    Reference documentation : CNIL · .

    Three volunteers prepare boxes of books in a fictional community organisation.

    Keep the information consistent

    When to review
    New approval or correction
    Who validates
    The publication owner reconciles version, status and date.
    Journey to replay
    Open the note from the news item and the activity section.

    Organise content approval →

    Understand an indicator

    Separate interest in an association from completed membership

    Fictional teaching example: these figures are neither market statistics nor measured client results. They illustrate a calculation and its limits.

    A fictional association tracks 50 distinct membership applications started during a defined period. Twenty have completed the required steps and have been validated at the reporting time.

    The proportion in this example

    40%20 / 50 × 100

    Memberships completed under the stated rules
    20
    Distinct membership applications started
    50

    What this figure means

    40% of tracked applications are complete. People who only read the page or ask a question are not counted as started applications.

    Define the count before comparing

    Define the start of the journey and completion conditions. Distinguish incomplete files, pending approval and withdrawal without publishing personal records.

    A fictional breakdown of the 50 applications is 20 validated memberships, 18 incomplete files, 8 pending approvals and 4 withdrawals. Assign one state per application at the snapshot date; adding a document to a file does not create another membership.

    A practical check on the website

    State the steps, required information and how applicants can learn their status. Test a complete application and one requiring more information.

    What the calculation cannot establish

    The rate describes this journey during this period. It measures neither volunteering engagement nor future renewals.

    Try with your own counts

    Use two counts from the same group and period, with the same unit. The selected cases must belong to the reference total. Leave unknown values blank.

    Whole counts only, up to one billion. Formula: selected cases ÷ reference total × 100. The displayed percentage is rounded to one decimal place.

    These values stay in this page without being sent or saved. The calculation provides no benchmark, prediction or quality score.

    To document real data, keep its origin, scope and quality limitations clear. Method reference : W3C · Data on the Web Best Practices (in English) · Consulted on . This source does not supply the fictional figures above.

    A content model to maintain

    Organize information by task: discovering an activity, taking part or becoming a member. The exercise can compare a public activity with a members-only one during a seasonal transition. Periods, conditions and contacts should remain distinct; an old calendar should not imply every registration remains open.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    A content model to maintain
    InformationContent to retainConsistency check
    Activity and audienceIdentify the activity, intended audience, dates and collective contact. State confirmed participation conditions and registration status.Follow links to a discontinued activity and a members-only one. Status should be explicit before requesting personal information.
    Membership periodRetain covered dates, approved arrangements and handling of pending requests. Separate membership from any activity payment.Start a request near the season’s end: the page, form and confirmation should identify the same period without implying automatic renewal.
    TeamRole, shared contact and permission for portraits.A personal address is not published by default.
    DocumentTitle, version, date and intended audience.An old document belongs in a clearly identified archive.
    Membership and participationSeparate membership, activity registration and donations; give the appropriate contact for each.Follow a first registration and check that membership fees cannot be mistaken for an activity price.

    A focused next step

    Prepare a fictional seasonal transition and have someone unfamiliar with the association check the journeys. They should distinguish contact, participation and membership. Then review received requests and public lists with the responsible person: an archived activity should retain context without offering apparently current registration.

    Schema.org: Organization — a reference for describing information, not evidence of a particular business or a guarantee of search features. · Source consulted

    A review case to reproduce

    An old campaign remains active

    Situation to examine
    A past campaign still has a prominent registration or contribution button. The team no longer knows who receives related enquiries.
    Proposed check
    Check dates, recipients and homepage links. Agree explicit archiving or an approved update. Test with fictitious data and verify that new enquiries reach the correct owner.
    Evidence to retain
    Keep the archive decision, displayed date and checked recipient. Historical content remains understandable without promising an activity no longer organised.
    Fictional finding example
    A fictional campaign closes on 30 September 2026. Its page remains visible afterwards with an unexplained “Register” button.
    Interpret this outcome
    Retain a useful archive and its outcomes, but state closure. A link to a later campaign should identify that campaign’s own dates and conditions.

    Method reference : W3C — Data on the Web Best Practices · Source consulted

    Learning scenario

    A scenario for planning the user journey

    Preparation exercise: A person wants to understand an action, join an activity or offer their help. Build three separate courses with test people. Do not post any actual beneficiary identity in the exercise. For a complete or complete activity, show what is left. Describe what happens after registration: reception, eventual examination and expected return. An old action must remain dated for the reader to distinguish between balance sheet, next meeting and ongoing commitment.

    Documents and information to prepare

    • Validated presentation of the missions and audiences concerned
    • Calendar with status of actions and activities
    • Conditions and contact for membership or volunteering
    • Photos with permissions adapted to the people represented
    • person who receives and processes each type of request

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. A past activity is not offered as the next session.
    2. Membership and volunteering have separate instructions.
    3. A complete activity displays its situation before the form.
    4. The requested data corresponds to the chosen route.
    5. The balance sheet of an action indicates its period and its origin.
    6. The visuals do not unnecessarily reveal a personal situation.

    Understand pre-launch checks

    Ongoing management and handover

    Organize a calendar review before each new activity period. Assign requests to a follow-up contact when volunteers change roles. For images, keep context and permissions rather than just a general mention. The balance sheet figures must be accompanied by their period and method of counting. If this information is missing, describe the action without inventing a numerical result.

    Organize site maintenance

    Compare two approaches

    Separate public information from exchanges intended for members. A private area adds value only if its permissions, administration and documents can be maintained.

    Public website with a named contact

    When to choose it
    Suitable for explaining activities, events and membership steps. A dedicated contact can handle individual situations.
    What to plan for
    Assign responsibility for dates and documents. Plan volunteer handovers and the correction of cancelled activities.

    Members-only area

    When to choose it
    Consider this for content genuinely intended for an identified group: internal documents, registrations or activity tracking. Distinguish what should remain public.
    What to plan for
    Organise account creation, departures and recovery. Avoid private areas without an owner or update process.

    A risk to anticipate

    Activity photographs, personal contact details and participant lists need approval before publication. Do not automatically copy an internal document into a public section.

    How to decide

    List the tasks the next team must take over. Choose a workflow whose responsibilities can be explained in a short document.

    Explore this decision further

    Compare scope and costs

    Setup
    Define actual journeys: joining, participating, helping or giving. A public presentation differs from member registration with its data and responsibilities.
    Recurring operation
    Compare content management, registration and contributor support. Separate licences from any valued volunteer time; volunteering establishes neither zero cost nor guaranteed availability.
    Exit and handover
    Specify content recovery and authorised access handover. Member data requires appropriate transfer; it must not be included in a public website archive by default.

    Compare the costs of three web solutions

    Frequently asked questions

    How can an activity report avoid inflated totals?

    Define what the figure counts: distinct people, attendances, sessions or requests. State the period and excluded duplicates. If activities reach the same people, do not add their counts as though they necessarily represent different beneficiaries.

    How should membership, donations and activity participation be distinguished?

    Name the selected intention before data entry and explain what the journey confirms. A payment or form should not suggest membership when it concerns only an event. The final message should identify the request type, relevant period and person or team handling the next step.

    What should be checked when the volunteer team changes?

    Review public contacts, form recipients and publishing permissions. Test an enquiry for each important intention and assign cover for absences. Retain organisational accounts and instructions so a departing volunteer does not leave a page impossible to update.

    How can a website stay current when volunteers change?

    Document sections, deadlines and the people who approve information. Prepare the transfer of permissions and the list of publications to monitor. A simple, maintained section is more useful than pages nobody knows how to manage.

    Further reading

    Additional reference: W3C Wai: Structure an accessible page. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.

    Browse other resources