Get six months of evidence before you write the review

Nine reports, nine evidence packs, one pass

The companion pulls each report’s goals and where each landed, the 1:1 updates in date order, and the peer feedback with authors. It quotes, so what you read on Thursday is what your report wrote in April. Gathering scattered evidence into one document is the data extraction move.

Ten minutes of assembly per person, done before you sit down, is the whole intervention. The writing stays yours.

Why is read-only the right shape here?

Reviews, feedback and goal history are the record of how somebody was managed.

The Lattice surface is reads only: no goal edits, no feedback submission, no review drafts pushed into a cycle.

So it is the easiest integration in this set to connect. Everything a companion produces lands in your own document where you can rewrite it, and nothing it touches changes what anyone else sees in Lattice.

What stays yours to write?

The argument.

A review is a case about someone’s career, made by the person accountable for it. Thursday-night reviews come out thin because nobody had time to go and get the evidence.

A companion hands you that evidence with links: what they set out to do, what happened, what their peers said, in their own words and in date order. Six months of proof on the page makes the document much easier to write.

Clean up the goals before the quarterly

The quarter is ending and half the goals in Lattice have not been touched since the week they were created. A companion reads every goal across a department and produces the short list: no update in six weeks, already at 100% and never closed, owner has changed teams.

That is a five-minute item in an ops meeting instead of a twenty-minute scroll. The reporting rhythm is the one in operations: the companion finds the drift, a manager fixes it in Lattice.

Frequently asked questions