diff --git a/board-procedures/non-voting-resource-members.tex b/board-procedures/non-voting-resource-members.tex
new file mode 100644
index 0000000..2a516c2
--- /dev/null
+++ b/board-procedures/non-voting-resource-members.tex
@@ -0,0 +1,49 @@
+\section{Non-voting resource members}
+\emph{effective [at time of ratification]; new}\\
+
+\subsection{Purpose}
+
+There are often occasions where it is valuable to the Board to 
+extend membership to non-voting resource members. While some such 
+non-voting members are defined elsewhere (e.g. the Council Speaker) 
+or externally (e.g. the Dean's Delegate), some have no external reference. 
+This procedure provides a central definition for any 
+internally-defined non-voting resource members of the Board.
+
+Any additions or removals to the list of non-voting resource members of the Board 
+must still be ratified within Bylaw 6.2.
+
+\subsection{Lead, Infrastructure}
+
+\subsubsection{Appointment}
+
+In the event that the Lead, Infrastructure role is vacant, a new 
+Lead, Infrastructure shall be appointed by the Board of Directors 
+of the Society at the first Board meeting of the term. 
+
+The Lead, Infrastructure should be appointed for a 1-year term.
+
+\subsubsection{Responsibilities}
+
+The Lead, Infrastructure is intended to be the single individual responsible for 
+MathSoc's technical infrastructure.
+
+As the primary developer of the MathSoc Website, the Lead, Infrastructure will:
+\begin{enumerate}
+  \item In coordination with the Website Committee, determine the 
+  direction of the new website and the feasibility of new requested functionalities.
+  \item Monitor MathSoc infrastructure to ensure continued uptime, especially during high-usage periods 
+  \item Support any additional volunteer web developers and content 
+  maintainers working on the MathSoc website
+  \item Support and enable the Vice President, Communications in making simple 
+  content updates to the MathSoc website
+\end{enumerate}
+
+Further, as the organization's primary infrastructural point of contact, the Lead, Infrastructure will:
+\begin{enumerate}
+  \item Support members of Council and Board with infrastructural concerns
+  \item Manage lines of communication with external partners, such as IST and MFCF 
+  \item Maintain clear documentation and lines of communication to support future Leads, Infrastructure.
+\end{enumerate}
+
+
diff --git a/board-procedures/public.tex b/board-procedures/public.tex
index 14e8a67..2b91bcd 100644
--- a/board-procedures/public.tex
+++ b/board-procedures/public.tex
@@ -33,6 +33,7 @@
 \input{rentals.tex}
 \input{trainings.tex}
 \input{website.tex}
+\input{non-voting-resource-members.tex}
 
 %%% Appendices
 \appendix
diff --git a/board-procedures/website.tex b/board-procedures/website.tex
index beae2d1..0c8d451 100644
--- a/board-procedures/website.tex
+++ b/board-procedures/website.tex
@@ -1,30 +1,31 @@
 \section{Website Committee}
-\emph{effective July 24, 2024; new}\\
+\emph{effective [at time of ratification]; updated}\\
 
 \subsection{Composition and Selection of Members}
 
 The membership of the committee shall be:
 \begin{enumerate}
-	\item Two (2) current voting members of the Board of Directors;
-	\item One (1) current voting member of Council;
-	\item At least one (1) lead web developer;
+	\item The Lead, Infrastructure
+  \item Two additional current voting members of the Board of Directors;
 	\item The Vice-President, Communications; and
 	\item The Business Manager.
 \end{enumerate}
 
-Directors and Councillors shall be appointed by their respective governing bodies.
-Lead web developer appointments shall be made by the committee, and ratified by the Board of Directors.
-Should a Director or Councillor seat become vacant, the respective governing body shall appoint a replacement at their earliest convenience.
+Members shall be appointed by the Board of Directors.
+
+Should a Director seat become vacant, the respective governing body shall appoint a replacement at their earliest convenience.
 
 The Board of Directors shall appoint one Director to serve as the Chair of the Committee.
-Directors and Councillor(s) who are also lead web developers may sit with a dual mandate, thus satisfying two membership requirements.
+The Director, Infrastructure may sit with a dual mandate, thus satisfying two membership requirements.
 
-All members, with the exception of the Councillor(s) and the Vice-President, Communications, shall serve on the committee for a period of at least eight (8) months or until they leave their position, whichever is first.
+All members, with the exception of the Vice-President, Communications, 
+shall serve on the committee for a period of at least eight (8) months 
+or until they leave their position, whichever is first.
 
 \subsection{Meetings}
 
-The committee shall meet at least once a month.
-Meetings may be called by the Chair of the Committee, or upon the written request of any two members.
+The committee shall meet as they determine necessary. Meetings may be called by 
+the Chair of the Committee, or upon the written request of any two members.
 
 \subsection{Powers and Duties}
 
@@ -32,16 +33,18 @@ \subsection{Powers and Duties}
 
 \begin{enumerate}
   \item Provide stable long-term guidance for the overall direction and development of the MathSoc website;
-  \item Oversee the hiring and direction of MathSoc’s web developers, in collaboration with the Vice President, Communications;
-  \item Hire lead web developers to be primarily responsible for website development;
+  \item Seek out and reccommend candidates for the Lead, Infrastructure role
+  \item In collaboration with the Lead, Infrastructure and Vice President, Communications, 
+  oversee the hiring and direction of any additional web developers;
   \item Manage solicited website feedback and incorporate it into the direction of the website;
-  \item Report hiring updates to the Board of Directors by no later than the second Board meeting of every term; and
-  \item Report development progress to the Board of Directors at the final Board meeting of every term.
+  \item Report development progress to the Board of Directors at the second Board meeting of every term.
 \end{enumerate}
 
-Web developers shall be operationally and administratively overseen by the Vice President, Communications, but are ultimately subordinate to the committee.
+Web developers including the Lead, Infrastructure, shall be operationally and administratively overseen 
+by the Vice President, Communications, but are ultimately subordinate to the committee.
 
-Although members may conduct the below activities independently from the committee according to their individual mandates, the committee as a whole shall not:
+Although members may conduct the below activities independently from the committee 
+according to their individual mandates, the committee as a whole shall not:
 \begin{enumerate}
   \item Manage website content;
   \item Manage detailed requirements; or
diff --git a/bylaws/content/board.tex b/bylaws/content/board.tex
index 8d557ae..2b89471 100644
--- a/bylaws/content/board.tex
+++ b/bylaws/content/board.tex
@@ -40,6 +40,7 @@ \subsection{Composition}
   \item The Business Manager, as defined in this document;
   \item The President of the Federation of Students, or designate; and
   \item The Dean of the Faculty, or designate.
+  \item Additional non-voting resource members as defined in Board Procedure 21
 \end{enumerate}
 
 If a person qualifies as both a voting and non-voting member of the Board of