Donations app handoff
The operations coordinator at fictional Cedar Giving needs a donations application. Received gifts and pending pledges must remain distinct. Add a fund relationship, validate positive gift amounts, calculate received totals on Account, and build a read-only reporting view.
The completed deliverable includes a reusable entry permission set, a received-gift report, and a dashboard. Amounts in this fictional practice dataset are not business results or prices.
You own the complete nonprofit donations app handoff described in the brief. The next person needs working configuration and enough evidence to explain its behavior. Start with the business requirement, then keep each completed part while you add the next one. Your own saved state carries between steps.
A later task can expose a mistake that an isolated form would hide. A queue may exist without usable membership, a report may have the right title but the wrong population, and a rule may work for the example while rejecting an allowed record. Test those boundaries as you go. The final step asks for the operational conclusion or completed deliverable, and the checker keeps earlier requirements in scope.
Business requirement → configuration → boundary tests → handoff
Build a connected deliverable and retain its controls.