Use When
- Use when supporting evidence needs to be assembled behind the main plan or proposal.
- Use when a bank, investor, DFI, or partner will expect documentary backup for the main claims.
- Use when the work needs an evidence matrix or data-room style appendix structure.
Do Not Use When
- Do not use as a dumping ground for unrelated material.
- Do not use before the main body claims are stable enough to map to evidence.
- Do not use appendices to hide core logic that should be visible in the main plan.
Required Inputs
- Completed or near-complete main sections
- All available supporting documents, exhibits, and datasets
- Audience type and likely due-diligence expectations
- The high-stakes claims, figures, and legal or financial assertions that need proof
Workflow
- Identify which main-plan claims require documentary support.
- Organise the evidence into logical appendix or data-room categories.
- Build the evidence matrix linking claims to proof.
- Standardise the naming, order, and purpose of each appendix item.
- Reconcile the appendix pack against the main document and the audience's DD expectations.
- Flag missing or weak evidence that still needs to be obtained.
Quality Bar
- Every material claim in the main plan can be traced to evidence or a labelled estimate.
- The appendix structure is easy for a lender or investor to navigate.
- Financial tables match the summary numbers exactly.
- Missing documents are visible rather than silently omitted.
Anti-Patterns
- Treating appendices as miscellaneous storage.
- Including documents with no clear link to the main decision case.
- Leaving unsupported claims unlabelled.
- Presenting appendix evidence that contradicts the main body.
Outputs
- Appendix structure or data-room map
- Evidence matrix
- Ordered appendix list with purpose and section reference
- A gap list of missing support documents
Generate a well-organised appendices section that provides the supporting evidence investors need without cluttering the main plan.
What to Generate
Standard Appendix Items
- Detailed financial tables - Monthly projections, detailed cost breakdowns
- Market research data - Survey results, industry reports, data tables
- Product specifications - Technical details, screenshots, prototypes
- Legal documents - Articles of incorporation, patents, licences, permits
- Team CVs/resumes - Full biographies of key team members
- Letters of intent / customer commitments - Evidence of demand
- Partnership agreements - Signed or draft agreements
- Lease/facility agreements - Property or equipment contracts
- Insurance documentation - Current or planned coverage
- Technical architecture - System diagrams if relevant
- Glossary - Industry-specific terms used in the plan
- References and citations - Sources for market data and claims
- Evidence matrix - Claim-to-proof table for critical assertions
- Data room index - Funder-specific list of available, pending, or missing diligence documents
Organisation Format
Each appendix item should be:
Appendix [Letter]: [Title]
Purpose: [Why this is included]
Reference: [Which plan section cites this]
Content: [The actual document or data]
Generation Process
- Review completed sections for claims needing proof
- List all referenced data, documents, and supporting materials
- Organise by category: financial, legal, market, team, technical, ESG
- Generate missing tables or summaries
- Build an evidence matrix for all high-stakes claims
- Create a table of contents for the appendices
Uganda Bank Loan Submission - Required Appendix Documents
| Appendix | Document | Template Available |
|---|---|---|
| A | Director / Guarantor CV | Yes - Template 1 |
| B | Personal Net Worth Statement | Yes - Template 2 |
| C | Loan Repayment Schedule | Yes - Template 3 |
| D | 3-Year Financial Summary | Yes - Template 4 |
| E | Character References | Yes - Template 5 |
| F | Supplier Reference Letters | Yes - Template 6 |
| G | URA Tax Compliance Certificate | Instructions - Template 7 |
| H | NSSF Compliance Certificate | Instructions - Template 8 |
| I | Business Registration Certificate / Certificate of Incorporation | Obtain from URSB |
| J | Land title / logbook / collateral documentation | Original documents |
| K | NEMA permit / UNBS certificate where relevant | Obtain from regulator |
Evidence Matrix Requirement
Create a one-page evidence matrix before finalising appendices:
| Claim / Figure | Main Plan Section | Appendix Proof | Status | Notes |
|---|---|---|---|---|
| [Example: Year 1 revenue] | 10 | Appendix B | Verified | ties to model |
| [Example: signed customer interest] | 07 | Appendix F | Pending | LOI expected |
Status options:
- Verified
- Partially evidenced
- Pending
- Management estimate
High-stakes claims should not remain unlabelled.
Data Room Architecture
Where the audience is an investor, DFI, or strategic partner, organise appendices like a simple data room:
- Corporate and legal
- Financial and tax
- Commercial and market proof
- Operations and technical
- Team and governance
- ESG / compliance
State what is available now, what is pending, and what still needs to be created.
Quality Criteria
- Every major claim in the plan has supporting evidence in the appendices
- Every high-stakes claim appears in the evidence matrix with a status
- Appendices are referenced from the main plan
- Financial appendices match summary figures exactly
- Legal documents are current and valid
- Organisation follows a logical structure with clear labelling
- For bank submissions: all CAMPARI document requirements are met
References
references/document-templates.md- Uganda-specific templates for director CVs, net worth statements, repayment schedules, and compliance certificates../meta-due-diligence/SKILL.md- use for investor and DFI data-room readiness../meta-consulting-synthesis/SKILL.md- use to identify the high-stakes claims that must appear in the evidence matrix