ATI Communication Vehicles
This section describes the types of communication channels available, and how they will be used
for this project.
Vehicles
Comments / Usage
Current
Suggested



Core Team Status
Meetings


ATI Steering Team Meetings – bimonthly or as needed
ATI Workgroups are also held for the
three priorities:
o Web Accessibility
o Instructional Materials
o IT Procurement
Biweekly meetings between ATI
Project Coordinator and IM
Specialist, Web Accessibility
Specialist
ATI specialists (Instructional
Materials, Web, and Procurement)
should begin meeting to discuss
areas progress etc.





Core Team Meeting
Minutes
Weekly Status Report



Steering Team minutes/agenda
Workgroup minutes
ATI Shared drive and SharePoint:
track documents, tasks, etc.

Instructional Materials Specialist and
Web Accessibility Specialist and ATI
Procurement Specialist provide
weekly reports to direct supervisor
and discuss items completed with
ATI Project coordinator during


Scheduled bi-weekly,
includes dial-in access.
Primary audience
includes Core Project
Team members.
Provides forum to
discuss status, issues,
strategies, and other
information relevant to
most or all Technical
Teams.
Provides interface
between this project
and external
organizations,
including peer project
teams (e.g. UCPD).
Not intended as a
working session to
address specific topics
in detail.
May be supplemented
with "ad hoc" working
session meetings with
limited audience if
needed.
Documents decisions
and action item
assignments from Core
Team meetings.
Facilitates
communication with
team members (Core
Team and others) who
were unable to attend
the Core Team
meeting but interested
in discussions and
outcomes.
Provides summary
information on project
status and issues,
focusing on
quantitative rather than
qualitative status.
1






Technical Team
Meetings





E-mail


Project Intranet Web
Site

weekly/bi-weekly meetings. Weekly
report can be seen in electronic copy
as well.
ATI Project Coordinator provides biweekly status updates to ATI
Executive Sponsor and discuss any
issues or information of interest
Yearly Status Reports are provided
to the Chancellor’s Office for all three
priority areas
Executive Summary of three areas
for Executive Sponsor
IMAP, Web, and Procurement
Workgroup Meetings – monthly or as
needed
CSU ATI Training Task Force
Meetings—weekly or as needed
ATI Training Taskforce minutes are
available through shared resource
(basecamp) as well as any meeting
agenda, minutes, milestone, to do list
items, and other important
documents.
Other Technical Team Meetings that
are impacted by Accessibility may
include Web Coordinators, My Sac
State uPortal team, and others
CSU systemwide Communities of
Practice meetings for three priorities
(Web, Instructional Materials,
Procurement) – monthly via
phone/Elluminate
Email used between ATI Project
Coordinator and ATI staff positions
ATI email ati@csus.edu – campus
community can inquire about ATI or
about accessibility in general at this
email address
Campus IT-listserv and Web
coordinators listserv
In the future there may be a need for
an individual email related
specifically to web accessibility, E&IT
procurement accessibility, and
instructional materials support.
Currently Instructional Materials
specialist, Procurement Specialist
and Web Accessibility specialist
receive ati@csus.edu email directly
to personal Saclink email account.
The Shared drive - ATI on ‘Sacfiles’
for ATI project staff
SharePoint on ATI
https://sacshare.csus.edu/ADMIN/IR

Provides advance
notification of nearterm upcoming events,
as well as other
information of general
interest.

Scheduled weekly or
as needed, may
include dial-in access.
Includes members of
specific Technical
Teams
Provides forum for indepth planning, status
reporting, and
discussion of topics
specific to a single
team.
Provides
communication
between Core Team
and other project
participants.






At the project level,
provides primary
distribution mechanism
for Core Team meeting
minutes,
announcements, status
reports, newsletters
and more.
For Technical Teams,
supplements meetings
as method of
distributing information
and resolving
questions / issues.
A general-purpose
information resource
containing project
planning documents,
2
T/ati/ can be used as a form of ATI
project intranet web site at
Sacramento State because we can
house documents, tasks, team
discussions, meeting minutes, etc.



Project Newsletter





Periodic Project
Reviews / Events






Website

ATI Newsletter issued yearly. ATI
Steering team, SSWD, ATCS, IRT
and others all participated in
submitting content for newsletter.
Newsletter and news and events are
available on Accessibility web page
csus.edu/accessibility
Newsletter mailed directly to
departments and/or linked from
Bulletin Newsletter page. Also
handed out during key events: New
Faculty Orientation, Technology Fair,
etc. Also made available upon
request.
IRT Newsletter & other newsletters
will also have articles about the ATI.
ITC Liaison Meetings held monthly
every second Wednesday. ATI
announcements can be made at
these meetings.
Teaching using Technology
Business Partners Roundtable
Meetings are held bi-monthly. ATI
announcements can be made at
these meetings.
Faculty Senate’s Academic
Information Technology Committee
and other meetings held monthly.
ATI Regional Meetings co-sponsored
by Chancellor’s Office
Other Chancellor’s Office sponsored
events (e.g. CSUN reception, ATI
Regional training)
ATI Forums
Other events
Sacramento State Accessibility
website www.csus.edu/accessibility
provides ATI Project information on
all three priorities, links to training
support resources, updated
regularly.
Other events may be posted on Sac
State home page, News, Bulletin, etc









current status
information, current
issues, meeting
minutes, and most
other formal
documents produced
during the course of
the project.
Updated no less than
once weekly with latest
information.
Distributed regularly
via e-mail and intranet
site.
Used to provide
general information
(high-level status, etc.)
to stakeholders who
are not direct
participants.
Targets stakeholders
who may not receive or
be willing to review
more detailed
information.
Held "as needed" but
no less than once
every two months.
Used to provide
general information
(status, etc.) to
stakeholders who are
not direct participants.
Targets stakeholders
who may not receive or
be willing to review
more detailed
information.
Facilitates informal
communication
between those who
might not otherwise
have an opportunity to
interact outside of
project meetings.
Website available to
employees & students.
May be used to provide
general interest news
releases or to publicize
occasional highinterest or potentially
high-impact events.
3
Communication Matrix
The sample table below maps communication vehicles to various stakeholder groups.
Communication
Vehicle
Core Team
Status Meetings
Core Team
Meeting Minutes
Weekly Status
Reports
Technical Team
Meetings
E-Mail
Project Intranet
Site
Monthly
Newsletter
Project Reviews
Social Events
Core
Project
Team
Other
Functional Impacted
Team
Managers Employees
Members
Business /
Application
Reps
Peer
Executive
Project
Management
Teams
P
S
S
X
X
S
P
P
S
S
S
S
S
P
P
P
S
S
S
S
X
S
P
S
S
P
S
X
P
P
S
S
S
S
S
P
P
P
P
P
P
S
S
S
P
P
P
P
P
S
S
S
S
P
P
S
P
P
P
P
P
P
S
P = Primary Target
S = Secondary Target
X = Not applicable
4