Tetra approaches margin gain and fade as a visibility and review workflow. The aim is to help the team see movement, trace the context, and investigate it in time to act.
That begins with a consistent comparison basis. Agree the periods, accepted versions, and definitions before producing a bridge or commentary.
Name the measure
Label margin dollars and margin percentage points distinctly. Record the comparison period and the scope of jobs included. Keep the definitions available to the people preparing and reading the report.
A shared definition is part of the data model. Ownership of the review is part of the operating model.
Trace the question back to its inputs
The review should connect a movement to the relevant accepted inputs and open questions. A CTC change or contract update may need explanation from a named owner; the workflow should make that responsibility visible.
Do not allow a generated narrative to turn an unresolved assumption into an accepted explanation. The reviewer needs to distinguish documented evidence from a question still being investigated.
Measure visibility without promising away fade
One useful process measure is the time between an available material change and its escalation for review. Agree what counts as material and when the clock starts with the client.
Earlier visibility does not mean the workflow eliminates margin fade, and faster reporting does not prove estimate accuracy. Measure the improvement the work can actually demonstrate.