Organizing Notices as a Team: A Practical Workflow

The scenario: a party with 12 ads and 4 people

Imagine you are managing a regional party campaign. You have four team members, 12 different advertisements across print and digital channels, and a deadline that is not moving. Each ad needs its own transparency notice, and the sponsor data needs to be consistent across all of them.

Without a system, this means 12 separate forms, each manually filled with the same party address, the same contact details, the same payer information -- and one typo in any of them creates an inconsistency that could raise questions during an audit.

This article shows you how to organize that workflow on The Taurus so it is fast, consistent, and reviewable.

Step 1: The Owner sets up the organization

One person -- typically the campaign manager or party secretary -- creates the organisation on The Taurus and takes on the Owner role. The Owner has full control: they manage members, configure defaults, and approve published notices.

When setting up the organization:

• Enter the official party name exactly as it should appear on all notices
• Add the registered address and contact details
• These become the organization-wide defaults that every notice inherits

This takes about five minutes, and it only needs to happen once.

Step 2: Create chapters for local branches

If your party has regional or local branches, set up chapters within the organization. Each chapter represents a unit -- a city branch, a district office, a thematic working group -- that manages its own ads.

Each chapter can have its own:

• Sponsor defaults -- the local branch name and address, pre-filled into every notice created within that chapter
• Members -- team members assigned to that branch
• Notices -- the ads managed by that branch

The key benefit: when a member in the Hamburg chapter creates a new notice, the sponsor fields are already filled with the Hamburg branch details. They do not retype them. They do not copy-paste from a shared document. The data is consistent by design.

Step 3: Editors create notices, Owner reviews

With the organization and chapters configured, the actual workflow becomes straightforward:

1. An Editor logs in and clicks Create notice within their chapter
2. Sponsor details, payer information, and contact data are pre-filled from defaults
3. The Editor adds the ad-specific information: description, costs, publication dates, targeting criteria
4. The Editor saves the draft

Before publishing, the Owner reviews the notice. This review step catches errors early -- a wrong date, a missing cost line, an incorrect election reference. The Owner either approves and publishes, or sends it back with feedback.

This separation of roles means:

• Editors focus on content -- they know the ad details and enter them quickly
• Owners focus on accuracy -- they verify that the notice is complete and correct before it goes public

Step 4: Campaign tracker aggregates everything

Group related notices into a campaign. A campaign is simply a container that ties multiple notices together -- for example, "Municipal Election 2026" or "Spring Membership Drive."

Within the campaign view, you can see:

• All notices linked to this campaign, across all chapters
• The total costs aggregated from every notice
• The status of each notice (draft, published, needs revision)
• A timeline of publication dates

This gives the Owner (and any auditor) a single view of the entire campaign's transparency footprint. Instead of checking 12 separate notices, you see one summary.

Step 5: Compliance Links keep publisher data in sync

If your ads are placed with multiple publishers -- a regional newspaper, a local radio station, an online platform -- each publisher may need to verify your transparency notices. Compliance Links connect your notices to the publishers' verification workflows.

When a publisher checks your notice through The Taurus, they see:

• The current published version of the notice
• Whether it is complete and valid
• The sponsor and payer information

Because all notices draw from the same organizational defaults, the data is consistent across every publisher interaction. There is no risk of Publisher A seeing a different sponsor address than Publisher B.

Why this matters: consistency and time savings

The biggest risk in team-based compliance is inconsistency. When four people independently fill in 12 forms, you get four slightly different versions of the same address, three different spellings of the treasurer's name, and at least one notice where someone forgot to update the costs.

Organizational defaults eliminate this class of error entirely. The sponsor data is entered once and inherited everywhere. Changes to defaults propagate to new notices automatically.

The time savings compound quickly:

• First notice in a chapter: about 5 minutes (ad-specific details only, since defaults are pre-filled)
• Subsequent notices: 3-4 minutes each
• 12 notices across a campaign: under an hour of total work, compared to several hours of manual entry

A practical example

Here is how the Hamburg branch of a regional party might handle their campaign:

The Campaign Manager creates the "Hamburg Municipal 2026" campaign and assigns it to the Hamburg chapter. The two Editors create their notices, pre-filled with Hamburg chapter defaults. The Treasurer reviews the cost aggregation. The Campaign Manager publishes all five notices after a final check.

Five notices, four people, one consistent dataset. That is organized compliance.

Getting started

1. Create an organization if you do not have one yet
2. Set up chapters for each branch or unit that manages its own ads
3. Configure defaults with accurate sponsor and payer information
4. Invite team members and assign appropriate roles
5. Create a campaign to group related notices

From there, creating individual notices is the easy part -- the structure does the heavy lifting.