Goals
Cycles by Indian financial year; objectives at company, team or person level aligned to one above, with key results as numbers, percent, money or milestones, and private goals.
Goals everyone can see and update
Set goals for the company, teams and people each quarter, track key results with check-ins, and review them at the end.
Cycles follow the Indian financial year (quarter or year). Objectives sit at company, team or person level and align to one above them (up to four deep), with an owner, a weight and an optional private flag; key results are a number, percent, money or milestones. People check in with a value, a confidence and a note; history is kept. Progress rolls up from key results to objectives to their parents by weight, with confidence taken from the worst key result and a pace against the cycle clock. Views are company tree, teams, my goals and at risk. At the end of a cycle each goal is reviewed with a 0 to 100 score and closed or carried forward; eight templates help to start. Targets are monthly numbers per person or team, typed or set through the API. Reminders go out by email in each business's own hour, once per overdue period. Teams come from Members and, when connected, People. API with PUT /api/v1/key-results/<id>/value and /api/v1/targets/<id>/value using an API key or the workspace key, a change feed and webhooks. Optional Claude features draft key results and summarise a cycle. A private goal is hidden from everyone but its owner and never counts in a roll-up. Not built: exports of a cycle, @mentions, bulk import.
What Goals does for you.
Cycles by Indian financial year; objectives at company, team or person level aligned to one above, with key results as numbers, percent, money or milestones, and private goals.
Check-ins with a value and confidence, roll-up by weight, pace against the cycle, and views by tree, team, my goals and at risk.
A score from 0 to 100 and close or carry forward; monthly targets per person or team that other apps can update through the API.
A suggested path for Goals. What you can do depends on your access in the app.
Pick the quarter or year.
Add objectives and key results.
Update progress and review at the end.
Live host, inventory, governance, health checks, verification, dependencies and history.
Cycles follow the Indian financial year (quarter or year). Objectives sit at company, team or person level and align to one above them (up to four deep), with an owner, a weight and an optional private flag; key results are a number, percent, money or milestones. People check in with a value, a confidence and a note; history is kept. Progress rolls up from key results to objectives to their parents by weight, with confidence taken from the worst key result and a pace against the cycle clock. Views are company tree, teams, my goals and at risk. At the end of a cycle each goal is reviewed with a 0 to 100 score and closed or carried forward; eight templates help to start. Targets are monthly numbers per person or team, typed or set through the API. Reminders go out by email in each business's own hour, once per overdue period. Teams come from Members and, when connected, People. API with PUT /api/v1/key-results/<id>/value and /api/v1/targets/<id>/value using an API key or the workspace key, a change feed and webhooks. Optional Claude features draft key results and summarise a cycle. A private goal is hidden from everyone but its owner and never counts in a roll-up. Not built: exports of a cycle, @mentions, bulk import.
Projects and tasks belong to Projects and Boards; performance reviews of people belong to People.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
goals.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.