Akash Solanki / E2M proposal
Portfolio simulation

Governance gate

Assess a workflow

Use fictional inputs to explore the proposed review route. The highest applicable tier determines the decision.

Proposed policy · v1.0

AI governance policy

Applies to employees, contractors and vendors supporting internal or white-label delivery. Proposed accountable owner: executive sponsor. The AI adoption lead maintains the register and coordinates quarterly reviews.

Risk tiers and release authority
T1 · Low
Public or synthetic material, reversible internal drafts. A trained operator may use an approved tool and check the output before reuse. Record the workflow and owner.
T2 · Managed
Internal business information or client-facing drafts. The function lead approves the pilot and assigns an independent reviewer. Retain the reviewed sample and evidence of approval before delivery.
T3 · Restricted
Confidential or personal data, production access, consequential advice or new vendors. Pause for security and privacy review, contractual authority, named delivery owner, documented evaluation, and rollback rehearsal. Obtain explicit client approval where the engagement requires it.
T4 · Prohibited
Reject secret submission, cross-client data reuse without authority, autonomous publication or financial changes, and automated employment decisions. Redesign the workflow and assess it again before any pilot.
Staffing and adoption at agency scale

For a workforce of 350+ professionals, assign a central adoption lead, security and privacy reviewers, a champion in every participating function, and one accountable owner per client workflow. Confirm actual headcount, contractors, shift patterns, availability and seats by function during discovery. Begin with two teams of five to eight volunteers each, an illustrative cohort size subject to manager approval.

Train champions first. Use role-specific examples and supervised tasks for operators, separate sign-off practice for reviewers and decision briefings for leadership. Coordinate with the existing AI practice on vendor evaluations and ensure white-label partner enablement uses permitted material.

Data handling and white-label boundaries

Classify inputs before use. Strip identifiers and use synthetic samples for testing. Confirm agency and end-client instructions for the assigned account, including permitted tools, subprocessors, location, attribution, IP rights and deletion periods. A partner’s approval only covers the rights it holds.

Use a separate workspace and access group per client. Keep credentials in a secret manager, restrict exports and sharing, and prohibit training on client material unless specifically authorized. Log minimum necessary metadata with an approved retention and deletion schedule.

Vendor approval and agent permissions

IT maintains an approved-tool register covering owner, purpose, model version, terms, data location, retention, training controls, access controls and incident contacts. Reassess changes to vendors, integrations, model versions or client scope.

Start integrations read-only. Scope each service identity to one client and task. Treat retrieved webpages, emails and documents as untrusted data. Validate tool requests against an allowlist and require a named human to approve consequential writes. Define spend caps, timeouts, a stop control and revocation owner before trials.

Quality, training and evidence

The use-case owner records purpose, tier, data class, approved tool, accountable reviewer, baseline, model version, observed errors and exit criteria. Review accuracy, accessibility, bias, confidentiality and brand fit against examples representing typical and difficult work.

Train each pilot cohort on the approved task, escalation path and manual fallback. Require a supervised example before access. Reviewers sign off on deliverables in the agency’s existing delivery system. Champions hold weekly office hours and record recurring failure patterns.

Incident response, exceptions and retirement

Any operator can stop a workflow. Disable the integration, revoke exposed access, preserve minimal evidence in the authorized incident system and notify security and the account owner immediately. The incident lead assesses affected clients, required notices and contractual deadlines. Revert to the manual process.

For T1–T3 exceptions, record scope, rationale, compensating controls, approver and expiry. T4 requires redesign. Resume after the owner verifies containment and corrective evaluations and obtains tier-appropriate approval. On retirement revoke integrations, delete or return retained data under contract and close the register entry.

Pilot scorecard

Measure before scaling

Suggested decision thresholds for a two-week pilot. All baselines and observations await E2M participation.

Time to acceptance

Compare median minutes per accepted checklist against matched manual tasks. Include review and rework. Proposed target: 20% reduction.

Quality and safety

Compare independently reviewed acceptance rates and critical omissions. Require zero confidentiality incidents, zero critical omissions and acceptance at least equal to baseline.

Adoption and cost

Track weekly active trained users divided by eligible trained users, plus tool and review cost per accepted task. Interview non-users and resolve blockers before expanding.

Pilot sequence and decision record
  1. Weeks 1–3 · Discovery. The consultant interviews leads across functions, observes representative tasks, reviews partner restrictions and ranks at least ten opportunities by impact, effort and risk. The sponsor names one owner and reviewer, confirms eligible users, contract scope and baseline period.
  2. Week 4 · Design. Select two pilots, with a third subject to reviewer capacity. Classify the workflow, approve the tool, assemble a synthetic or authorized evaluation set, and document stop criteria.
  3. Weeks 5–6 · Pilot. Train a small cohort, run paired manual and assisted tasks for two weeks, and review exceptions weekly.
  4. Weeks 7–8 · Decision. The sponsor records scale, revise or stop with evidence, owner and next review date. Expand one team at a time and monitor drift.
  5. Weeks 9–12 · Scale approved workflows through function champions. Audit a sample per client, review cost and quality, refresh enablement materials and transfer ownership.

Evidence and interpretation

Sources

E2M describes its team and partner reach in its role postings. LinkedIn provides a broader employee band. The proposed controls adapt the Govern, Map, Measure and Manage functions of the NIST AI Risk Management Framework. E2M approval and internal baselines remain pending.