Goals and OKRs in Pitch N Hire HRMS

What goals & okrs includes

What does OKR mean, and what is an objective versus a key result?

OKR stands for objectives and key results. The objective is the qualitative statement of what you are trying to achieve in the period. It should be memorable and slightly uncomfortable, and it carries no number of its own. The key results are the measurable evidence that the objective happened: each has a starting point, a target and a unit, so at the end of the period anyone can say whether it was met without arguing about interpretation. A short list of key results per objective is the usual working limit, because a long one turns into a task list. In Pitch N Hire the two are separate objects joined by a parent link, and that is what makes the OKR framework a structure rather than a formatting convention: progress rolls up from the key results, and the objective inherits a status nobody had to type.

How do objectives cascade from the organisation to individuals?

A company objective is created and published first, so everyone can read it before writing their own. Departments then create objectives naming the company objective as their parent, teams do the same against the department, and individuals against their team. The link is explicit rather than implied by similar wording, so the chain from one person's key result up to the company statement can be traced in either direction. Pitch N Hire does not force a level: a small organisation can run company and individual goals with nothing in between, and a matrixed team can point a goal at an objective outside its own reporting line. Goals without a parent appear as such in the alignment view, which is deliberate, because an orphan goal is either genuinely standalone work or a sign that the level above it was never written down.

What makes a key result measurable?

A key result needs three things before it can be saved: what is being counted, where it starts, and where it should end. The unit can be a count, a numeric value, a share of completion, or a binary done-or-not for work that genuinely has no midpoint. Because the start value is captured, progress is calculated from movement rather than from the owner's impression of how far along things feel. Milestone-style key results suit delivery work where the meaningful states are a sequence rather than a continuum. What the module deliberately does not do is score a key result against an external standard, because the target is the one your team agreed and the system reports movement against that. Anything that stays qualitative belongs in the objective, where judgement is expected, not in the key results, where it is not.

How often should check-ins update progress?

Cadence is configured per goal set, and the right answer depends on how fast the underlying number actually moves. A weekly rhythm suits sales and support metrics that change daily; a monthly one suits programme work where a week of movement is noise. Pitch N Hire prompts the owner when a check-in is due, and the update asks for the current value, a status of on track, at risk or off track, and a short comment explaining the number. The comment is the part managers read, so it is required whenever the status is anything other than on track. Missed check-ins stay visible rather than being silently skipped, because a goal nobody has touched for a month is itself information. Each update is timestamped, so the progress line shows when movement happened and not only where the number landed.

How does progress roll up to a company view?

Every check-in on a key result recalculates the objective above it, and the recalculation continues up the chain. A department objective's progress is derived from the team objectives beneath it rather than typed in by a department head, which removes the gap between what a rollup claims and what the underlying work shows. Weighting is available where child goals are not equally important, so a minor objective cannot drag a critical one down. Status is deliberately separate from progress: an objective can be behind on completion and still be flagged on track by its owner because the remaining work is scheduled, or complete on paper and flagged at risk because the number is not holding. Leadership sees both, plus the comment history, and the comments are usually what explains the difference between them.

What does the alignment view show?

The alignment view arranges goals as a tree rather than a list, so a company objective can be opened to reveal everything hanging beneath it. Reading downward answers what an objective actually depends on. Reading upward answers the question employees ask far more often, which is why a goal is on their list at all. Filters narrow the tree by department, owner, period or status, so a leader can see every at-risk goal supporting one company objective in a single view. Goals with no parent are grouped separately instead of hidden, and objectives with no children show as stated intentions nobody has taken work against yet. Both are useful findings in a planning review. Because the org chart supplies the reporting structure, the tree stays correct as people move between teams.

How do goal outcomes feed the review cycle?

When an appraisal window opens, the goals recorded for that period are pulled into the review form for both the employee and the manager: final values against targets, the status history, and the comments left at each check-in. Neither party retypes them, and neither is arguing from memory about what was agreed in a quarter that ended months ago. The cycle can weight goal achievement against competency scores, or show goals as context without scoring them, which suits organisations that write deliberately ambitious targets. Closed periods are frozen, so a goal edited afterwards cannot quietly rewrite what the review assessed. The mechanics of the cycle itself are described on performance reviews, and the buying view of the category on performance management software.

How is the OKR framework different from KPIs or a task list?

A KPI is a number you watch continuously, such as attrition, response time or revenue per head, and it exists whether or not anyone is trying to move it this quarter. An OKR is a deliberate push: a metric you have decided to change, with a target and a deadline attached. A task list is the work itself, which may or may not shift either of them. Confusing the three produces the two failure modes worth naming, namely OKRs that are really a restated job description and OKRs that are really a project plan with a hundred lines. Pitch N Hire keeps monitored metrics in hr analytics and improvement targets in goals, so the two are not competing for the same screen, and a goal that exists to move a metric names the metric it is aimed at.