The 80% Plan.
Every engineer schedules at least 40 points each weekly cycle and lands at least 32 by end of day Monday, Eastern. This page is the policy: how the cycle runs, what counts as done, and what's expected when the floor is missed.
The rule
- Schedule at least 40 points at planning. Going over 40 is fine — scope is only trimmed at planning, never before it.
- Land at least 32 points by end of day Monday, Eastern — the moment the Linear cycle rolls over. Landed means merged. In progress counts as zero.
- Post your cycle report in Slack every Monday — template below.
- Under 32? Your report explains why and what you're changing next cycle. Owning the miss is part of the job.
- Finished everything in your cycle early? The rest of the week is yours — tech debt, learning, tooling, anything you want to take on. Feature work still waits for planning.
The floor is counted in landed points because shipped work is the one measure that can't drift.
The week
EOD Mon ETCycle closes · report posted · next cycle's tickets final
→
Tue AMYou review and own every estimate
→
Tue planningScope settles here · cycle locks
→
Wed–MonShip · keep estimates current
| When | Who | What |
|---|---|---|
| EOD Monday ET | Product | Next cycle's roadmap and tickets are final, with decision-complete requirements. Product's estimates are placeholders, not commitments. |
| Tuesday AM | Engineering | Review your tickets, set or correct every estimate, flag anything under-specified. |
| Tuesday planning | Team | Over capacity? What pushes out is decided here — the only place scope moves. Planning locks the cycle. |
| Wednesday–Monday | Engineering | Ship. Keep estimates current as reality changes. Only bugs come in mid-cycle. |
The Monday report
Post in Slack before end of day Monday, Eastern — that's when the Linear cycle rolls over (11:59 PM ET), so the report lands before the flip. Keep it to a few lines:
Cycle report — <name> Landed: <X>/<Y> points (<Z>%)
Under 32? Add two lines. They're required — a miss with a clear correction is respected; a quiet miss is not:
Why: <what actually happened — honest, specific> Next cycle: <the concrete change you're making>
Estimates
- You own your estimates. Correct them before planning, keep them current during the cycle. Nobody gets to blame a number they signed off on.
- Scale:
XS=1·S=2·M=3·L=5. Large is the ceiling — anything bigger gets split before it enters the cycle. - Size with the rubric. Don't size by gut. Count the attention flags a ticket raises — unclear spec, unknown cause, multi-surface, risky, heavy review — and the count is the size. See The Sizing Rubric.
Mid-cycle work
- Bugs come in; features never do. Platform bugs and fallout from your own shipped work are the only mid-cycle additions — fixing what you shipped is a continuation, not new scope.
- They arrive ready. A detailed Linear ticket, usually with an agent-built PR attached — review, test, land.
- The floor doesn't move. Mid-cycle bugs don't lower the 32.
What you get from us
- The tools to hit the floor. Claude Max and agent workflows are the standard kit. Hitting plan limits is a good sign — say so and we upgrade.
- Tickets that are ready to build. Product tickets arrive decision-complete. If one isn't, flag it before planning — after planning, execution is on you.
PerkUp engineering policy · effective June 2026.