1. Home
  2. Census
  3. School Workforce
  4. England SWFC Errors 4740, 4760, 4780

England SWFC Errors 4740, 4760, 4780

Use this guide to resolve the SWFC Errors 4740, 4760 and 4780 using the following steps

For general SWF guidance see here

The School Workforce Census will look for Staff/Contracts that are active from 1/9/2025 to 5/11/2026. So if a staff member has a Current Contract, and/or a Contract that ended within those dates, then the Census is likely to pickup BOTH Contracts. This means that the data for both needs to be checked.

DfE Validation

Rule numberValidation CheckError Messages
4740<HoursPerWeek> must be provided. Note – this should be evaluated against both Post and Role details.Hours worked per week is missing
4760<FTEHours> must be provided. Note – this should be evaluated against both Post and Role details.FTE Hours per week is missing
4780Where <DailyRate> is not equal to ‘Y’, then <WeeksPerYear> must be provided. Note – this should be evaluated against both Post and Role details.Weeks per year is missing

Once a SWF Census has been generated we recommend running the Staff Contract Details Report from Reports>Census> School Workforce this report can be used to identify the missing data.

pathway

Resolution Steps

To begin, check either within the Census File, or the Contract Report (Reports>Census>Staff Contract Details) to see which Contracts are being returned and the data for each.

Below is an example where the bottom Contract is fine, as it has the Pay information. The top Contract is not, as it has no Pay information.

From here, navigate to Staff Record>Contract and see the Contracts within it (use Show All to see the past ones too).

Double click on the Contract to view.

Important: It may be necessary to check Inactive Contracts for this staff member to resolve this Query. Be prepared to check any Contracts that were Active from 01/09/2025, even if they are no longer Active.


Within the Contract, you can select Pay to see which record would be active in the 1/9/2025 to 5/11/2026 date range.

If the staff member only has one Contract from before the Census Date then this will the Contract to view.

Take a note of the Base Pay Structure name and the Spine Point.

Now go to Config>Administration>Base Pay Structure and find the Structure that the staff member is paid with.

Double click or press Edit to expand it.

Select the Version that was Active at the time of the Pay Record.

Select the Scale Point Group on the left, then the Spine Point on the right.

If the Spine Point has a value of 0, it will not be returned in the SWF Census.

It is highly likely that the Spine Point value not being present is the cause of these errors, but the above steps will help you to confirm this as you work through them.

Once all the steps are completed and you have saved any changes you made along the way, you can run a new SWF Census.

Summary of Resolution Steps

  1. When you go to the staff member’s record, go to the Contract between 01/09/25- 05/11/26 and go to the Pay section.
  2. Check which Base Pay Structure they are on (with the dates). If they have multiple Pay records in their Contract, find the one that would have been active within the aforementioned date range.
  3. Check which Scale Point Group are they on within their Pay.
  4. Check and make a note of which Spine Point they are on.
  5. Now go to Config>Administration>Base Pay Structures. Then find the Base Pay Structure that the staff member is on and select the Version that matches what they had on their Pay record.
    1. Is there an active Version that covers the aforementioned date range?
    2. Has the current Version ended?
  6. If the above is correct, then check the Scale Point Group and make sure it is active.
  7. If it is active, select the Scale Point Group and check the Spine Point that the staff member is on.
    1. Is the Spine Point active?
    2. Finally, does the Spine Point have a value (i.e. not 0.0)?

IMPORTANT in order for the resolved error/query to be removed from the list of errors/queries you would need to generate a new Census return and remember to use save & validate for the errors/queries to update/clear.

Updated on September 11, 2026
Was this article helpful?

Related Articles

Noticed a missing guide?
Fill the form below and we will get this created.
Suggest Help Article