The vocabulary the engagements are graded against.

The named weekly figure or observable frontline behavior we read on cell six of the Rules of Engagement at week six and onward.

A measurable number, or a small set of frontline behaviors read at the same cadence by the same named client-side owner — either way, it is the single anchor we sign together at week zero and read against for the life of the engagement.

The floor's ability to absorb one more simultaneous change without the readiness list stalling — read on the operating cadence, not on a calendar.

When change capacity is the named readiness gap, the floor opens up first; cell five (go-live criteria) waits for the floor, not the other way around.

The named accountable person inside your organization who reads cell-by-cell against the Rules of Engagement every Friday.

Cell four cannot be signed without this name. When we embed, we sit alongside them; when we exit, we transfer to them — formally, at the stabilization boundary.

The site where clinicians work the workflow our operator is mapping — surgical, ambulatory, inpatient, or front door, named at week zero.

Scribe engagements read on this floor; triage engagements live at its front door. The cell-by-cell readiness list is written against this floor, not against a slide deck of it.

The shape the go-live takes — site-by-site dual-run, single-site dry run, big-bang multi-business-unit, or currently-live-but-decaying.

The shape names what cell five (go-live criteria) has to carry. Site-by-site keeps the readiness list short; big-bang multi-BU pushes cell three to hold a multi-floor change on a single day, in which case we usually propose splitting it after week zero.

The cell that runs when the data your deployment depends on sits in someone else's hands — a vendor, a partner, or a sister team.

Cell two (solution scope) cannot be signed before the data-host question is. We open cell two side-by-side with whoever owns the data on the same call, in the same week.

Tier one. Fixed-scope diagnostic; ~3 weeks; a remote engagement lead embedding at week zero to walk the readiness list end to end.

The sprint signs the Rules of Engagement, maps the workflow as it actually runs, and walks integration sequencing before any change goes in. Where Tier two begins on the floor, this one begins in the air — diagnostic, not deployment.

The written fall-back the floor runs when the new system goes down — paper order sets, manual handoff logs, the named clinical owner on the page — written at week zero and rehearsed before go-live.

Cell five (go-live criteria) is not signed until the downtime procedure is read against the floor in front of us. A go-live without a rehearsed downtime procedure is a go-live that is one network blip away from the floor running without a system and without an owner — and that is the failure stabilization exists to repair. We answered who owns it during a cutover in plain words on the /faq — read it next.

The readiness-list convention where every cell is signed by a named FDE operator and a named client-side owner.

Nothing moves without both names. On the floor this is what the cell-by-cell list reads against at every Friday review; in the artifacts it is what the close of engagement transfers on.

A named Threshold FDE operator — the senior embedded engineer carrying accountability for the cell-by-cell readiness list against the Rules of Engagement.

Tier two engagements open with one on the floor in week one. They stay through go-live and into stabilization, then exit when the named client-side owner runs the program without us — the same operator throughout.

The operating posture where Threshold FDE's named operator sits on the floor during the work that matters — clinical, operational, technical, revenue-cycle, data, change leadership — running as one team with yours.

Not a remote status update, not a written progress note. The named operator is at the table where readiness is signed and where go-live criteria are read — operating the same problem the client-side owner is operating, in the same place.

The Tier-one discipline of reading the floor before any change goes in — workflow as it actually runs, owners as they actually sit, exceptions as they actually happen.

The output is the readiness list. The named FDE operator walks it with the named clinical and operational owners until each cell is read on the same floor, with the same names, in the same week.

Tier two. The full deployment: ~6–9 months; a named FDE operator embedded from readiness through go-live and into stabilization.

The named operator runs the readiness list cell by cell against the Rules of Engagement, coordinates multi-vendor sequencing on the same week, and signs adoption measures verbatim against cell six every Friday until the named client-side owner is running the program without us.

The named Friday cutover review where the readiness list is read cell-by-cell against the floor, in front of both names — the FDE operator and the client-side owner — and one of two words is signed.

The "go" word is signed only on cell five. The "no-go" word is signed without blame and without rescheduling pressure; we reschedule against the readiness list, not against the calendar, and the named client-side owner is the one who carries the call back to their leadership, not us.

Cell five of the Rules of Engagement. The signed readiness boundary at which the cutover is allowed to happen — independent of the calendar.

The criteria are read before the first change goes in and again at every site-by-site boundary. When go-live criteria are not signed, go-live does not happen, even if the calendar says so.

The seven-question readiness map at /rules-of-engagement — the prep we ask you to walk before the first engagement call.

The intake names the cell the readiness list opens on for your floor: audience, stage, workflow, readiness gap, named owner, cutover shape, week-six metric. An FDE operator reads the same seven answers against the same cell-by-cell list when work begins.

The week-by-week order in which the EHR, the platform, the integration partners, and your internal IT land on the floor during deployment.

Vendor-sequencing failures start at cell three of the readiness list. We write the sequencing at week zero so cell five names a single cutover date, not a vendor meeting.

The discipline of running cross-vendor deployment work on the same week, against the same readiness list, with the same named client-side owner — not in a series of handoffs.

In practice: the named FDE operator and the named client-side owner sit in the same coordination call as every vendor, sequencing the same week against the same cells, with nobody holding the change alone.

The named outcome we will say out loud when Threshold FDE is not the right shape for the engagement — at the intake call, at the first engagement call, or at any cell-by-cell review.

The no-fit naming is what the doctrine is for. We name it early so you are not paying us to discover it; when we are not the shape, we hand you to the team that is.

The cell-three operational discipline where the new system and the old system run side-by-side on the floor for a named window — same patient, same handoff, same named owner reading both — so the readiness list gets a real readout before either is taken down.

The window is named and bounded at week zero, not at the calendar. We end the parallel run when the named FDE operator and the named client-side owner have signed the same answers on both sides, on the same floor, in the same week — not when the vendor says the integration is complete.

The signed cell-five criteria, not the calendar date. The cutover is allowed only when cell five has been read against the floor in front of us.

A cutover at the readiness boundary is a cutover with two names on it. A cutover at the calendar is a cutover without anyone to call when the floor does not absorb the change — and that is what stabilization exists to repair.

Cell three of the Rules of Engagement. The cell-by-cell list, mapped against every requirement, signed by a named FDE operator and a named client-side owner.

The artifact that drives the engagement end to end. Nothing moves without both names on it; nothing closes without both names reading it on the same week.

The six-cell doctrine written with the client at week zero: problem, solution, readiness, owners, go-live criteria, adoption measures — each cell dual-named.

The document everyone points to when the work gets hard. It is not a memo we hand off at the close; it is the document the named FDE operator and the named client-side owner read verbatim against the floor for the life of the engagement and through the transition.

Tier three. Post-go-live operating rhythm on a rolling quarterly cadence; same named FDE operator, same named client-side owner.

Catches adoption drift and integration regression against cell six of the Rules of Engagement. Re-baselines the readiness list with the named client-side owner on a quarterly operating rhythm — not an annual review — so the engagement stays current as leadership and vendors rotate.

The signed exit point at which the named FDE operator transfers the program to the named client-side owner — adoption measured, integration stable, the named internal owner running it without us.

Not at the calendar date. Not at go-live. The named operator exits when the named internal owner is running the program — formally, with the readiness list and the Rules of Engagement transferred on the same week.