Verified Execution Record
Track commitments, score follow-through, and manage investor access to your execution history.
The Verified Execution Record gives each entity a structured history of what it said it would do, what actually happened, and who is allowed to review that history.
It is designed for founders, operators, investors, and diligence partners who need more than a point-in-time report.
What the execution record includes
- Planning cycles for quarterly or custom windows
- Quarter-scoped goals tied to a cycle
- Standalone goals that sit outside a quarter when the work does not match the reporting calendar
- Manual and financial goal resolution
- Execution score snapshots and score history
- Permissioned follower access for outside stakeholders
Founder workflow
Start an execution cycle for a quarter or another defined window. The cycle becomes the operating frame for the goals you want to commit.
Add manual or financial goals, assign category and weight, and decide whether the goal belongs to the cycle or should remain standalone.
Commit goals once they are ready, then lock the cycle when planning is complete. This turns the cycle into a stable execution record instead of a draft workspace.
Manual goals can be resolved by the founder or operator with notes and evidence. Financial goals can resolve against verified reporting flows.
Use the execution dashboard to review score history, goal timelines, and standalone goals, then export a JSON snapshot when you need to share or archive the current state.
Goal types
Manual goals
Use manual goals for milestones such as:
- hiring a leadership role
- launching a product
- signing a partnership
- closing a facility or operational project
Manual goals are resolved with an explicit status and supporting note.
Financial goals
Use financial goals when you want the system to evaluate performance against a defined metric or KPI.
Examples:
- revenue targets
- ARR
- customer count
- margin or cash-flow thresholds
What investors see
Investors do not automatically get execution access.
The workflow is:
- They request execution access from the entity page.
- The founder approves, denies, or later revokes the request.
- Approved followers can open the execution record and see execution activity in their feed.
The investor feed highlights events such as:
- cycle creation
- goal commitments
- goal resolution
- execution score updates
Execution followers
Founders manage execution followers from the execution workspace.
They can:
- approve requests
- deny requests
- revoke approved access
- review current follower status and access level
Execution access is intentionally separate from general entity access.
Privacy and report access
Execution access does not mean blanket access to every underlying artifact.
Founders can pair execution workflows with selective follow-access policies so a follower sees only what is appropriate:
- the whole report set
- goals only
- press releases only
- a custom subset of report artifacts
If linked artifacts are involved, use the most restrictive option that still supports the diligence workflow.
Execution sharing works best when you treat the execution record as the public narrative layer and the underlying reports as separately governed artifacts.
Recommended operating pattern
- Keep cycles aligned to a real operating cadence.
- Use standalone goals only when a milestone genuinely falls outside the normal quarter frame.
- Commit goals before you communicate them externally.
- Resolve manual goals quickly so the score history stays credible.
- Review follower access regularly and revoke stale diligence access.
Exporting the record
Use Export Snapshot from the execution history tab when you need a point-in-time package of the current execution state for review, audit, or internal archiving.