Ontario board sent a new AI guidance memo, anyone parse this yet
our board sent out a memo this week updating our AI guidance for the year and honestly i’ve read it three times and i’m more confused than when i started. one section says teachers should encourage ‘responsible experimentation’ with AI tools. two paragraphs later it says any undisclosed AI assistance is a violation of academic integrity policy subject to discipline.
nobody defines what counts as experimentation versus assistance. is a student trying chatgpt to see what it says about a topic experimentation? is using it to check their grammar assistance? the memo doesn’t say, and i don’t think whoever wrote it actually tried to apply it to a real assignment before sending it out.
meanwhile we’re supposed to explain this clearly to 30 teenagers who will absolutely find the loophole in the vague language faster than any adult in the building. anyone else’s board sent something similarly contradictory this fall? how are you translating it into something actually usable in your classroom?
1,020 Replies
Join the discussion.
Log In to Reply
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.
ban doesn't work, redesign does, but neither works if the policy itself is contradictory before you even start redesigning anything. Ray's suggestion to write your own operational definition is the right move, don't wait on the board to fix their own memo.
no policy is a policy, and a contradictory policy is functionally no policy too. write your own like Ray said.
drafting my own version this weekend based on what Ray suggested. will bring it to our department meeting and see if others want to adopt something similar rather than each of us guessing individually.
this contradiction you're describing is more common than boards want to admit, and its exactly the kind of gap that becomes a real liability the first time a case gets challenged formally. i'd recommend not waiting for the board to clarify, write your own classroom level definition of experimentation versus assistance, share it with your department head for sign off, and use that as your operating document. its not perfect but it beats operating on a memo that contradicts itself.