Approval Pre-check
This feature is in beta. It can change before it reaches every account, so this article may not match what you see yet. To try it, an account admin can turn it on in Settings > Account > Account Preferences, under Features. See Upcoming Changes for the planned date.
Approval Pre-check looks for gaps in a project before you request approval. It checks items such as missing service descriptions and blank project summary fields, then grades the project using your account’s rules.
Who can use it
Check Project Permissions for access to project reviews and approval requests.
- View results. You need at least View on Approval Pre-check.
- Run or re-run Pre-check and check off to-dos. You need Manage or Override on Approval Pre-check.
- Request approval. You need Manage on Request Approval.
- Submit below the passing grade. You need Override on Approval Pre-check and Manage on Request Approval.
- Edit the account rules. Under Settings Permissions, you need Manage on Approval Pre-check Settings. View gives you read-only access to the rules.
Give a role access to edit the rules
You need Manage on Roles to change an existing role.
- Go to Settings > Users & Groups > Roles.
- Select the role you want to edit.
- Under Settings Permissions, set Approval Pre-check Settings to Manage.
- Select Save.
On this screen: Edit Role groups permission dropdowns under Project Permissions, Settings Permissions, and Reports Permissions. Each dropdown shows the permission name and its available levels, with a short description below it.
See Roles and Permissions for more on editing roles.
Edit your account’s rules
- Go to Settings > Governance > Approval Pre-check.
- Under Mode, select Advisory or Required. If you select Required, choose a Passing Grade.
- Set each rule to Fail, Warn, or Off.
- Set the hint switches you want to use.
- Select Save.
On this screen: Approval Pre-check shows Mode and Passing Grade at the top. The box with the placeholder Filter rules, e.g. assumptions narrows the rules and hints below it. If you have Manage on Approval Pre-check Settings, the header counts your unsaved changes when you edit. Select Cancel to discard those changes. After you save, ScopeStack shows Approval Pre-check settings saved.
Mode and passing grade
Advisory is the default. Use it to grade projects without blocking approval requests. Required blocks an approval request when the grade is below the passing grade, unless a user with Override submits it anyway. Passing Grade applies in Required mode, with options A (90+), B (75+), C (60+), and D (45+).
When Approval Pre-check is enabled, Required applies to approval requests for every project in your account.
On this screen: When you save a switch from Advisory to Required, Switch to Required? explains how the passing grade applies on submission. Select Switch to Required to save, or Cancel to return to the form.
Rules
On this screen: The rule sections can include Service Language, Subservice Language, Narrative, Structure, LOE Sanity, and Content Quality. The Narrative rules use the labels and fields shown on your account’s Customer Summary page. A rule set to a different level shows Changed from with its default level and a Reset button.
Service and subservice language rules follow the language fields active in your account.
| Section | Rule | What it checks | Default level |
|---|---|---|---|
| Service Language | Service description, assumptions, deliverables, and out of scope | Checks for blank fields on each service. | Fail |
| Service Language | Customer language | Checks for a blank customer language field on each service. | Warn |
| Service Language | Other language fields | Checks for blank fields on each service. | Off |
| Subservice Language | Service description | Checks for a blank description on each active subservice. | Fail |
| Subservice Language | Other language fields | Checks for blank fields on each active subservice. | Off |
| Narrative | Executive Summary | Checks whether the field is blank. | Fail |
| Narrative | Solution Summary | Checks whether the field is blank. | Warn |
| Narrative | Our Responsibilities, Customer Responsibilities, and Out of Scope | Checks whether each field is blank. | Off |
| Structure | Project has at least one service | Checks for at least one active service. | Fail |
| Structure | A service is in an implementation phase | Checks for a service in a phase with “implement” in its name. | Fail |
| Structure | A service is in a planning or design phase | Checks for a service in a phase with “plan” or “design” in its name. | Warn |
| LOE Sanity | Service hours are not zero | Checks whether a professional service has zero hours. | Fail |
| LOE Sanity | Service hours above | Checks whether a professional service exceeds the hours limit. | Warn |
| Content Quality | Client name appears in the executive summary | Looks for the customer’s name in the executive summary. | Warn |
| Content Quality | Service language is not too brief | Looks for service language under 20 characters in filled fields whose Service Language rule is set to Fail. | Warn |
| Content Quality | Service language isn’t duplicated across services | Looks for identical blocks of service language over 100 characters across differently named services. | Warn |
If your account hides the Customer Summary page, the Narrative section does not appear and its rules are Off. If the page is minimized, only the Executive Summary and Solution Summary rules are listed.
- Fail gives a missed check zero points and marks it Failed.
- Warn gives a missed check half credit and marks it Warning.
- Off skips the rule and excludes it from scoring.
The overall score is the average of the category scores, rounded to a whole number. Each category counts equally. In Required mode, ScopeStack uses the overall grade to decide whether the project passes.
LOE Sanity checks the level of effort in hours for professional services. Enter a whole number above zero in Service hours above to change the default limit of 500 hours. The check uses the service’s total hours, including active subservices. If the total exceeds the limit, the check shows Warning by default.
Hints
On this screen: Hints (never affect the grade) has switches for Placeholder Text and Estimate Accuracy. If Service Suggestions is turned on for your account, you’ll also see a Missing Services switch.
Placeholder Text flags leftover text such as [Customer], TBD, TODO, or NUMBER in project summaries and service or subservice language.
The Estimate Accuracy switch controls a hint based on whether services consistently took more or fewer hours than estimated on past projects.
Run Pre-check on a project
- Open the project.
- In the project menu, go to Approvals > Approval Pre-check.
- Select Run Approval Pre-check.
On this screen: Before the first run, the Approval Pre-check page shows a card titled Check This Project Before Requesting Approval.
On this screen: After a run, the header shows Last run with the date and time. When there are scored checks, the grade card shows a letter grade, a score out of 100, and category scores. The card also counts completed to-dos. To-Do lists failed checks, warnings, and any placeholder text it found, with a checkbox beside each item. Use Hide Completed to filter out checked items, or Show Completed to bring them back. Expand the Passed Checks count to see which checks passed.
Use the links by service and subservice language findings to open the relevant services page. Make your edits there, then check off the items you addressed in To-Do.
If Service Suggestions and the Missing Services hint are both enabled, review the catalog suggestions in Missing Services. Each suggestion shows High or Medium and can list the services it is usually sold with. Use Dismiss to set a suggestion aside. To add one, select Add…, fill in the service details, and select Add Service. Adding a suggestion requires Create, Manage or Adjust Standards on Professional Services.
If the project changes after a run, a banner tells you to refresh the review. Select Re-run Pre-check to use the current project and account rules. Rerunning replaces the saved result and clears its checkmarks. When Mode is Required, requesting approval also runs Pre-check again for whoever submits, which clears the checkmarks too.
Request approval
Select Request Approval in the project header. If your account has renamed this button, select your account’s label. If Approval Pre-check is enabled and the account uses Required mode, submitting for approval runs a fresh Pre-check and clears the old checkmarks, even if the new grade blocks the request.
On this screen: If the grade is too low and you have Override, the Approval Pre-check below passing grade dialog shows the project’s grade, score, and passing grade. To proceed, enter an optional Reason and select Submit Anyway. Select Cancel to close the dialog and return to the project.
ScopeStack records a successful override on the project. The Required check runs before the approval workflow, even if Approval Workflow is off in Account Preferences or your plan excludes it. In either case, a successful submission moves the project to Approved.
When the approval workflow is on, ScopeStack emails the assigned approvers as the project reaches each applicable approval level, subject to notification settings.
See Project Approval Levels for the steps that follow submission when the workflow is on.
Troubleshooting
The settings page is missing or read-only. Ask someone with Manage on Roles to check Approval Pre-check Settings on your role. Use Manage if you need to make changes.
The pre-check could not be loaded. Select Try Again. If the page still fails to load, check that you have at least View on Approval Pre-check in Project Permissions.
Pre-check won’t run. Check that your role has Manage or Override on Approval Pre-check. Select Run Approval Pre-check for the first run and Re-run Pre-check for later runs.
New to ScopeStack?
ScopeStack automates scoping, pricing, and SOW generation for IT services teams. See how it fits your process.