Build · Create · Writing & Content
Build a protective-provisions and board-approval consent register
A structured JSON register enumerating each protected corporate action, the approving class, and the consent threshold, covering the required protective-provision items with valid thresholds.
You receive: A JSON object { dealName, series, items: [ { actionKey (enum), approvingClass, consentThresholdPct (number), basis (enum: protective_provision|special_board_approval) } ], coveredActionKeys }.
Part of Pitch Investors
What's verified: STUD verifies the register covers every required protected action, that thresholds are valid and meet the floor, and that the enums are well-formed. STUD does NOT judge whether these provisions are negotiable, enforceable, or appropriate for your leverage.
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"debtApprovalFloor",
"minConsentThresholdPct",
"requiredActionKeys"
],
"checkNames": [
"format_parses",
"items_present",
"no_duplicates",
"actionkey_enum",
"actions_covered",
"threshold_range",
"basis_enum",
"approving_class_nonempty",
"debt_floor_present"
],
"constants": {},
"deliverableLabel": "protective_provisions_register",
"documentKeys": [
"actionKey",
"approvingClass",
"basis",
"consentThresholdPct",
"coveredActionKeys",
"debtFloor",
"items"
],
"enumLiterals": [
[
"alter_rights_preferences",
"change_authorized_shares",
"create_senior_or_paripassu_class",
"redeem_common",
"merger_or_sale",
"amend_charter",
"amend_bylaws",
"change_board_size",
"declare_dividend",
"incur_debt_above_floor",
"significant_hire"
],
[
"protective_provision",
"special_board_approval"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.