Start with limited contract context. Share sensitive records only if the review proceeds.
The initial contract check is deliberately designed to collect only the information needed to understand the contract context and determine the appropriate next step. Payroll files and employee-level records are not required at this stage.
This service is operated as AwardTrueUp. For data-handling questions, contact hello@awardtrueup.com.
Last updated: October 2026
No payroll upload. No employee-level data. No required sales call.
The safest sensitive record is one you do not need to send yet.
A recovery analysis may eventually require payroll and other supporting records. But those records are not necessary to determine whether a contract appears worth reviewing.
We separate the preliminary contract check from the later evidence-review process so that sensitive information is requested only when it is actually needed.
- Collect less initially
- The first step focuses on contract and adjustment-event context.
- Request evidence progressively
- If a full analysis proceeds, the records requested depend on the specific case.
- Avoid unnecessary sensitive data
- Information that is not needed for the review should not be part of the intake process.
What we ask for at the first step
The public contract-check form evaluates customer-reported information locally in your browser to understand the potential adjustment event and explore preliminary review indicators.
Contract context
- Company name or reference label (optional)
- Contract number, if available
- Federal agency, if known
- Primary place of performance, if known
- Whether your company is the prime contractor or subcontractor
Adjustment context
- What changed
- Whether a collective bargaining agreement may apply
- Whether actual wage or H&W costs have already increased
- Approximate affected workforce
- Current stage of the price-adjustment process
- Which relevant records are readily available, if known
Company/reference label, contract number, agency, place of performance, and available-record information can be omitted. No email is required for screening. An optional cost illustration uses labor categories and aggregate hours without employee names. Review-request contact details stay in browser memory unless you choose to send the email message.
What you should not send through the initial check
The preliminary contract check is not a document-upload or payroll-intake form.
- Payroll files
- Employee names or employee IDs
- Social Security numbers
- Dates of birth
- Bank or payment information
- Exact employee wage or fringe records
- Tax documentation
- Workers' compensation policy records
- Contracting-officer correspondence
- Other employee-level supporting documents
Do not send sensitive employee or payroll records through the preliminary contract-check tool.
Sensitive records come later—and only when needed.
If the preliminary review indicates that a full analysis makes sense, we first confirm the scope and fee. We then identify the records needed for that specific case.
A Mutual Non-Disclosure Agreement (NDA) is available before exchanging sensitive payroll or tax records in a scoped engagement. Any paid review or consulting engagement is governed by the jurisdiction, confidentiality arrangements, and terms in the signed client engagement agreement.
If sensitive payroll or supporting records are required, we'll provide a separate secure method for submitting them.
Contract records
Relevant contract, option, or modification material.
Wage determination records
The information needed to establish the applicable wage and fringe requirements.
Payroll and labor support
Records needed to establish actual rates, affected employees, and supported hours.
Additional cost support
Only where relevant, records supporting fringe or qualifying employer-cost effects.
We do not ask customers to assemble every possible record before the scope of the review is understood.
The initial check is designed as a browser-local workflow.
Browser-local execution
Screening executes entirely in client-side browser JavaScript. Answers remain in transient React memory during your active session.
Zero server transmission
Questionnaire inputs and optional cost illustrations are evaluated locally on your device and are not transmitted to AwardTrueUp servers or backend intake APIs. A review-request email is shared only when you choose to send it from your email client.
Transient session state
Screening answers are discarded when you navigate away, close the browser tab, or reset the questionnaire. No questionnaire data is written to persistent browser storage or server databases.
Privacy-conscious analytics
Website analytics are kept separate from questionnaire inputs. Contract identifiers, company names, and form answers are not sent as analytics properties.
A deliberately small public data path.
The public website and preliminary screening workflow are designed with a minimal data path that avoids centralizing sensitive customer records.
- Static public site
- Browser-local screening
- In-memory evaluation
- On-screen result
- Voluntary direct contact
- Static public site
- The public marketing site is delivered as static content hosted on managed cloud infrastructure (including Amazon Web Services and CloudFront) rather than a server-rendered application handling customer records.
- Browser-local screening
- The preliminary contract check executes locally in your browser. It does not submit questionnaire answers to a public intake API or cloud database.
- Controlled infrastructure for separate engagements
- If a customer separately engages AwardTrueUp for a full recovery analysis, records provided under that engagement are handled in controlled cloud environments with defined access restrictions and encryption.
- No public document intake
- The public contract-check workflow does not accept file attachments or payroll uploads.
Specific controls are more useful than broad security promises.
We prefer to describe the controls actually used rather than rely on phrases such as “military-grade” or “bank-level security.”
Data handling is designed around minimizing what is collected, separating preliminary screening from sensitive evidence intake, and keeping submitted contract details out of analytics and routine application logs.
A few ways you can help protect sensitive information
- Do not put payroll or employee-level data into the initial contract-check fields.
- Use the submission method provided for the full analysis rather than attaching sensitive records to the initial check.
- Submit only the records requested for the particular analysis.
- Remove unrelated sensitive information where practical before providing supporting records.
Retention depends on the type of information.
We do not retain every type of information for the same length of time. Sensitive source records are scheduled for deletion sooner than the analytical work product needed for continuity and support.
| Information | Retention | Detail |
|---|---|---|
| Preliminary contract checks | In-memory only (browser session) | Preliminary contract-check answers are evaluated in your browser and are cleared when you navigate away or reset the questionnaire. Answers are not stored on our servers. |
| Raw payroll and employee-level evidence | 180 days after case closure | If a separate paid engagement collects sensitive source records such as payroll and employee-level evidence, those records are generally scheduled for deletion 180 days after case closure, unless they are still reasonably needed for active follow-up or another permitted retention reason applies. |
| Final analysis and case work product | 3 years after case closure | Final calculation workbooks, evidence indexes, analysis narratives, review findings, and limited case history for separately engaged analyses may be retained for up to 3 years after case closure for continuity, support, dispute handling, and related business purposes. |
| Accounting records | 7 years | Invoices and accounting records from paid engagements may be retained for up to 7 years where needed for financial, tax, or recordkeeping obligations. These records remain separate from raw payroll evidence. |
What “case closure” means
Case closure generally means the engagement is complete, the final analysis has been delivered, and no active follow-up work is underway.
Backups and recovery copies
When information is deleted from active systems, residual copies may remain temporarily in managed backups or point-in-time recovery systems until those copies expire through their normal retention cycle.
Retention exceptions
Retention may be extended where reasonably necessary for an active engagement, legal or accounting obligation, dispute, security investigation, preservation requirement, or another legitimate business need.
Customer deletion requests
Requests to delete information can be reviewed where the information is no longer required for an active engagement, legal or accounting obligation, dispute, security investigation, or other legitimate retention need.
Our deletion of records does not change the contractor's own contractual, statutory, accounting, or record-retention obligations.
Data-handling questions
Do I need to upload payroll to check a contract?
No. The initial contract check does not accept payroll or supporting-document uploads.
What if I don't have the contract or wage determination handy?
Complete the preliminary check with the information you already know. Contract number, agency, place of performance, and available-record information can be left blank if necessary.
When would you need employee-level records?
Only if a full analysis proceeds and those records are necessary to establish the affected workforce, actual rates, supported hours, or other calculation inputs.
Should I send Social Security numbers or banking information?
No. Those are not requested by the preliminary contract check and should never be entered.
Are my form answers used for website analytics?
Contract-check details such as company name, contract information, and form answers are not sent as analytics properties.
You don't need to share payroll to take the first step.
AwardTrueUp operates this service. Contact hello@awardtrueup.com with questions about data handling or a scoped review. If the situation appears worth reviewing, we'll explain what information is actually needed next.
No document upload. No required sales call.