I hope you find my writing and business tips and observations useful. My business and blog are dedicated to helping businesses communicate clearly and reach their potential.
Read, subscribe to my newsletter, enjoy!Tash
Does your business have a document register?
It sounds a bit dry and perhaps a bit overly interested in details, but a document register can save a lot of time and keep things simple and consistent – I’ve certainly seen this in action as Communications Manager for companies with many forms and standard letters.
A document register is simply a list of every document the business uses as standards. It can include forms, letters, marketing flyers, information guides, fact sheets, website banners, promotional articles, stationery items and eBooks.
If there are many documents, it is usually worth dividing into categories (list all the forms then all the flyers for example).
Document registers can also be a handy way to communicate with new team members – they can see what exists to help them learn about the business and ensure they don’t ‘reinvent the wheel’.
In its simplest form, the register just lists the documents so it’s easy to see what exists.
More complicated but infinitely more useful are registers that include a code for each document. These codes are changed each time a document is updated so the register becomes a reference for ensuring you have the most recent version of something.
And a record to spot any documents that are perhaps a bit old and overdue for a refresh.
Here are a few points I’ve learned from using document registers in different companies:
Any questions on who to make use of a document register?
Do you manage a lot of documents? Do you worry about old versions getting confused with new versions?
This is why you see a document code on many documents, especially those from major organisations. They make it easy to tell one version from another at a glance – this is known as version control and can save a lot of problems.
There is no central system for giving documents codes – each business makes up its own system and introduces it as it is the business who needs to use the codes.
While there is no single coding system, most codes will include the date as that is the simplest way to determine how old a document is.
Other than that, it is up to you how the code is created. The complexity of your code will also depend on the number of documents you deal with – a few documents can be numbered 1 to 20 for example, but a large number of documents may be better divided into types and then given a number (e.g. F1 is form 1 and L24 is letter 24).
Here are a few tips from the systems I have created and used in the past:
When I’m writing for some of my corporate clients, a number of people need to be involved in the document – usually a mix of technical experts and legal advisers, along with a manager or two. If you have ever had to deal with a committee consensus, you’ll know that this process can be frustrating and time-consuming.
The best results arise when everyone has the appropriate input with one or two people having responsibility for the final result – usually the writer and a senior manager.
Here are some of my tips to keep this process under control:
As a writer, it is my job to take their technical knowledge, legal requirements and document intentions and provide them with a clear, easy to read document. So sometimes I do exactly as their feedback requests (e.g. changing a measurement from 5mm to 5cm) and at other times I adjust their feedback for clarity.
Use your words wisely!
A few days ago, I posted about the importance of checking presentation as well as details of your content. Today, I am going to list the details I check for when reviewing a draft for a document’s design elements.
This list is in the order I think of them, not necessarily in any importance.
If you are happy with all of these details, you will be very close to the correct design for your needs.
Recent Comments