Course 8 · Uploading contracts one at a time

Course eight. The most common thing you will do here, uploading one agreement, done right. The proposal screen.

Lesson one. What to upload, and what reads cleanly. Two types only, PDF and Word, forty megabytes each. It checks the contents, not the name, so a renamed file cannot slip through. A document saved to PDF reads best, and a clear scan still works.

Push a proposal to the desk. Drop one file or twenty, and each starts reading the moment it lands. The vendor, the value, the term, the seat count fill in, shaded by how sure the read is.

Watch a chip shade gold or red. That is not an error, it is the platform flagging exactly where to check the paper yourself. Your correction always outranks the machine's first guess, and it is never overwritten.

Lesson two. The wizard, step by step. It is shorter than most. Drop the file. Check the chips the read filled in, correcting anything gold or red. Add one line telling the analysts what you want answered, the uplift cap, whatever the deal turns on. Then confirm the batch once.

Lesson three. What happens next. Your upload lands on the proposals ledger, and it moves along one path. Uploaded, in review, benchmarked, then delivered.

Your proposal goes to a human analyst. When one picks it up, you get the delivery date, then an email at every step to the finished report. The status pill answers, where is my benchmark.

And this happens on its own. A queued upload enters the analyst queue by itself, so you do not chase anything. The one exception is when your plan's benchmark allowance is spent, and then the proposal says so plainly and shows you how to resolve it in place.

Lesson four. A rejected upload is usually the wrong type or too big. PDF or Word, forty megabytes. Convert or split it. Two questions. Which file types are accepted, and where a submitted proposal goes.

Now you. Upload one real agreement from your estate. It takes about three minutes. Then Course nine, bulk intake, the Archive.