1. John D’Ambrosia Recording Secretary, IEEE 802 LMSC jdambrosia@ieee.org
Motion Template
John D’Ambrosia
Recording Secretary, IEEE 802 LMSC

2. Purpose of this document
The purpose of a motion template is to improve the quality of the work of the EC
Used properly, these motion templates should result in the reduction of motions that are incomplete or ambiguous and the reduction of gratuitous variation
This should save time of all concerned in the preparation and debate of the motions

3. Normative status of these slides
It is anticipated that any motion templates adopted by the LMSC EC will have no normative effect. They might be included in the LMSC OM as an informative annex, or might be a stand-alone document.
Regardless, the existence of a template here does not preclude somebody from presenting an alternative form of motion intended to achieve the same effect. Hopefully EC members will view these templates as a useful tool and use and maintain wherever appropriate.

4. Scope of motion templates
There is no attempt to capture all possible motions. That would be a huge waste of time, and it would make it hard to use an over-extended document.
Also not included are procedural motions such as approval of the minutes and approval of the agenda made or entertained by EC officers.

5. Linguistic style of motion templates
A motion is an agreement by the EC to perform some action. There is no need to include “fluff” words that do not describe this action. The words “motion”, or “move”, need never appear in the motion itself. The word “approve” is only appropriate when that is the only action being performed.
For example: “Motion: the EC moves to approve sending …” should be written “Send …”

6. Tabular style of motion templates
Each type of motion is described by a table, illustrated on the next slide. Only the shaded part is shown to the EC (once shading is removed, of course) .
The rest of the material provides information that may be helpful as to when to use the motion, the applicable rules, and the definitions of the placeholders (“tags”) used in the motion.
Note that the “<“ and “>” are removed when the tags are filled in .
Note also text between “[“ and “[“ needs attention. Either delete the delimiters or delete the entire delimited text as appropriate to your context.

7. Format of a these motion template slides –
Only the yellow shaded part is shown to the EC (without shading). The rest of the slide is there for your information.
Motion Text
(include)
(Insert contents of this cell into your presentation)
Motion to be used – with fields to be filled in as necessary
Other Info
Supporting information, not part of motion,
but required to be shown to EC
Background
Background information regarding motion. Do not include with motion.
Rules Reference
Reference to appropriate rules. Do not include with motion.
Field Definitions
Fields noted in motion field are defined here.

8. Example Motion Template:
Motion Text
(include)
Approve submission of the following project(s) to ISO/IEC JTC/SC6 for adoption under the PSDO agreement
<project> …
[conditional on approval by the IEEE SASB]
[conditional on publication of approved standard]
Other Info
Background
Applies to:
A draft standard that has received [conditional] approval to proceed to RevCom, or
A standard that has been approved by the IEEE-SA standards board
Rules Reference
LMSC OM:“IEEE 802 LMSC communications with other standards bodies”
Field Definitions
<project> : The name of the project, or (in the case of a PAR) the anticipated name of the project. E.g. P802.11ba

9. Example Motion
The previous template, once the placeholders are replaced and the conditional parts removed looks like:
“Approve submission of the following project to ISO/IEC JTC/SC6 for adoption under the PSDO agreement
P802.11zz
conditional on approval by the IEEE SASB
conditional on publication of approved standard”

10. List of Motions Accepting a report
Adoption of standards under PSDO agreement
Approval of PAR and CSD (non-maintenance)
Approval of PAR and CSD (maintenance)
Approval of updated WG P&P
Approval of updated LMSC OM
Approval of updated Chair’s Guidelines
Approval to send a draft to RevCom
Approval to start sponsor ballot
Conditional approval to start sponsor ballot
Conditional approval to send a draft to RevCom
Confirm elected WG and TAG officers
Confirm appointed WG and TAG chair
Confirm EC appointed positions
Fee Waiver
Liaison statement from 802
Liaison statement from subgroup requiring sponsor approval
Liaison of drafts under PSDO agreement
Study Group formation
Study Group extension

11. Motion: Accepting a Report
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to accept the report of the <subgroup-name> in <doc-url>
Other Info (include)
Background
Applies to:
The output report of a subgroup/committee
Note any recommendations that require approval of the EC need to be presented as separate motions.
Rules Reference
Robert’s Rules - “Adoption or Acceptance of Reports”
Field Definitions
<subgroup-name>: The name of a subgroup of the sponsor (e.g., a WG, TAG, EC SC or EC SG)
<doc-url> A URL to a permanent location of the document

12. Motion: Adoption of standards under PSDO agreement
Motion Text
(include)
(Insert contents of this cell into your presentation)
Approve submission of the following project(s) to ISO/IEC JTC/SC6 for adoption under the PSDO agreement
<project> …
[conditional on approval by the IEEE SASB]
[conditional on publication of approved standard]
Other Info
Background
Applies to:
A draft standard that has received [conditional] approval to proceed to RevCom, or
A standard that has been approved by the IEEE-SA standards board
Rules Reference
LMSC OM - “IEEE 802 LMSC communications with other standards bodies”
Field Definitions
<project> : The name of the project, or (in the case of a PAR) the anticipated name of the project.

13. Motion: Approval of PAR and CSD (non-maintenance)
Motion Text
(include)
( copy contents of this cell into your presentation)
Approve forwarding <project #> PAR [modification] documentation in <doc-url> to NesCom
Approve CSD [modification] documentation in <doc-url>
Other Info
See <doc-url> for supporting documentation
In the WG, PAR (y/n/a): <y>,<n>,<a>; CSD (y/n/a): <y>,<n>,<a>
Background
Applies to:
PAR content for a non-maintenance PAR and a CSD document that have met the requirements for posting and review under “Procedure for PARs” in the LMSC OM.
A non-maintenance PAR is a new PAR, or a modification PAR that materially affects the functionality of the project.
Rules Reference
OM - “Procedure for PARs”
Field Definitions
<doc-url> A URL to a permanent location of the document

14. Motion: Approval of PAR and CSD (maintenance)
Motion Text
(include)
(Insert contents of this cell into your presentation)
Approve forwarding <project #> maintenancePAR [modification] documentation in <doc-url> to NesCom
Other Info
See <doc-url> for supporting documentation
In the WG, PAR (y/n/a): <y>,<n>,<a>; CSD (y/n/a): <y>,<n>,<a>
Background
Applies to:
PAR content related to a maintenance PAR that has met the requirements for posting and review under “Procedure for PARs” in the LMSC OM.
A maintenance PAR is a revision or extension PAR, or a modification PAR that does not materially affect the functionality of the project.
Rules Reference
OM - “Procedure for PARs”
Field Definitions
<doc-url> A URL to a permanent location of the document

15. Motion: Approval of updated WG P&P
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to approve [<doc-name>]<doc-url> as the new IEEE 802 LMSC Working Group Policies and Pro
Other Info
Background
Applies to: an updated WG P&P brought to the EC for approval under the process described in the subclause “Revision of the IEEE 802 LMSC Working Group Policies and Procedures” of the IEEE 802 LMSC Working Group Policies and Procedures.
Rules Reference
LMSC P&P - “Responsibilities of officers / Sponsor Chair”
Field Definitions
<doc-name> The name of a document, such as part of the URL.
<doc-url> A URL to a permanent location of the document

16. Motion: Approval of updated LMSC OM
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to approve [<doc-name>]<doc-url> as the new IEEE 802 LMSC Operations Manual
Other Info
Background
Applies to: an updated LMSC Operations Manual brought to the EC for approval under the process described in the subclause “Revision of the IEEE 802 LMSC OM” of the IEEE 802 LMSC Operations Manual.
Rules Reference
LMSC P&P - “Revision of the IEEE 802 LMSC OM”
Field Definitions
<doc-name> The name of a document, such as part of the URL.
<doc-url> A URL to a permanent location of the document

17. Motion: Approval to send a draft to RevCom
Motion Text
(include)
(Insert contents of this cell into your presentation)
Approve sending <project> <draft> to RevCom.
Other Info
<project> <draft> had <number>% approval at the end of the last sponsor recirculation ballot. [Subsequently <number> of the “no” voters changed their vote to “yes” resulting in an approval of <number>%.]
See <doc-url> for supporting documentation
In the WG (y/n/a): <y>,<n>,<a>
Background
Applies to: a project that has passed sponsor ballot with at least 75% approval and has completed any necessary recirculation ballots.
Rules Reference
SB OM - “Submission of proposed standards to the IEEE-SA Standards Board”
Field Definitions
<project> The name of the project, or (in the case of a PAR) the anticipated name of the project, e.g. P802.11ba.x
<draft> The identifying revision of the draft, e.g. D1.2
<doc URL> An URL to a permanent location of the document

18. Motion: Conditional approval to send a draft to RevCom
Motion Text
(include)
(Insert contents of this cell into your presentation)
Conditionally approve sending <project> <draft> to RevCom.
Other Info
<project> <draft> had <number>% approval at the end of the last sponsor recirculation ballot. [Subsequently <number> of the “no” voters changed their vote to “yes” resulting in an approval of <number>%.]
See <doc-url> for supporting documentation
In the WG (y/n/a): <y>,<n>,<a>
Background
Applies to: a project that has passed sponsor ballot with at least 75% approval and ballot resolution efforts have been substantially completed. See IEEE 802 OM 12. Procedure for conditional approval to forward a draft standard for the definition of "substantially complete" and for the required supporting documentation.
Rules Reference
SB OM- “Submission of proposed standards to the IEEE-SA Standards Board”
OM - “Procedure for conditional approval to forward a draft standard”
Field Definitions
<project> The name of the project, or (in the case of a PAR) the anticipated name of the project, e.g. P802.11ba.x
<draft> The identifying revision of the draft, e.g. D1.2
<doc URL> An URL to a permanent location of the document

19. Motion: Approval to start sponsor ballot
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to:
Approve sending <project> <draft> to Sponsor Ballot
Confirm the CSD for <project> in <doc-ref>
Other Info
<project> <draft> had <number>% approval at the end of the last WG recirculation ballot. [Subsequently <number> of the “no” voters changed their vote to “yes” resulting in an approval of <number>%.]
See <doc-url> for supporting documentation
In the WG
forwarding to sponsor ballot (y/n/a): <y>,<n>,<a>[;
confirmation of CSD (y/n/a): <y>,<n>,<a>]
Background
Applies to: a project that has passed WG letter ballot with at least 75% approval and has completed any necessary recirculation ballots.
Confirmation of the CSD is required for non-maintenance projects.
Rules Reference
SBOM - “Standards ballot by the Sponsor”
Field Definitions
<project> The name of the project, or (in the case of a PAR) the anticipated name of the project, e.g. P802.11ba.x
<draft> The identifying revision of the draft, e.g. D1.2
<doc URL> An URL to a permanent location of the document

20. Motion: Conditional approval to start sponsor ballot
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to:
Conditionally approve sending <project> <draft> to Sponsor Ballot
Confirm the CSD for <project> in <doc-ref>
Other Info
<project> had <number>% approval at the end of the last WG recirculation ballot. [Subsequently <number> of the “no” voters changed their vote to “yes” resulting in an approval of <number>%.]
See <doc-url> for supporting documentation
In the WG (y/n/a) : <y>,<n>,<a>
Background
Applies to: a project that has passed WG letter ballot with at least 75% approval and ballot resolution efforts have been substantially completed.
Rules Reference
SBOM - “Standards ballot by the Sponsor”
OM - “Procedure for conditional approval to forward a draft standard”
Field Definitions
<project> The name of the project, or (in the case of a PAR) the anticipated name of the project, e.g. P802.11ba.x
<draft> The identifying revision of the draft, e.g. D1.2
<doc URL> An URL to a permanent location of the document

21. Motion: Confirm appointed WG and TAG chair
Motion Text
(include)
(Insert contents of this cell into your presentation)
Confirm the following individual(s) to fill the indicated IEEE LMSC appointed positions:
names and position
Other Info
WG/TAG election count
Background
Applies to:
one or more WG or TAG chairs after appointment by the Sponsor chair
WG or TAG that is in hibernation
Rules Reference
WG P&P - “Election or Appointment of Officers”
Field Definitions

22. Motion: Confirm elected WG and TAG officers
Motion Text
(include)
(Insert contents of this cell into your presentation)
Confirm the following individual(s) to fill the indicated IEEE LMSC elected positions:
names, position
Other Info
WG / TAG election count
Background
Applies to: one or more elected WG or TAG officers (chair, vice chair) after election in the WG/TAG
Rules Reference
WG P&P - “Election or Appointment of Officers”
Field Definitions

23. Motion: Confirm EC appointed positions
Motion Text
(include)
(Insert contents of this cell into your presentation)
Confirm the following individual(s) to fill the indicated IEEE LMSC appointed positions:
names and position
Other Info
Background
Applies to:
one or more EC officers/members after appointment by the Sponsor chair
Rules Reference
LMSC P&P- “Election or appointment of Sponsor officers”
Field Definitions

24. Motion: Liaison statement from 802
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to approve <doc-url> as liaison to <liaison-to>, granting the IEEE LMSC chair (or his delegate) editorial license
Other Info
when liaison originated from a WG
In the WG (y/n/a): <y>, <n>, <a>] –
Background
Applies to: Outgoing liaison from 802
Rules Reference
LMSC P&P - “Sponsor Public Statements”
Field Definitions
<doc-url> An URL to a permanent location of the document
<liaison-to> Name of the organization to which the liaison is addressed.

25. Motion: Liaison statement from subgroup requiring sponsor approval
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to approve <doc-url> as liaison to <liaison-to>, granting the IEEE LMSC <subgroup-name> chair (or his delegate) editorial license
Other Info
In the WG (y/n/a): <y>, <n>, <a>
Background
Applies to: Outgoing liaison from a subgroup of 802 that requires sponsor approval
Rules Reference
Field Definitions
<doc-url> An URL to a permanent location of the document
<liaison-to> Name of the organization to which the liaison is addressed.
<subgroup-name> The name of a subgroup of the sponsor (e.g., a WG, TAG, EC SC or EC SG)

26. Motion: Liaison of drafts under PSDO agreement
Motion Text
(include)
(Insert contents of this cell into your presentation)
Approve liaison of the following draft(s) to ISO/IEC JTC1/SC6 for information under the PSDO agreement:
<project> <draft> …
When ballot of that draft is pending or current, add “[conditional on passing the[working group|sponsor] recirculation ballot”
Other Info
In the WG: <y>, <n>, <a>
Background
Applies to:
A draft of a standard that has been balloted, and passed its last ballot with at least 75% approval
When it is intended subsequently to use the PSDO process to approve the standard
Rules Reference
LMSC OM- “IEEE 802 LMSC communications with other standards bodies”
Field Definitions
<project> The name of the project, or (in the case of a PAR) the anticipated name of the project. E.g. P802.11ba.
<draft> The The identification of specific version of a draft – e.g. D10

27. Motion: Study Group formation
Motion Text
(include)
(Insert contents of this cell into your presentation)
Move to approve the formation of <wg-name> <sg-name> study group to develop a Project Authorization Request (PAR) and Criteria for Standards Development (CSD) responses.
If not obvious from SG-name, then add “[for <sg-brief-description-of-purpose>]” at end of motion.
Other Info
See <doc-url> for supporting documentation
Vote in the WG: <y>,<n>,<a>
Background
Applies to: Formation of a study group that is operating under a working group. May not be on the consent agenda. Supporting documentation is expected.
Rules Reference
SB OM - “Voting rules”
LMSC OM - “Project Authorization”
Field Definitions
<wg-name> The name of a working group or TAG
<sg-name> The name of a study group
<for <sg-brief-description-of-purpose> a description of the purpose of the study group if the name alone is not sufficient.

28. Motion: Study Group extension
Motion Text
(include)
(Insert contents of this cell into your presentation)
Grant the <ordinal> extension of the <wg-name> <sg-name> study group.
Other Info
See <doc-url> for supporting documentation
Vote in the WG: <y>,<n>,<a>
Background
Applies to: Extension of a study group that is operating under a working group. The extension applies until the end of the next LMSC plenary meeting.
First extension will be initially placed on the consent agenda, and does not need supporting documentation.
Rules Reference
SB OM - “Voting rules”
LMSC OM - “Project Authorization”
Field Definitions
<ordinal> Used in study group extensions to indicate first, second, third…
<wg-name> The name of a working group or TAG
<sg-name> The name of a study group

29. (Insert contents of this cell into your presentation)
Motion: Fee Waiver
Motion Text
(include)
(Insert contents of this cell into your presentation)
Confirm meeting fee waivers for the <date-of-session> LMSC session for the following individuals:
<list of names here>
Other Info
The purpose of the fee waiver should be described.
Background
Rules Reference
LMSC Chair’s Guidelines: “Registration”
Field Definitions

30. Motion: Approval of updated Chair’s Guidelines
Motion Text
(include)
(Insert contents of this cell into your presentation)
Other Info
Background
The purpose of the chair’s guidelines is described
Rules Reference
LMSC OM “In order to maintain some consistency of operation, the Sponsor Chair may maintain a public document to be called the "IEEE 802 LMSC Chair's Guidelines and EC policy decisions"”
There is no requirement that the EC approve updates to the Chairs’ guidelines, and nothing that precludes the chair seeing EC approval.
Field Definitions

31. Related rules documents
Version
Roberts Rules
No specific version cited. Old version is available online.
OM (LMSC Operations Manual)
V1.9
Chair’s Guidelines
Note, this is not really a rules doc – see introduction in LMSC OM.
V2.3
SB OM (IEEE-SA Standards Board Operations Manual)
December 2015
WG P&P (Policies and Procedures for IEEE LMSC 802 Working Groups and Technical Advisory Groups)
V19 (July 2016)
LMSC P&P (IEEE 802 LAN/MAN Standards Committee Policies and Procedures)
June 2014