When does a document become a publication?

Not every document needs to become a publication.

Sometimes a document is exactly that: something created to record information, share instructions or provide a practical reference. It doesn't need elaborate design. It just needs to be clear and usable.

But there comes a point when the document has a job to do beyond just containing information.

Perhaps it's being sent to prospective clients. Maybe it is a report going to senior stakeholders, a recruitment pack being shared with candidates or a prospectus intended to influence someone's decision.

At that point, the way the information is presented starts to matter much more.

So when does a document become a publication?

There isn't a particular page count or format that defines it. It is more about purpose.

Think about the reader

A useful place to start is by asking what the reader is expected to do with the information.

Are they simply checking something? Are they expected to understand a complex issue, compare options, make a decision or decide whether they want to work for an organisation?

The more important that interaction becomes, the more thought needs to go into the publication itself.

A document that supports a significant decision shouldn't make the reader work unnecessarily hard to find the information they need.

Purpose changes the role of design

Consider a long internal policy document and a recruitment pack. Both might contain headings, paragraphs, tables and supporting information. Both could be created in Word.

But they have very different jobs.

The policy document may primarily need to provide an accurate reference. The recruitment pack needs to introduce an organisation, explain an opportunity and encourage the right people to take the next step.

That changes the design.

The recruitment pack needs a clear narrative. It needs to communicate the role, the organisation, the opportunity and the practical information a candidate needs. It also needs to create an impression of the organisation itself.

The same applies to reports, prospectuses, annual reports and other outward-facing publications.

When does publication design become important?

Once you start thinking about the reader, small design decisions become much more significant.

Where does the reader enter the publication? Is the first page doing enough? Can they quickly understand how the document is organised? Are the most useful pieces of information easy to find? Is there enough variation to prevent a long publication becoming visually exhausting?

These aren't questions you can answer simply by applying a template.

They require someone to look at the content as a whole.

A publication has a relationship with its reader

A publication isn't simply a container for information.

The order of the sections, the way information is grouped and the visual hierarchy all influence how someone experiences the content.

A contents page can tell a reader what to expect before they begin. Section openers can provide a sense of progression. A well-placed statistic can bring attention to something important. A diagram can explain a relationship that would otherwise take several paragraphs to describe.

These decisions may be subtle, but together they shape the way the publication is understood.

There's no single definition of a publication

A publication might be 12 pages or 120.

It could be printed, digital or both. It might be a formal annual report, a prospectus, a magazine, a recruitment pack or a carefully designed company profile.

What they have in common is that the presentation forms part of the communication.

The design isn't simply there to make the document look polished. It helps establish the order in which information is encountered and gives the reader clues about what deserves attention.

That's where editorial thinking becomes useful.

Not every document needs this level of attention

It's worth saying that more design isn't automatically better.

There are plenty of documents that don't need to become publications. Adding unnecessary design can make something harder to use rather than easier.

The question is really whether the document has become important enough, complex enough or outward-facing enough that the reader's experience needs to be considered alongside the information itself.

When the answer is yes, it's worth approaching the work as a publication rather than simply a formatted document.

That shift in thinking can change quite a lot.

Instead of asking, “How do we fit all this content onto the pages?”, you start asking, “How should this information be organised so that someone can actually use it?”

For substantial documents, that's often the more useful question.