The OSGi reactive service model provides a powerful way for components to wire with each other without global coordination. In some major use cases however this process is temporarily interrupted. This can cause subtle issues as well as backlash against using services due to perceived instability. One such use case is the well known whiteboard pattern. We will look at whiteboard from a holistic perspective: service providers, service consumers, and (often forgotten) OSGi system deployers. We will point out where the issues lie and then we will propose a way to fix them by leveraging the equally powerful, but declarative module layer (i.e. use bundle requirements and capabilities).