Career Growth
Taking an Acting Role? Agree on Duration, Authority, and Pay Review
A complete fictional acting-role agreement and end review clarify delegated authority, current-duty coverage, compensation decision and return to the original role.
Before accepting an acting role, agree on its start and end dates, the decisions you can make, the work someone else will cover, and who will decide any temporary compensation. Include what happens when the assignment ends. An acting title does not by itself authorize personnel decisions, establish an allowance, or promise a permanent appointment.
Ask for a short written assignment record rather than relying on “help out until we hire someone.” The record should distinguish agreed terms from any conditions that must still be settled before the assignment starts. This LandOffer.ai guide works through a fictional engineering assignment and its completed end review; no real employer approval, pay change, or employee appointment is claimed.

Identify the role you are actually being asked to cover
“Acting lead” might mean coordinating a team's work, covering a manager's delegated decisions, or taking on additional technical responsibilities. Those arrangements have different authority and workload implications. Ask which position or duties are being covered, why the coverage is temporary, and which responsibilities remain with another named owner.
Kennesaw State University's temporary-assignment guidance distinguishes acting or interim appointments from additional duties and project pay. It requires HR approval before work starts under its process and routes requests through the manager, HR business partner and compensation review. These are that employer's rules; its duration definitions and pay administration do not determine another employer's obligations.
For your own assignment, find the applicable policy and employee category through your manager or HR contact. A collective agreement, employment terms, or a different staff category may affect the answer. Ask for the current rule and decision owner rather than assuming that a public policy from another organization establishes your entitlement.
A completed temporary-assignment agreement
Lina is a fictional software engineer on a map-labeling desktop team. The team lead will be absent for six weeks. Director Amara proposes that Lina coordinate the team's planning and technical decisions during that period. People management and release authorization will remain with Amara and release owner Ben respectively.
Lina does not accept the phrase “full lead responsibilities” without clarification. She and Amara complete the following record. All names, dates, decisions and employer rules in this case are invented for teaching; the example's no-supplement decision is not a recommendation about what another employee should accept.
| Item | Completed agreement in the fictional case |
|---|---|
| Assignment and reason | Acting technical coordination for the map-labeling team during the lead's planned absence; no permanent vacancy or appointment promised |
| Duration | November 2 through December 11, 2026, inclusive; reversion on December 14; no automatic extension |
| Delegated decisions | Sequence already-approved labeling work, chair planning, document technical trade-offs and resolve routine task ownership within the existing plan |
| Reserved decisions | Amara retains personnel, performance-rating, leave and budget decisions; Ben retains production release approval; material roadmap changes go to Amara |
| Current-role coverage | Jorge takes Lina's label-import maintenance queue for the period, with Amara reallocating Jorge's existing backlog; Lina's optional rendering experiment is deferred |
| Workload boundary | Lina retains one bounded label-layout investigation; she does not keep the maintenance queue or add after-hours coverage through this assignment |
| Support and escalation | Amara holds a weekly decision meeting; urgent priority or authority conflicts go to Amara; Ben handles release decisions |
| Compensation decision | HR contact Saira explains the applicable fictional policy, and authorized compensation owner Owen records a no-temporary-supplement decision on October 29; base pay remains unchanged; Lina receives that written answer before choosing to accept |
| Activation | Amara confirms scope and coverage in writing on October 30 after the compensation answer; Lina accepts the finite arrangement; no earlier acting work is described |
| Reviews and ending | Midpoint November 20; end decision December 4; handback due December 11; original software-engineer duties resume December 14 |
This is a complete agreement rather than an allowance request with the other details left blank. Lina knows which decisions she can make, what she will stop doing, and what the compensation answer is. Had the answer remained pending, the proposed start would have remained conditional in this example.
Match authority to the decisions that will arrive
Use a few decision examples to define the delegation. In Lina's assignment, she can move a labeling task later within the approved plan when its dependency is unresolved. She cannot promise another team a new roadmap commitment, approve a hire, or authorize a production release because those decisions remain outside her delegation.
The team announcement should carry those boundaries. Amara's fictional note says: “From November 2 through December 11, Lina will coordinate technical planning and task ownership within the current approved plan. Personnel and budget decisions remain with me; release approval remains with Ben. Bring conflicts over these boundaries to me.” It gives colleagues a usable routing instruction without implying Lina has become their permanent manager.
Check that practical access matches the assignment. Lina needs the planning documents and decision meetings relevant to her scope. She does not need blanket access to confidential personnel files. Ask the appropriate owner to arrange necessary permissions through the normal process; an acting title is not permission to bypass access controls.
If someone asks for a decision outside the delegation, state the limit and route it. “I can prioritize this within the approved plan; Amara needs to decide a new commitment” is more useful than silently accepting accountability without authority. Record requests for personnel, budget or roadmap decisions outside your delegation so the director can correct the routing or revise the scope.
Make current-duty coverage real before adding responsibilities
Taking on a lead's calendar while retaining your complete engineering workload can make a temporary arrangement unworkable. Name each duty to transfer or pause, the receiving owner, and who will resolve capacity conflicts. Without a receiving owner and an agreed priority change, the original work may still reach you.
Lina's record names Jorge for maintenance coverage, but that transfer also affects Jorge. Amara confirms his capacity and moves part of his existing backlog before the assignment begins. The optional rendering experiment is explicitly deferred. Lina's retained investigation is bounded, so a new urgent request triggers a priority decision rather than becoming invisible extra work.
At the midpoint, check whether the transfer happened. If maintenance questions still route to Lina, Amara should correct the routing and decide any needed trade-off. Do not write the agreement as successful merely because a name appears in a table. The assignment owner must address differences between the written plan and the work actually arriving.
Discuss working hours, on-call expectations and available support under the applicable rules. This article does not determine overtime classification or pay rights. The practical question is whether the proposed schedule and responsibilities are understood by the people authorized to approve them.
Give pay review its own decision and timing
Ask whether the employer treats the arrangement as temporary higher duties, additional duties, project work, or another category. Then ask who decides eligibility, what documentation is needed, when the decision will be made, and whether an approved payment changes base pay or ends with the assignment.
University of Washington's professional-staff guidance says departments may request Compensation approval when duties temporarily increase, and that temporary pay is not a change to base pay. Its employee-category rules and thresholds belong to that employer. They are not a standard allowance formula for every acting role.
UC Davis's stipend guidance likewise describes temporary, non-base-building payments for designated periods, subject to its review and approval rules. It also distinguishes applicable collective-agreement and policy-covered arrangements. These examples show why a pay conversation needs the actual governing policy, not an assumed percentage copied from a search result.
In Lina's fictional case, Owen's written answer is no temporary supplement under the stated policy. She can evaluate the proposal with that answer rather than with an implied future payment. The example does not say that accepting unchanged pay is preferable, required, or appropriate for your situation. If an important term is unacceptable or unclear, explain that before confirming the arrangement and ask the responsible owner to revise it.
Where a payment is approved, retain its amount or calculation basis, effective period, approval record and end condition through the appropriate internal channel. Ask how payroll will handle an early end or approved extension. Do not infer a permanent increase, retroactive award, or benefit treatment from the word “acting.”

A completed end review that returns the role
On December 4, the fictional participants complete the end review instead of waiting until the last afternoon. This is a written teaching scenario, not evidence of an actual team's performance. The returning lead is expected back on December 14, and Amara decides not to extend Lina's assignment.
The completed review reads:
Decision: the acting technical-coordination assignment ends December 11 as agreed. Lina resumes her software-engineer role on December 14. No permanent appointment or promotion decision has been made.
Work and limits observed in this scenario: Lina maintained the planning decision record and routed one proposed roadmap change to Amara rather than accepting it. At the midpoint, maintenance questions were still reaching Lina; Amara corrected the queue routing with Jorge. The review does not claim delivery improvements or independent personnel-management experience.
Handback: Lina will send the returning lead the open labeling decisions, owners, unresolved dependencies and next review points by December 11. Ben retains release authority throughout. The returning lead will confirm receipt before assuming coordination on December 14; that receipt is still pending at this December 4 review, and Amara will cover any handback gap.
Original work: Jorge will return the maintenance queue with its outstanding items; Amara will reprioritize the deferred rendering experiment against current work before restarting it. Temporary planning-meeting ownership will return to the lead, and Amara will arrange removal of any assignment-specific access no longer needed.
Pay and records: the original written no-supplement decision remains unchanged; no temporary payment or new base rate is recorded. Amara will ask Saira to confirm the assignment's end in the applicable internal record. Administrative confirmation is pending until Saira responds.
Development follow-up: Lina and Amara will discuss feedback on technical coordination on December 18. That conversation is separate from any future recruitment or promotion process.
Notice that the record distinguishes a decision from an administrative confirmation still to come. It also preserves the workload problem found during the assignment alongside the observed coordination work, without inventing delivery improvements.
Handle extensions or permanent opportunities as new decisions
If the lead's absence continues, an extension should state revised dates, duties, coverage, authority, support and compensation treatment. Identify the required approvals and obtain an answer before relying on a new term. Lina's agreement does not silently renew because planning meetings remain on her calendar.
If the organization instead creates a permanent opening, ask about the actual appointment or selection process. Describe the acting work accurately if a permanent process requests evidence; its completion does not establish eligibility, selection or an appointment. Keep feedback about the work separate from a promise that the role will become yours.
Before accepting your own assignment, complete the record with the authorized owners and resolve the terms that matter to your decision. Put an end review on the calendar while the start is still being discussed. You should be able to explain what begins, what stops, who decides, and how you return. For more practical workplace conversations, visit LandOffer.ai.


