The report form: what each field means
A breakdown of every section in the weekly report form and what to put in each one.
A weekly report has several sections, each capturing a different dimension of your week. Understanding what belongs in each field makes your reports more actionable for leadership.
Last Week's Priorities (carry-overs)
The Results step opens with your carry-overs from last week. In the modal they appear side-by-side with the new results field. Check each item to mark it addressed, or leave it unchecked to carry it forward automatically.
New Results Delivered
List additional wins or deliverables from this week. Be specific: include project names, metrics, or concrete outcomes. This field is required unless you have marked at least one carry-over as addressed, in which case it becomes optional.
Organisational Impact Areas
Right after your results, a dedicated step asks which parts of the organisation this week's work touched. Available areas are: Revenue, Operations, Administration, Technology Infrastructure, Product / Software Development, and Customer Retention. At least one must be selected before you can submit. Impact areas are displayed on the report detail page and surface in dashboards so leadership can spot cross-team patterns.
Signals
Early indicators worth flagging: a client risk, a team morale concern, a process that's slowing things down. Signals are not blockers yet; they are things leadership should be aware of before they become problems.
Signal Types (optional)
On the same step, you can optionally tag your signals with one or more types: Achievement, Risk, Blocker, Opportunity, or Decision Needed. These tags help leadership quickly categorise and filter signals across teams in dashboards and standup prep — but a report can be submitted without any.
Blockers
Issues actively preventing progress. Each blocker has four fields: the description of the issue, how many days it has affected you, the impact if left unresolved, and an escalation flag for blockers that need a leadership decision. Filling in all fields gives managers the data they need to act quickly.
Efficiency / Improvement Opportunities
Ideas to reduce waste, speed up a process, or improve team dynamics. This is your channel for bottom-up feedback that can surface in leadership dashboards and summaries.
Next Week's Committed Priorities
What you commit to completing next week. These become carry-overs if left unresolved, and are tracked in your manager's team view.
Self scores, morale, workload, and ownership
The form includes five self-score dimensions (1–5), a morale rating, a workload rating, and an ownership signature. The signature field is pre-filled with your full name (you can edit it) and confirms that "by submitting this report" you take ownership of its contents. These fields help managers and leadership understand both delivery output and operating conditions.
Morale ≤ 2 and workload ≥ 4 trigger an immediate manager alert, sent the moment you submit (before the edit window closes). Other submission notifications are delayed until the edit window closes so recipients see your final version.
All text fields support @mentions: type @ followed by a colleague's name to notify them. If your organization has enabled @mention access in Settings, they also gain read access to the report.
Was this article helpful?