A commissioner's office receives a continuous flow of requests to attend, speak at, or participate in events and meetings — from internal divisions, external organizations, and community partners. At this regional county precinct, that process had no shared infrastructure. Requests arrived through scattered email threads and physical forms, were routed informally based on institutional knowledge, and moved toward a decision through a chain of manual handoffs between division leadership, senior staff, and the commissioner's administrative team.
There was no visibility into where a request stood, no accountability for response times, and no consistent record of what had been accepted, declined, or was still pending. For accepted engagements, logistics coordination — memos, talking points, advance assignments, communications — happened through separate email threads with no connection to the original request record.
Discovery focused on mapping the actual workflow rather than the assumed one — who was involved at each stage, what information they needed, how decisions were communicated, and where the current process consistently broke down. That mapping revealed two distinct operational needs requiring separate but connected surfaces: a structured intake and chief recommendation workflow serving 12 organizational divisions, and an administrative review and logistics platform serving a small team of senior staff.
The design decision to use two linked boards rather than a single board was deliberate. Division chiefs needed a clean, focused view of requests relevant to their division and a simple interface for submitting recommendations. The administrative team needed a richer operational environment with sequential review stages, multiple role assignments, logistics fields, and attachment management. Linking them at the item level gave both surfaces their own appropriate design while maintaining a single connected record across the full lifecycle.
The platform consists of two connected boards, 29 total automations, and four response time timers operating across the complete request lifecycle. The Request Board handles structured submission and chief recommendation workflow. When a request is submitted, an automation reads the responsible division and immediately assigns the correct division chief and primary contact, sends email notifications, and starts the Chief Response Time timer. Chiefs acknowledge and act on requests within the platform; their approval or denial automatically triggers creation of a linked record on the Administration Board.
The Administration Board routes each request through a sequential three-stage internal review with automated role assignment, stage progression, and timer tracking at every step. Accepted engagements move into logistics management within the same record — memo assignment, talking points, staff and advance assignments, communications coordination, and calendar scheduling are all managed within the item. Four response time timers start and stop based on specific workflow events, not manual tracking, giving leadership measurable data on how efficiently each review stage is being processed.
This engagement pattern applies directly to any government office, nonprofit, or public-sector organization where a senior leader's schedule is managed through informal email-based coordination. The two-board architecture is repeatable for any process that involves collecting input from multiple divisions before a small team makes a final decision. The specific application here is commissioner event requests, but the same pattern fits city council scheduling, executive director engagement management, school board member event coordination, or any office where a leader's time is a shared organizational resource requiring structured multi-party coordination.
Schedule a 30-minute conversation about your operational challenges.
ore.brigham@brigville.com