The Qualifying Wages Report lists student and employer names, start and end dates, wage per hour, approximate hours per week and total earnings. This report must be submitted with the annual Connecting Activities proposal, which is due in the spring. It is a long report, so only one copy is required with your submission.
Before printing the report, check your data for accuracy ...
From the Reports menu, go to the Qualifying Wages report.
Click the pink button to run the report. The script will find records with an "A1: Job/Internship" type of activity, paid, with a start date in the current fiscal year (July 1, 2002-June 30, 2003). The script will sort the records by employer name. You'll see total wages at the top of the screen, and when you print or preview the report, you'll see subtotals for each employer.
Compare the total with last year's total for the region to see if it is realistic. You could also divide the total qualifying wages by the number of students to see if the earnings per student seem realistic.
On the menubar, click View, View as Table to view the report in a "datasheet" format (rows and columns). One by one, sort each column, both in ascending and descending order. You'll notice if anything is amiss. For example, if you accidentally had an end date that is less than a start date, you'll have negative weeks and negative earnings.
Hours and wages must be numbers. If hours vary, enter an approximate average. Don't enter a range like 10-15 because the computer will misinterpret that!
If you need to make corrections, you can either make the correction right on this screen, or, if that isn't possible, use the layout button to go to Layout1. After you've made the correction, use the layout button to come back to the Qualifying Wages layout.
When you have finished editing, use View, View as List to return to the normal list. Use the pink button to rerun the report and then print when you are ready.
New instructions for FY2010
This year, with Connecting Activities collaborating with many sponsored/subsidized job placements, it is important to exclude these placements from the Qualifying Wages report. The qualifying wages report should be based on Employer-Paid placements only.
- Be sure that all placements are accurately coded with an Activity Name that allows you to see which placements were supported by which programs -- such as "Mill Valley Summer YouthWorks Program" or "Mill Valley ARRA Program."
- Generally, all of the Activity Names for work-based learning experiences should be coded with the Activity Code/Type: "A1: Connecting Activities Job/Internship Placement." Placements coded as "A1" are included in the quarterly report and the qualifying wages report. HOWEVER, for the Qualifying Wages report, we want to exclude all of the non-employer-paid placements. Therefore when you run the Qualifying Wages reports, do the following:
- First - on the reports menu, run the report called "Qualifying Wages by Activity" and print this report. This will be a useful reference.
- Next, open the Activity List screen (from the yellow button on the Main Menu).
- Use the book to scroll through each activity. For each activity that provides non-employer-paid placements, such as YouthWorks or ARRA, CHANGE THE ACTIVITY CODE/TYPE from "A1" to "EXCLUDE"
- Go to the Reports Menu, click to open the Qualifying Wages report, click the button to run the report, and then proofread and print.
- Once you are done with the Qualifying Wages report, you should change the "EXCLUDE" code back to "A1."
- If you need to re-run the Qualifying Wages report, please repeat these steps.
- Note - if some of your placements are partly-employer-paid and partly-subsidized we may have to use the "Qualifying Wages by Activity" report to adjust the qualifying wages total. Please check with Jennifer Leonard to agree on a formula.
Thank you for following these steps! The expanded YouthWorks and ARRA placements came about after the database was released for the year, and so that is why these extra steps are necessary.
Note to advanced users -- there are many other ways of using the database to accomplish this task, so if you have another method you can email to ask/confirm that your method will accomplish the same goal.
|