Best Practice for Managing Policies, Procedures, Manuals, etc?

We've been using Confluence for a few years to manage all of our company Policies, Procedures, Forms, Training Manuals and more, but theres got to be a better way to do it.

Our current problem is duplicate content.

We have spaces broken into departments like, HR Policies Space, HR Procedures Space, Finance Policies Space, Finance Procedures Space, and so on. The problem comes in when users need to include a Policy or Procedure or Form inside another space.

Example: Our Employee Manual is its own space that contains tons of duplicate pages from all other spaces. Whenever a change is made on the original page in HR Policies, its up to the user to search out all the duplicates in manuals and make that same change.

Theres got to be a better way.

I would think a better option would be to embed the entire page of the HR Policy they are trying to use in the Employee manual, that way if a change is made to the original, it is mirror to all the manuals because its embedded. But I don't think you can even embed a page like this.

Does anyone have any better ideas?

1 comment

This is exactly why Confluence has always had an "include" macro.

When you identify a duplicate, delete the entire body of the duplicate and replace it with a simple "include: source of truth" macro.

This is what I needed. Thanks a ton!

 Any suggestions as to the best structure to use?

Instead of us having 75 different spaces for "HR Policies", "HR Procedures", "Finance Policies", etc... I think it might be better to have 1 space that has all Policies and Procedures within it and then each space just uses that macro to organize those pages into other spaces?

Peter DeWitt Community Champion Nov 08, 2017

"Instead of us having 75 different spaces for "HR Policies", "HR Procedures", "Finance Policies", etc... I think it might be better to have 1 space that has all Policies and Procedures within it and then each space just uses that macro to organize those pages into other spaces?"  - I think this is the way to go.  I have used a similar approach for team status updates.  One space for the Status updates and includes back to the team spaces where each team can keep their own status up to date.

 

.pd

In addition to the Include Macro Nic mentioned you could also use the Excerpt Macro and the Excerpt Include Macro in case you need to reuse only one part of a page.

In case you have even more complex single sourcing requirements, you could use a third party plugin that supports multi-excerpt.

Davin Studer Community Champion Nov 10, 2017

Related to the multi-excerpt macro that Robert mentioned is a free offering that does the same thing. It called the Include Content add-on.

Comment

Log in or Join to comment
Community showcase
Bridget Sauer
Published Jan 29, 2018 in Confluence

Showcase: How LinkedIn does Content Lifecycle Management (12 Steps)

LinkedIn, the world's largest business network has an exceptionally large Confluence instance. In their case, large means millions of pages and thousands of spaces. In this Showcase, we're focusing i...

517 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot