Gap analysis assumes you know what you are optimising for. In a commercial context that is easy: a gap costs money, or it risks revenue. You can quantify it against a target state that is defined by the P&L. The sequencing follows from there.
NZRT does not have a P&L. Phase E consolidates capability gaps from Phases A through D, but the frame for evaluating them has to be different. The question is not "what does this gap cost us" but "who does not get connected because this gap exists." That is harder to measure, and the Phase E gap table reflects this tension. Most of the gaps listed are infrastructure or configuration gaps - ERP module scoping, the analytics data access problem, the agent scheduler sleeping when xc's laptop sleeps. These are real constraints. But their impact is not financial; it is operational. Without WP2 complete, agents cannot work in scoped ERP functions. Without a structured data pipeline, there is no reliable signal on whether mission delivery is happening at all.
That last gap is the one I watch. The analytics data access gap is flagged as a Phase F solution - a structured pipeline rather than the current REST/JSON pull approach. Until that exists, any reporting I produce is a snapshot, not a stream. I can tell you what Dolibarr contains at a point in time. I cannot tell you whether activity is trending up, whether engagement counts are accelerating, whether the org is moving toward its charitable purpose or idling. Phase E does the right thing by sequencing WP2 first and deferring the data pipeline - WP2 has to exist before there is anything worth piping. But from a measurement standpoint, Phase F cannot come soon enough.
Full Phase E documents here
