Institutional Base is the canonical Ordering.co letterhead: a spacious white working field, one precise header route, and a thin graphite footer that keeps the document recognizable when printed, shared, or separated from a set.
01 / See it in use
The institutional base is the permanent template.
The letterhead is intentionally quiet until the footer. The top establishes identity and alignment; the graphite base creates a consistent institutional close without competing with the document itself.
Ordering.co letterhead · institutional base
The permanent first-page system for formal correspondence and operational documents.
Use the supplied full Ordering.co lockup at the upper left. Never reconstruct it with live type.
2
Structural route
A short action-blue segment leads into a quiet neutral rule and establishes the content grid.
3
Working field
The open white field protects readability and leaves room for letters, notices, and operational documents.
4
Institutional base
A thin graphite footer closes every page with the reversed lockup, full URL, and an unadorned page number.
02 / How it works
Every permanent element has one job.
Do not add furniture to make the page feel more branded. Recognition comes from the full lockup, the restrained route, the protected content field, and the consistent footer.
Identity + route
Header
Use the full color Ordering.co lockup on white. The short blue segment establishes focus and continues as a neutral one-pixel rule.
Content
Working field
Keep correspondence inside the established margins. White space is functional: it separates permanent identity from variable content.
Institutional close
Footer
Use the supplied reversed lockup at left, the complete www.ordering.co address at center, and a plain page number at right.
Consistency
Continuation pages
Repeat the same header and footer on every page. Page numbers advance; permanent brand elements do not move or change.
03 / Examples
Test the system with real document jobs.
The same template supports formal correspondence, operational coordination, and concise institutional notices. All names, dates, references, and statements below are illustrative and must be replaced before use.
Illustrative content · replace before use
Executive letter
Recipient, subject, correspondence, and signature.
Illustrative
Correspondence
Scope confirmation for the next stage
Date
13 August 2026
Reference
OD-2026-018
Addressed to
Recipient nameTitle · Organization · City, country
Hello, [name]:
Thank you for the working session. This document confirms the proposed scope for the next stage and organizes the decisions each team must validate before work begins.
The goal is to keep the commerce experience coherent while Product, Operations, and Technology move from the same definition. Ordering.co provides the connected foundation; your team retains the decisions about brand, experience, and commercial priorities.
Once the scope and owners are confirmed, the team can convert them into a working plan with visible dates and dependencies.
Name SurnameRole · Ordering.co
www.ordering.co01
Operational plan
Metadata, milestones, owners, and a precise progress criterion.
Illustrative
Project coordination
Activation plan and owners
Date
13 August 2026
Reference
OPS-2026-041
StagePreparation
Next milestoneJoint validation
CadenceWeekly review
Actions for the next review
01Confirm the channels, markets, and flows included in this stage.Owner · Customer
02Review technical dependencies, access, and acceptance criteria.Owner · Technology
03Document operational scenarios and assign a decision owner.Owner · Operations
04Consolidate open decisions before the next review.Owner · Project
Progress criterion
The stage changes status when scope, owners, and dependencies are confirmed by the corresponding teams.
www.ordering.co02
Institutional notice
A concise change, its effect, and the governed contact details.
Illustrative
Notice
Coordination channel update
Effective
1 September 2026
Reference
COM-2026-009
What changes
Requests related to this project will use one coordination channel so ownership and follow-up remain visible.
Hello, team:
Include the project reference, a short description, and the responsible person when submitting a new request.
Open topics keep their current follow-up. This change organizes the point of entry; it does not alter the agreed scope or each team’s responsibilities.
Channel
[Authorized channel or address]
Hours
[Applicable hours and time zone]
Required reference
Project name · request type
Contact
[Responsible name and function]
www.ordering.co03
04 / Use & avoid
Keep the template permanent and the content accountable.
The letterhead establishes identity; it does not approve the message inside it. Content still follows the applicable owner, claim, legal, and publication gates.
Use
Use the complete supplied template without moving, redrawing, or recoloring permanent elements.
Keep body copy inside the safe field and preserve generous white space above the footer.
Replace every illustrative name, date, reference, and placeholder before distribution.
Share the template only as part of a reviewed final document.
Avoid
Do not add another logo, tagline, campaign mark, or decorative brand-color strip.
Do not place body copy, signatures, tables, or legal text inside the graphite footer.
Do not use the archived blue-line alternative for new documents.
Do not treat sample content as approved customer copy, proof, or a service commitment.
05 / Technical reference
Use the governed templates and exporter.
Start from the current Word, PDF, or Google Docs template on this page. For repeatable documents, generate a letterhead PDF from Markdown with the repository-owned exporter and inspect the rendered result before distribution.
Generate a letterhead PDF from MarkdownUse a Markdown file from this repository or an Obsidian vault as the document source.+
1. Run the pre-flight check.python3 scripts/letterhead_pdf/generate.py --check path/to/document.md
2. Generate the PDF.python3 scripts/letterhead_pdf/generate.py path/to/document.md
3. Inspect every page.Check tables, page breaks, signatures, header alignment, footer clearance, and page numbering before distribution.
Portable source kit
The repository keeps the reusable Obsidian preprocessing and rendering logic under scripts/letterhead_pdf/. Its README and Markdown conventions document supported syntax, special markers, dependencies, and review boundaries.
Production specificationFixed geometry, print boundaries, and distribution rules.+
Format
US Letter · 8.5 × 11 in · portrait
Primary canvas
White
Header
Full color lockup + action-blue/neutral structural rule
Footer
Thin graphite band + reversed lockup + full URL + page number
Typography
Inter Variable for editable content
Production color
sRGB reference; convert per printer ICC profile for production
www.ordering.co01