A procedure may be a process, standard operation procedure or similar. For process descriptions there are several different types of fomrat. You can either describe every step of the process in text one step after the other. Or you can use a flow chart type. In a process it should be clear what is the input and what are the steps to reach the output. Additionally the responsibilities should be clearly described. This starts wiht the responsible person who takes care that the process is being followed and ends with a clear description, who is repsonsible for each process step. It might also be helpful to add other stakeholders, for example who is informed about certain process steps. I personally like the swimlane diagram a lot, because you can easily see, who has to do what and how the relations between different process are.
A process might reference more detailled descriptions, often called standard operation procedure. This may be the description how a certain test or calibration procedure is actually performed. You could look at this like some kind of operation manual for specific tasks. Sometime these can be quite straight forward, sometimes they can be very complicated, depending on the complexity of the procedure they are describing.
The format of records should be individually adapted to the application. I don't think it is possible to prepare such a generic report template. A record may be a checklist that is filled in always before a certain test or calibration is performed. But also a management system review report or an internal audit report is such a record. A signed NDA may be such a record. A calibration certificate of your test equipment may be a record. The records should enable you to show the auditor, that you work according to your procedures.