The contractor is scheduled to start next Monday.
The onboarding spreadsheet is mostly green. The shared folder has plenty of PDFs in it. Someone remembers sending the last requested document. The customer portal looked fine the last time anyone checked it.
Then Friday afternoon arrives and somebody asks whether the paperwork is actually ready.
That is a surprisingly difficult question when the work has been spread across email, spreadsheets, portals, shared folders, and several people for the last three weeks.
Recent discussions among property managers and contractors show the same basic failure mode: expiration dates are tracked in spreadsheets, replacement documents arrive through a different inbox, and a problem is discovered only when somebody is about to show up for work. The issue is not necessarily that nobody collected the documents. The issue is that nobody performed one deliberate operational review against the upcoming start date.
A short pre-start review can catch a lot of that mess while there is still time to do something about it.
Work backward from the start date
Most document trackers are organized around document dates: expiration dates, request dates, renewal dates, and sometimes follow-up dates.
The project team is thinking about a different date.
When does this contractor need to start?
Put that date into the administrative workflow early enough that it can drive attention. If a subcontractor is expected on site September 8, an unresolved customer requirement on September 4 deserves different attention than the same unresolved item for a contractor starting in November.
This does not mean declaring whether a contractor is legally or technically cleared to work. That decision belongs wherever your organization has assigned it. The administrator’s job is more practical: make the tracked gaps visible before the start date turns them into somebody else’s emergency.
For active onboarding, a simple review date several business days before the expected start is often more useful than another color in the spreadsheet.
Review the customer requirements, not just the vendor folder
A contractor can have a beautiful folder full of current documents and still have unfinished customer work.
That is because the folder answers what do we have?
The pre-start review needs to answer what does this customer still appear to be waiting for?
Suppose your standard vendor record contains a W-9, a current certificate, company information, and several employee records. For Customer A, that may be everything your team is tracking. Customer B may also have a portal task and a project-specific form. Customer C may have sent an additional request by email after the original packet was submitted.
Those differences are why a generic “vendor complete” checkbox is weak evidence of operational readiness.
Open the customer-specific record or checklist and review each tracked requirement in that context. If something is missing, say what is missing. If it was submitted, record where. If somebody else has the next move, record who has the ball.
The point is not to create a bigger checklist. It is to stop assuming that a complete document library means every customer workflow is complete too.
Treat old statuses like old milk
A status without a recent observation can look much more reassuring than it deserves.
Submitted may mean somebody uploaded the file nine days ago.
Pending may mean the customer portal was reviewing it when someone last logged in.
Complete may mean the onboarding packet was complete in June, before the customer added another request.
During the pre-start review, look at the age of the information as well as the status itself.
For example:
| Requirement | Last known state | Last checked | Next action |
|---|---|---|---|
| Customer packet | Submitted | Aug. 19 | Check customer response |
| Training roster | Received | Aug. 22 | Internal processing |
| Portal profile | Pending review | Aug. 18 | Recheck portal |
| Project form | Missing | Aug. 23 | Follow up with project coordinator |
That table tells a much better story than four green or yellow cells.
Nothing here requires constant portal refreshing. Stable work can stay quiet. The purpose of the pre-start review is to revisit the items whose state matters to the upcoming job and make sure the tracker still reflects reality.
Check the handoffs that are easiest to overlook
External document chasing gets attention because an unanswered email is visible.
Internal handoffs are sneakier.
The broker sent the replacement document, but nobody attached it to the customer requirement. The project manager has the project-specific form but has not returned it. The portal submission happened, but nobody scheduled a check on the result. A customer replied to one administrator while another administrator owns the tracker.
These are exactly the places where administrative coordination becomes harder than document storage.
During the review, every unresolved item should have an understandable waiting state:
- waiting on the contractor or vendor,
- waiting on an outside contact,
- waiting on the customer or platform,
- or waiting on your own team.
If the answer is simply Pending, keep digging until the next action is clear.
You should be able to hand the record to a coworker and have them understand why the item is still open without asking for a guided tour of your inbox.
Separate “needs action now” from “needs another look later”
One reason administrators stop trusting trackers is that everything unresolved looks urgent.
It is not.
If the customer portal is reviewing a submission and your next check is Wednesday, staring at it Monday morning will not improve its character. If a contractor owes a missing form before a start later that week, that may need action today.
Give waiting items a next review or follow-up date. Then let the quiet ones be quiet until that date arrives.
This creates a much cleaner pre-start view:
Needs action: something your team can move now.
Waiting: somebody else has the next move, with a date to check again.
No known open action: nothing in the tracked workflow currently needs attention.
Those are administrative states, not compliance judgments. They simply tell the team where the work stands.
Run one final exception review instead of rereading everything
The final review should be fast because the detailed work has already been happening.
A day or two before the scheduled start, look only for exceptions: missing tracked requirements, unanswered requests, documents received but not processed, stale portal statuses, upcoming expirations that affect the current customer workflow, and waiting items whose review date has arrived.
If the review produces fifteen mysteries, the problem started earlier in the process. Fix those mysteries, but also notice what they tell you about the workflow.
Maybe customer requirements are living only in email. Maybe received documents are not being connected back to requests. Maybe portal checks have no dates. Maybe the spreadsheet has a status column but no owner or next action.
Those are useful discoveries because they can be fixed before the next contractor reaches the same Friday-afternoon scramble.
Sidecar can help by keeping customer requirements, documents, waiting states, follow-ups, tasks, and expiration dates in one operating view alongside the systems your team already uses. The value is not a magical “ready” badge. It is being able to open the customer record and see the tracked gaps without reconstructing three weeks of activity.
Make the start date part of the workflow, not the surprise ending
The best pre-start document check is boring.
Nobody discovers an email from two weeks ago. Nobody realizes the replacement file went to the wrong inbox. Nobody asks whether Pending means waiting on the customer or waiting on your own team. The administrator reviews a short list of exceptions, moves what can be moved, and knows when the remaining items will be checked again.
That kind of boring takes a little preparation.
Keep the expected start date visible. Keep customer-specific requirements separate from the generic vendor record. Timestamp important statuses. Give every open item an owner, waiting party, or next action. Recheck the exceptions before the work date arrives.
Then when someone asks the question contractor administrators hear constantly — “What am I missing?” — the answer is already in the workflow instead of scattered across the office.