This is an example structure for an engineering change. Depending on requirements and/or preferences this can be as simple as a list of changes (revision history) a semi-formal report as outlined below or a highly specific process..
You need to add/remove/modify content to suit and then save as a template (Template Menu) if you want to re-use in your projects.
IMPORTANT: The information below is intended to provide some helpful content that may be relevant during a project revision. It is not fit or suitable for any particular purpose without user review and input.
First, the need for an ECO is identified. Why are we making the change, what is the source of the request, what is the priority, etc.
Engineer evaluates request on it's technical merits and difficulty to arrive at cost benefit conclusion.Technical notes and implentation detail / timescale can go here.
Is the change authorized or rejected and on what basis. Constraints on the project, notes and amendments go here so the specification is clear.
If authorized, details of modifications go here, along with timescale and notes of any problems or possible impacts that were uncovered during the change process. Rules for interchangeability (e.g. form/fit/function) and re-annotation can be detailed here.
You can add links on parts from the top toolbar so they can be clicked on to navigate to the part on either the schematic or the layout. The internal clipboard makes it simple to copy and paste bits of schematic or layout into the document here.
The change is checked and approved or rejected. Testing can either be a separate section above this or rolled into the approval process.
Any notes on completion and log of the revision number assigned to the ECO.
Work completed on <date>. Project Revision Number <num> Assigned.