INTERIM DEPUTY CTO MANDATE

Editable resource — adapt to the real organization and appointment.
Do not include passwords, tokens or private customer records.

Use this outline as an internal discussion document before converting it into recruitment or engagement terms. It is not a contract, a vacancy announcement or a substitute for the organization's own approval process. Replace the prompts with accurate information and remove responsibilities that are not part of the actual role.

Reason for the appointment: State the departure, absence, capacity constraint or organizational change. Describe its effect on decisions and commitments rather than relying on a broad request for senior leadership.

Role relationship: Identify whether the person holds the CTO mandate temporarily or acts as deputy to a named CTO. If a deputy also covers an acting appointment, state when that additional authority applies.

Owned responsibilities: List the functions, technical decisions, management responsibilities and executive communications included. Identify existing leaders whose responsibilities remain in place.

Authority and limits: State what the appointee can decide, recommend and escalate. Record reserved matters, approval limits and the process for disagreements.

Capacity and support: Describe expected availability, necessary time-zone overlap, internal assistance and specialist support. Identify work that will be reassigned if an existing employee takes additional responsibility.

First-phase outputs: Request a decision inventory, continuity review, responsibility map or other concrete outputs that address the reason for the appointment. Name the person who accepts each output.

Review and transition: Define review dates, extension decisions, handover conditions and the information the next leader needs. Do not make completion dependent only on the passage of time.

Prepared from https://fractionalctoexperts.com/comparisons/interim-cto-vs-deputy-cto