MLDR 6175 Week 9 Working Agreement Draft Example

Course	MLDR 6175 Managing, Mediating, and Resolving Conflict
Week	Week 9
Paper type	Agreement draft
Length	About 680 words, 5 pages
Format	APA 7 student paper
School	Walden University
Program	MS in Leadership
Updated	October 2026

Free sample paper for MLDR 6175 Week 9

Working Agreement Between Production and Development: Defined Terms, a Calendar Lock Date, Limits on Events During Technical Periods, a Named Calendar Owner and a Loop-Back Step Before Escalation

Student Name

Walden University

MLDR 6175: Managing, Mediating, and Resolving Conflict

Instructor Name

Month Day, Year

What this page is doingThe title lists the agreement's clauses in order and makes clear it is an internal working document.

Working Agreement Between Production and Development: Defined Terms, a Calendar Lock Date, Limits on Events During Technical Periods, a Named Calendar Owner and a Loop-Back Step Before Escalation

Status of This Agreement

This is an internal working agreement between the Production Department and the Development Department of Lantern Hall Theater Company. It is not a legal contract. It records how the two departments will share the main stage, as agreed by the production manager and the development director following the mediation of August 26, and it takes effect when both sign below and the managing director acknowledges it. Brett et al. (1990) argue that dispute systems work best when they route disagreements first to the parties' own negotiation and offer a way back to it, rather than escalating straight to a ruling. This agreement is built on that principle.

What this page is doingThe agreement says what it is not, so no one mistakes an internal working document for a contract.

1. Definitions

1.1 Main stage means the 640-seat auditorium, its stage, wings, fly system and the backstage areas used by production.

1.2 Technical period means the days on which technical rehearsals are scheduled for a mainstage production, beginning with the first day of technical rehearsal and ending with the final dress rehearsal.

1.3 Calendar lock means the date after which the season calendar for the main stage may be changed only under clause 5.

1.4 Outside event means any use of the main stage other than rehearsal or performance of a scheduled production, including galas, receptions, rentals and tours.

2. Calendar Lock

2.1 The main stage calendar for each season locks on April 1 of the preceding spring.

2.2 Before lock, production will enter the planned technical period for each mainstage production, and development will enter planned outside events.

3. Outside Events During Technical Periods

3.1 No outside event will use the main stage during a technical period without the written consent of both the production manager and the development director.

3.2 Development may hold up to two donor open rehearsals per season, at a final dress rehearsal or first preview, under the stage manager's rules for audiences.

3.3 Production will not withhold consent under 3.1 for events that require no scenery moves and take place outside rehearsal hours, unless the production manager states a safety reason in writing.

What this page is doingEach obligation names a party and a trigger, so a reader can tell who must do what and when.

4. Calendar Owner

4.1 The company manager keeps the single main stage calendar. No department may book the main stage except through the company manager.

4.2 The company manager will notify both department heads in writing of any overlap within five working days of its appearing on the calendar.

5. Changes After Lock

5.1 Either department may request a change after lock by writing to the company manager and the other department head.

5.2 The other department head will respond within ten working days. If both agree, the company manager updates the calendar.

6. Loop-Back Before Escalation

6.1 If the department heads disagree about any matter under this agreement, they will meet within ten working days, with the general manager present if either asks.

6.2 Only if that meeting does not resolve the disagreement will either head refer it to the managing director.

7. Review

7.1 The two heads will review this agreement each June, after the season ends, and may amend it in writing.

Signatures

Production manager: Owen Brandt. Date: September 4.

Development director: Celia Marsh. Date: September 4.

Acknowledged by the managing director: Paul Ainsley. Date: September 8.

Drafting Notes

Definitions come first because the original dispute turned on words each side read differently, especially "technical period," which development understood as weekday rehearsal hours and production as the whole week. Each obligation sits in its own clause with a named party, in the active voice, so responsibility is clear. Clause 3.3 limits production's power to refuse events; without it, the agreement would hand production a veto. Fisher et al. (2011) recommend agreements built on objective criteria, and the safety reason in writing serves that function. The loop-back clause reflects the cost of the August dispute, which went to the managing director before the two heads had met; disputes settled by rank tend to return (Ury et al., 1988).

References

Brett, J. M., Goldberg, S. B., & Ury, W. L. (1990). Designing systems for resolving disputes in organizations. American Psychologist, 45(2), 162-170. https://doi.org/10.1037/0003-066X.45.2.162

Fisher, R., Ury, W., & Patton, B. (2011). Getting to yes: Negotiating agreement without giving in (3rd ed.). Penguin Books.

Ury, W. L., Brett, J. M., & Goldberg, S. B. (1988). Getting disputes resolved: Designing systems to cut the costs of conflict. Jossey-Bass.

What the MLDR 6175 Week 9 instructions ask for

Week 9 asks you to draft an agreement that resolves the conflict in your case. State plainly what kind of document it is and who it binds. Define the terms that caused the dispute before writing any obligations. Write each obligation as its own numbered clause, in the active voice, with a named party and a date or trigger. Name who owns any shared resource. Include a procedure for changes and a step that sends disagreements back to the parties before anyone escalates. Add a review date and signature lines. Close with brief drafting notes explaining your main choices, especially any clause that limits one party's power.

Inside the MLDR 6175 Week 9 example

The draft opens with a status statement and cites Brett and colleagues on routing disputes back to the parties. Seven numbered sections follow: definitions, calendar lock, outside events during technical periods, calendar owner, changes after lock, loop-back before escalation and annual review. Clause 3.3 limits production's power to refuse events that need no scenery moves. Signature lines for both heads and an acknowledgment by the managing director close the agreement. Drafting notes explain why definitions come first, why clauses use the active voice, why 3.3 prevents a veto and why the loop-back exists, citing Fisher and colleagues and Ury and colleagues. Signatures from both heads and an acknowledgment from the managing director make clear who is bound.

Where the marks sit in the MLDR 6175 Week 9 rubric

Agreement drafts earn credit for clarity and enforceability. Defining disputed terms before any obligation is weighted heavily because ambiguity caused the original conflict. One obligation per clause, with a named party and a date or trigger, shows careful drafting. Naming an owner for the shared resource addresses the process conflict directly. A loop-back step and a change procedure show the agreement is designed for future disagreements. Balancing clauses that prevent either party from gaining a veto demonstrates fairness. Drafts written in the passive voice, left undated or presented as legally binding when they are not tend to receive lower marks. Drafting notes that explain each balancing clause help a reader see why the agreement is fair to both sides.

MLDR 6175 Week 9 help: mistakes that cost marks

List the words that caused confusion in your dispute and define each one precisely before you write anything else. Then write each obligation in a separate clause that names who must do what and by when. Read each clause as the party who would least like it and ask whether it could be read two ways; if so, rewrite it. Add a clause that says what happens when people disagree under the agreement, and make the first step a conversation between the parties. Students often write agreements in general language such as "the departments will cooperate," which settles nothing. If your clauses keep turning into paragraphs, our writers can help you break them into single obligations.

Get a MLDR 6175 Week 9 example written to your instructions

Send the Week 9 prompt and rubric with the dispute and any earlier analysis the agreement should follow, and a clause-by-clause draft returns inside 24 to 48 hours, free on the opening request. Agreements between two individuals rather than two departments go through the same tests, with the definitions adjusted to their situation.

More MLDR 6175 papers and MS in Leadership samples

MLDR 6175 Week 9 questions, answered

Where can I find a free MLDR 6175 Week 9 sample paper?

The full working agreement and its drafting notes are open to read below at no charge.

What kind of document is the MLDR 6175 Week 9 draft?

An internal working agreement between two departments, not a legal contract.

Which terms does it define?

Main stage, technical period, calendar lock and outside event.

Who keeps the calendar?

The company manager, who must notify both heads of any overlap within five working days.

What happens when the heads disagree?

They meet within ten working days before either can refer the matter to the managing director.