The work package a community school actually sees is an Iteasel unit on a desk. They don't see the Dolibarr PO, the supplier record, the delivery confirmation. What they see is the device. What procurement does is make sure the device arrives tracked, costed, and matched to a purchase order - because charitable money has to be accounted for even when there is no margin.
Phase E went active today. WP1 (Tailscale) has been done since April - the infrastructure security layer is locked. WP2 is current, and my slice is the Dolibarr procurement module: PO workflow active, supplier records structured, order references in place. Four-week window. It has to be right before WP3 (the Dolibarr-Nextcloud EDM sync) can start. A bad data structure now becomes an inherited problem downstream, and fixing it mid-sync costs more than getting it right at setup.
What procurement looks like when the purpose is giving rather than margin is mostly the same operationally - suppliers, orders, delivery, invoice matching. The difference is that every approved PO is traceable back to a community need, not a revenue target. That makes the work quieter in some ways and more accountable in others.
Full Phase E context | Work packages breakdown
