Presentation standards for government agencies: structure, template and design

A presentation standard for a government agency is a short internal document plus a master template that define the structure of a briefing, slide design, rules for numbers and the approval process. It exists so that every department prepares presentations in the same clear and fast way, and the head of the agency does not waste time reworking slides before every meeting.

Below is a practical guide: what such a standard consists of, how to set up the template, which rules must be written down and how to roll it out so that staff actually use the new format instead of going back to their old files.

Why an agency needs a single standard

In most organisations, presentations are prepared by dozens of people from different departments. Everyone has their own habits: one person pastes an entire table from a report onto a slide, another chooses a bright background, a third writes ten-line paragraphs. As a result, the head of the agency flicks through files that look as if they came from different organisations, and the important message gets lost in small print.

A single standard solves several problems at once:

• It saves time. Staff do not reinvent the design; they fill in a ready-made structure.
• It improves clarity. The audience gets used to the same position of headings, conclusions and sources.
• It builds trust. Neat, consistent materials are perceived as the result of systematic work.
• It simplifies approval. Reviewers spot errors more easily when all slides follow the same logic.

The required structure of a briefing

A good government presentation answers the questions of the decision-maker in the order they ask them. We recommend fixing a basic seven-part skeleton in the standard:

1. Title slide: title, department, date and access marking if needed.
2. Key conclusion: one or two sentences on the essence of the briefing, what happened and what is proposed.
3. Context: the task, instruction or programme the briefing relates to.
4. Facts and figures: key indicators with sources and the date of the data.
5. Problems and risks: what is getting in the way, where there are delays, what the constraints are.
6. Proposals: specific steps, owners and deadlines.
7. Appendices: detailed tables that do not need to be on screen but should be at hand.

The conclusion-first principle matters most: senior officials often see only the first few slides and then move on to discussion. If the main point is hidden on slide twelve, it may never be heard at all.

The master template: what it should contain

A template is not just a nice background. It is a set of configured layouts in PowerPoint or Google Slides with fonts, colours, a grid and placeholders already defined. A minimum set of layouts includes:

• a title slide and a section divider;
• a key conclusion slide with large text;
• a slide with a single chart and a takeaway caption;
• a key indicators slide with three or four large numbers;
• a slide with a table of limited size;
• a two-column problem and solution slide;
• a slide with a regional map or process diagram;
• an action plan slide: step, owner, deadline.

Colours should come from the organisation's corporate identity, and the palette should be limited: one primary colour, one accent colour to highlight what matters and neutral greys. The typeface must properly support both Cyrillic and Uzbek Latin script, including the letters o' and g', otherwise bilingual presentations will show empty boxes and broken lines.

Plan template versions separately as well: a widescreen version for the screen in the hall, a print version for handouts and, where needed, Uzbek, Russian and English versions with an identical structure.

Rules for text, numbers and charts

This is where most problems arise, so the rules should be written down specifically rather than as general wishes:

• A headline is a conclusion. Instead of Nine-month indicators, write Programme delivery is ahead of plan in two of three areas.
• One idea per slide. If a slide needs two conclusions, split it.
• A text limit. For example, no more than five bullet points and no more than two lines per point.
• Units and periods. Always state units of measurement, the period and the date the data is valid for.
• A source under every number. A small caption at the bottom of the slide: where the data comes from and as of what date.
• Charts instead of large tables. Any table longer than five rows goes to the appendix; the slide keeps a chart or highlighted values.
• Consistent rounding. The same number of decimal places throughout the presentation.

We cover how to turn complex data into clear visual blocks in more detail in our article on infographics for government reports.

A presentation standard only works when it is shorter than the habit of breaking it: two or three pages of rules and a convenient template are more useful than a thick regulation nobody opens.

Typical mistakes in agency presentations

Even with a template in place, the same mistakes keep coming back. It helps to include a list of them in the standard itself as a set of things not to do:

• screenshots of Excel tables or documents that cannot be read on screen;
• different chart styles in one presentation, with mismatched colours, fonts and legends;
• decorative photos and clip art that carry no meaning;
• animations and transitions that distract and slow the presentation down;
• no slide numbers, which makes it hard to refer to a specific slide during discussion;
• mixing languages on a single slide without a clear need;
• outdated figures copied from a previous version of the briefing.

How to roll out the standard in an organisation

A document without implementation quickly becomes a formality. A workable sequence looks like this:

1. Audit. Collect ten to fifteen typical presentations from different departments and list the recurring problems.
2. Agree on goals. Decide who the main audience is, whether senior management, a board or external partners, and what matters to them.
3. Develop the template and rules. Structure and rules first, visual design second.
4. Pilot. Ask two or three departments to prepare real briefings in the new format and collect feedback.
5. Training. A short one-hour session with before and after examples works better than emailing a file.
6. An owner for the standard. Appoint someone who updates the template and answers questions.

If your organisation already uses neural networks to prepare drafts, decide in advance what data may be uploaded to them. We discuss safe scenarios in our article on AI-assisted presentations for ministries and hokimiyats.

Approval, versions and file storage

Many problems arise not from design but from file chaos. Before a meeting, five versions of a briefing circulate by email, edits are made in different copies and the wrong version ends up on screen. That is why the standard should include simple organisational rules:

• A consistent file name. For example: date, department, topic, version number. That way it is immediately clear which file is current.
• One storage location. A shared folder or document management system instead of sending attachments through messengers.
• A clear approval chain. Who checks the numbers, who is responsible for wording and who approves the final version.
• A submission deadline. The final file goes to the front office or organisers in advance, for example the day before, not five minutes before the start.
• A PDF copy. A PDF version is saved alongside the source file: it opens the same way on any computer and is suitable for sending to participants.

These rules may seem minor, but they are often what determines how calmly the presentation goes.

A checklist before the presentation is shown

• The key conclusion is visible on the second slide.
• Every headline states an idea, not a topic.
• All numbers have units, a period and a source.
• Tables longer than five rows have been moved to the appendices.
• Colours and fonts match the template.
• Slides are numbered and text is readable from the back row of the hall.
• There is no confidential data that is not meant for this audience.
• The file has been checked on the computer that will be used for the show, including fonts.

If you need a master template, rules and training examples tailored to your organisation, the Dasta Creative team can help through its presentation and report design service, from an audit of your current materials to a ready set of layouts in three languages.