A team writing style is a shared structure everyone in your organisation drafts against, so submissions read consistently regardless of who wrote them.
It matters most where several people draft in parallel on the same bid. Without a shared style, an evaluator reads a submission that changes voice and structure question by question — which reads as a team that does not talk to each other.
How it differs from a personal style
The mechanics are identical. Creating, testing and setting a default work exactly as described in Writing styles: creating, testing and applying — the only difference is which toggle you use.
Personal | Applies to your own drafts only. |
Team | Available across the team, and used by anyone without a personal default of their own. |
Create a team style
Go to Settings → Writing Styles.
Ensure Structure is toggled on.
Toggle Team.
Click + New Structure, name it, enter the template, and save.
Then set it as the team default from the card, so it applies without anyone having to select it.
The rule that catches teams out
A personal default always overrides the team default.
Setting a team style does not force anyone to use it. Anyone with a personal default keeps drafting in their own structure, and nothing tells them otherwise — their drafts simply come out as they always have.
So if you are rolling out a house style and drafts are still inconsistent, the cause is almost always personal defaults, not the team style failing to apply.
Rolling out a house style
Develop and test the style properly before setting it as the team default. Everyone will be drafting against it.
Test against real questions from a live project, ideally across several question types — a structure that suits a 200-word policy question may not suit a 1,000-word method statement.
Tell the team it exists, and ask anyone with a personal default to clear it if they should be using the house style.
Revisit it after a bid or two. The first version of a house style rarely survives contact with a real tender unchanged.
Related articles
Writing styles: creating, testing and applying — the full mechanics, for both scopes.
Generating drafts — where the style is applied.
Team Content Controls — other organisation-wide drafting defaults.
Applying Win themes to a draft — shared messaging, alongside shared structure.
