ALBUKHRExternal Project Builder Guide
NETWORK
PRACTICAL BUILDER GUIDE

External Project Builder Guidance

A practical preparation guide for project owners before creating and submitting an External Project application.

Version 1.0Practical Guide for Project OwnersApplies to External Projects submitted to ALBUKHR
ALBUKHRGUIDE
v1.0
✓
Best preparation principle: Prepare the evidence first. Submit the story second.
01

Prepare Before You Open the Form

Be ready to explain:

What the project is
Who owns or controls it
What problem it solves
Its current business stage
Exactly what funding will finance
What evidence supports the claims
Its principal risks
What happens if assumptions fail
02

State the Correct Business Stage

Use the real stage: concept, setup, pre-operation, operating, expansion or mature.

Operating businesses: Explain existing operations and why additional capital is needed.
03

Define the Funding Purpose

Identify whether funding is for startup/build, expansion, working capital, replacement, branch/product growth, restructuring or a mixed purpose.

04

Build an Itemized Funding Plan

Each material cost should identify description, quantity, unit, unit cost, total, purpose and supporting evidence where appropriate.

Do not inflate costs to manufacture an artificial funding requirement.
05

Understand the Three Funding Concepts

Capital Requirementoverall project funding need
Required Liquidityliquidity determined or approved through ALBUKHR
Verified Liquidityfunds actually verified through the applicable evidence/control process

Declared assets or liquidity are not automatically verified liquidity.

06

Prepare Ownership Evidence

Prepare evidence showing who owns or controls the project, who is authorized to represent it, and any relevant ownership or related-party relationships.

07

Prepare Business Evidence

Where applicable, prepare registration documents, licences, location evidence, financial statements, management accounts, invoices, contracts, sales/production records, asset records and other credible commercial evidence.

Forecast discipline: Forecasts must be clearly presented as forecasts, not historical facts.
08

Write a Clear Project Description

Problem→Solution→Customers / Users→Operations→Economics→Capital Use→Execution Team→Risks

Avoid promotional language that hides material limitations.

09

Prepare the Team

Provide accurate names, roles, titles, contact details where appropriate, relevant experience and primary-contact status. Do not add people merely to make the team appear larger.

10

Upload Supporting Documents

The applicant workflow supports:

Business RegistrationProject ProposalBusiness PlanFinancial StatementIdentity DocumentOwnership DocumentOther

Use authentic, readable files and only submit documents you have authority to provide.

11

Protect Private Information

Use the designated ALBUKHR private upload workflow. Do not expose private storage objects, share credentials, or attempt to bypass document-access controls.

12

Understand Due Diligence

Be prepared for verification of owner identity, ownership authority, registration, business identity, location, operating status, legal/regulatory dependencies, related-party conflicts and business evidence.

13

Understand Risk Review

Business modelExecutionFinancial/economicLiquidityOperationalOwnership/governanceFraud/market integrityLegal/regulatory
Risk→Evidence→Mitigation→Remaining Exposure

Do not hide material risks.

14

Prepare for Funding Review

Expect ALBUKHR to compare declared funding, itemized funding, reserves, contingency, project stage, operating cycle and evidence. The approved capital amount may differ from the original request.

15

Prepare for Custody Controls

Some projects require custody, segregation, deposit verification, release authorization, release conditions, reconciliation or exception controls.

Do not claim a control is complete until it has been verified.
16

Understand Terms

Terms may address investment model, asset, target capital, minimum/maximum investment, duration, funding window, return model, principal treatment, exit, fees, distributions, default and conditions.

17

Prepare Disclosure

Verified factsSupported by authoritative or reliable evidence.
Project declarationsStatements supplied by the project that require appropriate context.
Forecasts / assumptionsForward-looking expectations that must not be presented as historical facts.

Disclose material risks, conflicts, legal/regulatory dependencies, liquidity limitations, custody arrangements and material restrictions.

18

Understand Technical Readiness

Technical review may verify application/project binding, network alignment, registry integrity, owner binding, metadata, project logo and uniqueness.

19

Understand Approval vs Activation

Application→Ownership Verification→Due Diligence→Risk Assessment→Funding Structure→Custody Controls Where Required→Terms→Disclosure→Funding Readiness→Technical Readiness→ACTIVE

An approved project can remain inactive until all required gates pass.

20

Common Causes of Delay

Inconsistent names
Incomplete ownership evidence
Missing registration evidence
Unexplained funding figures
Unsupported financial claims
Incomplete team
Missing documents
Unclear funding purpose
Unresolved risk factors
Incomplete custody controls
Inconsistent terms/funding
Outdated disclosure
Technical inconsistencies
21

Never Do These

Fabricate documents
Alter financial records
Exaggerate performance
Claim unverified liquidity is verified
Promise guaranteed returns
Hide ownership relationships
Submit unauthorized documents
Bypass review controls
Manipulate the database/API
Mix Mainnet and Testnet information
22

Final Submission Checklist

IdentityAuthority and ownership are clear.
BusinessIdentity, registration and location are accurate.
ProjectPurpose, model and team are clear.
FundingCosts are itemized and reasonable.
EvidenceRequired documents are authentic and readable.
RiskMaterial risks and conflicts are disclosed.
TechnicalRegistry information is complete and consistent.
23

What Happens After Submission?

The application enters the review workflow. ALBUKHR may request evidence, perform due diligence and risk assessment, review funding, require custody controls, prepare/review terms and disclosure, verify technical readiness, and finally evaluate the authoritative activation gate.

Best practice: Prepare the evidence first. Submit the story second.