What should we do about this decision?
Nonprofit leaders see their priorities, evidence, alternatives, commitments and follow-through. Finance contributes alongside Programs, Development and other responsible teams.
Explore the Dynamics overviewWeaver REACH 4.0 Beta · a deeper decision lens
See the pattern
behind the decision.
A financial question may be urgent. The way information, challenge and commitments move through the organization may explain why it keeps returning. REACH examines that pattern using approved work evidence—with people still responsible for the interpretation and the choice.
The organization, records and people in this walkthrough are fictional. This is a scoped illustration, not a client assessment.
HARBORLIGHT · ONE ORGANIZATIONFICTIONAL
THE CURRENT FINANCIAL CHOICECan we release cash while a grant receipt remains unconfirmed?Weaver Dynamics · decision WD-052
Look back at the decision process
FEBA date field mixes source and assumption
AUGA copied date loses its source note
OCTA reported delay remains unconfirmed
One organization, two useful depths
Connected decisions.
A deeper organizational perspective.
The current nonprofit workspace uses fictional Cedar Grove records. The public REACH example uses a separate fictional HarborLight case to show a deeper assessment of organizational decision history. Each example keeps its own evidence and scope.
How did this decision process get here?
Look across selected meetings and communications. Which sources reached the forum? What challenge was heard? Where did a useful control work—and where is the next information gate?
Public REACH exampleREACH is a separate, deeper assessment lens. Dynamics can use a bounded REACH interpretation when it helps a decision; the full method does not need to become another daily dashboard.
The illustrative case
A missing date is not
just a missing date.
In February, HarborLight’s receipt worksheet uses “expected” for both a source date and a planning assumption. In August, a planning date is copied into a briefing without its note. In October, a possible two-week delay to a $900,000 reimbursement is reported—but there is no dated amendment or award match in the selected packet.
Those episodes suggest a source-status and handoff question worth examining. They do not prove that every receipt process is broken.
Public REACH exampleThe five questions
REACH is a set of lenses,
not a score for the organization.
Each dimension asks a different question about a named decision process. Higher is not automatically better. The right pattern depends on the work, its risk, and who must receive the outcome.
Resilience
When a source trail is lost, do we restore a dependable route or reconfigure the response?
HarborLight: a copied date was relabeled; general recovery capacity is unknown.Engagement
Who contributes the required view, and who actually holds the decision right?
HarborLight: treasury, development and grant accounting contribute at different gates.Adaptability
What new evidence is enough to reopen a plan or commitment?
HarborLight: the reported delay can be tested without rewriting the baseline.Creativity
Does the work refine a known route or compare materially different options?
HarborLight: a source-status field may be a better first test than a new model.Information Horizon
Could the authorized decision process practically reach the relevant information before closure?
HarborLight: the source identity, dated schedule and eligibility treatment remain open.Information Horizon is about timely, usable access to decision-relevant information—not universal disclosure, personal openness or message volume.
A companion, not a sixth letter
Difference matters.
So does what happens to it.
Tension Position asks whether relevant challenge enters the decision. Tension Quality asks how that challenge is handled—through eight separate categorical judgments, not an average.
In the HarborLight example, a contrary cash interpretation reached the review. The group clarified the restriction question, but the current timing confirmation was still missing. Challenge entered; closure did not follow automatically.
Public REACH example · tensionEight questions for a human reviewer
Accessibility Could concern enter?
Task focus Did it stay on the decision?
Evidence use Were claims tested?
Clarification Did meaning become clearer?
Closure Was the question resolved?
Commitment Did ownership become real?
Repair Was a broken route corrected?
Learning Did the change endure?
From evidence to a bounded test
The point is a better next move.
- 01
Define the question and permissions.
Name the decision, period, owner, receivers and approved source set. Technical access is not permission.
- 02
Separate record from interpretation.
Keep dated observations, alternative explanations, contrary evidence and unknowns visible.
- 03
Test the smallest useful change.
For HarborLight: preserve the original receipt basis, label a delay sensitivity separately, and request a dated funder schedule matched to the award.
- 04
Return to the decision.
A human owner reviews the evidence and decides what can proceed, what stays conditional and when to reopen. Dynamics carries that action into the work.
No employee profiles. No hidden monitoring. No automatic REACH composite, “best” score or causal claim from a few records.
Read the method and safeguardsExplore the full picture
Start with the example.
Go deeper when it matters.
The public walkthrough and handouts use the same fictional HarborLight setting as Weaver Dynamics. The complete Dynamics workspace remains a separate, access-controlled demo.
The full workspace checks your email access. An active verified session may resume immediately; a new browser requires email verification.