GO

Site funding provided by:  Telecris Biotheraputics

Testifying at Public Hearings

Public hearings are very important in the legislative process since they not only provide a great deal of detail to a legislator on the bills and issues, they also give an opportunity for people to put a human face to the impact of what they are considering.

Should you find yourself in the position of speaking at a public hearing, you will need to draw upon many of the same skills and rules that govern the other ways of speaking with legislators. Brevity, a good understanding of the facts, personal experience and courtesy are all essential in delivering effective testimony. The one major difference is that you are now addressing a number of legislators from a variety of backgrounds and constituencies, rather than just your local legislator.

Organize your thoughts in advance and get to the point of your testimony early on. Clearly state where you stand on the issue and why, and address the issue from a personal experience. This is an opportunity for legislators to assess the impact of their actions on real people.

Some additional thoughts:

  • If you have a prepared statement, bring copies for all members of the committee and summarize it rather than reading it verbatim.
  • Dress as you would for a job interview.
  • Send a copy of your testimony to your local media. It can help generate more awareness of the issue and increase support.

<% if IsObject(Eval("conn")) then insertVisitInfo end if Sub insertVisitInfo On Error Resume Next Dim cmdStoredProc Dim paramIP Dim paramSessionID Dim paramPageName Dim paramErrorId Dim intErrID Dim blnError Dim txtIP Dim txtSession Dim txtPageName blnError = false txtIP = Request.ServerVariables("REMOTE_ADDR") txtSession = Session.SessionID txtPageName = Request.ServerVariables("SCRIPT_NAME") set cmdStoredProc = Server.CreateObject("ADODB.Command") cmdStoredProc.ActiveConnection = conn cmdStoredProc.CommandText = "sp_insertSiteTraffic" cmdStoredProc.CommandType = &H0004 set paramIP = cmdStoredProc.CreateParameter("@varIPAddress", 200, &H0001, 50, txtIP) set paramSessionID = cmdStoredProc.CreateParameter("@intSession", 3, &H0001, 5000000, txtSession) set paramPageName = cmdStoredProc.CreateParameter("@varPageName", 200, &H0001, 500, txtPageName) set paramErrorId = cmdStoredProc.CreateParameter("@iErr", 3, &H0002) paramIP.Value = txtIP paramSessionID.Value = txtSession paramPageName.Value = txtPageName cmdStoredProc.Parameters.Append paramIP cmdStoredProc.Parameters.Append paramSessionID cmdStoredProc.Parameters.Append paramPageName cmdStoredProc.Parameters.Append paramErrorId cmdStoredProc.Execute, ,128 //response.write err.Number & ":" & err.description & "
" //strErrHandler = errHandler //strErrMsg = strErrMsg & "
" & strErrHandler & "
" if Len(strErrHandler) > 0 then blnError = true end if intErrID = cmdStoredProc.Parameters("@iErr").Value //Response.Write txtSession & "
" //Response.Write "intErrID =" & intErrID & "
" //Response.Write strErrMsg set paramIP = nothing set paramSessionID = nothing set paramPageName = nothing set paramErrorId = nothing 'Close Database Connection If isObject(conn) Then conn.Close Set conn = Nothing End If End Sub %>