Steps for required document upload
- 01
Open the franchise’s documents and select the required document.
- 02
Read its guidance, due date and any note that it holds report uploads.
- 03
Upload the current version with the details it asks for.
- 04
Check its review status before you consider it done.
What the finished work leaves you with
A record linking the requirement, the uploaded file, the review result, and the date the requirement was covered again.
What to do when the review finds a problem
The franchise has several requirements or versions
Open the exact requirement and read its instructions before choosing a file.
The file meets the requirement’s instructions
Upload the current version.
The file needs approval or does not meet the instructions
Send it for review, or ask for a corrected file.
The upload and review are finished
Go back to the requirement and confirm it shows as covered before closing the task.
A common mistake to avoid
Uploading a file without checking that it belongs to the selected requirement and reporting period.
Franchise required document upload checklist
Use this checklist when a franchise needs to upload a specific required document. It keeps the instructions and due date in view, checks you have the current version, sends it for review when needed, and confirms the requirement is covered, because uploading a file is not the same as meeting the requirement.
Before you start
- Open the franchise’s requirement and read its instructions, due date, and whether it blocks reporting.
- Have the current version of the document ready before choosing a file.
- Know whether the next step is review, a correction, or simply confirming coverage.
When a required franchise document will not upload
A failed upload can come from the file, the wrong requirement, or a review that has not finished. Keep the requirement and period in view while you fix the file, and check the status after uploading rather than stopping at the success message.
The upload rejects the file type or size.
Check first
- Compare the file type and size with the requirement’s instructions.
- Open the file to confirm it is readable and not empty or damaged.
- Check whether a renamed file is still in its original, unsupported format.
Next action
Save a readable copy in an accepted format and within the size limit, then upload it to the same requirement. Keep the original elsewhere if you need to show how it was converted.
Confirm the result
The requirement shows the file name, upload time, and a file the reviewer can open.
The file uploads, but the requirement still shows as missing.
Check first
- Confirm the file went to the right requirement, franchise, and period.
- Check whether it is waiting for review.
- Refresh the requirement and compare its current file with your upload time.
Next action
Complete the review or send the mismatch to the requirement owner. Do not upload a second copy until the first file’s status is clear.
Confirm the result
The requirement shows the uploaded file and a current status, or names the review step still needed.
A valid file went to the wrong requirement.
Check first
- Compare the requirement name and instructions with what the file covers and its dates.
- Check whether the right requirement already has a file or a pending review.
- Note which upload was wrong before moving or replacing it.
Next action
Keep the history, ask a reviewer to deny the wrong upload, and upload the file to the right requirement. Do not mark the wrong requirement complete just because a file is there.
Confirm the result
The right requirement holds the correct file, and the wrong upload has a recorded outcome without changing anything else.
A reviewer cannot find the uploaded document.
Check first
- Search by the exact franchise, requirement, and waiting-for-review status.
- Confirm the reviewer has access to that franchise.
- Check whether the upload is a draft or new version that the review list filter hides.
Next action
Tell the reviewer which requirement and file to open, fix the filter or access, and leave the file in its current state. Do not upload a duplicate to make it show up.
Confirm the result
The reviewer can open the same requirement and file and record a decision.
When you need to hand it on
- Include the requirement, franchise, file name and size, exact upload message, and upload time.
- Keep the original and converted files without sharing more of the document than needed.
- Ask the requirement owner to fix a wrong requirement, review status, or link.
Link to the record instead of copying passwords or unrelated personal details into your note.
A situation to work through
A franchise has a document due, and the requirement’s instructions say what it must cover. The franchise user opens that requirement, uploads the current file, and waits for review before treating it as done.
Match the file to the requirement and its instructions, then confirm the review result and that the requirement shows as covered.
This is a planning example, not a customer result.
How does a franchise satisfy a required document?
Open the document, read its guidance and due date, upload the current version, and check that it has been accepted. An old upload does not cover a requirement that has since renewed.
Put the workflow into practice
In Granite, franchise users upload required documents on their franchise and can see when each one is accepted.
Set it up in Granite with your own franchises, reporting periods and billing rules.