1. What This Criterion Is For
Fit assesses whether a control is appropriate for the setting, roles, and operational context in which it is applied.
Even a well-intentioned or clearly defined control will fail if it doesn’t match the realities of the work, the environment, or the people involved. Fit asks whether the control makes sense for the specific conditions it’s meant to operate within.
This includes physical fit (e.g., does the procedure match the space?), role fit (e.g., can this person realistically do this?), and contextual fit (e.g., does this make sense in our type of program, with our community?).
2. How to Use It
Use the Fit criterion when:
- A control is being followed inconsistently or informally adapted
- Staff report that expectations don’t match real-world constraints
- A new control is introduced across varied teams, sites, or delivery models
Fit is critical when rolling out central policies to decentralized programs, or when attempting to standardize high-risk practices.
3. Examples Across Controls
| Control Type | Example of How Fit Applies |
|---|---|
| Security | Are supervision or access control rules workable in small or multi-use facilities? |
| Training | Is content tailored to different roles and contexts, or is it generic and mismatched? |
| Behavior Expectations | Are boundary guidelines feasible in settings that require physical care or contact? |
| Intake | Are screening procedures realistic for volunteer-run or low-resource programs? |
| Record-Keeping | Are documentation requirements manageable given staff time, literacy, or system access? |
4. What Strong, Fragile, and Failing Look Like
| Level | Indicators |
|---|---|
| Strong | Staff say the control makes sense. They can explain how it fits their role. No need to workaround or improvise. |
| Fragile | The control is followed, but only by bending rules or making informal adaptations. “It depends” becomes the norm. |
| Failing | The control is ignored, resisted, or quietly replaced with local workarounds. People say: “That doesn’t work here.” |
5. Common Pitfalls
- Assuming what works at head office will work everywhere
- Designing controls based on ideal scenarios, not real constraints
- Mandating steps without accounting for resources, role differences, or setting limitations
- Confusing standardization with fairness or effectiveness
6. Design Prompts
When designing or reviewing a control:
- Does this control match how people actually work?
- Can it be realistically applied in all relevant settings?
- Are staff improvising because the control doesn’t fit?
- Are there cultural, physical, or role-based differences that need to be accounted for?
- If this control feels difficult, is it because of the content or because of the context?
Fit is where policy meets reality. Controls that don’t fit are rarely resisted because of disagreement — they’re resisted because people know they can’t make them work without breaking something else.