A year-in-review post becomes a yearbook when it tries to prove that everything mattered. Every opening, announcement, studio visit, and staff moment gets the same amount of space, and the reader is left to build the meaning alone. A useful review makes a smaller argument. It chooses one reader, selects the parts of the year that support that point of view, and ends by showing what is still in motion.
A strong year-in-review post is an edited argument about the year, not a complete chronology. Choose the reader first, limit the story to one point of view, make images comparable, write transitions that explain the movement between moments, credit the people involved, and end with what continues. If the archive has no honest shape, publish nothing rather than padding it.
What makes a year-in-review post different from a yearbook?
A year-in-review post is an edited argument about what the year meant, while a yearbook is a record of what happened. The review chooses a point of view and leaves some events out. It asks the reader to notice a pattern, a change, or an unfinished thread instead of counting every entry on the calendar.
A complete chronology feels safe because nothing gets judged. The opening appears, then the exhibition, then the studio visit, then the holiday gathering, all in the order they happened. The result can be accurate and still feel strangely empty. Sequence alone does not explain why one moment belongs beside another.
Editing introduces a useful risk. If the post is about how a program became more focused, it does not need every announcement. If it is about a year of making space for new voices, it may need fewer finished images and more evidence of the choices that made that space possible. The missing material is not a failure of documentation. It is what lets the chosen material make a point.
Think of the post as a short essay with images, not a folder converted into paragraphs. The archive is the source material. The article is the decision about what the archive is saying. That decision is what turns a recap into something worth reading after the dates have gone by. A little omission is often what makes the larger meaning visible.
Who should a gallery write its year-in-review post for?
Choose one primary reader before choosing the images. A collector, an artist, a future collaborator, a donor, and a first-time visitor each need a different version of the year. The post can still welcome everyone, but its selection and explanation should answer one reader's useful question first.
A collector may want to understand the shape of the program and where the work moved over the year. An artist may care more about the conversations, working relationships, or conditions that made a project possible. A new visitor may need a clear sense of what the organization values before deciding whether to follow along. These are not interchangeable reasons to publish.
Write the reader's question in one sentence. What did this year make possible? What kind of work does this gallery choose to stand behind? What changed in the way the organization made room for artists and audiences? A question like that gives the archive a filter. Images and moments that cannot help answer it can stay in the larger internal record.
This is also where tone gets decided. A note to artists can be intimate and process-aware. A note to a broader public may need more context around the work and fewer internal references. Neither tone is more correct. The mistake is asking one post to sound like a thank-you letter, an annual report, and a recruitment pitch at the same time.
How much of the year belongs in the story?
Limit the story to the smallest set of moments that can support its central point. A year-in-review becomes clearer when the reader can see why each section is there and what it adds to the argument. If a moment is included only because it happened, it is probably part of the archive, not the post.
Start by gathering broadly, then edit in passes. The first pass can include openings, installations, studio visits, conversations, publications, and quieter work that never became an announcement. The second pass should group those moments by meaning rather than date. The final pass should keep only the material that changes the reader's understanding of the year.
Limiting the story does not mean pretending the year was tidy. A useful review can include a detour, a pause, or a project that changed direction. It just needs to explain why that irregularity matters. One unresolved thread can carry more life than a row of polished milestones that all make the same point.
Give the post an ending before you finalize the middle. If the last section needs to show what continues, earlier sections should build toward that future rather than using every paragraph to close a separate loop. The calendar can hold the rest. The post needs enough room for a reader to feel the shape of the year without being asked to carry its entire weight.
How can a year-in-review make different archive material comparable?
Make archive material comparable by giving unlike moments a shared question, scale, or visual treatment. An opening photograph, a studio detail, and a quiet installation view do not become a story merely because they sit in the same folder. The surrounding text needs to explain what each image reveals about the same larger idea.
Comparison can come from the work itself. You might place an early installation beside a later one to show how the organization learned to use space differently. You might pair a finished view with a process image to show what changed between an idea and its public form. The point is not to manufacture a before-and-after result. It is to make the relationship visible.
Crop and sequence matter too. A wide room view can establish context, while a closer detail can slow the reader down and let a material or gesture carry the next sentence. If every image is the same distance and shape, the page starts to feel like a catalogue grid. Variation gives the archive a rhythm, as long as the variations have a reason.
Use captions to supply information the image cannot. Name the moment, place it in the larger thread, and state what the reader should notice without turning the caption into a second essay. Comparable does not mean identical. It means the reader has enough shared language to understand why these particular images belong together.
Why do transitions matter in a year-in-review post?
Transitions explain why one part of the year leads to the next. Without them, a review becomes a stack of captions, each accurate on its own and disconnected from the paragraph before it. A good transition names the change in scale, mood, or focus so the reader can follow the argument rather than reconstruct it.
The transition does not need to announce itself. A sentence about a program becoming more outward-facing can lead from an installation to a public conversation. A sentence about returning to the studio can move from finished work to the slower decisions behind it. The connection can be quiet, but it has to exist somewhere in the text.
Look for repeated verbs in the draft. If every section says the organization hosted, showed, or shared something, the year will feel flat even when the material is varied. Transitions give the writing different kinds of movement: from making to presenting, from gathering to reflecting, from one person's work to the relationships around it.
Read the post without the images and mark where your attention drops. Those are often transition problems, not image problems. Add the sentence that tells the reader what changed between the two moments. Then read it again with the images restored. The photographs should deepen the movement, not be forced to perform all of the connective work themselves. The reader should feel guided, never handed a puzzle.
How should a year-in-review credit the people who made it?
Credit the people whose work, permission, labor, or care made the year possible, and make each credit precise enough to be useful. Artists, writers, installers, photographers, staff, collaborators, and venues may have different relationships to the same moment. A broad thank-you can sit beside those details, but it should not replace them.
Start with the image and project records, not memory. Confirm names, spellings, roles, and whether a person or organization should be named publicly. A year-end post often brings old material back into circulation, so the fact that a name was correct in an earlier announcement does not mean it can be copied without checking the current record.
Credit is part of the editorial structure, not a legal footer added after the writing is finished. A caption can tell the reader who made the work. A paragraph can acknowledge a team whose contribution would otherwise vanish behind the institution's name. A link can give a collaborator a clear way to continue the conversation.
Keep the language proportional. Do not inflate a contribution with praise the record cannot support, and do not make a quiet role sound invisible because it did not appear in the final image. The review should show how the year was made, not only what the gallery chose to put on the wall. That is a more honest form of institutional memory, and it gives readers a fuller record of the work.
When is it better not to publish a year-in-review?
Skip a year-in-review when the archive has no honest point of view, the material cannot be cleared for use, or the post would repeat a list the audience has already seen without adding meaning. A quiet year does not require a padded recap. Publishing less can be the more accurate editorial decision.
There is a difference between a year with little public activity and a year with little to say. A small program may still contain a clear change in direction, a meaningful collaboration, or a new way of working. A busy program may produce only disconnected announcements. Count is not the test. The test is whether the material can form a readable thought.
Permission can be the deciding boundary. If key images cannot be published, if credits are unresolved, or if an artist's work needs context the post cannot provide, wait or choose a different format. A private internal record, a letter to collaborators, or a smaller update may serve the material better than a public article built around gaps.
Padding is easy to recognize once you remove the dates and look at the sentences. If several sections say that something happened without explaining why it belongs, the post is asking the reader to applaud the calendar. Leave those sections out. A review should earn its length through meaning, not through the number of items it manages to mention.
How should a year-in-review end?
End with what continues, not with a generic thank-you or a promise that the next year will be bigger. The closing should identify the thread that remains active, a relationship, question, way of working, or body of work, and show the reader where it goes next. That turns a retrospective into a useful handoff.
The future does not need to be announced as a schedule. It can be a sentence about continuing to make room for a kind of conversation, carrying a method into a new project, or staying with a question that the year did not resolve. Specific direction is more convincing than a list of ambitions that could belong to any organization.
Bring one image or detail from the opening back into the close if it has changed meaning along the way. A blank wall can become a space waiting for the next install. A small archive stack can become evidence of a method the team plans to keep. This kind of return gives the post shape without pretending the year was a neat circle.
We approach monthly media with the same restraint. The point is not to make every month look full. It is to keep the work legible as it develops, with enough context that a reader can see what has happened and what is still unfolding. A year-in-review is strongest when it leaves the archive open, rather than sealing it into a finished display.
Frequently asked questions
How is a year-in-review post different from an annual report?
A year-in-review post is an editorial story with a point of view, while an annual report usually prioritizes formal records, updates, and accountability. A review can leave events out if they do not support its central idea. It should still be accurate and properly credited, but its job is helping a reader understand the shape of the year, not presenting every activity in equal detail.
How many projects should a gallery include in a year-in-review?
There is no useful universal count. Include the smallest group of projects that can support the post's central point of view. A quiet year may need only a few connected moments, while a larger archive may need more evidence to make a change or pattern visible. If an item appears only because it happened, keep it in the internal record instead of forcing it into the public story.
Should a year-in-review post be organized chronologically?
Chronology can help when the order of events explains a real change, but dates alone rarely create a story. Group the archive by meaning first, then use dates to orient the reader inside each section. This lets an installation, conversation, or studio moment sit beside another event because they reveal the same thread. The calendar can support the argument without becoming the argument itself. That keeps the post readable after the year has ended.
What should a gallery do if it does not have enough material for a recap?
Do not pad the recap. First ask whether the quieter material contains an honest thread, such as a change in focus, a useful collaboration, or a way of working that deserves context. If it does not, choose a smaller update, a private note, or no year-in-review at all. A short, accurate absence is better than a public post that asks the reader to celebrate a list.
How should people and collaborators be credited in a year-in-review?
Check the project and image records before publishing, then confirm names, spellings, roles, permissions, and links where relevant. Credit artists, writers, installers, photographers, staff, collaborators, and venues according to what each contributed. Put useful credit near the related image or passage instead of hiding every name in a final list. Precise credit shows how the year was made, not only what the institution presented. It also makes the archive easier to revisit later.
Give the quiet month something to say.
We help galleries build content out of the ordinary weeks too, pulling from the archive, planning ahead, and keeping the feed honest between openings.
Explore monthly media →