Unions and labor

Operating systems for unions that need governed daily work.

Myte has already delivered union systems where leadership needs traceability, member trust, contractor visibility, and repeatable workflows instead of scattered files and inbox memory.

3
Ironworker community clients served
4
union and labor systems built
38
documented workflow modules delivered
1 year
time to market for the three newest systems
Built for accountable operations

The proof is strongest when the work is specific: market recovery, organizing intelligence, dispatch, member portals, documents, approvals, and audit trails.

Leadership sees the whole operating picture without spreadsheet chaos.
Field teams capture evidence, history, and next actions in governed records.
Members, contractors, staff, and administrators get role-specific portals.
Documents, email, approvals, payments, and audit trails stay connected to the work.
Delivered proof

Union systems already shaped into working software.

These are specific operating systems with named leaders, usable workspaces, connected records, role-based access, and daily workflows that support real operational pressure.

Proof from delivered systems
Jason Fussell profile
Live operating systemIronworkers Local 29

Market Recovery System

A working command center for Market Recovery requests, contractor communication, Letters of Commitment, treasury movement, document history, and operational follow-up.

Client lead

Jason Fussell

Financial Secretary / Business Manager / Treasurer

Local 29 can run Market Recovery from one governed workspace instead of relying on scattered files, manual follow-up, and memory.

System modules
Dashboard and reportingContacts and companiesProject operations queueMarket Recovery intakePromissory notes lifecycleLetter of Commitment centerEmail communications ledgerTreasury workspaceSystem settings
What changed
  • Next actions, stale items, offer decisions, and notes are visible by project.
  • Every critical notice connects back to project, contractor, note, or document context.
  • Treasury balances, reserves, releases, and exports live beside the operational record.
System proof: Live Market Recovery operating system
Jason Fussell profile
Field operating systemIronworkers Local 29

Organizer System

A field organizing operating system for records, governed memory, campaigns, communications, administration, and auditability.

Client lead

Jason Fussell

Financial Secretary / Business Manager / Treasurer

The platform helps organizers search first, capture field intelligence, govern memory, coordinate campaigns, and preserve a clear audit trail.

System modules
Dashboard command centerReporting and organizer KPIsContacts directoryContact control roomAssistant review workflowContractor workspaceProjects workspaceCampaigns workspaceCalendar, messages, and notificationsAudit logs and telemetry
What changed
  • Field teams get one place to capture contacts, contractors, projects, observations, and campaign context.
  • Assistant and OCR flows become reviewable suggestions before they enter the governed record.
  • Administrators can control roles, retention, sessions, imports, and sensitive access.
System proof: Organizer field operating system
Dan Segovia profile
Dispatch operating systemIronworkers Local 848

Dispatch System

An end-to-end dispatch operating system spanning contractor requests, staff review, rank-window crawler, member offers, referral slips, documents, dues, notifications, RBAC, and audit governance.

Client lead

Dan Segovia

Local 848 Dispatch System sponsor

Local 848 gets distinct public, applicant, member, contractor, staff, local admin, and system admin surfaces tied to one dispatch operating model.

System modules
Contractor job requestStaff review and dispatch queuePrepared slots and rank-window crawlerSecure member offersReferral slip outputCloseouts and work historyApplicant and document verificationMember portalContractor portalPolicy and audit governance
What changed
  • Contractor demand moves into staff-controlled dispatch without exposing internal controls.
  • Members see scoped standing, dues, documents, offers, history, resources, and notifications.
  • Admins govern qualifications, policies, users, documents, audit evidence, and permission boundaries.
System proof: Dispatch operating system for contractor requests, member offers, and referrals
Tim Strecker profile
Private data systemIronworker International Community

Privacy-First IMPACT Chatbot

A private natural-language data retrieval system that lets leaders ask database questions in simple language and receive deterministic charts, tables, and numbers without sending actual client records to a third-party language model.

Client lead

Tim Strecker

IMPACT chatbot system sponsor

Myte normalized and migrated Ironworkers data, tuned Myte Chat around the domain schema, and enforced read-only database execution so sensitive records stayed inside the client-controlled data layer.

System modules
Schema-guided natural-language chatData normalization and migrationPrivate prompt context with mock/schema dataRead-only aggregation guardrailsDeterministic MongoDB query executionCharts, tables, stats, and narrative answersConversation historyFeedback review workflowEngagement analytics
What changed
  • Third-party LLM calls receive schema and safe examples instead of live client database records.
  • Generated queries are validated, restricted to aggregation reads, and blocked from write-style operations before execution.
  • Leaders can ask operational questions in natural language while the system returns governed numerical evidence.
System proof: Private chatbot for deterministic database answers
Ownership path

Your union does not need another rented dashboard.

Myte builds the operating system around your people, rules, records, and governance. The result can run inside the Myte environment or on infrastructure you own.

Owned stackRole-based accessPrivate dataMaintainable ownership
Start the build