State and local program delivery

    Define the work for your Maryland program.

    For primes delivering awarded Maryland state and local programs: bring the requirement, a delivery challenge, or an existing work package. Together, we can assess where program leadership, AI, data, or mission technology may fit.

    Discuss Your Program Show Us the Scope

    Start with the awarded requirements

    Rutledge & Associates studies public requirements and information you are authorized to share. Possible delivery pressures remain hypotheses until your team validates them. A concept may help clarify the need; it is not necessarily the capability ultimately delivered.

    For work procured through arrangements such as CATS+, ADEPT, Agile 2.0, or an agency-specific contract, start with the actual award and task-order terms. Vehicle names alone do not establish a delivery role, subcontracting permission, current availability, or Rutledge's participation.

    Discuss your procurement requirements

    Share the delivery role, applicable contract requirements, and the documentation your procurement team needs. We can discuss how a defined work package fits the program.

    Explore our capabilities

    Program contexts and possible work packages

    Illustrative approaches for defining a bounded work package around your program's needs.

    Human services and benefits

    Relevant requirements

    Medicaid, SNAP, TANF, and related eligibility programs involve different rules, source systems, access permissions, reporting obligations, and user workflows. Cross-program reporting requires careful definition of what each measure represents.

    Illustrative approach

    Map an agreed enrollment-reporting workflow and a bounded set of source fields; deliver a data dictionary, reconciliation checks, and a non-production reporting concept using illustrative data.

    What discovery clarifies

    Which benefits and measures are included? Who owns source access and definitions? How are exceptions handled, and what privacy, retention, integration, and acceptance requirements apply?

    Shared services and application modernization

    Relevant requirements

    Agency applications may depend on shared identity, hosting, release processes, and legacy interfaces. A modernization package needs explicit boundaries between the application, the platform, and other vendors.

    Illustrative approach

    Assess one application release path and define a build/test/deploy workflow, environment prerequisites, rollback steps, and a handoff runbook. Production implementation would be separately agreed.

    What discovery clarifies

    Which environments are available? Who authorizes releases, supplies licenses, manages identity, and operates the service? What testing demonstrates an acceptable release?

    Public safety and justice

    Relevant requirements

    Case and correctional-health workflows require attention to access restrictions, operational continuity, data sharing, and oversight. Clinical and custody responsibilities must remain clearly distinguished.

    Illustrative approach

    Document one referral or case-status workflow, its role-based access needs, and interface acceptance tests, using non-sensitive examples during discovery.

    What discovery clarifies

    Which users and facilities are in scope? What agency security policies and clinical requirements apply? Who validates the workflow and controls the cutover?

    Program governance and oversight

    Relevant requirements

    Multi-vendor delivery needs a shared view of milestones, decisions, risks, and dependencies while respecting each party's contractual responsibilities.

    Illustrative approach

    Establish a schedule and RAID baseline for one workstream, with an agreed executive reporting format and escalation cadence.

    What discovery clarifies

    Which source schedules are authoritative? Who approves baseline changes? What documentation is needed for the actual oversight and gate reviews?

    Four capabilities, a defined delivery role

    Executive Program Delivery

    Reduce execution complexity with disciplined governance, executive oversight, and structured program management.

    Explore possible scope

    AI Decision Support

    Reduce decision complexity with AI-enabled reporting, knowledge management, and operational intelligence.

    Explore possible scope

    Data Intelligence

    Reduce information complexity by transforming fragmented data into actionable executive insight.

    Explore possible scope

    Mission Technology

    Reduce operational complexity with secure, modern systems designed for highly regulated government environments.

    Explore possible scope

    From conversation to contracted delivery

    Discovery clarifies the users, operating environment, access, data sensitivity, dependencies, oversight obligations, and acceptance authority. We agree scope boundaries, deliverables, milestones, reporting, commercial terms, and handoff before delivery begins. Production testing, security authorization, integration, cutover, rollback, and support must be scoped; a prototype alone does not satisfy them.

    Delivery uses Discover, Design, Deliver, Govern, Transition within the agreed scope. Selected pursuit support and direct government work may also be considered where the role and requirements fit.

    Discuss Your ProgramShow Us the ScopeSee How We WorkExplore delivery approaches