A checkable manifesto system for a state campaign
Thirty-nine manifesto editions built to one standard, where every promise carries a name, a place, a date, a mechanism and a way for citizens to check it.
Read the case studyEvery project page states what the client needed, what we built, what changed and what we would do differently. Published only with written client consent, and anonymised where consent covers the work but not the name.
Thirty-nine manifesto editions built to one standard, where every promise carries a name, a place, a date, a mechanism and a way for citizens to check it.
Read the case studyA complete identity, asset library and approval workflow, so hundreds of materials could be produced without losing consistency.
Read the case studyA public accountability platform showing delivered, in progress and delayed commitments with equal prominence.
Read the case studyStructured logging from door to door rounds, routed weekly to decision makers with named owners and dates.
Read the case studyAn organisation chart, twelve standard procedures and eight training modules, with a certification register.
Read the case studyVoice, channels, cadence and delivery reporting, with the client's own officers trained to run it.
Read the case studyWard logs collected on ordinary phones where coverage is unreliable, syncing when a signal returns.
Read the case studyRegistration, induction, deployment and retention, with nobody deployed before induction.
Read the case studyEvery contract, cost, contractor and timeline published where any citizen can check it.
Read the case studySome work cannot be published because consent covers the engagement but not disclosure. Clear the filter to see everything we can show.
Every engagement begins with a short conversation about what you are trying to achieve and what already exists.