SOP: Collaboration Branding & Footer Standards

This SOP defines how Chenla Agathos Solutions presents its identity in collaborative documents and establishes the required footer structure for all formal, client-facing, and partner-facing materials.

To ensure consistent, professional, and technically aligned branding across all documents produced jointly with partner organizations or issued externally. This SOP creates a unified system for:

• Representing Chenla in collaborations
• Balancing partner identities
• Maintaining standard footer information
• Supporting version control and document clarity

This SOP applies to:

• Joint documents created with architectural, engineering, or consulting partners
• Client questionnaires, briefs, presentations, and reports
• Internal documents prepared for external review
• Any template or document that requires shared authorship presentation

Use a neutral, typographic collaboration mark when representing Chenla alongside another organization.

• Format: `PARTNER × CHENLA`
• Typeface: Monospace or technical sans
• Case: ALL CAPS
• Tracking: Slightly positive to enhance clarity
• Color: Black or dark grey

This mark may appear on cover pages, section dividers, or headers.

A micro-mark may be used in technical contexts or footers:

• `P × C` or similar abbreviation
• Center-aligned
• Monospace preferred

Full logos may be used only when:

• Required by formal submission standards
• Placed on cover pages or introductory sections
• Explicitly requested by the partner firm

When logos appear together:

• Scale to optical rather than literal equality
• Align along a shared baseline
• Increase delicate logos slightly
• Reduce visually heavy logos slightly
• Maintain ample negative space around both

Logos may not:

• Be recolored outside approved palettes
• Be placed in decorative frames or boxes
• Compete for dominance in the header
• Appear without sufficient clear space

Chenla uses a consistent technical footer format across all formal documents.

Left block:

• Revision number (e.g., “Rev 1.0 — 5 Dec 2025”)
• Document number (internal standard format)
• Optional: Confidentiality notice

Center:

• Micro-mark (e.g., `B × C`)

Right:

• Page number (e.g., “Page 2 / 3”)

• Rev 0.x = draft versions
• Rev 1.0 = first issued version
• Include revision date
• Increment revisions with meaningful document changes

Use standard Chenla internal numbering:

• Pattern: `CAS-{PartnerCode}-{DocumentType}-{Index}`
• Example: `CAS-BLOOM-DSR-001`

PartnerCode may be omitted for internal-only documents.

When required:

• Color: light green
• Tone: factual and understated
• Placement: left block of the footer
• Keep to a single line

Example: *Confidential — Internal planning only*

• Footer typeface: IBM Plex Sans or IBM Plex Mono
• Use Regular weight unless otherwise specified
• Avoid heavy or stylized typography

• Left block left-aligned
• Center mark optically centered (not grid-centered if logos shift layout)
• Page numbers right-aligned to the frame margin
• Maintain consistent vertical spacing across pages

• Maintain consistent footer height for all templates
• Ensure adequate breathing room between footer text and page border

• Start with the approved company template.
• Insert the collaboration mark or partner logos (per rules above).
• Apply the typographic hierarchy defined in Chenla branding standards.
• Insert revision number, document number, and micro-mark.
• Set the page number to auto-generate from the template system.
• Review for alignment and spacing consistency.
• Export as PDF for external sharing.

All collaborative documents must use:

• The standardized collaboration mark
• The required footer structure
• Approved typographic and alignment standards

Deviations require approval from the branding or document-control lead.

• Chenla Brand Identity Guidelines
• Document Branding Standards
• SOP: Document Formatting & Hierarchy