Vayasya

Brand Handbook

A compliance-first field manual for how Vayasya should be introduced, written, shown, and represented across everyday work.

Open visual reference

Quick entry

Version

v4.1.0

Effective

30 Mar 2026

Audience

Field teams first, specialists on demand

Overview0%

Chapter Gateway

Foundation

Start with identity, service scope, naming, and the daily behavior standards that shape representation.

Handbook Section

Overview

Start here for the fastest correct answer by role, task, and channel.

Use This When

You need a correct answer in under a minute.

Do This

Pick your role or task first, then use the linked checklist or full section only if needed.

Never Do This

Do not improvise wording, promises, service scope, or asset usage from memory.

Who Needs This

All employees, with first priority for field/site and client-facing teams.

This handbook is the operating reference for how Vayasya should be introduced, described, written, shown, and represented in daily work. Use it to answer real work questions quickly, then move deeper only when the task needs it.

Who this is for

Primary audience: field/site teams, supervisors, sales/account staff, HR/admin, leadership, and any employee speaking, writing, or sharing something client-facing.

If You Only Remember 5 Things

Use approved words, scripts, and assets. Do not invent your own version.

If you cannot prove a claim, remove it or downgrade it.

State owner, timing, and next action in every external update.

Use the correct brand or vertical name before you shorten anything.

If a message could create legal, commercial, or client confusion, escalate before sending.

By role

Site supervisor

Must know

How to introduce Vayasya on a site visit
Uniform and ID expectations
How to report delay, risk, or dependency factually

Top tasks

Client visit introduction
WhatsApp status update
Site closeout summary

Common mistakes

Speaking beyond approved scope
Giving verbal guarantees
Sharing casual updates with no owner or date

Escalate when: The client asks for commitments, pricing, legal/compliance promises, or a service outside the approved scope.

Field staff

Must know

How to identify yourself correctly
When to use WhatsApp versus escalation
What not to say about capability or timelines

Top tasks

Daily status note
Delay update
Client-facing introduction

Common mistakes

Using unapproved shorthand for the company
Overpromising on someone else's behalf
Sharing incomplete updates

Escalate when: A client asks for a decision, a commitment date, or a capability explanation you do not own.

Sales / account

Must know

Approved company description and service map
Quotation and proposal cover-note rules
Claims and evidence boundaries

Top tasks

Capability introduction
Quotation sharing note
Proposal and deck review

Common mistakes

Using broad leadership or guarantee language
Mixing verticals without clear ownership
Describing services more narrowly or more broadly than the public site

Escalate when: Measured claims, contractual wording, joint-offering material, or any exception to the standard service description is needed.

HR / admin

Must know

Approved company intro for candidates and vendors
Signature, bio, and profile copy rules
How to route non-standard asks

Top tasks

Recruiter explanation
Profile or signature setup
Routine external communication

Common mistakes

Describing Vayasya as a staffing marketplace or job portal
Using outdated bios or signatures
Adapting templates silently

Escalate when: New public-facing copy, new templates, or any claim about scale, compliance, or service performance is requested.

Handbook Section

Identity

The approved company description, service map, operating model, and scope boundaries.

Use This When

You need to explain what Vayasya is, what we do, or what we should be called.

Do This

Use the approved intro, service map, and scope boundaries exactly as written.

Never Do This

Do not describe Vayasya as a staffing marketplace, a job portal, or a generalist company that does everything.

Who Needs This

Field/site teams, sales/account, HR/admin, leadership, recruiters, and anyone client-facing.

Vayasya should be described as a compliance-first industrial services company with defined operating services, clear ownership, and disciplined delivery. This section is the source of truth for how the company is introduced and scoped.

Short intro

Vayasya supports industrial and operational environments with compliance-first services across workforce deployment, housekeeping, warehouses and logistics, civil and fabrication works, maintenance, and equipment or material support.

Approved paragraph

Vayasya is a compliance-first industrial services company serving operational environments that need dependable execution, clear ownership, and disciplined controls. We support workforce deployment, housekeeping, warehouses and logistics, civil and fabrication works, machinery maintenance, and equipment or material support through a structured operating model from intake to compliance closure.

Recruiter version: Vayasya is not a job marketplace or staffing app. We run structured industrial service operations for client environments with strong compliance, supervision, and delivery controls.

Compliance-first and audit-aware

Industrial and operations-grounded

Clear on scope, ownership, and timelines

Professional, disciplined, and non-dramatic

Service map

Workforce deployment

Deployment and management support for workforce requirements in operational environments.

Scope boundary

Do not describe this as a job marketplace, hiring app, or open-ended recruitment service.

Housekeeping

Managed housekeeping support for industrial and operational facilities with defined supervision and service controls.

Scope boundary

Keep the language operational and managed-service focused, not lifestyle or hospitality-focused.

Warehouses and logistics

Operational support for warehouse and logistics environments where process reliability and compliance matter.

Scope boundary

Do not imply a national logistics network or software platform capability unless it is specifically approved.

Civil and fabrication works

Defined civil and fabrication support for client operating environments with controlled scope and supervision.

Scope boundary

Do not generalize this into unlimited turnkey construction capability.

Machinery maintenance

Maintenance support for machinery and operational equipment within approved service boundaries.

Scope boundary

Do not use OEM, fail-proof, or zero-downtime language without specific evidence and approval.

Equipment and material support

Support for equipment or material-related operational needs where the scope, owner, and delivery method are defined.

Scope boundary

Do not broaden this into open-ended procurement or supply-chain capability.

Operating model

Intake

Clarify requirement, site context, ownership, and scope before committing language or timelines.

Scope definition

Document what is included, what is excluded, and what depends on client input or approval.

Execution setup

Assign owners, checkpoints, and operating controls before active delivery begins.

Service delivery

Run the work with visible status, dated updates, and disciplined escalation.

Compliance closure

Close the loop with documentation, follow-through, and evidence where required.

Scope boundaries

Not a staffing marketplace or consumer job portal.
Not a lifestyle, wellness, or inspiration-led brand.
Not a vague general contractor for every possible business need.
Do not say we do everything for every industry.
Do not promise outcomes, dates, or compliance states that have not been confirmed.

Rules

Describe the company using approved service categories, not improvised umbrella labels.

Lead with operating clarity, compliance, and scope control rather than hype or abstraction.

If a client asks about a service beyond the approved map, state that the scope must be confirmed first.

Use one approved intro for the situation instead of writing a fresh one every time.

Keep service breadth aligned with the public site and current approved capability.

Handbook Section

Brand Architecture

Choose the right brand name and vertical before you write, share, or present anything.

Use this section as a naming choice guide. Pick the right brand owner first, then apply the approved name consistently through the rest of the material.

Say Vayasya

Use the master brand for group-level communication, shared governance, or any material where no single vertical clearly owns the message.

Say a vertical

Use the full vertical name only when that vertical clearly owns the work, service, or communication context.

Joint offering

State it as joint only when both vertical owners have approved that framing.

Abbreviations

Do not abbreviate vertical names in formal or client-facing communication.

Rules

Use the full name on first mention: Vayasya or Vayasya <Vertical>.

Do not shorten to initials or invented shorthand.

Choose one clear brand owner for each document, deck, or message.

If ownership is unclear, default to Vayasya until the scope is confirmed.

Handbook Section

Operating Pillars

Daily behavior standards for handoff quality, escalation, compliance, and client interaction.

The pillars are daily operating behaviors. They matter most when work is under pressure, when something changes, or when the client needs a clear answer.

Clarity

Every update should make the current situation understandable without a follow-up call.

Behaviors

Name the owner, status, next step, and timing in every update.
State what is included and what is not included before work starts.
Use plain language when handing off tasks across shifts or teams.

Red flags

Update has no owner or date.
Scope is implied instead of written.
People leave a meeting with different interpretations.

Reliability

Commitments should be realistic, visible, and tracked until closed.

Behaviors

Commit only to dates and actions you own or that have been confirmed.
Raise risk before the deadline is missed, not after.
Close the loop with the client or internal owner once the action is complete.

Red flags

Repeated status updates with no movement.
Surprise delay messaging.
Verbal promises with no written follow-through.

Accountability

Decisions, changes, and exceptions should always have a named owner.

Behaviors

Record who approved the decision and what changed.
Escalate when a request moves beyond your authority or approved scope.
Own the message even when the news is negative.

Red flags

Everyone references 'the team' but no person is named.
Scope changes are discussed but not recorded.
People assume prior approval still applies after wording changes.

Respect

Professional discipline should show in tone, appearance, and client handling.

Behaviors

Use factual, calm language in delays or disagreements.
Show up with approved identity, appearance, and purpose on site visits.
Respect the client's time by making every meeting or update action-ready.

Red flags

Blame-focused or emotional language.
Casual or unclear site introductions.
Long updates that hide the actual decision or request.

Rules

If an update does not tell the receiver what changed, what to do, and by when, it is not ready.

If a date or promise is not confirmed, label it as pending or target-based.

If you are not the owner, do not make the commitment on behalf of someone else.

If the interaction is client-facing, the pillar test applies before the pre-share test.

Chapter Gateway

Visual System

Use approved assets and defaults on the root handbook. Open the deeper visual reference only for specialist work.

Handbook Section

Logo Usage

For most employees: use the approved logo pack as-is and do not edit it.

Most people only need to grab the right pack, choose the right background variant, and avoid the common failures.

Download approved logo packs

Logo Source PackZIP / SVG Logo PNG PackZIP / PNG Complete Media KitZIP / FULL KIT

Choose the right logo

Master on light background

Use on most documents, slides, templates, and light digital surfaces.

Switch variants only for contrast, not personal preference.

Master on dark background

Use on dark hero areas, dark UI surfaces, and approved dark-background placements.

Do not place the light-background logo on dark surfaces just to match a layout mood.

Vertical logos live in the pack

Use only when one vertical clearly owns the material, service, or release context.

Never type, abbreviate, or rebuild a vertical lockup manually.

Specialist reference

For Marketing, design, product, and engineering teams. Use the root handbook for the safe default, then open the deeper reference only when you need production or implementation detail.

Open full logo usage reference

Handbook Section

Color Palette

Use neutrals for most of the surface, one owner accent for ownership, and semantic colors only for meaning.

Most people only need three color rules: neutrals carry readability, one owner accent carries brand ownership, and semantic colors carry operational meaning.

Fast default

If you are not designing from scratch, stay inside approved templates and exported assets.
Use one clear brand owner per artifact. Do not mix vertical accents to make a routine piece feel richer.
Treat semantic colors as states and alerts, not decoration.

Choose the right palette lane

Foundation neutrals

Default lane

Most of the artifact should live in neutrals so reading, spacing, and hierarchy stay calm and legible.

One owner accent

Ownership only

500

600

Use gold for master-brand ownership or one vertical family when a specific vertical clearly owns the piece.

Semantic meaning colors

States and alerts

SuccessInfoWarningDangerPending

Use semantic colors only when the color itself is carrying a real status or alert meaning.

Specialist reference

For Design, product, and engineering teams. Use the root handbook for the safe default, then open the deeper reference only when you need production or implementation detail.

Open full color reference

Handbook Section

Typography

Use the right type role quickly: Anek for headings, Hind for reading and UI, JetBrains Mono for data.

Most people only need to choose the right family role, use the approved pack, and avoid the few failures that make typography look improvised.

Download the approved font pack

Vayasya Font PackZIP

Pick the right type role

Anek

Compliance-first industrial services

Page titles, hero headings, deck headlines, and other high-emphasis display moments.

Do not use Anek for long reading paragraphs or dense UI text.

Hind

Use Hind for the sentences people actually need to read, from emails and proposals to UI labels and helper text.

Body copy, labels, UI text, summaries, email-like content, and long-form reading.

Do not switch away from Hind locally just because a file or tool is rendering badly.

JetBrains Mono

WO-1842 24 technicians 09:30 IST PPE ok

Operational data, reports, IDs, table values, and code-like precision fields.

Keep mono out of narrative paragraphs and normal body copy.

Specialist reference

For Design, product, and engineering teams. Use the root handbook for the safe default, then open the deeper reference only when you need production or implementation detail.

Open full typography reference

Handbook Section

Imagery

Use imagery only when it adds proof, context, or operational meaning.

Imagery should support understanding of service environments, outcomes, and processes. Avoid abstract visuals that do not add operational meaning.

Employee-safe default

If the image does not prove or explain something, leave it out.
If the image contains client-sensitive information, mask it or do not use it.

Critical imagery rules

Prefer real operational scenes, interfaces, or context-rich photography.

Use images with clear rights and documented source attribution.

Avoid stereotypes and exaggerated success imagery.

When showing people, ensure role relevance and consent status.

Keep overlays minimal to preserve clarity.

Specialist reference

For Design, marketing, and content approval teams. Use the root handbook for the safe default, then open the deeper reference only when you need production or implementation detail.

Open full imagery reference

III

Chapter Gateway

Communication

Use approved scripts, claim discipline, and short-form channel patterns for everyday communication.

Handbook Section

Voice & Tone

Use calm, specific, and professional wording that works in real client and site situations.

Use This When

You are speaking, messaging, or writing on behalf of Vayasya and need safe wording quickly.

Do This

Lead with facts, owner, next action, and timing. Use the approved scripts before you improvise.

Never Do This

Do not use hype, blame, emotional wording, or casual guarantees.

Who Needs This

Field/site teams, supervisors, sales/account, HR/admin, leadership, and anyone client-facing.

Vayasya should sound calm under pressure, specific about facts, and disciplined about ownership. Use the scripts below as the default operating language for common situations.

Voice rules

Lead with facts before interpretation.

Name the owner and next action whenever the message is operational.

Keep blame, emotion, and comparison language out of routine updates.

If the right answer depends on approval, say so directly.

High-frequency scripts

Client or site intro

Phone / in person

Approved script

Hello, this is <name> from Vayasya <vertical or team if relevant>. I am here regarding <topic>. My role today is <purpose>, and I will close with the agreed next action.

State your name, company, and purpose in the first sentence.
Mention only the relevant approved service or visit purpose.
End the interaction with one clear next step or owner.

Escalate when: The conversation expands into pricing, contract terms, new scope, or capability beyond the approved service map.

Delay update

Email / WhatsApp / call

Approved script

Current status is amber. <What changed>. Impact: <specific delay or risk>. Owner: <name>. Next action: <specific action> by <date/time>.

Acknowledge the issue early.
State impact and owner in the same message.
Use one apology at most, then move to resolution.

Escalate when: The delay affects cost, scope, contract terms, or client trust beyond routine operations.

Capability explanation

Call / meeting / message

Approved script

For this requirement, the relevant Vayasya services are <approved services>. In this context, we do not confirm anything beyond the approved scope until the requirement and owner are reviewed.

Start with relevant approved services only.
State the out-of-scope boundary cleanly.
Do not use leadership or guarantee claims to sound confident.

Escalate when: A new service line, public statement, or comparative claim is being introduced.

Recruiter explanation

Phone / message / in person

Approved script

Vayasya is a compliance-first industrial services company. We support operational environments through approved services such as workforce deployment, housekeeping, warehouses and logistics, civil and fabrication works, maintenance, and equipment or material support.

Do not describe Vayasya as a marketplace or job app.
Keep the description industrial and operational.
Avoid unapproved scale or growth claims.

Escalate when: A recruiter or HR user needs new public copy or candidate-facing claims about scale, performance, or expansion.

Terminology to prefer

Replace

Guaranteed

Use: Targeted / committed if contractually stated

Avoid: Guaranteed, Assured, Promised

Use only when there is contractual basis and approved wording.

Replace

Best / leading / unmatched

Use: Structured / dependable / compliance-first

Avoid: Best-in-class, Industry-leading, Unmatched

Comparative claims require measured evidence.

Replace

ASAP / soon

Use: By <date/time> / next update at <time>

Avoid: ASAP, Soon, Shortly

Specific timing is stronger than vague urgency.

Handbook Section

Claims Discipline

Use the claim ladder before you say anything about services, timelines, performance, or guarantees.

Most claim risk comes from casual language, not bad intent. Use this section to decide what you can safely say, what you must soften, and when the answer is to remove the claim entirely.

Can I say this?

1Can we prove this right now with current evidence? If no, remove it or downgrade it.
2Is this about what we intend, what we are working toward, what we measured, or what the contract says?
3Does this create a legal, commercial, or expectation risk if repeated by the receiver?
4If the wording changes scope or promise level, does it need approval before release?

aspirational

Allowed: We aim to... / Our intent is... / We are building toward...

Evidence: Leadership-approved direction or current plan.

Avoid: We already do this / This is guaranteed / This will definitely happen.

Review trigger: Public or client-facing use outside routine internal planning.

directional

Allowed: We are working toward... / We are currently strengthening...

Evidence: Active initiative with owner and current status.

Avoid: Delivered capability described as already complete when it is still in progress.

Review trigger: Decks, proposals, leadership notes, or client-facing updates.

measured

Allowed: Based on <period> and <sample>, <metric> moved from X to Y.

Evidence: Current data source, method, time range, and owner.

Avoid: Much faster / significantly better / best without numbers.

Review trigger: Any performance or comparison claim.

contractual

Allowed: As stated in the signed contract / clause <x>...

Evidence: Executed contract wording or approved legal reference.

Avoid: Promise language that is not tied to signed terms.

Review trigger: Quotations, proposals, contracts, or legal/commercial communication.

Safe wording patterns

Use: based on current approved scope.

Use: target date, subject to required approvals or dependencies.

Use: as defined in the signed agreement.

Use: based on data from <date range>.

Avoid: guaranteed, zero-risk, fail-proof, immediate.

Avoid: best, leading, unmatched, superior.

Field examples

Deployment start date

Safer

We are targeting deployment on 22 Mar 2026, subject to final client approval and document readiness.

Unsafe

Deployment will definitely start on 22 Mar 2026.

Compliance statement

Safer

We operate with compliance-first controls and can confirm the exact requirement set for this scope.

Unsafe

Everything is fully compliant in every case.

Maintenance capability

Safer

We can review maintenance support for this requirement within approved scope.

Unsafe

We handle all maintenance needs end to end.

Fast claim checks

If you cannot prove it, remove it or soften it.

If a date is still dependent on someone else's input, label it as a target.

If a sentence sounds stronger after a last-minute edit, re-review the claim class.

When in doubt, use the approved service description instead of improvising capability language.

Handbook Section

Writing & Messaging

Channel rules for fast, clear updates across WhatsApp, quotation notes, and profile copy.

Use This When

You need a short written update and want to know the right channel and pattern quickly.

Do This

Keep every message clear on status, owner, request, and timing for the channel you are using.

Never Do This

Do not write vague updates that hide the real action or use public-profile copy from memory.

Who Needs This

Field/site teams, supervisors, HR/admin, sales/account, and any employee writing externally.

Most employee writing is short-form, not long-form. This section gives safe patterns for the channels people actually use during the day.

WhatsApp update

Approved script

Status: <green/amber/red>. What changed: <fact>. Required action: <specific ask>. Owner: <name>. Next update: <date/time>.

Use WhatsApp for short operational updates, not for new commercial commitments.
If the issue affects scope, contract, or pricing, move it to email or escalation.
Do not send long paragraphs when a short status block will do.

Escalate when: The message needs legal/commercial wording, a new commitment, or explanation beyond current scope.

Quotation cover note

Email / document note

Approved script

Please find the quotation for <scope>. This version covers <included items>. Assumptions: <list or reference>. Owner for follow-up: <name>. Next step requested: <specific action/date>.

State the scope before the amount or attachment details.
Call out assumptions instead of hiding them inside the attachment.
Do not add capability or promise language that is not in the quotation.

Escalate when: The quotation introduces new commercial terms, performance claims, or unapproved service descriptions.

LinkedIn or public-profile line

LinkedIn / profile

Approved script

Working with Vayasya on compliance-first industrial service operations across approved service areas.

Keep the wording professional and generic enough to stay accurate.
Do not publish confidential client, scale, or performance claims in a personal profile.
Use approved company description, not a creative rewrite.

Escalate when: A public post or profile needs new official company language or measured claims.

Rules

Choose the channel based on risk: short ops updates can be short; commercial and legal messages need formal channels.

Keep paragraphs short and purpose-led.

Use bullet structure for assumptions, exclusions, and requests whenever possible.

Chapter Gateway

Application

Use these rules for quotations, proposals, decks, email, calls, site visits, and final release checks.

Handbook Section

Proposals, Quotations & Documents

Use scope-first document structure for proposals, quotations, shared notes, and formal documents.

Documents should help the receiver understand what is being offered, what is excluded, and what decision or action is needed next. Most document failure comes from hidden assumptions and loose scope wording.

Rules

Start with purpose, scope, owner, and date.

Put assumptions and exclusions in a visible section, not buried at the end.

If the document is commercial, keep claims discipline and contract language aligned with the approved source.

Use the same service description in the cover note and in the attached document.

Close every shared document with one clear next action.

Templates

Quotation cover structure

Standardize the short note that accompanies quotations and commercial attachments.

When to use

Any quotation or commercial attachment shared externally.

Document: <quotation/proposal>
Scope: <approved scope>
Includes: <top items>
Assumptions: <list or reference>
Owner: <name>
Required action: <review/approve/respond>
Next checkpoint: <date/time>

Guardrails

Do not add new commitments in the cover note.
If assumptions are important, surface them clearly before send.

Handbook Section

Presentations

Use decks to explain approved scope, evidence, and decisions without adding new promises.

Presentation quality matters because decks are often forwarded without the presenter. Each slide should still read safely and correctly when seen out of context.

Rules

Use one specific message per slide.

When describing services, match the approved service map and current scope language.

Use measured or directional claims only when evidence is ready and current.

If the slide asks for a decision, state the owner and date on the slide.

End with the next action, not a generic thank-you slide only.

Handbook Section

Email

Use email when the message needs formal record, fuller context, or approval-safe wording.

Use email when the receiver needs formal context, clear dependency handling, and a durable record. If the message is a simple operational ping, use the short-form channel rules instead.

Situation

Quick operational status with no scope or legal risk

Use: WhatsApp or internal chat

Avoid: Long formal email thread

Situation

Quotation, approval, scope clarification, or dependency note

Use: Email

Avoid: WhatsApp-only handling

Situation

Call-based discussion with real decisions

Use: Call, then confirm by email

Avoid: Verbal closure with no written record

Rules

Use a subject line that tells the receiver the action and timeline.

State current status and required response in the first two lines.

List dependencies and consequences if they affect timing or scope.

If a call changed the decision, confirm the outcome in writing.

Close with owner, next checkpoint, and the best reply route.

Templates

Client update email

Give formal client email one consistent structure.

When to use

Milestone updates, dependency notes, commercial follow-up, and escalations.

Subject: <action> by <DD MMM YYYY> - <topic>
Hello <name>,
Current status: <green/amber/red and one-line summary>.
Required action: <specific ask and due date>.
Impact if delayed: <specific effect>.
Owner: <name>.
Next checkpoint: <DD MMM YYYY, HH:MM IST>.
Regards,
<name and role>

Guardrails

Do not hide the required action below the fold.
If the message changes commitment level, re-check the claim wording before send.

Handbook Section

Meetings, Calls & Site Visits

Run meetings and site interactions with clear purpose, approved identity, and action-ready closeout.

Use This When

You are going into a meeting, call, or site visit and need to know how to represent Vayasya correctly.

Do This

Open with role and purpose, stay inside approved scope, and end with one clear next step.

Never Do This

Do not arrive casually, speak beyond your authority, or leave without a recorded outcome.

Who Needs This

Field/site teams, supervisors, sales/account, leadership, and client-facing staff.

The brand shows up most visibly in live interaction. Meetings and site visits should feel prepared, disciplined, and easy to trust.

Site visit behavior

Carry the correct ID and use approved uniform or appearance guidance for the context.
Introduce yourself with name, company, role, and purpose within the first interaction.
Use only the approved service description relevant to the visit.
Do not treat site observations as approved commitments until the owner confirms them.
Close every visit with the next step, owner, and timing.

Call handling

Start calls with identity and purpose, not small talk that delays the point.
If a decision is made verbally, confirm it in writing after the call.
If the conversation becomes commercial, contractual, or out-of-scope, move to the correct owner.

Rules

Share agenda or purpose in advance when the interaction is planned.

Use one owner per action item.

Keep meeting and visit notes factual; do not record speculation as decision.

Escalate unclear commitments before they become assumed commitments.

Templates

Site visit closeout note

Turn live interaction into a usable record.

When to use

After site visits, review meetings, and important client calls.

Visit / meeting: <name>
Date and time: <DD MMM YYYY, HH:MM IST>
Purpose: <why we met>
Key observations: <facts>
Agreed next step: <action>
Owner: <name>
Checkpoint: <date/time>

Guardrails

Do not turn observations into commitments without owner confirmation.
Send the note on the same day when the interaction affects delivery.

Handbook Section

Pre-Send / Pre-Say / Pre-Share

Run the same final gate before you send, say, or share anything that represents Vayasya.

Use This When

You are about to send a message, speak in a client setting, share a document, or post public-facing copy.

Do This

Check identity, scope, claim safety, owner, and next step before release.

Never Do This

Do not assume a casual channel removes brand or claim risk.

Who Needs This

All employees, especially field/site and client-facing teams.

This is the final quality gate for email, WhatsApp, quotations, decks, site-visit notes, and public-profile copy. If the item fails the gate, fix it before release.

Identity and scope

Correct company or vertical name is used.
Service description matches approved scope.
No informal shorthand creates confusion about ownership.

Pass condition

The receiver will understand exactly who we are and what this item covers.

Claims and safety

Any capability, timeline, or performance claim is supported or clearly qualified.
No guarantee or comparative language appears without approval.
If approval is required, it is already recorded.

Pass condition

No sentence creates a stronger promise than we can prove or own.

Actionability

Owner is named.
Required action is clear or intentionally marked as none.
Next checkpoint, reply route, or next step is stated.

Pass condition

The receiver can act correctly without asking what happens next.

Channel fit

The chosen channel is appropriate for the risk level.
Verbal decisions are confirmed in writing if needed.
Attachments, assets, or scripts are the approved versions.

Pass condition

The item is being shared in the right format and channel for the situation.

Rules

This gate applies to messages, spoken representations, shared files, and public-profile copy.

If the item fails one check, fix it before release rather than adding a verbal caveat later.

If the item mixes scope, legal, or commercial risk with urgency, escalate instead of rushing it out.

Chapter Gateway

Appendix

Use this area for approvals, self-serve assets, and searchable real-world scenarios.

Handbook Section

Governance & Approvals

Governance is for exceptions, risky claims, and public-facing changes, not for routine approved assets.

The default mode is self-serve for standard assets, approved copy blocks, and routine usage. Governance is only for exceptions, public-risk language, new templates, or non-standard brand decisions.

Approval needed only when...

Measured or contractual claims are being added or strengthened.
New public-facing company or service copy is being created.
A new template, asset variant, or structural template change is being introduced.
Joint-offering material involving multiple verticals is being published.
Legal, commercial, or scope wording changes the meaning of the item.

Self-serve allowed

Using approved signatures, logos, bios, and copy blocks exactly as supplied.
Using the approved representation pack with no structural changes.
Routine logo, font, and signature usage inside approved templates.

Rules

If the wording becomes stronger, broader, or more public, re-check approval need.

If you edit an approved template structurally, it is no longer routine usage.

If legal or commercial meaning changes, prior approval no longer covers it.

Handbook Section

Representation Pack & Assets

Use self-serve approved assets and copy blocks for everyday representation work.

This section replaces a controlled-access mindset for routine assets. Standard representation materials should be easy to use without waiting for approval each time.

Approved email signature

self-serve

Use the standard company signature block with approved logo, role title, and contact format.

Audience: All employees

When to use: Any official company email account.

Short company intro

self-serve

Vayasya is a compliance-first industrial services company supporting approved operational service areas with clear ownership and disciplined execution.

Audience: Field/site, sales/account, HR/admin

When to use: Introductions, profile text, quotation notes, and first-contact communication.

Vertical descriptions

self-serve

Use the approved one-line vertical descriptions only when the context is clearly vertical-specific.

Audience: Sales/account, leadership, HR/admin

When to use: Decks, bios, capability notes, and role-specific communication.

Phone and site scripts

self-serve

Use approved intro, closeout, and delay-update scripts from the handbook without rewriting them.

Audience: Field/site teams and supervisors

When to use: Calls, site visits, and live client interaction.

New public copy or custom asset

approval-required

Anything outside the approved pack requires governance review.

Audience: Owners and reviewers

When to use: Public copy changes, new templates, new logo variants, or high-risk claims.

Rules

Routine approved assets are self-serve by default.

If you edit an approved template structurally, route it through governance before reuse.

Do not create alternate bios, signatures, or intro paragraphs when an approved one already exists.

Handbook Section

Common Scenarios & Edge Cases

Plain-language answers for the real questions employees ask during the workday.

This index is written for browser-find and quick lookup. Use the tags exactly as an employee would search for them during real work.

WhatsApp: can I send a client update on WhatsApp?

Yes for short operational updates with status, owner, and next checkpoint. No for new commitments, pricing, legal wording, or anything that changes scope.

whatsappclient updatemessage

Phone: how should I open a client call?

State your name, company, role or team, and purpose in the first sentence. Keep the call scope-specific and move risky commitments to the right owner.

phonecallintro

Quotation: what should the cover note say?

State the scope, key assumptions, owner, and next action. Do not add new promises or broaden the approved service description in the note.

quotationproposalcover note

Site visit: what should I say when I arrive?

Introduce yourself with name, company, role, and visit purpose. Close the visit with the next step, owner, and timing.

site visitarrivalintro

Uniform / ID card: when do these matter for brand representation?

Whenever you are in a client-facing visit or on-site context. Use approved identity and appearance guidance so the company presentation is professional and consistent.

uniformid cardappearance

Recruiter: how do I describe Vayasya to candidates?

Describe Vayasya as a compliance-first industrial services company, not a staffing marketplace or job portal.

recruitercandidatehr

Supervisor: can I confirm a date on behalf of another owner?

No. You can communicate the current target and dependency status, but confirmed commitments should come from the owner or approved plan.

supervisordatecommitment

LinkedIn / social: can I write my own company description?

Use the approved short company intro and keep it general. Do not publish unapproved scale, performance, or service claims in personal profiles.

linkedinsocialprofile

Client visit: what if the client asks for an adjacent service?

State what is in scope for the current discussion and say the wider requirement will be reviewed before confirmation.

client visitscopeadjacent service

Delay: what is the minimum acceptable update?

Current status, what changed, impact, owner, and next checkpoint. If cost, scope, or contract is affected, escalate.

delaystatusescalation

Version

v4.1.0

Effective

30 Mar 2026

Owner

Vayasya Brand Office

Contact

brand-office@vayasyaseva.com