Frame → Assemble → Govern → Transfer.

Four phases. Six evidence gates.

The four phases describe the operating arc. Six lower-level gates keep the seams inspectable.

The method is not a funnel that advances automatically. A gate can return work to an earlier phase, narrow it, change its shape, hold it for a decision, or stop it.

Start with the smallest decision that changes the work.

A bounded start names:

• the condition that triggered the work and the consequential decision;

• the intended outcome and concrete work products;

• client and IT Modality responsibilities and decision rights;

• assumptions, dependencies, exclusions, and specialist questions;

• systems, data, access, environment, and location boundaries;

• the evidence required at the next gate;

• acceptance authority and the escalation path; and

• the condition to stop, revise, hand off, or expand.

The first package may be an inventory, readiness assessment, target-state decision, transition plan, one use case, one release, one interface, or one controlled service boundary. Its value is a useful decision and artifact set even when the correct next step is to stop.

Put judgment where the decision belongs.

Proposals and engagement orders name the actual people and roles included. When a managed-delivery scope uses professionals assessed through The Rigors, the buyer reviews the actual proposed people and role evidence. A team change follows the written communication and approval path; no undisclosed substitution is permitted.

Every gate answers four questions.

Frame · Discover

Question: What condition, decision, and consequence make this work necessary?
Evidence: current state, trigger, stakeholders, systems, prior work, constraints, data and access context, unresolved questions, and decision deadline.
Owner: client sponsor with the accountable IT Modality principal.
Consequence: proceed to scope, seek more evidence, reframe, or stop.

Frame · Scope

Question: Is the work sufficiently bounded to commit?
Evidence: outcome, work products, roles, inputs, dependencies, assumptions, exclusions, acceptance, commercial shape, and change path.
Owner: authorized client and IT Modality owners.
Consequence: approve, revise, defer, decline, or split the work.

Assemble · Ready

Question: Can the named team begin without crossing an unresolved dependency or control boundary?
Evidence: people, context, access, environments, source material, reviewers, work plan, data and security decisions, quality method, and known risks.
Owner: working owners and required specialist reviewers.
Consequence: begin, conditionally begin, return to preparation, or stop.

Govern · Deliver

Question: Does current evidence support continued execution, and are exceptions understood?
Evidence: artifact versions, decisions, review or test results, defects, scope changes, unresolved risk, and recommendation.
Owner: named delivery and review owners.
Consequence: continue, rework, escalate, narrow, or seek a client decision.

Govern · Accept

Question: Does the evidence support the authorized release or acceptance decision?
Evidence: agreed criteria, validation results, exceptions, conditions, rollback or support plan, and residual risks.
Owner: client acceptance authority; IT Modality supplies the in-scope evidence and recommendation.
Consequence: accept, conditionally accept, return, defer, reject, or stop.

Transfer · Transfer or Continue

Question: Can the receiving owner operate the result, or has a continuing scope been explicitly defined?
Evidence: accepted artifacts, documentation, knowledge transfer, owners, access changes, open decisions, unresolved risk, support route, and continuing-service terms where applicable.
Owner: receiving owner and IT Modality delivery owner.
Consequence: close, extend, move to a managed scope, or return to complete transfer.

Report decisions and evidence, not activity theater.

The engagement defines cadence and audience. A useful working record includes:

• the intended outcome and current phase;

• work completed, under review, blocked, changed, or accepted;

• decisions made, needed, and overdue;

• risks, issues, dependencies, and named owners;

• quality, test, review, and acceptance evidence;

• scope, assumption, access, data, or schedule changes;

• client inputs needed before the next gate; and

• the next decision and recommended action.

A status label without attributable evidence does not resolve a risk.

Escalate while the decision is recoverable.

The scope names impact categories, first owner, client and IT Modality escalation paths, communication channel, required evidence, decision authority, and any contractual timing expectation.

A common path moves from delivery professional to project or workstream lead, to delivery principal, to client working owner or sponsor. Qualified clinical, privacy, security, legal, financial, or regulatory authorities join when the issue enters their decision scope.

Public copy makes no universal incident-response, service-level, after-hours, or resolution-time promise.

Continuity starts before capacity changes.

Continuity depends on shared work-product ownership, current documentation, decision and risk records, access inventory, knowledge-transfer expectations, critical-role identification, and a receiving owner.

When a team change is required, the client receives the reason, proposed person, relevant evidence, transition plan, access change, and approval route defined by the engagement. The method does not promise an instant or identical replacement.

Delivered is not the same as accepted. Accepted is not the same as transferred.

Delivery makes the work available for review. Acceptance records the authorized disposition against agreed criteria. Transfer makes the result operable by the next accountable owner.

Closeout identifies accepted artifacts, exceptions, open decisions, unresolved risk, operating notes, access changes, knowledge transfer, support boundaries, and one receiving owner. A date alone does not close the work.

Choose the commercial shape that matches the ownership problem.

No public price or savings comparison appears here. The right shape follows the work, management burden, risk, control needs, and acceptance model.

Review managed-delivery teams

One counterparty makes accountability clearer, not risk disappear.

IT Modality's U.S. entity contracts and invoices for the agreed scope. The engagement states which delivery, commercial, professional, security, privacy, and continuity responsibilities IT Modality owns and which remain with the client or another party.

One counterparty does not eliminate client diligence, settle worker status by label, transfer professional or regulatory duties, or remove security, privacy, tax, legal, vendor, and operational risk.

Review vendor readiness

Review data and access before granting either.

Before access, the engagement identifies systems and data, purpose, environments, people and locations, minimum necessary access, device and identity expectations, subprocessors, contractual and business-associate questions, logging, incident handling, retention, and offboarding.

For healthcare work, the model uses HIPAA-trained, BAA-ready processes where the scope requires them. IT Modality does not claim HIPAA certification. EHR work is described through ecosystem fluency, not unsupported vendor certification.

Review security and data handling

The method needs accountable owners on both sides.

More likely to fit

• the priority can be bounded into a decision, work package, recurring queue, or milestone;

• client sponsors and working owners can make and maintain decisions;

• required context, access, reviewers, and input time can be supplied;

• evidence and acceptance can be defined before execution; and

• both sides will surface constraints and stop when a gate cannot be passed honestly.

Not a fit

• anonymous labor or undisclosed substitution;

• a guaranteed result, unstaffed service window, or hidden dependency;

• unapproved access, data, tools, environments, or providers;

• a legal, compliance, clinical, or financial conclusion without the qualified authority; or

• a buyer unwilling to retain its decisions, diligence, and receiving ownership.

Review the complete consulting FAQ

Start with the decision, not a shopping list of roles.

Share the priority, desired work product or operating change, current owners, systems and data, constraints, deadline or event, and acceptance question. The first conversation determines whether a project, managed service, managed-delivery team, or no-fit decision is the right shape.

Inquiry outcome: A valid submission creates a receipt and routes the request. It does not promise fit, availability, scope, service level, result, price, or response time.