Reusable blocks

A reusable block is one or more finished sections you can drop into any proposal. It is where the boilerplate lives: the team introduction, the terms, the case studies, the “how we work” section.

Creating one

A block has a title, a description and a category, and holds its sections built in the same editor as everything else. The description is what distinguishes two similar blocks in the list, so write it for the colleague choosing between them.

Categories group the library — for example by purpose (intro, proof, terms) or by service line. Blocks without one appear under Other.

Like templates, blocks can be active or inactive. Inactive blocks stay in the library but disappear from the insert list.

Inserting one

Library in the editor toolbar opens the block library, searchable by title and description. Inserting a block copies its sections into the proposal at your chosen position.

The copy is one-way, exactly as with templates: editing the inserted sections does not change the block, and updating the block does not rewrite proposals that already use it. That is deliberate — a sent proposal should not change retroactively because someone edited a block — but it does mean a wording fix has to be made in the block and in any draft that already carries the old text.

What makes a good block

Blocks earn their keep when they are self-contained. A section that only makes sense after a specific preceding section is a source of confusion in a library; the team introduction, the guarantee, the terms and the reference list are the sort of thing that reads correctly wherever it lands.