BrightWeb and the Bright Horizons HEART Principles

Internal communication can shape a workplace just as strongly as formal policies.

A short message can make expectations clear or create confusion. A comment can help a coworker solve a problem or make the situation more difficult. An announcement can build trust or leave employees wondering what actually applies to them.

BrightWeb is part of that internal communication environment for Bright Horizons employees.

Because the portal is used for company information and internal interaction, the way employees communicate through it matters. Bright Horizons connects appropriate BrightWeb use with its HEART Principles, which are intended to reflect the organization’s culture and expectations.

Those principles are not limited to formal leadership statements.

They also apply to everyday choices:

  • How a message is written
  • How disagreement is expressed
  • How private information is handled
  • How coworkers are described
  • How concerns are raised
  • How internal information is shared

Professional communication is not only about avoiding inappropriate language. It is about making internal information useful, respectful, and trustworthy.


What the HEART Principles Represent

Bright Horizons uses the acronym HEART to describe several cultural principles:

  • Honesty
  • Excellence
  • Accountability
  • Respect
  • Teamwork

These principles can be understood as a practical standard for workplace behavior.

They influence not only how employees work with children, families, customers, and partners, but also how they communicate with one another internally.

On BrightWeb, the HEART Principles may apply whenever an employee:

  • Reads or responds to an internal message
  • Shares a company resource
  • Comments on a workplace issue
  • Asks for support
  • Corrects inaccurate information
  • Discusses a process
  • Posts content intended for coworkers
  • Communicates with a wider internal audience

Each principle offers a different way to evaluate whether a message belongs in a professional company environment.


Honesty: Share What You Know Without Inventing the Rest

Honesty in internal communication means being accurate about facts, uncertainty, and responsibility.

Employees should avoid presenting assumptions as confirmed information.

For example, there is a major difference between writing:

The schedule has changed for everyone.

and:

I heard there may be a schedule change, but I have not seen an official notice yet.

The second version is more honest because it clearly separates rumor from confirmed information.

Honesty may also mean saying:

  • “I do not know.”
  • “I need to verify this.”
  • “The information I shared earlier was incorrect.”
  • “This applies only to our location.”
  • “I missed the deadline.”
  • “I need help understanding the requirement.”

These statements can feel uncomfortable, but they are more useful than guessing or hiding a mistake.


Avoid Spreading Unconfirmed Information

Internal rumors can move quickly.

One employee hears part of a conversation, sends it to a coworker, and within hours several people believe an unofficial statement is company policy.

BrightWeb should not be used to give rumors the appearance of authority.

Before sharing an update, employees should consider:

  • Did this come from an official source?
  • Is the information current?
  • Does it apply to my location or role?
  • Am I repeating something I only heard informally?
  • Can I link or refer to the original internal notice?
  • Has the information already changed?

If the answer is unclear, the message should reflect that uncertainty.

A professional internal post should help people understand what is known, not make an uncertain situation sound final.


Correct Mistakes Directly

Honesty also matters after an error has already been made.

If an employee shares incorrect information, the best response is usually a clear correction.

A useful correction may say:

Correction: The deadline is Friday, not Thursday. I referenced an older notice in my previous message.

This is better than quietly deleting the original statement and hoping nobody noticed.

A direct correction gives coworkers the information they need and protects trust.

Mistakes happen.

The damage often comes from leaving inaccurate information uncorrected.


Excellence: Make Communication Useful

Excellence does not mean every BrightWeb message must sound formal or complicated.

It means the communication should be good enough to help the reader understand what matters and what to do next.

A useful message usually answers several basic questions:

  • What happened?
  • Who is affected?
  • What action is required?
  • When is it due?
  • Where can more information be found?
  • Who can answer questions?

A vague message such as:

Please take care of this soon.

creates more work because the reader must ask what “this” means and how soon “soon” is.

A clearer version might say:

Employees assigned to the upcoming training should review the updated instructions before Friday. Questions can be directed to the center leader.

The second message is not longer by much, but it gives the reader a usable path forward.


Clear Writing Is Better Than Corporate Language

Professional communication does not require complicated vocabulary.

In fact, overly formal language can make simple information harder to understand.

Employees should prefer:

  • Specific dates
  • Direct verbs
  • Short explanations
  • Clear responsibilities
  • Simple structure

Instead of:

Team members are encouraged to ensure timely completion of all applicable requirements.

A clearer message may say:

Complete the assigned form by July 24.

The goal is not to sound impressive.

The goal is to remove uncertainty.


Use Headings and Structure for Longer Updates

Long internal announcements are easier to follow when they are organized.

Useful headings might include:

  • Who This Applies To
  • What Is Changing
  • Required Action
  • Deadline
  • Questions
  • Additional Information

Employees should not bury an important deadline inside a large paragraph.

The more important the information, the easier it should be to find.

BrightWeb communication should respect the reader’s time.


Accountability: Own the Message and the Outcome

Accountability means taking responsibility for what you post, share, or communicate.

An employee should not assume that internal communication becomes someone else’s problem once the message is sent.

If a post creates confusion, the author may need to clarify it.

If a deadline changes, the original information should be updated.

If a coworker asks a reasonable question, the issue should not be ignored simply because the first announcement has already been published.

Accountable communication includes:

  • Checking facts before posting
  • Correcting mistakes
  • Following up
  • Responding to relevant questions
  • Explaining changes
  • Directing people to the correct owner
  • Removing outdated material when appropriate

Ownership continues after the message is published.


Do Not Blame People Publicly

Accountability does not mean publicly naming and embarrassing someone whenever something goes wrong.

A message such as:

This was delayed because Alex failed to complete the task.

may create more conflict than clarity.

A better internal update may focus on the current situation:

The document is delayed and is now expected tomorrow. The team is completing the remaining review.

Personal performance concerns should usually be handled through the appropriate private process.

Public internal communication should explain the operational impact without turning BrightWeb into a place for blame.


Admit When You Are the Source of the Delay

The opposite problem also occurs.

People may use vague language to hide their own responsibility.

For example:

There were some issues, so the update was not completed.

If the delay belongs to the author, a more accountable message may say:

I was unable to complete the review today. I will finish it by 10:00 a.m. tomorrow.

This is clearer and gives coworkers a realistic expectation.

Accountability builds credibility when people communicate honestly about their own commitments.


Respect: Write as Though the Person Will Read It

Respect is one of the most important standards for internal communication.

A useful test is simple:

Would you write the same message if the person being discussed were standing beside you?

Employees should avoid posts that include:

  • Mocking language
  • Personal insults
  • Sarcasm aimed at a coworker
  • Comments about appearance
  • Dismissive descriptions
  • Aggressive accusations
  • Humiliating details
  • Unnecessary criticism

Internal systems can create a false sense of distance.

A message typed quickly can still affect another person’s reputation, confidence, and relationship with the team.


Tone Can Change the Meaning

The same request can sound respectful or hostile depending on how it is written.

Compare:

Why is this still not done?

with:

I noticed this is still open. Is there anything preventing completion, and what is the updated timing?

The second version still addresses the problem.

It simply avoids beginning with an accusation.

Respect does not mean avoiding difficult questions. It means asking them in a way that supports resolution.


Disagreement Can Still Be Professional

Employees do not need to agree with every internal decision.

Professional disagreement may include:

  • Explaining the concern
  • Providing examples
  • Asking for clarification
  • Suggesting an alternative
  • Identifying potential consequences
  • Separating facts from personal preference

A respectful disagreement might say:

I am concerned that the new deadline may be difficult for center teams because the required materials have not yet arrived. Could the timeline be reviewed?

An unhelpful version might say:

This decision makes no sense and nobody thought it through.

Both express dissatisfaction.

Only one gives the organization something useful to respond to.


Respect the Intended Audience

Not every internal message should be sent to the widest possible group.

Employees should consider who actually needs the information.

Sending a local issue to a large company audience may create unnecessary concern.

A message should be directed to:

  • The affected team
  • The correct department
  • The responsible leader
  • The relevant location
  • The person who can act

Respect includes protecting other employees from irrelevant noise.

People are more likely to pay attention to important updates when they are not overwhelmed by messages that do not apply to them.


Teamwork: Communicate to Help the Group Move Forward

Teamwork in BrightWeb communication means sharing information in a way that supports collective work.

A helpful message does more than identify a problem.

It may also include:

  • What has already been tried
  • What help is needed
  • Who is involved
  • What decision remains open
  • What the next step should be

For example:

The supply request is still pending. I contacted the regional office this morning and expect an update by 3:00 p.m. No additional action is needed from center staff yet.

This prevents several people from repeating the same work.

Good internal communication gives the team a shared understanding of the situation.


Share Context, Not Just Instructions

Coworkers are more likely to support a request when they understand why it matters.

Instead of:

Use the new form immediately.

A stronger message may say:

Use the updated form beginning today because the previous version does not include the new required field.

The explanation is brief, but it helps employees understand the reason for the change.

Context supports better decisions when unusual situations arise.


Do Not Hide Useful Information in Private Messages

Some issues should remain private.

Other information becomes more useful when shared with the affected team.

If several employees are asking the same question, the answer may belong in a common internal space rather than being repeated individually.

Examples may include:

  • A corrected deadline
  • A clarified instruction
  • The location of an official resource
  • A confirmed process change
  • A common troubleshooting step

Teamwork includes recognizing when information can reduce confusion for everyone.


Protect Confidential Information

The HEART Principles should also influence how employees handle private information.

BrightWeb is an internal environment, but that does not mean every employee should see every detail.

Employees should be cautious about sharing:

  • Information about children
  • Family details
  • Employee medical information
  • Private performance concerns
  • Personal contact information
  • Sensitive incident details
  • Confidential business material
  • Information restricted to leadership or a specific team

Internal does not mean unrestricted.

Before posting, employees should ask:

  • Does the audience need this information?
  • Can the issue be discussed without personal details?
  • Should this be sent privately?
  • Is there a designated reporting process?
  • Am I sharing more than is necessary?

Privacy is part of respect and accountability.


Avoid Identifying Children or Families Unnecessarily

Bright Horizons employees work in environments where information about children and families must be treated carefully.

An internal question may sometimes be discussed without using a full name or detailed personal history.

Employees should avoid posting identifiable information simply because the portal is limited to company users.

The safer approach is to share only what the intended audience needs in order to act.

Detailed or sensitive situations should follow the appropriate internal reporting and communication process.

BrightWeb should not replace formal channels for confidential matters.


Screenshots Can Create Privacy Problems

Screenshots are easy to make and easy to share.

They can also capture more information than intended.

A screenshot may include:

  • Names
  • Email addresses
  • Internal navigation
  • Private messages
  • Identifying details
  • Information from another conversation
  • Company-only material

Before attaching or forwarding a screenshot, employees should check the entire image, not only the section they intended to show.

Cropping may reduce unnecessary exposure, but sensitive information should still be handled through approved processes.


BrightWeb Is Not a Personal Social Network

Employees may feel comfortable with coworkers, but BrightWeb remains a company environment.

Posts should not be treated like private social-media updates.

Content that may be inappropriate includes:

  • Personal disputes
  • Political arguments unrelated to work
  • Public criticism of individual coworkers
  • Offensive humor
  • Rumors
  • Harassment
  • Unapproved advertising
  • Personal fundraising outside company rules
  • Content unrelated to the intended internal purpose

Professional standards still apply even when the tone of the workplace is friendly.


Humor Requires Caution

Humor can build connection, but written jokes are easy to misunderstand.

A comment that sounds harmless in person may appear insulting or dismissive without facial expression or tone of voice.

Employees should avoid humor involving:

  • Personal characteristics
  • Children or families
  • Job performance
  • Cultural stereotypes
  • Sensitive workplace events
  • Medical issues
  • Private mistakes
  • Leadership decisions

The larger the audience, the greater the risk that the message will be interpreted differently than intended.


Read the Message Again Before Posting

A brief review can prevent many communication problems.

Before posting on BrightWeb, employees should check:

✅ Is the information accurate?

✅ Is the intended audience correct?

✅ Is the required action clear?

✅ Is the tone respectful?

✅ Have private details been removed?

✅ Does the message reflect the HEART Principles?

✅ Could this be misunderstood?

✅ Is BrightWeb the correct place for this topic?

✅ Does the message help the team move forward?

This check takes only a moment and can prevent a much longer correction later.


How to Raise a Concern Professionally

Employees sometimes need to raise serious concerns.

A useful internal concern should explain:

  1. What happened
  2. When it happened
  3. Who or what was affected
  4. What evidence is available
  5. What immediate risk exists
  6. What response is needed

The message should focus on observable facts.

For example:

The current instruction lists two different deadlines. The announcement says July 26, while the attached form says July 22. Can the correct date be confirmed?

This is more useful than:

Nobody knows what they are doing and the instructions are always wrong.

The first version identifies a specific problem that can be fixed.


Know When BrightWeb Is Not the Right Channel

Some topics require a private or formal reporting channel.

BrightWeb may not be appropriate for:

  • Immediate safety emergencies
  • Confidential employee complaints
  • Personal performance disputes
  • Sensitive child or family information
  • Medical information
  • Legal concerns
  • Detailed incident reports
  • Urgent issues requiring immediate action

Employees should use the company process designed for the situation.

Posting publicly inside an internal portal can make a sensitive issue harder to manage.


Common Questions About HEART Principles and BrightWeb

Do the HEART Principles apply to written messages?

Yes. Internal written communication should reflect honesty, excellence, accountability, respect, and teamwork.

Can employees disagree with an internal announcement?

Yes. Disagreement should remain factual, respectful, and focused on the issue rather than attacking individuals.

Should unconfirmed information be shared?

Employees should avoid presenting rumors or assumptions as official facts.

Is all information safe to share because BrightWeb is internal?

No. Confidential and personal information should still be limited to the people and channels that require it.

Can mistakes be corrected after posting?

Yes. Employees should correct inaccurate information clearly and promptly.

Is BrightWeb appropriate for a personal complaint about a coworker?

Usually not. Personal or performance-related concerns should follow the correct private process.


A HEART-Based BrightWeb Message

A strong internal message may reflect all five principles at once.

For example:

The updated classroom checklist takes effect on July 27. It applies to all teaching staff at our center. Please review the new section before your next scheduled shift. The previous version should no longer be used. I mistakenly shared the older file yesterday, and I apologize for the confusion. Questions can be sent to the center leadership team.

This message shows:

Honesty

The author acknowledges the earlier error.

Excellence

The date, audience, action, and document status are clear.

Accountability

The author takes responsibility for the correction.

Respect

The tone is professional and does not blame others.

Teamwork

The message helps everyone use the correct resource.

The HEART Principles become useful when they shape real communication like this.


Why the HEART Principles Matter on BrightWeb

BrightWeb is more than a place where internal information appears.

It is also part of how Bright Horizons employees experience the organization.

Every clear announcement reduces confusion.

Every accurate correction protects trust.

Every respectful disagreement makes it safer to raise a real concern.

Every careful privacy decision protects children, families, coworkers, and the company.

The HEART Principles provide a practical standard for these choices.

Honesty keeps information accurate.

Excellence makes communication useful.

Accountability ensures people own what they share.

Respect protects professional relationships.

Teamwork helps the organization move forward together.

When employees apply these principles consistently, BrightWeb becomes more than an internal page.

It becomes a communication environment people can trust.

Leave a Reply

Your email address will not be published. Required fields are marked *