HR · App Starter
OKR Tracking Template
A working goals system — objective tree, weekly check-ins, review cycles, feedback — generated into a codebase you own.
Describe how your company sets goals, and Dual7 generates this OKR system around it: six connected entities, a goal tree from company to team to individual, and a check-in cadence, shipped as a real full-stack app. Change the scoring scale, the cycle length, the whole ritual — it's your code, not a seat license per employee.
- 6 core entities
- Goal tree
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
Goal systems die when the structure fights the ritual — cycles that don't match your calendar, scoring you don't believe in. Six connected entities model the ritual you actually run, and everything below reads from them.
| table | what it holds |
|---|---|
objectives | Qualitative goals at company, team, or individual level, each linked to its parent — the tree from mission to Monday. |
key_results | The measurable commitments under each objective — start value, target, current, and a status the check-ins keep honest. |
check_ins | Weekly updates per key result: new value, confidence, and a note on what changed — the heartbeat that separates OKRs from wall art. |
review_cycles | Quarterly (or your cadence) windows that open, score, and close a set of objectives, keeping history comparable across periods. |
feedback_entries | Peer and manager notes plus 1:1 records tied to people and objectives — the qualitative half of the review conversation. |
teams | The org units that own objectives — membership, lead, and the roll-up level between company goals and individual ones. |
02 · Screens
Signature modules
Goal tree
01Every objective links upward, so the tree shows how an engineer's quarter connects to the company bet it serves. Orphan goals and over-loaded objectives are visible at a glance — alignment becomes something you can inspect, not assert.
Weekly check-ins
02Each key result asks its owner one small weekly question: current value, confidence, what changed. The roll-up turns those answers into a live status page for the quarter, and stale check-ins are flagged before the goal quietly dies.
Review cycles
03Cycles open with goal-setting, run on check-ins, and close with scoring — on whatever scale you use. Past cycles stay queryable, so 'do we always sandbag Q4' is a question with an answer.
Feedback and 1:1 notes
04Peer feedback and 1:1 notes accumulate against people and objectives through the quarter, so review week is a reading exercise instead of an archaeology project. Visibility rules are yours to set — and to read in the code.
03 · Process
How it works
- 1You
Describe your goal cadence
Tell Dual7 how goals work at your company — cycle length, who sets what, how you score, whether individuals carry OKRs. Plain language is enough; the starter supplies the structure.
- 2Vibe mode
Generate and iterate in Vibe mode
Get the working system in minutes, then tune the ritual conversationally: rename confidence levels, add a private-goal flag, change the check-in day. Every adjustment lands in code you can read.
- 3Governed mode
Ship through the governed pipeline
When the org is ready to adopt it, promote it through Dual7's approval gates to production — audit trail included, deployed on your infrastructure, your goals in your database.
04 · Fit
Who the OKR Tracking starter is for
Leadership teams running OKRs in slides
The quarter kicks off in a deck and is never opened again. Moving the same goals into a tree with weekly check-ins changes one thing that changes everything: status is written down while it's still cheap to act on.
Companies that quit their OKR platform
Many teams have adopted a goals platform, used a tenth of it, and cancelled. A generated system is the opposite bet: only your ritual, nothing else, and no per-employee fee for what is ultimately a well-structured list.
People ops building performance infrastructure
Reviews, feedback, and goals want to live together, but vendor suites bundle them with pricing to match. Starting from this codebase, ops owns the whole loop — and the sensitive data in it stays on infrastructure the company controls.
Founders instilling the habit early
At twenty people, process tools are a hard sell. A lightweight goal tree with a Friday check-in nudge is the minimum honest version of OKRs — and because it's code you own, it grows into review cycles when the company does.
05 · Yours
Customize it, own it
Make it yours
The ritual is the spec. Rename anything — objectives to rocks, check-ins to pulse updates — set your scoring scale, and decide whether key results carry numbers, milestones, or both. In Vibe mode these are conversational edits that land as real schema and code changes.
Deeper changes are ordinary engineering: pull key-result values automatically from your analytics or data warehouse, post check-in digests to chat, or add a calibration step to review cycles. The generated app has no runtime dependency on Dual7, so your team can extend it directly.
Why a starter, not a subscription
Goal platforms charge per employee per month for what is, structurally, five tables and a reminder. This starter generates those tables, the screens, and the cadence logic as source code in your repository, deployable on your infrastructure. Performance data — goals, scores, feedback — is exactly the data most companies would rather not park in another vendor's cloud.
In exchange, you run the app. Dual7's governed pipeline keeps that responsible: approval gates before changes reach the org, an audit trail of who changed what, and regeneration when the ritual itself evolves — new cycle structure, new scoring — without hand-patching.
06 · Industries
Industry versions
OKR Tracking template — frequently asked questions
What does the OKR tracking template include?
A working full-stack goals system generated into a codebase you own: six connected entities (objectives, key results, check-ins, review cycles, feedback entries, teams), a goal tree with alignment view, weekly check-ins with confidence, cycle scoring, and 1:1 feedback records.
Can I change the scoring scale and cycle length?
Yes — both are yours. Run quarters, trimesters, or six-week cycles; score 0.0–1.0, red-yellow-green, or your own scale. These are rules in your code, changed conversationally in Vibe mode, not plan-tier settings.
Do individuals have to carry OKRs, or just teams?
Either. Objectives attach at company, team, or individual level, and many organizations stop at team level — the tree works the same. If you later add individual goals, it's the same structure one level deeper, not a migration.
How is this different from tracking goals in a spreadsheet?
The sheet holds the same rows but has no cadence: nothing asks owners for weekly updates, flags stale key results, or keeps cycles comparable across years. The system's value is the ritual it enforces — and unlike a vendor's ritual, this one is defined by you.
Can it send check-in reminders?
A scheduled nudge on your check-in day is part of the cadence logic, and wiring it to email or your chat tool is a normal extension of code you own. The escalation path — who hears about a skipped check-in — is your policy, written down.
Related
Dual7 App Starters
Build your OKR Tracking on your terms
A working goals system — objective tree, weekly check-ins, review cycles, feedback — generated into a codebase you own. Describe your version to start — the output is a project you own.