ADUD is seeking a SharePoint information-architecture specialist to organize and standardize the structure of AICE, our existing Microsoft 365 internal information and collaboration environment.
AICE already contains institutional content and workspaces supporting Board/Trustees, committees, operations, programs and projects, volunteer resources, training, finance, communications, partnerships, compliance, IT/support, and other organizational functions. ADUD has also completed or is completing broader assessment and target-architecture work for the environment.
This project will translate that direction into a practical and reusable information architecture for SharePoint: how AICE content should be organized, named, classified, owned, stored, archived, and found.
The volunteer will help ADUD rationalize navigation, site/workspace relationships, taxonomy, metadata, naming conventions, document and content classifications, library structures, ownership, and current-versus-archived content rules. The project should preserve useful existing institutional content while reducing ambiguity about where information belongs and how future content should be organized.
The objective is to establish a consistent structural foundation that later AICE projects can use for homepage and role-based gateway development, workflow automation, dashboards/reporting, and governance/administration.
This project is focused on information architecture and SharePoint structural standards. It does not include homepage construction, dashboard development, workflow automation, comprehensive governance policies, administrator/user manuals, or organization-wide training.
By the end of this project, ADUD wants a clear, reusable information architecture for AICE that can guide later homepage, automation, dashboard, and governance work.
The volunteer will:
1. Develop an approved AICE navigation and site/workspace map covering Governance, Committees, Operations, Programs/Projects, People/Volunteer Operations, Finance, Communications, Partnerships, Compliance, IT/Support, and Knowledge/Records.
2. Create an information-architecture standard covering sites/workspaces, libraries, lists, folders vs. metadata, naming, content classifications, current/archive distinctions, source-of-record principles, and content-placement rules.
3. Define a taxonomy and metadata framework with required/optional fields, standardized labels, document categories, functional/program classifications, ownership fields, lifecycle/status fields where appropriate, and conventions supporting future search, automation, and reporting.
4. Create a reusable SharePoint library/workspace pattern covering structure, metadata, views, navigation placement, ownership, and archive handling.
5. Produce a content-placement map showing where major content categories belong, who owns them, and whether they are active, reference, or archived.
6. Create an ownership and content-stewardship matrix identifying business, site/library, content, and technical-support responsibility.
7. Provide a concise implementation specification documenting approved standards, dependencies, assumptions, configuration recommendations, and unresolved items.
Success means ADUD has a documented, understandable, reusable SharePoint structure that future AICE projects can implement without reconstructing the logic.
Out of scope: homepage/gateway build, dashboards/Power BI, workflow automation, comprehensive permissions redesign, formal governance policies, administrator/user manuals, training, Secure Workspace implementation, wholesale migration/deletion, or ongoing Microsoft 365 administration.