As part of our controllership processes, the Delegation of Authority (DoA) is a key internal document. We updated the existing DoA to align with our current rules, processes and Enterprise Standards. We also reflected the latest governance and organizational changes. You will find the updated DoA here and in the Controllership Support Central section at this link.
The DoA describes the different functions and roles whose approval is required before certain decisions can be taken on behalf of Power Conversion. The DoA is divided into 12 different sections (e.g. Property, Plant & Equipment, Inventory, Procurement and sourcing etc.). Within each section, the relevant triggers / decisions are set out in a matrix which specifies the roles (at Region, PC HQ or Corporate level) whose approval is required for each decision. Please note this DOA does not address commercial transactions – Syreeta Jeffs communicated the new ITO DOA earlier.
We’ve added the tab “D- Revision History” to show you the changes versus the 2020 version. As you’ll see we’ve been working to clarify a few items and increase thresholds to support further regional decision-making.
Please note the following points:
- The DoA is not intended to cover each and every task and duty assigned to employees. It only indicates mandatory approvals for those decisions identified as critical. Please continue to use your common sense and ask the Controllership Team if you have questions.
- The DoA defines the approval of decisions, not the performance and recording of transactions. (e.g. who can approve a purchase order, as opposed to who can issue it and record it in the ERP). For each transaction, the approval should be segregated from performance and recording.
- The DoA (being an internal controllership tool) is different from a Power of Attorney (PoA) which is a legal document formally authorizing someone to do or sign something on behalf of a specific legal entity.
- To be clear, agreements with third parties or other external documents can only be signed in the name of a specific legal entity, by someone designated in the PoA. But first, the transaction contained in that document must be approved by all the persons identified in the DoA.
- Most of the tools to enforce the DoA and the audit trail are via email. Please make sure to retain them for audit trail purposes.
- The DoA is effective immediately.
Please help ensure this updated DoA is effectively implemented, and shared with the relevant stakeholders within your regions.
Grand River Avenue originated as an Indian trail before Michigan statehood. It later was used as a wagon road across the state. The roadway was included in the State Trunkline Highway System in 1919 as M-16 and later the United States Numbered Highway System as US 16. Construction of a freeway along the length of the corridor was proposed in the 1940s, and included as part of the Interstate Highway System in the mid-1950s. This construction was started in 1956 and initially completed across the state to Detroit in 1962. The proposed route for the Jeffries Freeway in Detroit was moved in the 1960s; it was built in the 1970s. I-96 was completed on November 21, 1977, in the Detroit area, closing the last gap along the route. Since then, additional interchanges and lanes have been added in places to accommodate traffic needs.