# Project Completion Report and Video Requirements

To complete your Catalyst-funded project, you must submit a **Project Completion Report (PCR) and a Project Completion Video (PCV)** as part of your final milestone Proof of Achievement (PoA). 

These will be reviewed by the milestone reviewers assigned to your project and by Catalyst for final approval.

Please use the headings below to structure your PCR. For each section, provide concise, evidence-based information and include links and metrics wherever relevant. Create the PCR as a single PDF document. Include a hyperlink to it in your final PoA submission

The PCR and PCV are intended to showcase the impact and measurable outcomes of your work. This submission will become part of your public ecosystem track record, so please treat it as a chance to strengthen your reusable brand assets and demonstrate value to the wider Cardano community.

### Project Completion Report

**Required fields:**

* Project Name
* Project Number (the 7-digit number shown in your Milestone Module, starting with the fund number) 
* Project Manager
* Project Start Date
* Project Completion Date

### 1. Deliverables

Describe what you built and delivered. Focus on the actual outputs, not a repeat of the original milestone description.

Include the relevant items below where applicable:

* On-chain evidence: policy IDs, transaction hashes, or smart contract addresses.
* Off-chain evidence: GitHub repositories, research papers, or documentation links.
* Single URL hosting all outputs: website, IPFS link, live application link, spreadsheets or docs that support your accomplishments.
* Open source status: Yes/No, and license if applicable.
* Testing performed: unit tests, QA, beta testing, or similar. 
* User feedback: Where possible include relevant user feedback on what you have delivered. 
* Visual evidence: photos or videos.

### 2. Usage

Describe who is using, or expected to use, the project and how they interact with it.

Include, where available:

* User count.
* \# of Transactions or interactions.
* Key actions completed.
* Evidence of engagement: analytics dashboards, on-chain activity, screenshots, or reports.

### 3. Impact

Explain the measurable value created by the project. Where possible, compare before and after states.

Include, where available:

* Performance change.
* Cost or time savings.
* Quality proof: testimonials, partner endorsements, or audit reports.
* Cardano ecosystem benefit: how the project improved utility, adoption, or chain health.
* Partnerships, recognition, or policy changes.

### 4. Sustainability

Explain how the project will continue after Catalyst funding ends. State whether it is ongoing or a one-off project.

If ongoing, include:

* Maintenance model.
* Revenue model.
* Future roadmap.

If one-off, include:

* Forking instructions.
* Permanent storage location, such as GitHub, IPFS, or an archive link.

### Project Completion Video

You must include a **public YouTube or Vimeo link** with no access restrictions. Add the video link in the PCR, and in your final PoA submission.

The video should:

* Show evidence of the completed work in action.
* Include a live technical walkthrough or demo showing the solution working.
* Tell the story of the project, including why it matters to the ecosystem, what challenges were encountered, how they were overcome, and what comes next.
* Have audio commentary in English to describe what you are showing.
* Ideally be no longer than 5 minutes, though this is a guide rather than a strict rule.

### Final Check

Before submitting your PCR, check every link carefully. If any link does not work, the PCR may not be approved.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.projectcatalyst.io/current-fund/general-information/project-completion-report-and-video-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.