Forge Academy: Brand Voice Setup

A recognisable brand voice comes from choices a reviewer can explain: how you describe the buyer's situation, how much certainty you express, which evidence you use and what you ask the reader to do. “Professional” is too broad to guide all of those decisions. The aim of this lesson is to turn your preferred style into a small, testable set of writing decisions.

In Forge, the documented controls used for this work are the Node's offer information, buyer–pain–proof relationships and Content intelligence settings, followed by draft review. The Forge User Guide documents these controls. Keep approved writing examples as a reference for your editor; do not assume that a separate brand-voice dashboard or an example-training function is available.

Choose one message to calibrate

Use an offer you know well and a buyer you can describe precisely. Avoid beginning with a corporate announcement that combines several audiences and promises. You need a message whose accuracy and tone can be judged separately.

Our illustrative example is a feedback-skills workshop for managers. The buyer is a learning and development manager assessing programme suitability. The pain is not knowing whether a proposed workshop includes meaningful practice. The available proof is an approved sample exercise with an assessment checklist. This is a hypothetical teaching example, not a customer result.

The desired voice is practical, respectful and evidence-led. That means explaining what participants practise, treating the buyer as an informed professional and showing what the sample can establish. It does not mean claiming that one workshop will transform productivity. Write down the offer facts before choosing the style so an attractive tone cannot conceal an unsupported promise.

Write a short editorial reference before changing settings

Create a working reference your reviewer can use alongside Forge. It can be a short document maintained by your team. It is not a new interface field. Include a reader description, 3 writing rules, 3 avoid rules and a small selection of approved phrases.

Decision	Example reference for the workshop
Reader relationship	Speak to a manager comparing programme content, not a novice who needs to be persuaded that learning matters
Writing rule 1	Name the activity or deliverable before describing its value
Writing rule 2	Use clear, measured statements and explain what the evidence shows
Writing rule 3	Offer a concrete next step, such as reviewing the sample exercise
Avoid rule 1	No guaranteed performance improvements without approved supporting evidence
Avoid rule 2	No generic superlatives such as “ultimate” or “unmatched”
Avoid rule 3	No language that belittles managers who need support

Choose examples because they demonstrate a decision, not because they contain favourite adjectives. A useful reference might include an opening that names a buying question, an explanation of a deliverable and a restrained invitation to inspect it. Add one sentence explaining why each example works. This gives reviewers a reason to accept a different sentence that follows the same principle.

Make the Node carry accurate positioning

Open the Node through Edit node. Check that the description names the workshop and its actual activities. The value proposition should reflect the benefit you can responsibly offer, and the differentiator should explain a real difference in the approach. A factual statement such as “participants practise a feedback conversation using an agreed checklist” gives the writing stronger material than “world-class learning that unlocks potential”.

Review the linked buyer, pain and proof. If the buyer is a programme evaluator, a draft should help that person judge suitability. If the only evidence is a sample exercise, explain the structure it reveals rather than implying that it proves a workplace outcome. Save corrections to the underlying facts before using style settings to refine the presentation.

Do not fill factual fields with a long list of tone commands. Keep the business information intelligible to another operator. Put the documented objective and personality choices in their appropriate controls, and use the editorial reference to assess the finished writing.

Set objective, personality and length deliberately

Under Content intelligence, review Content objective. Select an objective available in your account that reflects the job of this particular content. A message intended to help a buyer evaluate the workshop should provide enough substance to support that decision. An objective cannot repair a missing offer or unsupported proof.

Set Content personality using up to 2 tones. For this example, evidence-led and educational are a coherent starting combination. Do not interpret the number of available descriptors as a reason to pursue every style at once. A challenger approach may suit an argument against a common practice, but it needs a clear argument and evidence, not simply more forceful language.

If the target surface and message benefit from a ceiling, use Max words per post. An illustrative cap of 140 words can help this short workshop message stay focused. It is a working choice, not a universal recommendation or a guarantee that every platform will accept the output. Review the actual draft and the selected surface's constraints.

Compare writing decisions, not just which draft you prefer

Use Manual on the selected surface and generate a draft for review. Check the factual content first, then compare its wording with your editorial reference. The examples below show the kind of change you are looking for; they are illustrative copy, not generated test results.

Before	After	What changed
Revolutionise your team's productivity with our unmatched workshop.	In this workshop, managers practise a feedback conversation and review it against an agreed checklist.	An unproved outcome became a specific, reviewable activity
Struggling managers need to stop making basic communication mistakes.	When choosing a feedback workshop, ask how participants will practise the conversations they need at work.	Judgement of the audience became a useful buying question
Contact us today to unlock your team's full potential.	Ask for the sample exercise to assess whether the practice fits your managers' needs.	A vague invitation became a concrete evaluation step

The revised wording has a voice because it makes consistent choices about respect, specificity and evidence. It can still vary in rhythm and vocabulary. Requiring every post to begin with the same phrase would make the pattern more obvious while making the content less useful.

Check Arabic and English against the same promises

For bilingual work, create an approved counterpart in each language. Judge Arabic as natural professional Arabic rather than a word-for-word reproduction of English sentence order. Preserve the offer, evidence, conditions and reader action.

For example, “Ask for the sample exercise to assess whether the practice fits your managers' needs” can become “اطلب نموذج التمرين لتقييم مدى ملاءمة التدريب لاحتياجات المديرين لديك”. The Arabic retains the evaluation step without introducing a guarantee of improvement. A version promising “نتائج مضمونة” would change the claim, not merely the tone.

Maintain a short list of accepted product names and specialist terms. Decide when an English UI label should remain unchanged so instructions still match the product. If a phrase sounds natural in one language but exaggerated in the other, revise it locally while preserving its meaning. The Arabic content quality guide gives a fuller review method.

Use a pass-or-revise calibration check

Before treating the setup as ready, inspect 3 short drafts that address different buying questions about the same offer. These are review samples, not a statistically meaningful performance test. Apply the same criteria to each:

• The reader can identify the subject and relevant problem without decoding generic language.
• Every factual promise remains within the supplied evidence and service scope.
• The tone follows the reference without copying its sentences mechanically.
• The next step is specific, available and appropriate to the reader's stage.
• The language is natural and any bilingual counterpart preserves the same conditions.

For each failed criterion, record the cause. An invented result requires a factual correction. An exaggerated adjective may require a wording edit. A repeated mismatch across drafts may justify changing the objective, personality or Node context. Recheck the affected decision after making one change, so you can understand what improved.

Human review remains part of the process. Forge's Terms of Service make the business user responsible for accuracy and review. A completed voice exercise is not a reason to approve sensitive or unfamiliar claims automatically.

Save the decisions that another reviewer needs

Finish with an approved reference, accurate Node inputs and a brief note explaining the objective, personality and length choices. Identify who may change the reference when the offer develops. For ongoing control across people and channels, continue with Forge Brand Voice Consistency. To create fresh angles within the agreed voice, use the Content Ideas Engine lesson, then follow the Publishing Workflow lesson for release checks.

Open Forge and calibrate one offer against your reference. If the team needs help translating its positioning into usable settings and review decisions, request a demo focused on brand voice. The platform overview explains how this setup connects to the wider marketing workflow.