# Taskbook Criteria Checking

DOI Agencies (BIA, BLM, NPS and FWS)...\
When Initiating a Taskbook, the system will take the Initiate Date
(figure 1) and check the Prerequisite Criteria that are in effect at the
time of the initiate date for that particular Taskbook. If the criteria
have not been met, you will receive an error message (figure 4).

When doing an Evaluation (figure 2), the system will take the Initiate
Date (figure 1) and check the Prerequisite Criteria that are in effect
at the time of the initiate date for that particular Taskbook. If the
criteria have not been met, you will receive an error message (figure
4).

When Certifying the Taskbook (figure 3), the system will take the
Initiate Date (figure 1) and check the Prerequisite Criteria that are in
effect at the time of the initiate date for that particular Taskbook. If
the criteria have not been met, you will receive an error message
(figure 4).

DOA Agency (Forest Service)

When Initiating a Taskbook, the system will take the Initiate Date
(figure 1) and check the Prerequisite Criteria that are in effect at the
time of the initiate date for that particular Taskbook. If the criteria
have not been met, you will receive an error message (figure 4). And the
system will not allow you to save the data.

When doing an Evaluation (figure 2), the system will take the
[Evaluation Date (figure 2)]{.mark} and check the Prerequisite Criteria
that are in effect at the time of the Evaluation Date for that
particular Taskbook. If the criteria have not been met, you will receive
an error message (figure 4). And the system will not allow you to save
the data.

When Certifying the Taskbook (figure 3), the system will take the
[Certify Date (figure 3)]{.mark} and check the Prerequisite Criteria
that are in effect at the time of the Certify Date for that particular
Taskbook. If the criteria have not been met, you will receive an error
message (figure 4). And the system will not allow you to save the data.

In short...

For DOI Agencies, whether evaluating or certifying, whatever the
criteria was in effect (via the 310-1) at the time of the initiation
date, is still in effect.

For the Forest Service, when evaluating or certifying, if the criteria
has changed (via the 5109.17) since the initiation date, the responder
has to meet the criteria that is in effect as of the evaluation date or
the certify date.

![](media/image1.png){width="5.993055555555555in"
height="1.8166666666666667in"}

Figure 1

![](media/image2.png){width="5.997222222222222in"
height="3.4430555555555555in"}

Figure 2

![](media/image3.png){width="5.993055555555555in" height="1.44375in"}

Figure 3

![](media/image4.png){width="5.995138888888889in"
height="1.3159722222222223in"}

Figure 4

# How 310-1 / 5109.17 Criteria Date Works

Note: This was previously labeled the "Attained Date".

The 310-1 / 5109.17 Criteria date (figure 5) is found on the Qual Card
page, at the right side of each Position row. It is used to identify
what set of criteria (in the 310-1 or the 5109.17) should be used to
check that particular position against for qualification.

For example, if a responder has a Criteria Date for the FFT1 position in
Jun 2003, then the criteria changed in Mar 2005, the Qualification
Process would check the responder's position against the criteria that
was in affect in 2003, NOT the new criteria in 2005. This would allow
the responder to remain qualified under the criteria that was in effect
according to that date.

The greatest benefit to this is that this will reduce how often the
"Admin Action" is used to keep someone qualified after the position
criteria changes.

The one exception to this is when the 310-1 or 5109.17 (or the Agency)
mandates that ALL responders in a given position HAVE to meet the new
criteria. This is indicated in the setup (or control) data of the role,
and overrides this Criteria Date.

How is the Criteria Date calculated?

-   The Criteria Date functionality was implemented in IQCS the first
    week of February, 2006, during the implementation of the new 310-1
    rules. For all positions that already existed, we used a set of
    business rules to calculate that date. The business rules used
    were...

    -   If a Position Taskbook exists in IQCS for that particular
        position, set the Criteria Date equal to the Initiate Date if
        Active, or set to the Certify Date if Certified.

    -   If no Position Taskbook exists and the Position Competency
        exists, set the Criteria Date equal to the Effective Date of the
        current Position Competency.

    -   If neither the Position Taskbook nor the Position Competency
        exists, then hardcode the date to Jan 29, 2006.

-   If a responder starts a new Position Taskbook after Feb 6, 2006, the
    Criteria Date is set by the Position Taskbook. When the taskbook is
    Active, the Criteria Date is equal to the Initiate Date. When the
    taskbook is Certified, then the Criteria Date is set equal to the
    Certify Date (Forest Service Only), or remains equal to the Initiate
    Date (DOI Agencies), and should not change after that.

-   If a taskbook is NOT used and the position is awarded to the
    responder by awarding the Position Competency on responder's
    Competencies pages, the Criteria Date is set equal to the effective
    date of that Position Competency.

Note: The Criteria Date field has been left editable. If the user knows
the Criteria Date is wrong, it should be corrected.

![](media/image5.png){width="5.99375in" height="2.4784722222222224in"}

Figure 5

# Troubleshooting Pages -- Known Problem

With the new functionality of the Criteria Date on the Qual Card, the
functionality of the trouble shooting pages (figure 6) have been
impacted. How it works now.

If the position being selected on the trouble shooting page does NOT yet
exist on the responder's Qual Card page, the most current criteria for
that position are used to check against the responder's related
competencies. This is useful when looking at future positions for a
given responder and what they need to become one.

If the position is already on the responder's Qual Card page, the
criteria that is returned for the position is determined by the
following business rules...

-   The criteria for the position that is in effect at the time of the
    Criteria Date is used to check against the related responder's
    competencies.

-   If the 310-1 or 5109.17 (or the Agency Lead) mandates that the
    current criteria for the position is used, as indicated in the setup
    (or control) data, then that overrides the Criteria Date and the
    current criteria is returned.

So are there any problems with all of this??? YES!

The problem currently arises when there is an Active Taskbook! Because
the Criteria Date for the position is equal to the initiate date of the
taskbook, when entering the trouble shooting pages, the criteria that is
returned is the criteria that was in effect at the time of the Criteria
Date (or taskbook initiate date).

This is ok for DOI Agencies, because evaluations and certification of
the taskbook are checked against the criteria in effect at the time of
the initiate date.

But for the Forest Service, if the criteria have changed since the
initiation date (like a new 5109 update), and an evaluation or
certification is attempted, the taskbook process checks against the
criteria that is in effect at the time of the evaluation or
certification dates. And if the responder does not meet those new
criteria, the error message (figure 4) is returned. At this point, the
natural action of the user is to go to the troubleshooting pages and see
what the responder is not meeting. But the troubleshooting pages pull
the criteria that are in effect as of the Criteria Date -- or the
Initiate Date of the Taskbook -- and NOT the criteria that are in effect
as of the Evaluation or Certification Date. So the troubleshooting pages
indicate the responder meets all criteria, but the taskbook pages
indicate differently. **All because the troubleshooting pages use the
Criteria Date (or Initiate Date) and the taskbook pages use the
Evaluation or Certification date.**

Is this going to be fixed??? YES!

Sometime in the next few weeks, we will be implementing some changes to
the troubleshooting pages that will resolve this problem.

![](media/image6.png){width="5.99375in" height="3.472916666666667in"}

Figure 6