Prove an action
Learn what good proof looks like, how much to share, and why several signals may be combined.
Proof should show that the requested action happened under the Mission’s published conditions. The Mission may ask for a photo, a form response, an attendance signal, a partner confirmation, or another relevant record.
Strong proof is:
- related to the exact action;
- created or captured within the allowed window;
- clear enough to review;
- limited to what the Mission needs;
- honest about uncertainty.
More data is not automatically better
Do not add unrelated personal information “just in case.” If a photo includes other people, consider whether they should appear. If a location or account detail is unnecessary, leave it out.
Higher-value or abuse-prone Missions may combine independent signals. That does not mean every Member should face maximum friction. The strength of proof should match the risk.
A submission can move through waiting, review, approval, rejection, hold, or challenge states. If the reviewer needs additional evidence, the Mission policy should say whether additions are allowed and by when.
Never manufacture, alter, borrow, or resubmit another person’s proof. That harms the community and can lead to rejection or restriction.