Your commitment.
Clear rules.

Participants, age and access

The Programme recognises genuine volunteering. Each person has one wallet even when volunteering with several NGOs. Points have no monetary exchange rate, cannot be cashed out or sold and do not replace entitlements under a volunteering agreement. The Programme has an international scope. Current numbers of directory entries, confirmed participants and countries of origin are published separately, with an update date, in the register: https://punktydobra.pl/organizacje. A directory entry does not establish a signed agreement or admission to the Programme.

Just Do It admits only adults aged 18 or over to its own volunteering and tasks. Participants aged 13–17 may join only through another approved organisation after the volunteering agreement and required legal-representative consent are confirmed. Independent registration under age 13 is unavailable.

The admitting NGO is responsible for agreements, consents, supervision, safety and suitable tasks. The portal Organiser retains duties concerning accounts, data and rewards. For activities abroad the NGO checks applicable local law; the Polish age model does not replace local requirements.

Card activation and partner benefits require approval of the declaration and membership. Reward redemption additionally requires available Points and identity verification before the first fulfilment. Signing in or selecting a dream does not reserve a reward.

Base rate and coefficients

One verified hour in a Points-enabled project earns 100 Points at coefficient 1.00. Formula: completed 15-minute units × 25 × the task coefficient.

1.00: standard activities including packing, administration, design, online work and event support. 1.20: substantial sustained physical effort or special responsibility requiring verified qualifications. 1.30: an approved emergency response or urgent duty at difficult hours.

The rate is set for the task before acceptance. An administrator approves the coefficient on the coordinator’s proposal. Coefficients do not stack; the maximum is 1.30. Coordinator status, profession, origin or membership of Just Do It do not by themselves increase the rate. Unnecessary risk is not rewarded and individual physical ability is not graded.

Examples: 4 hours × 100 = 400 Points; 4 hours × 120 = 480; 45 minutes at 1.30 = 3 × 25 × 1.30 = 97.5. Points are recorded precisely to at least 0.5 Point.

Time, 15-minute units and evidence

Actual minutes are recorded. Approved minutes are aggregated for the same person, project, quarter and coefficient; completed 15-minute units earn Points and the remainder carries to the next entry in that group. Individual reports are not rounded up.

Example: 20 and 25 minutes total 45 minutes and earn 75 Points at 1.00. A 35-minute entry earns 50 Points with 5 minutes in the buffer. When the project or quarter closes, a remainder below 15 minutes stays in the time record without Points. It is not transferred between quarters or coefficients.

Eligible time includes the task and necessary preparation and completion. Required briefings or training count when included in the project beforehand. Normal commuting does not count; transport performed as a task may count. Absence, excluded breaks, paid work, donations alone, card purchases and fictitious referrals do not earn Points.

Evidence may be an attendance record, accepted deliverable, stage description or leader confirmation. Photographs of aid recipients and sensitive data are not routinely required. The same minute cannot be credited to two projects.

Project allocations and other NGOs

Before recruitment a project has a lead organisation, objective, dates, tasks, rates, places and hours, coordinators, a Points limit and secured reward coverage. Coordinators cannot issue Points independently. Other NGOs use the same rates when their projects receive an allocation. Without one they may record hours and use partner benefits, without automatic Points issuance.

Free allocation = approved limit – net issued Points – active task reservations. Assigning someone 5 hours at 1.20 reserves 600 Points. After approval of 4 hours, 480 are awarded; the remaining 120 are released when the assignment closes. Spending Points on a reward does not replenish the project allocation.

Insufficient coverage blocks new Points commitments, not settlement of already secured work. Extra hours require an expanded assignment and allocation before they are requested. An 80% utilisation alert supports planning. A joint project has one accounting organisation and one record of the activity.

An NGO applying for an allocation states tasks, hours, verification and the source of rewards or funding. A partner discount alone does not cover an unlimited number of Points. The administrator approves a scope consistent with actual coverage.

500 and 2000 Point bonuses

500 Points is a one-off volunteer registration bonus. Before approval of the declaration and membership it may appear as pending; this does not establish reward availability. Using it requires an active account and verification before the first redemption.

An approved coordinator receives 2000 Points in total after organisation approval and assignment of the role by the portal administrator. If 500 were already awarded, the top-up is 1500. Another organisation, changed email, repeat sign-in or role assignment does not create another bonus. A person receives at most 2000 registration-bonus Points.

Bonuses use a separate central allocation secured before a promotion starts. They do not increase activity rankings or volunteer hours. A valid bonus is not removed solely because a role ends. Example: 1000 people including 50 coordinators receive 500,000 + 75,000 = 575,000 bonus Points.

First redemption and identity

Identity must be verified before the first Points redemption. The default is an administrator-led non-biometric procedure. Stripe Identity, involving a document and selfie, may be used only after separate information about data, biometrics, legal basis, retention and an alternative has been provided and the Participant has given explicit, voluntary consent. Refusing consent does not remove entitlement to a reward and initiates a proportionate alternative procedure. Verification is free for the Participant and paid for by the Organiser. Minors must not be sent through Stripe Identity.

Minors must not be sent through Stripe Identity. Ages 13–17 require a procedure involving the legal representative and confirmation by the organisation. Points remain attached to the volunteer’s profile, not the guardian’s. Where a country or document is unsupported or biometrics are reasonably declined, a proportionate non-biometric alternative is provided within legal and provider restrictions.

A securely received provider result does not replace person-level duplicate checks. A session ID, surname, shared address or payment card alone does not prove a duplicate. Suspicions require review rather than automatic account deletion. Further checks require a reason, such as a material data change or suspected account takeover.

Before the procedure, a notice explains data use, biometrics, legal basis, retention and the alternative. Documents and selfies are not exposed to ordinary coordinators or partners. The portal stores only the result and information necessary for operation and duplicate checks.

Reports, decisions and wallet

Assignment and reservation → performance → report of minutes and result → decision by another authorised person → credit. Reports should normally be submitted within 7 days; complete reports are decided within 7 days. Delays are reviewed without automatically forfeiting credit for completed work. Appeals are submitted within 14 days and answered within 14 days of completion, subject to statutory deadlines.

Nobody approves their own hours or bonus, including coordinators and administrators. The wallet distinguishes available balance, reward reservations, amounts held for review and pending credits not yet awarded. Project reservations and reward reservations are different operations.

The history records source, person, organisation, project, minutes, rate, rules version, decision and resulting balance. Errors are corrected through a linked entry without deleting history. A minute correction recalculates the full group of 15-minute units and posts the difference; 45 → 30 minutes at 1.00 is −25 Points.

The same verified Google or email-link address leads to one profile. Changing the address or merging two accounts requires proof of control or a documented administrator procedure. Valid history is preserved and duplicate bonuses are reviewed.

Rewards, refunds and validity

Before ordering, the Points price, availability, fulfilment terms and extra costs are shown. The reward and Points are reserved together. Fulfilment converts the reservation into a debit; cancellation releases it. A return under the offer terms creates a separate credit. Unavailable products are not presented as available and substitutions require consent.

Negative available balances and double fulfilment are prohibited. Disputed Points already spent require individual review and do not automatically create a monetary debt. Holds are proportionate and subject to complaint. Ordinary partner discounts do not consume Points unless the offer explicitly provides for redemption.

During participation, approved Points do not expire automatically. A change of organisation, a break or card replacement does not erase the balance. After resignation the Programme Rules govern settlement, including the 90-day period for requesting use. No separate monthly minimum activity time applies.

Ranking, checks and budget

An organisation’s quarterly score is Points from verified activities performed in the quarter, after corrections, attributed to the lead organisation. Bonuses, reward refunds and current balances are excluded. Spending Points does not reduce the score. A community-balance table is not this ranking.

The activity date and Europe/Warsaw time apply. Results remain provisional through day 14 after the quarter; justified later corrections update the proper quarter with a change notice. Ties use minutes, then active-person count; a full tie shares a place. NGOs without allocations may have a separate hours ranking. Ranking alone awards no prize.

Checks cover overlapping hours, duplicates, self-approval and allocation overruns. More than 8 hours per day triggers review rather than automatic rejection; over 24 hours is contradictory. A shared address or device does not prove fraud. Administrators have operational access and coordinators only their authorised scope.

Planning example: 100 people × 8 hours × 100 = 80,000 Points; 40 new people add a 20,000 bonus and 5 coordinators in this group add 7,500: total 107,500. This is solely for internal planning by the Organiser and does not determine a Points exchange rate for participants. Monthly reporting covers issuance, reservations, rewards, coverage, outstanding hours and disputes.

Changes, implementation and versions

The Organiser may amend the Rules and Points System for specific reasons: a change in law or a binding competent-authority decision; a documented security vulnerability or abuse; adding or withdrawing a feature requiring a procedural change; or a change in secured rewards or their costs requiring future allocations and offers to be adjusted. The scope must correspond to the cause.

The full text, reason, scope and date are emailed and published in an account notice and downloadable document at least 14 days beforehand. A shorter period applies only to a necessary change required by a legal deadline or immediate security threat, with notice without undue delay. This does not permit arbitrary retrospective changes.

New rates apply to new tasks from the announced date. Valid Points, accepted tasks and confirmed orders retain their conditions; errors and abuse use a separate correction procedure. Resigning before a change does not remove accrued rights, settled under the Programme Rules. Previous versions remain available.

Version 1.2 dated 11 November 2026 is an annex to Rules 6.0. The new model applies to tasks announced under these terms from the official launch on 1 December 2026; it does not automatically recalculate historical hours or balances. This document states rules, not confirmation that every automation is live. Until implementation, authorised staff keep decisions and records subject to the same controls.

Technical implementation requires transactional credits, duplicate-request protection, server-side authorisation and versioned history. Tests must cover account-merger bonus duplication, simultaneous approvals, minute corrections, reservation release and quarter attribution. Algorithm updates must not overwrite valid historical entries.