Skip to main content
After Launchboard extracts data from a document, it moves to PARSED status and waits for your review. You verify the extracted fields in the Inspector panel, and once you’re satisfied, you merge the document to create the corresponding cap table records. Every record created this way carries a permanent link back to its source document.
Always review extracted data before merging. AI extraction is accurate in the vast majority of cases, but legal documents vary in structure and language. A missed field or an incorrect value will flow into your cap table — take a minute to check each field in the Inspector before clicking Merge.

​
Reviewing and merging a document

1

Open the Inspector

In the Dataroom, click on a document with PARSED status. The Inspector panel opens on the right side of the screen, showing the extracted fields organized by category.
2

Review each extracted field

Work through the fields the AI extracted. Each field shows its extracted value. Check that names, amounts, dates, and other terms match what’s in the document.
3

Approve or reject fields

For each field, you can approve it (confirming the value is correct) or reject it (flagging it as wrong). If you reject a field, you can edit the value directly or re-run extraction to try again.
4

Mark the document as Reviewed

Once you’re satisfied with all extracted fields, click Mark as Reviewed. The document status updates to REVIEWED. This step is required before you can merge.
5

Merge to the cap table

Click Merge in the Inspector. Launchboard validates the extracted data against the Open Cap Format (OCF) schema. If validation passes, the data is written to your cap table as new records — stakeholders, securities, share classes, or other entities depending on the document type.

​
The Inspector panel

The Inspector is where you interact with a document’s extracted data. It shows:
  • Extracted fields — the structured data pulled from the document, organized by type
  • Confidence indicators — signals from the AI about how certain it is for each field
  • Document preview — the original PDF alongside the extracted data so you can compare
  • Signatures section — signer status and seal hash (when signatures have been requested)
  • Attestation section — record of who reviewed and approved the document

​
OCF validation

Before Launchboard allows a merge, it validates the extracted data against the Open Cap Format (OCF) schema — an industry-standard format for cap table data. If the data doesn’t pass validation, the merge is blocked and the Inspector shows which fields need attention. This prevents malformed data from entering your cap table.

​
What a merge creates

When you merge a document, Launchboard creates the corresponding cap table records and links each one back to the source document:

​
Provenance

Every cap table entry created through a merge carries a provenance link — a permanent reference back to the document it came from. From the cap table, you can click View source document on any record to jump directly to the original PDF in the Dataroom. This gives you a complete audit trail from ownership data back to the legal agreement that authorized it.