When a facility's requirements change, upcoming placements catch up on their own
Add or change a facility, health system or MSP requirement and every open, not-yet-started placement there is updated automatically.
Facility requirements change. A health system adds a new screening, an MSP updates its packet, or a facility gets linked to a program after a placement is already in motion. Before, a placement only picked up the requirements that existed when it was created.
Now, every upcoming placement keeps up.
What changed
- Any change is noticed. Adding, editing, switching off or removing a requirement, at the facility, health system, MSP or VMS level, or linking a facility to a new program, is picked up automatically, whoever or whatever made the change.
- Batched, not noisy. Wolf waits a few minutes after the last edit, so updating thirty rules across two hundred facilities becomes one tidy update per placement rather than a flood.
- Only the placements that should change. Open placements that haven't started yet are updated. Clinicians already working are left alone.
- Work already done is protected. If a requirement is removed, items nobody has started are switched off; anything with evidence, documents or completed steps is kept and flagged for your team to decide.
- Clear history. Each placement shows what triggered the update and what changed, so you can always see why a new item appeared.
Placements are also now linked to the exact facility record in your Library, not just a facility name, so the right requirements are always the ones applied.
Why it matters
Your contracts stay the source of truth. When a client's rules change, your in-flight placements follow, and nobody has to remember to re-check them by hand.
See it work a real file.
Thirty minutes, one placement, worked live — start to submit-ready.