Repeated boilerplate on its own almost never triggers duplicate treatment. Shared headers, footers, navigation, disclaimers, and templated blocks repeat across a site by nature, and Google discounts them, weighing the main content instead. The panic that any text appearing on more than one page counts as duplication overstates the risk badly; the search engine largely reads past the boilerplate and judges the page on what is unique to it. So the answer is no, not by itself.
The risk only becomes real at a specific point: when the boilerplate dominates and the unique content is thin. The danger is not the repetition, it is the ratio. If the shared blocks make up most of a page and the part that is genuinely the page’s own is sparse, then the page stops standing on its own, and a run of such pages starts to look like thin, near-duplicate content. Thin content makes this worse, because thinness is what leaves room for the boilerplate to take over. The classic case is location pages where the templated body is identical and only a city name in the title changes; at that point the repeated text has moved into the main content, and what looked like boilerplate is effectively body duplication.
That distinction is the whole thing. Boilerplate confined to the furniture of the site, with substantial unique content beside it, is fine and common among well-ranking sites. Boilerplate that crowds out the unique content is the actual problem, and it is a thin-content problem wearing a duplication costume.
So the editor makes sure the unique main content clearly outweighs the shared boilerplate on each page, treating the balance between the two as the thing that matters rather than the mere presence of repeated text.