From 994b33bc4d6c1c250e2a58e262c900c4e553a823 Mon Sep 17 00:00:00 2001 From: "Andrew Dunkman (he/him)" Date: Fri, 3 Jan 2025 12:51:00 -0500 Subject: [PATCH 1/5] Adjust organization of TTSC Tock page (#4052) --- .../tts-consulting/operations/tock.md | 94 ++++++++----------- 1 file changed, 41 insertions(+), 53 deletions(-) diff --git a/pages/about-us/tts-consulting/operations/tock.md b/pages/about-us/tts-consulting/operations/tock.md index effcf2693..817de4453 100644 --- a/pages/about-us/tts-consulting/operations/tock.md +++ b/pages/about-us/tts-consulting/operations/tock.md @@ -3,10 +3,29 @@ title: Tracking your time and using Tock cspell: ignore Nonbillable, Tocks --- -## How should TTSC staff allocate our time? +Tock is a different tool than [HRLinks](https://hrlinks.gsa.gov/). Here is a quick comparison: + +| | Tock timesheet | HRLinks timesheet | +|--|----------------|-------------------| +| **Level** | TTS | GSA | +| **Cadence** | Weekly | Bi-weekly | +| **Goal** | Tracks how time is spent, so we bill partners appropriately | Tracks how much an employee is working, so we track leave appropriately | +| **Timesheet shows** | How time is spent within a given week (billable and nonbillable) | How much time was spent working within a pay period, and what kind of leave was taken (sick, annual, award, admin, etc.) | + +## Billable expectations + +{% alert %} + Failing to Tock on time prevents Operations from running financial reports and creates a lot of work for other people. Please make sure you Tock before you end your workday on Friday. If Friday is a holiday, then you’ll be expected to complete your timecard by the first workday following. + + Timecards for the current week should be available no later than Monday at 9AM PST. +{% endalert %} TTSC employees are expected to bill a certain amount of hours towards assigned billable projects each week. TTSC does not penalize employees for lower utilization if they haven’t been assigned billable work. +- **All TTSC employees** are expected to Tock weekly by COB (close of business) each Friday, and submit HRLinks timesheets every two weeks. +- **Supervisors** are responsible for [checking hours logged by their direct reports in Tock](#supervisor-review), including billable and nonbillable time. They also approve HRLinks timesheets every two weeks. +- **AM/EL/EMTs** review and approve time billed to engagements on a monthly basis via the engagement Tock report. + Supervisors’ utilization expectations are based on the number of direct reports, detailed in the table below: | Number of direct reports | Utilization % target | Target hours | @@ -18,14 +37,14 @@ Supervisors’ utilization expectations are based on the number of direct report | 1-3 | 65% | 20-26 hours | | 0 (individual contributors) | 80%+ | 32+ hours | -## What is billable? What is not billable? +### What is billable? What is not billable? What codes do I use? Generally: - **Billable time** = Work that enables engagement delivery - **Nonbillable time** = Indirect work that does not provide direct value to engagement delivery -### Billable time +#### Billable time You must bill all time that is a direct cost to a project. This includes: @@ -47,7 +66,7 @@ You must bill all time that is a direct cost to a project. This includes: Sometimes internal TTSC meetings provide direct value to your engagement and can be billed — for example, a discussion with your supervisor about a deliverable, attending a guild session where you learn tips for your current ATO process, or getting feedback in a critique group. Talk to your supervisor if you’re unsure if an activity is billable or not billable. -#### Billable TTSC Tock codes +##### Billable TTSC Tock codes We are in the process of consolidating nonbillable codes across TTSC, but for now please continue to use the appropriate codes for your team: @@ -58,7 +77,7 @@ We are in the process of consolidating nonbillable codes across TTSC, but for no | **Fully reimbursable details.** If a detail is not fully reimbursable, talk to leadership first. | ? | 1995 | | **Helping TTS/GSA.** If you are asked to assist with any hiring or support activities outside of 18F/CoE, please talk to your supervisor. They can advise you on the proper code and billability. | Ask supervisor | Ask supervisor | -### Nonbillable time +#### Nonbillable time {% alert %} Supervisors will review other non-billable circumstances and provide further guidance. Ask your supervisor if you are unclear what to bill. @@ -75,7 +94,7 @@ You must not bill for the following activities because these are indirect costs - Performance reviews - New hire onboarding -#### Common nonbillable TTSC Tock codes +##### Common nonbillable TTSC Tock codes We are in the process of consolidating nonbillable codes across TTSC, but for now please continue to use the appropriate codes for your team: @@ -100,59 +119,32 @@ We are in the process of consolidating nonbillable codes across TTSC, but for no | **Non-reimbursable details.** Talk to leadership before taking non-reimbursable details and for guidance on how to report the time. | Ask leadership | Ask leadership | | **Helping TTS/GSA.** If you are asked to assist with any hiring or support activities outside of 18F/CoE, please talk to your supervisor. They can advise you on the proper code and billability. | Ask supervisor | Ask supervisor | -## Frequently asked questions - -### About Tock and time tracking - -#### What is Tock and why do we use it? - -Tock is a different tool than [HRLinks](https://hrlinks.gsa.gov/). Here is a quick comparison: - -| | Tock timesheet | HRLinks timesheet | -|--|----------------|-------------------| -| **Level** | TTS | GSA | -| **Cadence** | Weekly | Bi-weekly | -| **Goal** | Tracks how time is spent, so we bill partners appropriately | Tracks how much an employee is working, so we track leave appropriately | -| **Timesheet shows** | How time is spent within a given week (billable and nonbillable) | How much time was spent working within a pay period, and what kind of leave was taken (sick, annual, award, admin, etc.) | - -#### Who is responsible for time tracking? - -- **All TTSC employees** are expected to Tock weekly by COB (close of business) each Friday, and submit HRLinks timesheets every two weeks. -- **Supervisors** are responsible for checking hours logged by their direct reports in Tock, including billable and nonbillable time. They also approve HRLinks timesheets every two weeks. -- **AM/EL/EMTs** review and approve time billed to engagements on a monthly basis via the engagement Tock report. - -#### How and when do I log my time in Tock? - -The weekly time reporting period lasts one week, beginning on Sunday and ending on Saturday. You must review and submit your timecard each week by the end of the day (close of business) on Friday. When submitting your timecard, choose the correct week for your entries from the list on the homepage, adjust your Tock entry to reflect how you spent your time, and then submit your timesheet. +### Where do I go for guidance on specific Tocking activity? -Failing to Tock on time prevents Operations from running financial reports and creates a lot of work for other people. Please make sure you Tock before you end your workday on Friday. If Friday is a holiday, then you’ll be expected to complete your timecard by the first workday following. - -Timecards for the current week should be available no later than Monday at 9AM PST. - -#### Where do I go for guidance on specific Tocking activity? - -##### For billable engagement work +#### For billable engagement work The AM/EL is your first point of contact regarding Tock guidance. If the activity is still in question or is not related to a specific engagement, escalate up to the supervisor, and then your director for further guidance. If you ARE the AM/EL, go to your Supervisor. -##### For non-billable Work +#### For non-billable Work Your supervisor is the first point of contact regarding Tock guidance on non-engagement work. -### Working more than 40 hours +## Working more than 40 hours -#### Can I Tock more than 40 hours in a week? +### With an Alternate Work Schedule (AWS) -We can’t work more than 40 total hours without being compensated for that time. Working overtime without prior approval violates the [Antideficiency Act](https://www.gao.gov/legal/appropriations-law/resources). +Tock will limit you to 40 hours per week by default. Please request an alternative work schedule in {% slack_channel "tock" %} if you are on an AWS. You do not need to do this if you are on a flexible week schedule. -If you find yourself needing to work more than 40 hours, here are the steps to take *before* you work any extra hours. +### With a standard working schedule -{% alert %} - If you have an established Alternate Work Schedule (AWS), your situation may be [slightly different](#how-does-aws-impact-how-i-tock?). +{% alert "", "warning" %} + We can’t work more than 40 total hours without being compensated for that time. Working overtime without prior approval violates the [Antideficiency Act](https://www.gao.gov/legal/appropriations-law/resources). {% endalert %} +If you find yourself needing to work more than 40 hours, here are the steps to take *before* you work any extra hours. + First, ensure you can work the extra hours: 1. Talk to your Engagement Lead, Account Manager or Project Lead **and** supervisor to figure out if and how much over 40 hours you can work. @@ -170,11 +162,7 @@ Then, make sure to accurately track your overtime hours in Tock and HRLinks: No matter how many hours you work, it is crucial that you accurately report those hours in Tock. Knowing the actual amount of time you work helps us better scope and estimate costs and rates. -#### How does AWS impact how I Tock? {#how-does-aws-impact-how-i-tock?} - -Tock will limit you to 40 hours per week by default. Please request an alternative work schedule in {% slack_channel "tock" %} if you are on an AWS. You do not need to do this if you are on a flexible week schedule. - -#### Can I ‘save’ billable hours to apply to a subsequent week? +### Can I ‘save’ billable hours to apply to a subsequent week? No. Please don’t “save” hours or avoid billing for time you’ve worked in a given week. In addition to hurting our capacity to improve our engagement scoping assumptions, it is illegal not to bill for time spent working for partners. @@ -185,19 +173,19 @@ There are several mechanisms and processes in place to make sure engagements don In short, we need to know if our scoping is accurate and understand the cadence of work throughout an engagement. We’d rather be over budget and have our teams deliver value than be under budget and hide how many hours it truly takes to deliver on our engagements. -## How do I correct a prior Tock submission? +## Correcting prior Tock submissions Submit a Tock change request using [the Tock Change Request form](https://docs.google.com/forms/d/e/1FAIpQLSe5RDFOlyWm0IXv7_eXjZ3CEjaGj2CmM-_TNgqwMjdspfQz7Q/viewform). You can also ping the Tock team in the {% slack_channel "tock" %} Slack channel. Make sure to inform your AM/EL with any submitted change requests. -## How do I log my time for upcoming leave? +## Logging time for upcoming leave -If you are going to be out of the office for an extended period of time, head to the {% slack_channel "tock" %} channel in Slack before you leave and ask that the team submit your Tock hours for you during your out of office period. +If you are going to be out of the office for an extended period of time and that time period is not available to report yet, head to the {% slack_channel "tock" %} channel in Slack before you leave and ask that the team submit your Tock hours for you during your out of office period. Example: > “I will be out of the office from Monday September 16th through Monday September 23rd: could you enter 40 hours for me to \#670 for the 16th-20th time period?” -## How do supervisors review hours logged in Tock? +## How do supervisors review hours logged in Tock? {#supervisor-review} Supervisors should regularly review the hours their direct reports are logging. From 49065c3db525a88e360b250b24f013aee3998c1e Mon Sep 17 00:00:00 2001 From: "Andrew Dunkman (he/him)" Date: Mon, 6 Jan 2025 11:57:10 -0500 Subject: [PATCH 2/5] Update channel name. (#4053) --- pages/18f/chapters/design.md | 4 ++-- .../projects-partners/consulting-engineering-guide.md | 2 +- pages/18f/projects-partners/leading-projects.md | 10 +++++----- pages/about-us/tts-consulting/operations/brand.md | 2 +- .../tts-consulting/operations/delivery-assurance.md | 6 +++--- pages/getting-started/classes/writing-lab.md | 2 +- 6 files changed, 13 insertions(+), 13 deletions(-) diff --git a/pages/18f/chapters/design.md b/pages/18f/chapters/design.md index 1af9f4faf..2167b141c 100644 --- a/pages/18f/chapters/design.md +++ b/pages/18f/chapters/design.md @@ -51,7 +51,7 @@ Find us on Slack: - {% slack_channel "product-design" %} - {% slack_channel "g-content" %} - {% slack_channel "g-research" %} -- {% slack_channel "18f-help-wanted" %} +- {% slack_channel "ttsc-help-wanted" %} - {% slack_channel "dev-frontend" %} - {% slack_channel "18f-methods" %} @@ -181,7 +181,7 @@ Trello]({% page "/trello" %}) page. #### Research - Please read [Doing Research at TTS]({% page "/research-guidelines" %}) for - more information on the tools and techniques. + more information on the tools and techniques. - The [18F UX Guide](https://ux-guide.18f.gov/) provides additional guidance on how we conduct research. - **Analytics:** We recommend leveraging the [Digital Analytics Program](https://digital.gov/services/dap/) whenever diff --git a/pages/18f/projects-partners/consulting-engineering-guide.md b/pages/18f/projects-partners/consulting-engineering-guide.md index 171f9436b..54804b513 100644 --- a/pages/18f/projects-partners/consulting-engineering-guide.md +++ b/pages/18f/projects-partners/consulting-engineering-guide.md @@ -186,7 +186,7 @@ skills. If so, some options you might want to look at include: - Billable projects — Cloud.gov and Login.gov often can use some extra help across a broad range of skill sets. Check their staffing issues. -- {% slack_channel "18f-help-wanted" %} may have a small (less than 12 hours, +- {% slack_channel "ttsc-help-wanted" %} may have a small (less than 12 hours, usually) project that needs some engineering help - Non-billable projects — talk with your supervisor about pitching in on an internal project like Tock diff --git a/pages/18f/projects-partners/leading-projects.md b/pages/18f/projects-partners/leading-projects.md index 8f634f571..28160a943 100644 --- a/pages/18f/projects-partners/leading-projects.md +++ b/pages/18f/projects-partners/leading-projects.md @@ -63,7 +63,7 @@ Missteps on projects will happen. Teams do not have a crystal ball into partner expectations or communication preferences. This is a good time to bring in a facilitator from outside the project to help the team reflect on what is and isn’t going well, and then help the team come up with alternative methods in the -future. Try {% slack_channel "18f-help-wanted" %} to ask for a facilitator. +future. Try {% slack_channel "ttsc-help-wanted" %} to ask for a facilitator. ### Manage work so it is equitably distributed @@ -104,7 +104,7 @@ happening. tools and deliverables) - If artifacts (e.g. RFQs, final reports, decks) should be durable over time, consider budgeting time to make them accessible (talk to your account - manager or use {% slack_channel "18f-help-wanted" %} if the team doesn't + manager or use {% slack_channel "ttsc-help-wanted" %} if the team doesn't have this ability) - Ensure sprint planning, review, and other recurring meetings are scheduled - Facilitate identification of project management tracking tools @@ -191,14 +191,14 @@ most common types of 18F project endings are some combination of the following: engagement]({% page "/18f/projects-partners/projects-in-distress/" %}) - **Document and share learnings** - Conduct, document, and post a Project Reflection at the end of the project (or - every 3-4 months for longer projects). Reference the [facilitation guide](https://docs.google.com/document/d/1lB8w_U2SR3X4U78KTOWril_JOINaF98NQwQoR7oYVeo/edit), [conversation guide](https://docs.google.com/document/d/1bsaRrm9Mjnk87UOsHDyTsfK2yVbsnLLywvfFuVXL5HE/edit#), and [summary template](https://docs.google.com/document/d/1R10zQ5hpHYtSA3utxydte-Xk4ktdjUWnlMOrZp3pSwA/edit) to get started. + every 3-4 months for longer projects). Reference the [facilitation guide](https://docs.google.com/document/d/1lB8w_U2SR3X4U78KTOWril_JOINaF98NQwQoR7oYVeo/edit), [conversation guide](https://docs.google.com/document/d/1bsaRrm9Mjnk87UOsHDyTsfK2yVbsnLLywvfFuVXL5HE/edit#), and [summary template](https://docs.google.com/document/d/1R10zQ5hpHYtSA3utxydte-Xk4ktdjUWnlMOrZp3pSwA/edit) to get started. - Request a facilitator from outside the - project in {% slack_channel "18f-help-wanted" %} so everyone on the project team can fully + project in {% slack_channel "ttsc-help-wanted" %} so everyone on the project team can fully participate. - Post the reflection summary to {% slack_channel "project-reflections" %} - Link the completed project reflection to the project record in the 18F dashboard using [this form](https://airtable.com/shrDVLEqUpLYGnvKS). - Share re-usable or example tools, presentations, docs, and other resources by [submitting them to the Project Resource Library](https://airtable.com/appkBrEBVTMd9M5VC/paggmwfuX2sEXbiW8) - + - As an optional step, use the [project reflection for performance evals template](https://docs.google.com/document/d/1ko28PDLcEa_VB3ulMKbEjLzi88u8K8WJqXsBryrBV-U/edit?usp=sharing) to collaborate on drafting individual performance language. In some cases, an diff --git a/pages/about-us/tts-consulting/operations/brand.md b/pages/about-us/tts-consulting/operations/brand.md index beefe2dad..440c5da92 100644 --- a/pages/about-us/tts-consulting/operations/brand.md +++ b/pages/about-us/tts-consulting/operations/brand.md @@ -43,5 +43,5 @@ Reports, presentations, and other collateral should also follow our delivery sta Many of the referenced guides explain how to use them. If you need more help: - Ask the designers on your team -- Post a message in {% slack_channel "18f-help-wanted" %} +- Post a message in {% slack_channel "ttsc-help-wanted" %} - Use the [CoE Content Support Intake Form](https://docs.google.com/forms/d/e/1FAIpQLSdFO_8RgAGSoI3nbFNQHQ7johMzK1Z83CHTSzjqtD3IzM-bqg/viewform) diff --git a/pages/about-us/tts-consulting/operations/delivery-assurance.md b/pages/about-us/tts-consulting/operations/delivery-assurance.md index 09cd472a5..b1da05abb 100644 --- a/pages/about-us/tts-consulting/operations/delivery-assurance.md +++ b/pages/about-us/tts-consulting/operations/delivery-assurance.md @@ -8,14 +8,14 @@ Here are some of the mechanisms TTSC has to do this kind of work: | Resource | Helps with | |----------|------------| -| [**\#18f-help-wanted**](##18f-help-wanted-slack-channel) | **Short, fast, billable or non-billable tasks** like writing review, graphic design, general volunteers | +| [**\#ttsc-help-wanted**](##ttsc-help-wanted-slack-channel) | **Short, fast, billable or non-billable tasks** like writing review, graphic design, general volunteers | | **[Delivery Assurance (aka TLC)](#18f-delivery-assurance-\(aka-tlc-crew\))** | **Two week or less, non-billable tasks** like Facilitating project reflections, making updates or fixing bugs on 18F products, | | [**18F Working Groups**](#18f-working-groups) | **A few hours a week for a few months** like Internal surveys and analysis, developing smart default templates, revising performance plans | | [**TTS Operations support services**](#tts-operations-support-services) | **Recurring TTS-level ops tasks or improvements** like processing agreements, outreach approvals, hiring actions | -## \#18f-help-wanted Slack channel {##18f-help-wanted-slack-channel} +## \#ttsc-help-wanted Slack channel {##ttsc-help-wanted-slack-channel} -TTSC staff may request help from peers for a few hours of billable or non-billable work by posting to the {% slack_channel "18f-help-wanted Slack" %} channel. +TTSC staff may request help from peers for a few hours of billable or non-billable work by posting to the {% slack_channel "ttsc-help-wanted Slack" %} channel. If your task is specifically for writing/editing help, use `@writing-editors` to ping the content designer group. diff --git a/pages/getting-started/classes/writing-lab.md b/pages/getting-started/classes/writing-lab.md index 6ed45bd8b..db786818d 100644 --- a/pages/getting-started/classes/writing-lab.md +++ b/pages/getting-started/classes/writing-lab.md @@ -74,7 +74,7 @@ ask for guidance on getting somebody assigned to your project. ### How do I ask for help? -You can post your request in {% slack_channel "18f-help-wanted" %}, or +You can post your request in {% slack_channel "ttsc-help-wanted" %}, or {% slack_channel "tts-help-wanted" %} if you are not in 18F. ### What should I do if my issue isn't picked up? From e3ea1fc3714bae1f4e84a5ca5c57ad53edb60867 Mon Sep 17 00:00:00 2001 From: Alex Soble <96746002+alexsobledotgov@users.noreply.github.com> Date: Tue, 7 Jan 2025 13:50:08 -0600 Subject: [PATCH 3/5] Add content on hosting an accessible Zoom meeting, in particular how to spotlight ASL interpreters (#4056) * Update supporting-deaf-hoh-colleagues.md -- add info on accessible Zoom meetings * Update supporting-deaf-hoh-colleagues.md * Update supporting-deaf-hoh-colleagues.md * Update supporting-deaf-hoh-colleagues.md * Update supporting-deaf-hoh-colleagues.md * Ooops spelling * link to accessibility instructions --------- Co-authored-by: Greg Walker --- .../supporting-deaf-hoh-colleagues.md | 26 +++++++++++++++++++ pages/tools/zoom.md | 3 +++ 2 files changed, 29 insertions(+) diff --git a/pages/general-information-and-resources/employee-resources-policies/supporting-deaf-hoh-colleagues.md b/pages/general-information-and-resources/employee-resources-policies/supporting-deaf-hoh-colleagues.md index da400b86a..a6ec84d2a 100644 --- a/pages/general-information-and-resources/employee-resources-policies/supporting-deaf-hoh-colleagues.md +++ b/pages/general-information-and-resources/employee-resources-policies/supporting-deaf-hoh-colleagues.md @@ -17,3 +17,29 @@ Tips for working effectively & inclusively with your Deaf and Hard of Hearing co * Practice ASL. Signing and/or spelling shows you are making an effort. * Facial expressions, body language, and the chat are all non-verbal ways to add context and color to the meeting conversation — use them! * When working with Deaf and/or Hard of Hearing colleagues, don’t focus on *what* they are (Deaf), focus on *who* they are. + +## Hosting accessible meetings + +When we host a large meeting, we'll often record it so that people can watch after-the-fact. + +We need both the meeting itself and the recording to be fully accessible. + +That means making sure that ASL interpreters are highlighted in the recording, so that a Deaf or Hard of Hearing person can watch the ASL interpretation along with the recorded meeting. + +Here's a short guide to facilitating an accessible meeting -- + +### Before the meeting ++ Request ASL interpreters and CART transcription. + + Send the interpreters and transcriber the agenda plus any presentation materials ahead of time. ++ Consider using [Zoom]({% page "tools/zoom" %}) to host the meeting, since Zoom's [Spotlight feature](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0066300) allows the facilitator to spotlight ASL interpreters. + +### The day of the meeting ++ Join the Zoom room 10 to 15 minutes early. Chat with the interpreters, captioner, and presenters to make sure all have what they need. ++ Make interpreters co-hosts of the meeting. + + This allows the interpreters to pin Deaf participants during the meeting. It also allows them to Spotlight themselves. + +### During the meeting ++ During the meeting, the facilitator needs to Spotlight each speaker when they begin presenting, and un-Spotlight each speaker after they are done. + + Actively facilitating a meeting while managing Spotlight controls as host is tricky -- consider splitting these into two separate roles and delegating. ++ During the meeting, the facilitator needs to keep their Zoom set to Speaker view. + + Switching to Gallery view will affect the recording and ASL interpreters will show up as tiny thumbnails, instead of Spotlighted. diff --git a/pages/tools/zoom.md b/pages/tools/zoom.md index 9f9ea8a5e..fb5026ff7 100644 --- a/pages/tools/zoom.md +++ b/pages/tools/zoom.md @@ -22,6 +22,9 @@ GSA offers [Zoom for Government](https://zoomgov.com/). [General instructions.](https://support.zoom.us/hc/en-us/articles/201362613-How-Do-I-Host-A-Video-Meeting-) +To help ensure people can fully participate, see our Handbook page on +[hosting accessible meetings]({% page "/general-information-and-resources/employee-resources-policies/supporting-deaf-hoh-colleagues/#hosting-accessible-meetings" %}). + ### For meetings longer than 40 minutes You can check [your Zoom profile](https://gsa.zoomgov.com/profile) to see your From 39d3f8e87e940ba2a42101e5a52b7dcd9625459f Mon Sep 17 00:00:00 2001 From: Alex Soble <96746002+alexsobledotgov@users.noreply.github.com> Date: Tue, 7 Jan 2025 13:54:02 -0600 Subject: [PATCH 4/5] Update deaf-hoh.md (#4055) Point to https://www.section508.gov/create/accessible-meetings/, the GSA InSite page links/redirects out to section508.gov Co-authored-by: Greg Walker --- .../employee-resources-policies/deaf-hoh.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pages/general-information-and-resources/employee-resources-policies/deaf-hoh.md b/pages/general-information-and-resources/employee-resources-policies/deaf-hoh.md index 2d258e54d..db6e82563 100644 --- a/pages/general-information-and-resources/employee-resources-policies/deaf-hoh.md +++ b/pages/general-information-and-resources/employee-resources-policies/deaf-hoh.md @@ -263,8 +263,7 @@ Each program office is responsible for the cost of these services. ### Planning for accessible events -GSA maintains a very useful InSite page on -[hosting accessible meetings](https://insite.gsa.gov/employee-resources/information-technology/it-accessibility-section-508/hosting-accessible-meetings). +Section508.gov maintains a useful guide to [hosting accessible meetings](https://www.section508.gov/create/accessible-meetings/). It includes actions to take before, during, and after your meeting. ## Who to contact From c28823166c627bca08a625f5aeff4330c1940dd8 Mon Sep 17 00:00:00 2001 From: Rebecca Refoy Date: Tue, 7 Jan 2025 14:58:13 -0500 Subject: [PATCH 5/5] Update sharedcalendars.md (#4054) --- pages/tools/sharedcalendars.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/tools/sharedcalendars.md b/pages/tools/sharedcalendars.md index 69d418904..93634955b 100644 --- a/pages/tools/sharedcalendars.md +++ b/pages/tools/sharedcalendars.md @@ -46,7 +46,7 @@ availability with your partner: above. - Partners using Microsoft Outlook can use this “Share your calendar with everyone” instructions - [here](https://www.bettercloud.com/monitor/the-academy/3-ways-to-share-your-outlook-calendar-with-others/). + [here](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/share-calendars-with-external-users?view=o365-worldwide). 7. Finally, import the partner calendar link into Google Calendar and see if you are able to view calendar events, including updates.